Announcing Windows 10 Insider Fast+Skip Ahead Build 17035 for PC Insider

HippsieGypsie said:

Just got back from shopping. What the...hey. Still no AMD update yet?

I expect they'll skip this build for AMD.

My desktop is working fine, AFAICT.

The laptop is exhibiting a few weird issues.

I am trying to add an older Brother printer Thai is networked on my LAN (I know everything regarding what I am supposed to do to get the generic Brother driver installed) but when I go to let Windows Update expand the driver list, after a vast amount of time, I get an error message saying ”Windows was unable to get a list of drivers from Windows Update. Please try again later.”

Been trying for 2 days. Anyone else seen this?

johngalt said:

My desktop is working fine, AFAICT.

The laptop is exhibiting a few weird issues.

I am trying to add an older Brother printer Thai is networked on my LAN (I know everything regarding what I am supposed to do to get the generic Brother driver installed) but when I go to let Windows Update expand the driver list, after a vast amount of time, I get an error message saying ”Windows was unable to get a list of drivers from Windows Update. Please try again later.”

Been trying for 2 days. Anyone else seen this?

What build are you runing.? If you successfully upgraded to 17035 whick Intel chip? Can you revert to 17025 was that build trouble-free?

HippsieGypsie said:

Nooooo!

Yes. I absolute cannot boot build 17035 on an AMD processor. Microsoft needs to address this issue on the next build.

It cannot be bypassed using VMware, VirtualBox or Hyper-V virtualization platforms. So why in the world did they release something with this bug? We may never find out from Wintel.

martyfelker said:

What build are you runing.? If you successfully upgraded to 17035 whick Intel chip? Can you revert to 17025 was that build trouble-free?

Lol. Um, I thought it was self evident, but, yes, 17035.

I don't want to revert, I want it to work in this build.

I cannot say if this is build specific or a symptom of something else, hence me asking if anyone else was seeing this.

martyfelker said:

It cannot be bypassed using VMware, VirtualBox or Hyper-V virtualization platforms. So why in the world did they release something with this bug? We may never find out from Wintel.

Because if they can fix the AMD CPU going into bugcheck with a single line of code, such as a registry edit, then they can tell everyone ”Hey, if you own a machine with an AMD CPU and want to get 17035, be sure to add / edit this registry entry before starting the update process and it will work just fine.”

IOW, they probably believe it is a minor fix, so they went ahead and released the build with the CPU caveat, expecting a fix really soon after.

I would do the same if I had an Intel CPU (which will never happen - I'm saving for a Ryzen Chip and compatible mobo)