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

Thanks Stephen,

Your thoughts, suggestions and interest are about all that's keeping me going right now - I was a toothbrush away from throwing myself in front of a bulldozer. :) :)

Sorry, but the Nvidia chipset that uses the nForce 750i drivers are absolutely essential as they're an integral component of the motherboard, there's no way to bypass them in the BIOS - a Vogon construction ship could certainly do the job nicely and I'm just short of calling in that option! :) :)

Back home now so progressing with some more tests.... After downloaded the 32 bit ISO of 16232 from the Microsoft web site and using a Rufus USB; I've run out of DVDs :( ; I've been able to install the 32bit version of build 16232.1000, switched from the Slow to Fast ring and, as I write, the update to build 16241.1001 is progressing - downloaded and 76% through the installation phase. Assuming that completes successfully I'll be in the same state as @thecreator.

I'll go back to Microsoft and download the 64bit version of build 16232 and use Rufus to create a USB and see it that works.... the DVD ISO I have of that build was created using UUPtoISO so perhaps that route will be successful... if it is I'll be delighted and it'll get me back on the Fast track again..... having skipped the builds in between 16199 and 16232...... but that's for tomorrow.

Cheers

Hi all,

First about my Network/Graphics mix-up: Oops, talk about egg on your face. But it's ok, I can handle it. I'm a cool frood who knows where his towel is |--). (a rather soiled one)

Anyway, the case does interest me, so if you don't mind I'll give it another try.

George, you say a Clean Install fails because it asks you for drivers you cannot supply. I am wondering what happens if you just disable the NForce750i chip. You don't absolutely need it for a CI, so perhaps you can get it to install 16232 that way. Ideally, you would disable it from the BIOS, but that may not be possible. If not there are some other things you can try.

BTW Please don't hesitate to tell me if you judge I've 'contributed' just about enough junk and I'll quietly get lost |--)

Regards,

Stephen

PS I looked, but I have no hardware with that chip, so I cannot test anything myself.

Why would the drivers necessarily be corrupted?  Why not a change in Windows code causing a block or something causing incompatibility?  Who knows?

Hi @ All,

I referenced this thread in Feedback Hub.

feedback-hub:?contextid=81&feedbackid=a7ffb56b-b4f1-4b7e-b0be-63cbc29f1f37&form=1&src=1

Title: 64-Bit Builds 162## and Higher

https://aka.ms/ioymlb

Link does not take you to the Feedback. Created via Share process in Feedback Hub.

Hi Colin,

Agreed but what still puzzles me is how I was able to clean install and update all the way from 14393, through 15063, to 16199 on 64bit builds without a problem yet none of the ISOs I have of subsequent builds, including 15063 and 16199, will allow me to clean install on a bare drive.

As I've said elsewhere, the ISO of 15063.0 kicks off OK but halts in the old school way requesting drivers (the old Windows 7 64bit ones are not surprisingly rejected) which are either missing or corrupt, before I get to the stage of selecting a partition on which to install the OS.

My thought was that the drivers went missing or were corrupted some time after build 14393 (although updates to 15063.483 went well) leading me to surmise that the UUP process, in some way up to but not after build 16199, migrated the already installed 64bit drivers. Either that or something in the later builds rendered the drivers useless whether they were included or not.

Whatever caused the problem means there's no way to clean install from build 15063 or later - unless reverting to 32bit works which I have yet to test. If that does work then I guess it's better than nothing but it does mean a clean install, downgrade 3rd party apps and, without doubt, will cause havoc for a number (how many I can't guess) of happy users with 64bit installations when the Fall update is let loose.

Communicating all this via the Feedback Hub is next to impossible given the limited space available. I can only hope that someone from Microsoft involved with Windows 10 development is reading the posts on this forum AND actually informs someone who can do something to correct the problem. 

Cheers.