Announcing Windows 10 Insider Preview Slow Build 17074.1002 - Jan. 11 Insider

Josey Wales said:

I understand that ,but since it only fixes two issues and some users cannot even get this installed, wouldn't it be easier to just upload the 2 patches to Windows Upload Catalog? Or posts links to them in the HUB?

johngalt said:

No. Because those two patches cannot be applied on system that cannot boot. And one of the two patches fixed an error that systems cannot boot when installing the original 17074.

So, if you upgraded to 17074, and your system cannot boot, how do you apply a patch?

Even more simple...

in 17074 those systems were blocked to even receive new build, so MS have to remove old build and replace it with new one. And since it's basically the same build + those two patches, we got mino increment..

Josey Wales said:

That being true then how does one get a new build if their system will not Boot. It is the same thing. But enough of this MS will do what they do.

Josey, look at the post above. Those systems were blocked to receive new build

I've just read about the 17074.1002 on the forum, looked in settings and its just about to upgrade now.

Josey Wales said:

Then how are they getting this one if their system will not boot without using MR or any other backup. When I started with the IP Builds I had no backups, I did not have MR then. The builds just seemed to work. Now please lets move on, I am sorry I brought this up.

Their system can boot, since they were never offered 17074 before... :)

AndreTen said:

Their system can boot, since they were never offered 17074 before... :)

Possibly not as this link shows what the original problem was,Here's why some AMD systems are failing to boot after installing Microsoft's patches

Fabler2 said:

Possibly not as this link shows what the original problem was,Here's why some AMD systems are failing to boot after installing Microsoft's patches

Those are not patches for Insider builds.... But Of course, I have no idea if any / how many AMD systems were updated to Insider build 17074 before this build came out.

slicendice said:

Have you tried running the following command in elevated CMD and rebooting?

Gave it a shot and no go. Same issue with VMware and it's a Microsoft bug likely created by fixing the install issue with virtualization.