System Requirements for Windows 10 Pro 64-Bit Build 16237.1001?

Hi Colin,

I can only offer comments as I'm pretty much done with the Insider program based on my recent experience!

I viewed my efforts in tracing the problem as being part and parcel of my participation in the Insider Program (updates are every bit (sorry of the pun) as important as the functionality of a build) but, so far, you and only a very few others have appreciated the hours, no days, spent in doing so.....

I've said it before and I'll say it again... No warnings, no meaningful error messages, little respect shown for the Insiders struggling to discover the root cause of this problem, not a comment from a forum moderator nor a explanation from Microsoft participants here SHAME ON MICROSOFT!! Where the *1%^ is Jason?? His silence indicates that Microsoft just don't give a damn! 

Despite numerous contributions here, and via the Feedback Hub, Microsoft have abjectly failed to acknowledge

A) that there is a problem

B) that they're working on it

.... or....

C) that this is the end of the road for the Nvidia chipset (and how many others?)

So, the question is... how many Windows 10 users are going to be stuffed when the Fall update is unleashed? 

Well, assuming 1% of the user base are DIYers.... plus others with OEM PCs... how many other users on platforms, in addition to those with an Asus / Nvidia combination, will be impacted by this change? Bearing in mind that this will very likely have the same impact not just on drivers but on many 3rd party apps ....  hmmm...

As of July 2015 the number of Windows 10 users was put at 14,000,000... many more today.... 100,000,000 + according to a recent count... so that'll only be a maximum of 1,000,000 DIY users then, all of whom are the more savvy PC users and who Microsoft would probably prefer remained Windows users... 

Many of these PC savvy users like me support other Windows users (myself 30+) and, if this is not resolved, either with a graceful, layman understandable, EoL message and/or error report then it'll be a major headache for many less knowledgeable, PC literate, users. 

Perhaps Microsoft knows the number of users impacted and is willing to cast them to the wind... if so.... Linux, iOS here I come with 30+ "clients"!

Cheers

Nvidia got the drivers signed properly, but subtle changes to elements in Windows, like the WOW64 layer for example, would outdate a driver once in a while.  Each OEM surely has small idiosyncratic style in coding and those change over time with personnel changes, etc.  I can think of reasons why code from a single OEM suddenly doesn't work.  Microsoft must surely be tracking those things down all the time based on impacts.  These ASUS boards were pretty popular with DIYers back in the day, but DIYers are probably less than 1% of the user base at any one time.

You have done a terrific job on this.  I hope it is rewarded with action by Microsoft to get past the problem, whatever it actually turns out to be.

Have you tried running an upgrade from iso and unchecking the box that permits downloading updates during the installation?  

Hi @ https://answers.microsoft.com/en-us/profile/87869dbd-08f4-45ba-9704-bf5a5a97bab5Cbarnhorst ,

I have and it fails as well. The problem is that Microsoft doesn't give any reason in layman terms that is understood by a Beta Tester and leaves the Beta Tester guessing.

All suggestions posted are guesses as to why it isn't working and quite possible, is a result of Manufacturer's not getting their Drivers signed by Microsoft for the drivers to work in Windows 10.

Have you tried running an upgrade from iso and unchecking the box that permits downloading updates during the installation?

FINAL UPDATE

I paused before restarting the 564th update from 16193.1001 to 16241.1001 and looked to see what, if any, drivers might be missing or changed. Looking in....

C:$WINDOWS.~BT\NewOS\Windows\System32\drivers directory and compared those found in the 16393.1001 C:\Windows\System32\drivers

No sign of the following files being migrated from 16193.1001 to 16241.1001 - perhaps intentionally dropped or possibly the two nv*.* files are to be replaced/updated?

• ASACPI.sys
• HdAudio.sys
• nvhda64v.sys
• nvmf6264.sys
• srv.sys

While many had changed in size a number of new files were found - perhaps the two nv*.* are the replacements?

• bttflt.sys
• invdimm.sys
• ipt.sys
• mshwnclx.sys
• nvdimmn.sys
• pnpmem.sys
• ramdisk.sys
• rteth.sys
• vnvdimm.sys
• wdnsfltr.sys

I also looked into the C:$WINDOWS.~BT\NewOS\Windows\System32\DriverStore*FileRepository**and again compared what I found there with what I found in C:\Windows\System32\DriverStore*FileRepository ....

No sign of the following being migrated from 16193.1001 to 16241.1001 - perhaps intentionally dropped or possibly the six nv*.* files (I've  yet to confirm that they are all Nvidia drivers) are to be replaced/updated?

22/07/2017 13:00 <DIR> asacpi.inf_amd64_11b845f17a848cf7

22/07/2017 12:56 <DIR> nvakwu.inf_amd64_0b3c1a15295d17ee

22/07/2017 14:41 <DIR> nvakwu.inf_amd64_c2d098dcb7ee3982

22/07/2017 14:44 <DIR> nvhda.inf_amd64_30b89a90eebdf982

22/07/2017 12:59 <DIR> nvhda.inf_amd64_62ea605b81fc54cf

22/07/2017 14:44 <DIR> nvstusb.inf_amd64_cb0c0a9d1bff2fba

22/07/2017 12:59 <DIR> nvstusb.inf_amd64_f9c4b7a768bcba99

22/07/2017 12:34 <DIR> prnms001.inf_amd64_8eb6ec78bfd5a9e4

22/07/2017 12:34 <DIR> prnms009.inf_amd64_eb7a2ca5e2a58c6e

While new drivers were found - perhaps the invdimm.inf or the vnvdimm.inf is the replacement? - possibly misnamed?

09/07/2017 20:32 <DIR> bcmwdidhdpcie.inf_amd64_977dcc915465b0e9

09/07/2017 20:31 <DIR> c_smrdisk.inf_amd64_db3318c408663f9e

09/07/2017 20:31 <DIR> c_smrvolume.inf_amd64_edb8f9ffe86aab53

09/07/2017 20:32 <DIR> invdimm.inf_amd64_34a83d0e816c97ce

09/07/2017 20:32 <DIR> smrdisk.inf_amd64_192f16c519def7a2

09/07/2017 20:32 <DIR> smrvolume.inf_amd64_6a564fa4bbe10898

09/07/2017 20:32 <DIR> uiccspb.inf_amd64_188a56d9cf296eee

09/07/2017 20:31 <DIR> usbncm.inf_amd64_f71960c42863f828

09/07/2017 20:32 <DIR> virtdisk.inf_amd64_ba139d68720c3d09

09/07/2017 20:32 <DIR> vnvdimm.inf_amd64_4f12e9e33dbdc0d3

Anyway, copying the files and directories from C:\Windows into the corresponding locations in C:$WINDOWS.~BT

didn't help the upgrade complete but it did screw up the LAN drivers when it eventually, after another restart, booted back into build 16193. Hey I didn't think it would work either but it was worth a try! :)

I might just try once more removing the first character of the nvdimm.inf files just for **** and giggles.

That said, I doubt that'll work either so this will be my last update on the topic unless it does work or I find another solution but, for now, I think I've gone as far as I can so back to 15063.481 and wait to see what happen when the Fall update arrives...... 

Thanks to everyone for their suggestions and assistance but it's now over to Microsoft!

Cheers