Win 10 RS-4 not compatible with Intel DX58SO motherboard

bordi · 26 Dec 2017

For reference:
Found a quick and easy way to inject drivers into install.WIM
I know its cheating but for those of us too old to memorise dism commands

DISM GUI download link: https://dismgui.codeplex.com/downloads/get/913554

Create new folders C:\drivers; C:\iso; C:\ mount
Export the drivers from Windows 10 installation
From Elevated PowerShell “dism /Online /Export-Driver /Destination:C:\Drivers”

Mount the ISO and copy the contents to the C:\ISO folder or just use a bootable Windows Setup on a USB flash drive

Download and Launch GUI DISM as admin
Click Choose WIM and Point it to C:\iso\sources\install.wim or to install.wim on USB
Click Choose Folder and Point it to C:\ mount
Click Mount WIM; wait for it to finish mounting
Click Driver Management Tab: then Click Choose Driver Folder
Point it to the Drivers folder
Check 'Force Unsigned' if necessary
Click Add Drivers; wait for it to finish adding drivers

Switch back to Mount Control tab and click Dismount WIM
When prompted click Yes to commit changes to the WIM
Image will be updated with the drivers injected into the install.WIM
Exit

Fafhrd · 26 Dec 2017

Another festive experiment might be to see if the 170xx firstly will run for you on your dx58so as a virtual machine on a 16299 host with Hyper-V, and with VMWare. If successful try to move it closer to running on bare metal with a hypervisor such as vSphere, which is free to use.

bordi · 26 Dec 2017

Ok mate thanks I’ll try it, the problem is that no 17xx will boot from USB on this machine no matter what I do so:

I replaced the complete boot.wim in 17025 from 16299 and now setup boots ok from the USB but only up to where you chose which partition to install on, where I get the error:

“A media driver your computer needs is missing. This could be a USB flash drive please insert it now. “

Which apparently is a “Driver load error when using boot.wim image” according to the link below, so I injected the old drivers into boot.wim and install.wim. Still boots to the same point then same error message.

https://support.microsoft.com/en-gb/help/4041170/windows-installation-cannot-find-driver-boot-wim

Cause:
“This issue occurs because the setup.exe file that's in the updated boot.wim image doesn't not match the setup.exe file that's in the original source media.”

Which is obvious really

No point changing the setup.exe otherwise how much of the 17xx will remain on the USB setup. :)

Fafhrd · 26 Dec 2017

With a VM install, the windows setup ISO file (e.g. an untouched 17025 iso download) is mounted as a virtual drive which is used by the vm to create the installation on a virtual hard disk (VHD format in Windows hyper-v). The VM software has its own virtual bios, virtual devices etc, which will sort of insulate the virtual machine from the actual hardware. No USB involved.

Loads of experienced TF folk here on the Virtualization forum to advise.

EQuito · 26 Dec 2017

@bordi
I was advised by a moderator at Insiders Forum to do the following:

"MELERIX replied on December 26, 2017

if you are trying to install any build post 17025 such as 17035, 17040, 17046 and 17063 and you experience one of the following bugs, this are the know workarounds for now…

1 - Windows stuck in logo after first reboot: enter in your mainboard BIOS settings and disable Virtualization or disable ACPI HPET Table, depending of your mainboard."

It doesn't apply to me but maybe it will help you. Good luck!

bordi · 26 Dec 2017

EQuito said:

@bordi
I was advised by a moderator at Insiders Forum to do the following:

"MELERIX replied on December 26, 2017

if you are trying to install any build post 17025 such as 17035, 17040, 17046 and 17063 and you experience one of the following bugs, this are the know workarounds for now…

1 - Windows stuck in logo after first reboot: enter in your mainboard BIOS settings and disable Virtualization or disable ACPI HPET Table, depending of your mainboard."

It doesn't apply to me but maybe it will help you. Good luck!

Thanks mate I appreciate your help but my problem started with the first release of the RS-4s

I haven’t been able to install any of them at all; I’m stuck on 16299 RS-3s

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
Build 17063 19/12/2017 - Failed in SAFE_OS error during BOOT 0xC1900101-0x20017

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

EQuito · 26 Dec 2017

Sorry, even though I've read your entire thread trying to find a solution to my problem, I forgot about that.
You're stuck at FCU and I'm stuck at 17040 on my 32bit laptop

I was having previously unseen problems installing 17063 on my 64bit laptop using legacy bios without virtualization enable. As soon as I switched (against my wishes) to UEFI, even with virtualization enable, 17063 installed perfectly.

Makes you wonder, doesn't it?

bordi · 26 Dec 2017

I’ve tried both legacy bios and UEFI when I first came across this problem, as well as disabling and enabling virtualization in bios but it didn’t do any good

Might try UEFI once more when I feel like formatting the hard disk again, not that it’s going to do any good but I still have a few more months before I'm able to get a motherboard, ram and Hydro Cooler for an upgrade

bordi · 29 Dec 2017

Went to the loft yesterday and brought down an old Vista laptop with a failing hard disk and 1GB of RAM. Installed windows 10 and after installing it said “can’t update, needs 2GB of RAM minimum.

So I went to CEX and got a second hand 140GB hard disk for £5, and 2GB of RAM for £4, fitted them on, installed 16299, updated everything, used a windows 7 key for activation, joined the insiders with a new MS account, put a USB with 17025 on it and it installed perfectly.

Now instead of being happy about it I’m even more upset

Why wouldn’t this stupid system boot with any of the RS-4s?
Someone must know

johngalt · 29 Dec 2017

Could very well be that it is a hardware conflict, flaky hardware, or who knows what else.

You've tried single stick of RAM, BIOS reset (and I assume you didn't go back and set it all back up, that you left everything at full default after rest), marginal hardware, driver injection....

I am not willing to say that WinX is incompatible with that motherboard family. But I am definitely willing to agree that WinX doesn't like your particular hardware setup.

Hell, grab that new HD you just bought and try to use it in the Intel board (no other HDs installed) and try to install 17025 via . ISO without any modifications.