Win 10 RS-4 not compatible with Intel DX58SO motherboard

Fafhrd said:

If you can open these files, you may be able to pinpoint the problem driver(s).

Understanding Failures and Log Files.

Although written with earlier Windows versions in mind, the use of DISM to service the Install.wim file is the same for Windows 10, so you may be able to replace failing drivers with successful ones from 16299, before deployment. Further diagnostic files may be available according to the article.

You may need assistance from some of the gurus here or elsewhere if you fall into difficulties!

Thanks mate; I did an extended cleanup yesterday so I’m not sure if I lost all the log files.
I’ll have to install from a mounted ISO setup again if they’re all gone.


If we can pinpoint the problem drivers and replace them from 16299 I would be over the moon.

That’s exactly what I’ve been trying to do all along but wasn’t sure it was possible and without success, so far.:)


Just found Setuperr.log and Setupact.log in C:\Windows\Panther dating from last week


-------------------------------------------------------------------------
In the setuperr.log there is only one line that reads:

2017-12-07 10:28:30, Error [0x0606ae] IBS [SetupCl library] Required profile hive does not exist: [\??\F:\WINDOWS\system32\config\systemprofile\NTUSER.DAT].

----------------------------------------------------------------------------

These are the only “errors” and “warnings” in setupact.log the rest of them are all just “Info”



2017-12-07 10:20:25, Warning UI CLanguages::v_InitLanguage - Failed to load en-US resources with error 2. Will load fallback binaries

2017-12-07 10:20:30, Warning [0x070026] DIAG Win32_Processor : Unable to retrieve Stepping, vtType = 8. Error code = 0x0

2017-12-07 10:20:35, Warning [0x07008d] DIAG Win32_Processor : CoInitializeEx returned RPC_E_CHANGED_MODE. Continue. Error code = 0x80010106

2017-12-07 10:20:36, Warning [0x070026] DIAG Win32_Processor : Unable to retrieve Stepping, vtType = 8. Error code = 0x0

2017-12-07 10:20:39, Warning UI [APPCOMPAT UI] Got CallbackAppCompatProgress without compat progress page active

2017-12-07 10:21:33, Warning [0x0606cc] IBS DeleteFileEx: Unable to clear out attributes on [F:\$WINDOWS.~BT\Sources\Rollback\bootsec.dat]; GLE = 0x2

2017-12-07 10:30:16, Warning IBSLIB RewriteBlackboardPaths:Corresponding path not found. Key name [\LangPacks\LanguageList\en-gb] Value name [SrcLocation]. Path name X:\Langpacks\en-gb.

2017-12-07 10:30:16, Info IBSLIB RewriteBlackboardPaths:Rewrote BB value \DiskInfo\Disk0\RegionAtOffset1048576!DrivePath; [C:\] ==> [G:\]

2017-12-07 10:30:16, Info IBSLIB RewriteBlackboardPaths:Rewrote BB value \DiskInfo\Disk0\RegionAtOffset576716800!DrivePath; [F:\] ==> [C:\]

2017-12-07 10:30:16, Warning IBSLIB RewriteBlackboardPaths:Corresponding path not found. Key name [\DiskInfo\Disk1\RegionAtOffset1048576] Value name [DrivePath]. Path name D:\.

2017-12-07 10:30:16, Warning IBSLIB RewriteBlackboardPaths:Corresponding path not found. Key name [\DiskInfo\Disk1\RegionAtOffset576716800] Value name [DrivePath]. Path name G:\.

2017-12-07 10:30:16, Warning IBSLIB RewriteBlackboardPaths:Corresponding path not found. Key name [\InstallSource] Value name [InstallSourcesPath]. Path name E:\Sources.

2017-12-07 10:30:16, Warning IBSLIB RewriteBlackboardPaths:Corresponding path not found. Key name [\ImageInfo\OSImage] Value name [FilePath]. Path name E:\Sources\install.wim.

2017-12-07 10:31:12, Warning SYSPRP DetermineIfReRegisterOnUpgrade: setupApplicationsKey.Open() failed 0x80070002, assuming Yes

2017-12-07 10:31:13, Warning SYSPRP Ignoring folder Deleted because could not convert to family name

2017-12-07 10:33:53, Warning TOOL SpecializeBcdStore: The /detecthal switch could not be removed because it was not found.

2017-12-07 10:33:54, Warning [setup.exe] read xml file (\Recovery\ReAgentOld.xml) failed: 0x3

2017-12-07 10:33:54, Warning [setup.exe] ReAgentXMLParser::ParseConfigFile failed to read config xml file (0x3) in file base\diagnosis\srt\reagent2\reinfo\parser_2.0.cpp line 779

2017-12-07 10:33:54, Warning [setup.exe] ReAgentXMLParser::ParseConfigFile (xml file: \Recovery\ReAgentOld.xml) returning 0x3

2017-12-07 10:33:54, Warning [setup.exe] ReAgentConfig::ParseConfigFile returned with 0x3

2017-12-07 10:33:54, Warning [setup.exe] ReAgentConfig::Init failed to init reagent xml parser (0x3) in file base\diagnosis\srt\reagent2\reinfo\parser_2.0.cpp line 1916

2017-12-07 10:33:54, Warning [setup.exe] failed to get child attribute by tag: 0xd

