Win 10 RS-4 not compatible with Intel DX58SO motherboard

Yeah, I know, just making sure.

Microsoft does not endorse or support UUPtoISO etc., generated ISO clean installs, only those ISO images that MS distributes AFAIK.

Yes, I know that as well. That is why I was checking to make sure Bordi had tried the official release, to rule out this as a possible factor with his installation issues.

Bordi, do you have a spare drive, or else can you make a new, small partition and try installing 17025 directly (without first installing 16299) to see if it breaks when doing a clean install?

johngalt said:

Yes, I know that as well. That is why I was checking to make sure Bordi had tried the official release, to rule out this as a possible factor with his installation issues.

Bordi, do you have a spare drive, or else can you make a new, small partition and try installing 17025 directly (without first installing 16299) to see if it breaks when doing a clean install?

I try fresh installing directly with every new release mate, after the normal upgrade fails

It just doesn’t go past the windows logo each and every time

Some part of my hardware or BIOS is incompatible with the RS-4s

bordi said:

Windows 10 Fall Creators Update (RS3)
Build 16299.15 10/2/2017 installed perfectly, working perfectly even now

Windows 10 (RS4)
Build 16353 8/31/2017* only released to Skip Ahead not tried
Build 16362 9/13/2017* only released to Skip Ahead not tried
Build 17004 9/27/2017* only released to Skip Ahead not tried
Build 17017 10/13/2017 - Failed in SAFE_OS error during BOOT 0xC1900101-0x20017
Build 17025 10/25/2017 - Failed in SAFE_OS error during BOOT 0xC1900101-0x20017
Build 17035 11/8/2017 - Failed in SAFE_OS error during BOOT 0xC1900101-0x20017
Build 17040 11/16/2017 - Failed in SAFE_OS error during BOOT 0xC1900101-0x20017
Build 17046 11/22/2017 - Failed in SAFE_OS error during BOOT 0xC1900101-0x20017

I've tried upgrading, fresh install, formatting the hard disc, always the same result.
Can’t get past the frozen windows logo to the spinning/circling dots

Indeed so.

Just had an idea, leu me check something.

Failed in SAFE_OS error during BOOT 0xC1900101-0x20017

googling this, led to many different causes and solutions, many from fairly long ago.

going through the \panther\setuperr.log seems a good idea

one solution involved deleting a CPU check file: Windows\system32\mcupdate_genuineintel.dll

another required reducing RAM to original specs for the hardware,

Install errors finally solved with an hour to spare - Forums - CNET

and

How to fix error 0xc0000017 when installing Windows 10

all pointed to memory errors - either real bad memory or falsely reported errors

these led to removal of badmemory markers in the BCD store to enable installation following the error message you posted.

and so on

Probably worth going through some of the solutions with a clear mind tomorrow.

OK, Your motherboard is pretty analogous to mine, I have an eVGA x58 Classified 3 motherboard, with many of the same features (and pitfalls) as yours.

My motherboard uses the Marvell chipset for providing the SATA III connectivity onboard, whereas yours provides a Marvell chipset for controlling the 2 eSATA ports you have available. For my setup, even though the Marvell doesn't provide true SATA II speeds (5 Gbps max versus normal 6 Gbps), I still use it for my two primary drives, both of which are SATA III SSDs. The only things I have connected to the regular ICH10R SATA II ports are my storage (mechanical) drives as well as my BluRay burner.

I'm curious - in your setup, how are your drives connected? Is everything connected to the SATA II ports, or is anything connected to the eSATA ports?

Also, I'm assuming that you've installed as many of the drivers listed here as you can get installed: Downloads for Intel® Desktop Board DX58SO

Fafhrd said:

Failed in SAFE_OS error during BOOT 0xC1900101-0x20017

googling this, led to many different causes and solutions, many from fairly long ago.

going through the \panther\setuperr.log seems a good idea

one solution involved deleting a CPU check file: Windows\system32\mcupdate_genuineintel.dll

another required reducing RAM to original specs for the hardware,

Install errors finally solved with an hour to spare - Forums - CNET

and

How to fix error 0xc0000017 when installing Windows 10

all pointed to memory errors - either real bad memory or falsely reported errors

these led to removal of badmemory markers in the BCD store to enable installation following the error message you posted.

and so on

Probably worth going through some of the solutions with a clear mind tomorrow.

That reminds me of another of the foibles of the eVGA x58 mobos - Though I never personally experienced this, the word in the eVGA forums was that, particularly when installing Windows 8+, you reduce the RAM in your motherboard to a single stick in the main bank (and with your motherboard, that would be bank 0 in channel 0, the closest one to the CPU). Since we both have LGA1366 CPUs, I made full use of my triple channel slots (I have 6 to your 4) and thus have a stick in each of the 0 banks for each channel, but if you were to make use of triple channel, you'd have it in the first and last 2 (from CPU outward) skipping that second slot for true triple channel features. However, almost everyone else posting in the eVGA forums back when Windows 10 first came out kept running into really weird errors, which were (usually) resolved by users dropping down to a single stick of RAM, and this advice was carried over from the first days of the eVGA x58 line being released and folks trying to install Windows 7 on those boards.

As I said, I never had any issues with my mobo causing me to have to drop the # Memory DIMMs in my computer, that I can recall, and I also have it overclocked in the BIOS, which was another thing that was mentioned to remove when installing, and particularly clean installing Windows 7 / 8 / 10.

I suspect that the reason I have had few issues is because of my quick incorporation of SSDs in the build. Who knows?