New Windows 10 Insider Preview Fast & Slow Build 17763 - September 20 Insider

Dave44 said:

yes but new builds are 4GB and CU's are lot smaller than that

That does not change the fact that cumulative updates change the build number, in essence being new builds. As @cereberus mentioned, we had that scenario when MS released version 1709; originally the GA release was meant to be 16299.1, but due some issues, it was immediately replaced with 16299.15.

Although the 16299 base is same, 16299.1 and 16299.15 are two (slightly) different builds.

Dave44 said:

i know number change i never said they didn't

My point is that 16299.1 and 16299.15 were two different builds. The original 16299.1 was a few gig download, but 16299.15 upgrade only some few hundred megs. Yet, they really are two different builds.

It's not quite that simple @Kari.

16299.1 is a completely new build, where every single bit in the OS has been defined, recompiled and relinked.

A Cumulative update is just a partial update where the definitions has not changed, but some of the implementions has. There still remains a lot unchanged code from revision .1.

There are certain parts of the OS that are impossible to update as cumulative update and must be completely recompiled and relinked. And everything that uses or inherits from those components must also be recompiled and relinked even if no code ever changed. Failing to do this will cause those components to crash.

slicendice said:

It's not quite that simple @Kari.

16299.1 is a completely new build, where every single bit in the OS has been defined, recompiled and relinked.

A Cumulative update is just a partial update where the definitions has not changed, but some of the implementions has. There still remains a lot unchanged code from revision .1.

There are certain parts of the OS that are impossible to update as cumulative update and must be completely recompiled and relinked. And everything that uses or inherits from those components must also be recompiled and relinked even if no code ever changed. Failing to do this will cause those components to crash.

16299.15 was not a cumulative update - it went through the full uup build upgrade process not the normal WU process. The lines get blurred with uup build upgrades as they do not necessarily download everything, but all that is needed. However the update process is fundamentally different.

I have had trouble installing an unsigned wifi driver.


ou have always been able to install an unsigned driver with secure boot off and go via recovery menus, restart options and select to allow unsigned drivers to be installed - this being a one-off exercise.

I did this and it installed fine and it worked fine.

THEN I REBOOTED and it did not work. I looked in device management, and it said driver was install but would not work as unsigned! Previous versions never did this. I had to go round loop of unsintalling adapter, deleting driver, reinstalling as above etc.

So I tried things like test signing on etc, but no joy.

I tried updating drivers and got the message my driver was latest. I even tried a couple of driver packages and they claimed to have more updated drivers but always installed same old one.

After tearing out what few hairs I have left on my head out, I finally found a more updated driver from end of 2016, and this installed with a digital signature, and I could install it and it would remember it



If MS have tightened up it so unsigned drivers can only be installed for one off instances, and forget after reboot, this is going to cause massive problems for people with older hardware.