2017-12-07 10:33:54, Info [setup.exe] GetChildAttributeByTag(IsAutoRepairOn) failed: 0xd

2017-12-07 10:33:54, Warning [setup.exe] failed to get child attribute by tag: 0xd

2017-12-07 10:33:54, Info [setup.exe] GetChildAttributeByTag(IsServer) failed: 0xd

2017-12-07 10:33:54, Warning [setup.exe] failed to get child attribute by tag: 0xd

2017-12-07 10:33:54, Info [setup.exe] GetChildAttributeByTag(DownlevelWinreLocation.Dir): 0xd

2017-12-07 10:33:54, Warning [setup.exe] failed to get child attribute by tag: 0xd

2017-12-07 10:33:54, Info [setup.exe] GetChildAttributeByTag(DownlevelWinreLocation.DiskSignature): 0xd

2017-12-07 10:33:54, Warning [setup.exe] failed to get child attribute by tag: 0xd

2017-12-07 10:33:54, Info [setup.exe] GetChildAttributeByTag(DownlevelWinreLocation.Offset): 0xd

2017-12-07 10:33:54, Warning [setup.exe] failed to get child attribute by tag: 0xd

2017-12-07 10:33:54, Info [setup.exe] GetChildAttributeByTag(DownlevelWinreLocation.DiskId): 0xd

2017-12-07 10:33:54, Warning [setup.exe] failed to get child attribute by tag: 0xd

2017-12-07 10:33:54, Info [setup.exe] GetChildAttributeByTag(IsWimBoot) failed: 0xd

2017-12-07 10:33:54, Warning [setup.exe] failed to get child attribute by tag: 0xd

2017-12-07 10:34:07, Warning [setup.exe] Recovery file not found at C:\Windows\system32\Recovery\ReCustomization.xml

2017-12-07 10:34:07, Warning [setup.exe] winreBackupRecoveryFile (C:\Windows\system32\Recovery\ReCustomization.xml, ReCustomization.xml) failed, Err: 2

2017-12-07 10:34:15, Warning [0x0f008f] SYSPRP RunRegistryDlls:Registry key is either empty or malformed: SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\SysPrepExternal\Specialize
--------------------------------------------------------------

johngalt said:

Hmmmmmmmmm.

Could you post your HDD and partition structure for the drive you are installing to?

Thanks mate, is this what you mean?

I’m installing on C:

E: is just a backup drive

Plus I’ve always only had the C: drive, I only put the other extra hard disk on since I’ve had this problem, so I can play about without losing anything important

johngalt said:

I have used only USB for installs on Windows 10 for a long time now. Did you mention that it doesn't work via USB?

Yes mate I mostly do use a USB.

Fafhrd said:

more thoughts later.

Yes please mate

Maybe I should delete all the log files and try a new install so we can get a better picture of what is going on. What do you think?

It’s all confusing now because I’ve used 2 different USB drives and a DVD to install from.

One called LEXAR which has 16299 on it and I can see many references to it as well as 16299 in the log file.

One called SanDisk with 17046 on it but I can’t find any references to that or any references to 17046 at all in the log file.

-----------------------------------------------

2017-12-07 10:20:25, Info [0x0606cc] IBS LogDeviceInfo: Friendly name = [Lexar USB Flash Drive USB Device]
2017-12-07 10:20:25, Info [0x0606cc] IBS LogDeviceInfo: Service = [disk

2017-12-07 10:20:25, Info [0x0606cc] IBS LogDeviceInfo: Driver version = [10.0.16299.15]

------------------------------------------------

johngalt said:

I would suggest the following:

1. Wipe the drive - if at all possible, use diskpart during install and clean the drive and then let Windows 10 installer create the partitions it wants.
2. Use an installer for 16299 (aka FCU)
3. After you have it installed, go ahead and set everything up.
4. After you have FCU running exactly the way you want to, all settings and programs installed, etc., make a Macrium Reflect (or your own choice of HD partition backup software, such as CloneZilla, etc.) backup that you can later restore if need be
5. Now try to install 170XX.

Also, I have a working 17046 install .ISO that I created when my computer downloaded the installation files via Windows Update, which I then made into an .ISO using UUP2ISO. If you want, I can send you the .ISO that I have now used 3 times to upgrade FCU directly to 17046 on my desktop with similar hardware to yours.

I also have 17017, 17025, 17035, & 17040 available (and I'm seriously considering trying to install 17040 over 17046, 1) as a test (I think it is supposed to fail) and 2) because 17046 is a MAJOR PITA with it continuously suspending apps that I am actively working on, particularly software installations....

Seeing as they have stopped distributing 17046 via Windows Update....

Let me know and I'll fire up either my Google Drive or else something similar to share the file (whichever you choose) to you...

Thanks mate I do appreciate all your help but before we go on to that I have to apologise.

The setupact & setuperr logs posted on post no #92 can only be from a successful 16299 install.

I just run a 17046 ISO setup again unsuccessfully as normal but the C:\Windows\Panther setupact & setuperr logs are the old ones dating from last week 07-12-2017, they haven’t been overwritten like I thought they would be.

I’ll try and find today’s setupact & setuperr logs if I can so we can compare the differences


Edit:
Ok got today’s one from $WINDOWS.~BT&crumb=location:C%3A%5C$WINDOWS.~BT\Panther

Let’s see what we have