This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Hi @ All and Support,
I have Windows 10 Pro 64-Bit Build 16193.1001 installed and reused the ISO to fix anything that may have been wrong and it installed just fine.
However, I can't seem to install 64-Bit Build 16237.1001 on this computer.
I do have 32-bit Build 16237.1001 installed on another Hard Drive this computer and it is running just fine except for bugs not related to installing.
Why doesn't the 64-Bit version install?
***Personal information deleted by the moderator. Please see the Microsoft Community Frequently Asked Questions for more information on how you can protect your privacy.***
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
@ GeorgeOgden and I have is the Nvidia NForce Networking Drivers, written by Microsoft.
Hi, the problem is the missing or corrupt 64bit nForce 750i SLI chipset drivers. That driver package may include the LAN drivers but I think they'll be in a separate package. Either way they're written by Nvidia - Microsoft merely deliver them..... or maybe not in this case!
Cheersi
Microsoft will probably investigate the Windows code related to the drivers and see if they can put in a shim or something to get it working. Same idea as games where the dev no longer supports. I doubt if either Nvidia or Asus will rewrite the drivers at this late date.
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.
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
Link does not take you to the Feedback. Created via Share process in Feedback Hub.
Why would the drivers necessarily be corrupted? Why not a change in Windows code causing a block or something causing incompatibility? Who knows?