Win 10 RS-4 not compatible with Intel DX58SO motherboard

So bordi should put his Corsair 1333MHz in the 3 Blue slots, avoiding the black one.

There is over other thing - that would be to try a clean install of fall Creators update on a clean partition (preferably a clean HD) and then try to upgraded by joining the Insider Preview program Insider settings and see if it takes it that way.

My set up is a bit newer, because my eVGA x58-based Mobo has 2 USB3 ports, and add I mentioned, the Marvel SATA controller on my machine is used for SATA III 'emulation', and the motherboard was put into sake around Oct. 2010, with the last BIOS released only a year later, but my peripheral hardware having been upgraded piecemeal a lot, but essentially we are running the same setup in terms of CPU family as well as main chipsets, so I really don't understand why yours is being faulty, and particularly since everything up to FCU worked.

Have you done anything special to the OS, like move the \Users tree using Kari's tutorial (FWIW, I have and that hasn't affected me either), or else have you used the HAD being used for OS in another machine at all?

I really think a clean HD will do the trick.

Unless Microsoft had officially blocked older Intel made hardware, but then that should lead to some sort of message stating that, I would think.

Looks like next week for a new build. For no particular reason I can think of, apart from exercising a bunch of 32-bit drivers, why not try a 32-bit version from the 17025 slow ring ISO?

bordi said:

If you mean a clean install of 16299 on a freshly formatted HD then download and upgrade to 17046, I’ve done that many times with the same results unfortunately.

By clean HD, I mean one where you've started Windows 10 setup, then used the CL to enter diskpart and used the clean function to clear everything on it, all partitions, and then let Windows 10 use the clean, unformatted and unpartitioned drive to install upon. Whenever I clean install, that is exactly what I do. Do realize that if you do this, though, it remvoes all partition and formatting information from the entire drive. All partitions, not just selected ones - clean is for the whole disk.

bordi said:

They’ve changed something with the RS-4s that’s just not compatible with this motherboard; I don’t think it’s to do with the CPU.
Intel is saying that these DX58SO boards don’t support windows 10 at all so unless there is some sort of unofficial generic BIOS update for these boards, or MS reverts whatever they did to make these boards incompatible, I think I’ve had it.

Intel is saying they don't support Windows 10 on the system boards - as in they won't help you at all, just tell you that it is not supported. eVGA says they won't support anything beyond Windows 7 on my board - and yet I've been using Win 10 since the Technical Preview 2 builds on this machine with very few issues. If I tried to get eVGA to support an issue I had, I would be told that 'officially' they don't support Windows 10 on this motherboard, and that I might find some help in their community forums.

bordi said:

I’ve done nothing to it at all to it; in fact this is a completely fresh install of a freshly formatted hard disk which I only installed early this morning.

OK, that's good to know - I'm still concerned about the multiple System partitions on your machine, almost as if your first clean install creates one, and then the Windows Insider Preview upgrade creates a second one....

bordi said:

It seems to me that’s exactly what they have done, who knows?

I'm still leery of saying this, though, because, for all intents and purposes, our hardware is the same. Same CPU family, same chipsets, etc. - the major difference is that yours is a n Intel manufactured board, whereas mine is an eVGA manufactured board. Hence my reluctance to say that this is it.

Since you're trying the 32 bit install, see if that goes - if not, see if you can copy all of the stuff you need off the system drive and perform that clean and then install.

I think you mentioned it before, but you are disconnecting the peripherals, like printers, etc. when installing, right?

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.

bordi said:

Mounting didn’t work I’ll have to do a fresh install from USB

but I just reinstalled and got everything just right again, I don’t fancy going through the same process again.

I’ll keep it in mind for another day.

One thing you could do would be to get Macrium Reflect free installed and backup your current install, so you could play, and if it didn't work, restore the backup with very little time lost.

Worth considering, especially with all this playing around that we Insiders tend to do