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

Hi Whoosh7,

As I've discovered, through exhaustive testing, you appear to have been correct... It may even have been reading your earlier post that set me off on that very long and excruciatingly painful tack..... thank you very much!! :) :) :). Anyway, if anyone made you feel that you'd been shot down in flames they weren't worth listening to - even if they are technically more knowledgeable than you (and me)!

I'm as certain as I can be regarding the missing or corrupt nForce 750i drivers required by my motherboard - short of any confirmation from Microsoft..... and I don't see any signs of that happening any time soon. I'm just waiting for the Fall update to see if the problem gets fixed or history refers to it as the Fail update.

You don't say whether you're running 32bit or 64 bit Windows 10 but assuming the latter....

I took a quick look at the specs of your Asrock g31m-gs motherboard and, as the chipset is from Intel, I'm doubtful that you will experience the same issues as I'm having with my Asus P5N32-E SLI Plus. If you read back up here, a similar Asus motherboard... but with and Intel chipset... seemed to be working fine. That said, the last driver update for your motherboard was back in 2009 so it may well be on the list for EoL in the future. However, the drivers were updated to support Windows 7 64bit but a later generation generation of Windows 8 64bit drivers failed on my motherboard when I tried to force feed them during an install.... the 322nd if I recall correctly. :)

As for the your graphics, it's possible that the on-board NVidia may suffer the same fate  as the aging Intel chipset but the drivers for your GTS 250 were updated to support 64bit Windows 7 in 2016 so they will probably remain supported for a while yet....

Of course, at some point in the future, you may well end up with a graphics card that remains supported by Windows 10 64bit in one hand, staring at a motherboard that previously worked perfectly well with Windows 10 64bit in the other but is no longer supported

• if it's any comfort, you'll not be alone!

Best of luck.

Cheers

p.s. your final comment regarding using a USB to install got me thinking.... again.... which build was it that succeeded? Also had you previously tried and failed with the same build using a DVD ISO?

Thanks guys, after never having an upgrades issue for many moons, then not being able to upgrade from 16199 and posting several threads I was getting very depressed at the normal and repeated responses. When I suggested that there might be many more (less technical than I) users out there that would be thwarted by thus issue, I was shot down in flames as I guessed it was m/b or graphics card Nvidia drivers that were the issue.

Suggestions were and I did all I could find without success and the same failed upgrade symptoms

Troubleshoot

Remove all 3rd party s/w

check for file corruptions

Change stuff in bios i don't have

You have been lucky so far

You will have to do a clean install

Blah blah blah

By creating a usb boot from a constructed ISO I finally got to current insider build.

I have Asrock g31m-gs and an Nvidia gts 250 - do you think my issue is related?

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.