Win 10 RS-4 not compatible with Intel DX58SO motherboard

Fafhrd said:

You may need to run setup from within the sources folder, not from the root of the virtual dvd that mounting created.

Ah I see. DISM Apply would work cross architecturally.
You could create a VHD and install to that, without destroying your 16299 installation.

Interesting. I did not know that DISM apply would work across different architectures....

Basically, the wimfile is a compressed archive. DISM just decompresses the contents and checks the file structure integrity. This is bit-length agnostic. Only when the system is booted for the first time does OOBE install drivers and of course these are all from within the same bit-length system.

Fafhrd said:

Basically, the wimfile is a compressed archive. DISM just decompresses the contents and checks the file structure integrity. This is bit-length agnostic. Only when the system is booted for the first time does OOBE install drivers and of course these are all from within the same bit-length system.

Ahhhh. That makes sense. I did not realize the file integrity check by DISM was architecture-independent.

bordi said:

Too tired to try anthing else now, tomorrow is another day.

I’m going to concentrate on the parts for two new bulds now


Tomorrow im getting a MSI nVidia GeForce GTX 1070 8GB

All at bargain prices, new sealed boxed yet almost half price

Just hope I can find the rest of the components for almost half price

See, now I am jealous. You're well on your way to a new build, something my 6 year old machine desperately needs....[emoji39]

Dism was designed to service all platforms: 32-bit, 64-bit & Itanium, if you see old Windows 7 references. Thus you can service a 64-bit image from a 32-bit host and vice versa.

Well, it's not X58 that is the issue, nor is it the ICH10R chipset either, nor is it a Marvell 9128 chip causing the issue, as I have all 3. My CPU is a Bloomfield family just like yours, though it is unlocked for overclocking.

The reason I said about the formatting (technically using diskpart and the clean command) was because I didn't like the multiple system partitions (I assumed both were on the install drive), and I don't really care for having those hidden partitions having been assigned a drive letter.

I use Kari's 'Move Users folder' tutorial every time I clean install Windows, putting most of Windows on my 1TB SSD and moving the \Users folder to my 256GB SSD, both of which occupy the only 2 SATA III ports, which are controlled by the Marvell 9128 controller, not the ICH10R. In it he specifically states to make sure that you have the drives in the correct order, that you disconnect drives and peripherals you do not need to use during installation, and even disconnect network while installing. Numerous other tutorials that he has written here make similar admonishments - keep it simple, while using the least amount connected devices and hardware for the best chances of success.

I have never bothered disconnecting my network, but when I do a clean reinstall, I disconnect all peripherals, and usually disconnect all but the two SSDs and my optical (since it is interior, versus the rest of my drives being in quick load bays). Last night, using a combination of 3 tutorials (main Windows 10 install guide, the move \Users tree tutorial, and the 'officially supported way to clean install the latest IP build' tutorial, when checking for updates on my system for fast ring from Fall Creators Update, it would not find anything, so I mounted the 17046 .ISO in Explorer, started setup, and in about 45 minutes I was back on 17046.

With all your testing, I think you said you've already tried this method, so the next thing I can think of is:

Do you have *any* hardware showing in Device Manager with any issues?