Windows 10 1709 32 bit Fails to upgrade with error 0xC1900101 - 0x20017

2018-01-09

Question

_{Tuesday, January 9, 2018 8:58 PM | 1 vote}

This is not your average upgrade failure.

error 0xC1900101 - 0x20017
The installation failed in the SAFE_OS phase with an error during BOOT operation.

This happens in Legacy Boot mode (not UEFI) with the BIOS setting of AHCI (not on the Intel RAID option). The system has an M.2 NVMe SSD. Here's the kicker:
A FRESH install of Windows 10 1709 doesn't work either.
DISKPART within 1703 reveals:

DISKPART> detail disk

THNSN5256GPUK NVMe TOSHIBA 256GB
Disk ID: 7C32A85C
Type   : NVMe
Status : Online
Path   : 0
Target : 0
LUN ID : 0
Location Path : PCIROOT(0)#PCI(1B00)#PCI(0000)#NVME(P00T00L00)
Current Read-only State : No
Read-only  : No
Boot Disk  : Yes
Pagefile Disk  : Yes
Hibernation File Disk  : No
Crashdump Disk  : Yes
Clustered Disk  : No

  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
                
  Volume 1         System Rese  NTFS   Partition    500 MB  Healthy    System
  Volume 2     C                NTFS   Partition    237 GB  Healthy    Boot

Disk ID: 7C32A85C

And with using the BootPE of the 1709 media:

DISKPART> detail disk

THNSN5256GPUK NVMe TOSHIBA 256GB
Disk ID: 00000000
Type   : NVMe
Status : Online
Path   : 0
Target : 0
LUN ID : 0
Location Path : PCIROOT(0)#PCI(1B00)#PCI(0000)#NVME(P00T00L00)
Current Read-only State : No
Read-only  : No
Boot Disk  : No
Pagefile Disk  : No
Hibernation File Disk  : No
Crashdump Disk  : No
Clustered Disk  : No

There are no volumes.
Disk ID: 00000000

This leads me to believe it's driver-based, however on the Upgrade, the driver would be migrated through the Windows 10 upgrade procedures to at least use the one that is installed and working.

Troubleshooting:

Ran a Disk Cleanup as Admin and checked everything. Ran this through 2 times.
Tried installing from the WSUS download 3 times, tried from the Downloaded iso file 3 times, and tried from bootable USB Media 3 times.
The BIOS has been flashed with the latest Dell BIOS for this unit (OptiPlex 7040), and the latest drivers have been installed (as per Dell System Detect) as a troubleshooting measure, and there was 1 driver update which was the Intel Rapid Storage Technology driver, but even after this, the upgrade fails.
I've gone into Device Manager and removed all hidden devices that are no longer connected.
I've physically removed the connection to our Calibration equipment, and removed the drivers from device manager.

I cannot install x64 on this system as it's hooked up to calibration equipment that has a 32bit program that won't run under x64 (tried and failed).

The system will boot to the 1703 media and allow you to install the system as shown in the below image:

But using the 1709 Media, I get this:

Does anyone have any idea?

Adam Marshall, MCSE: Security
http://www.adamj.org
Microsoft MVP - Windows and Devices for IT

All replies (16)

_{Thursday, June 21, 2018 7:58 PM ✅Answered}

I wanted to report back on my situation. I contacted Dell as we have Pro Support, but they had not seen this ever. They didn't help me but to say that 32 bit is not supported. (The initial tech before I escalated to a supervisor even said "I have never heard of 32 bit Windows 10... is there such a thing?").

So. 1709 and 1803 DO NOT install properly in 32 bit mode with SecureBoot turned off and Legacy Boot mode turned on instead of UEFI. I end up getting the same result as the images above in my initial post. After researching and researching waiting for Dell's escalation team to call me back (they called me back while typing this after I figured it out, only to say that they can't help me), I tried injecting different Intel drivers (due to it being an Intel RAID Controller) but those didn't work. Something didn't sit right with me because the SSD was identified and was able to be seen without any help - it was just in some almost read only mode. I then stumbled upon (OK, let's be real, Googled upon)

https://www.win-raid.com/t29f25-Recommended-AHCI-RAID-and-NVMe-Drivers.html

I took the modified drivers from Fernando's second post

- mod+signed drivers:
  - >"pure" 32bit OCZ NVMe driver v1.2.126.843 mod+signed by me (at 01/18/2018)< (>MIRROR<)
  - >"pure" 64bit OCZ NVMe driver v1.2.126.843 mod+signed by me (at 01/18/2018)< (>MIRROR<)
  These mod+signed drivers additionally do support the Toshiba "XG4" NVMe Controllers with the DeviceIDs DEV_0103 and DEV_0115 and the "XG5" ones with the DeviceID DEV_0116. Thanks to alvarezegam and Jan for having tested them.

and I loaded the 32 bit version of the driver on top of what was already coming up from the WindowsPE - Immediately I saw the volumes on the drive (rather than seeing the drive with all space free) and I was able to load Windows 1803, 32 bit on the OptiPlex 7040. After it was finished, the list under storage controllers shows the Intel SATA/PCIe RST Premium Controller, Microsoft Storage Spaces Controller, Microsoft VHD Loopback Controller, and the "XG4-DEV_0115" which is the result of loading the modified drivers. Without these drivers, loading 32bit Windows 10 wouldn't be possible.

Adam Marshall, MCSE: Security
https://www.ajtek.ca
Microsoft MVP - Windows and Devices for IT

_{Thursday, January 11, 2018 9:29 AM}

Hi Adamj,

We received similar feedback and submitted it via our channel. No any update so far.

For now, please update your BIOS and NVME driver to the latest version.

And then perform upgrade again to see if it can be succeed.

It is possible that removal of peripherals (extra PCIe adapters etc) and/or some BIOS setting tweaks could alter the system memory layout in such a way that avoids this issue. This would require ad-hoc trial and error experimentation that may be unfruitful and therefore frustrating to device owners. Another thought would be to limit the amount of memory on the install device to 4GB.

If the issue persist, please backup your important data and consider to perform a Clean Installation.

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

_{Thursday, January 11, 2018 2:43 PM | 1 vote}

For now, please update your BIOS and NVME driver to the latest version.

And then perform upgrade again to see if it can be succeed.

Already done as mentioned in my original post under Troubleshooting

It is possible that removal of peripherals (extra PCIe adapters etc) and/or some BIOS setting tweaks could alter the system memory layout in such a way that avoids this issue. This would require ad-hoc trial and error experimentation that may be unfruitful and therefore frustrating to device owners. Another thought would be to limit the amount of memory on the install device to 4GB.

The system is untouched internally from the original system spec. There are no added adapters, ram, or anything. I already went through the BIOS to see if I could find anything that may help, but all attempts failed. Having the RAM limited to 4 GB (currently has 2x4GB sticks) doesn't make sense that it would affect how it detects the NVMe Drive, but I'll do that to troubleshoot as that's the only thing out of your entire post that I haven't tried.

If the issue persist, please backup your important data and consider to perform a Clean Installation.

I was trying to do a clean installation - as per the screenshots - those were taken with 1703 and 1709 bootable USB Media.

We received similar feedback and submitted it via our channel. No any update so far.

If there are any logs or diagnostics I can provide, please let me know and I'll provide them. Something changed in the installer between 1703 and 1709.

Adam Marshall, MCSE: Security
http://www.adamj.org
Microsoft MVP - Windows and Devices for IT

_{Tuesday, January 16, 2018 8:58 AM}

Hi,

Thanks for your patience and so detailed reply. No log needed so far since we have collect to analysis.

Here I suggest you check and install Windows update on time in order that get the hotfix as soon as possible when it's available.

And if any update, I will also post here to let you know.

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

_{Sunday, January 28, 2018 11:01 PM}

I have the same issue using windows 10 1709 x86 boot wim to image machines.

when running diskpart the disk Id is all 0's and no volumes are shown.

for one of the machines that has a samsung NVME drive i can inject the samsung driver in to the wim and it detects the drive correctly. I cant do this for all the drives as i can't get a driver to inject for the newer samsung drives and some of the machines come with other brands of drives lenovo and toshiba that i can't get drivers for.

If i use the x64 boot wim it all works correctly without any drivers.

but i need to be able to image 32 bit machines

need a resolution to this problem

_{Wednesday, February 7, 2018 9:50 PM}

Hi, I had the same problem

the solution that helped me: I put the sdcard on the card reader and Windows started installing. I think it's about the empty devices that the cardreader generates

Disable General USB Devices (example - Smart Card Reader)

_{Wednesday, February 7, 2018 10:04 PM}

To evaluate the computer environment please post logs for troubleshooting.

Using administrative command prompt copy and paste this whole command:

Make sure the default language is English so that the logs can be scanned and read.

https://www.tenforums.com/tutorials/3813-language-add-remove-change-windows-10-a.html

The command will automatically collect the computer files and place them on the desktop.

Then use one drive or drop box to place share links into the the thread for troubleshooting.

https://support.office.com/en-us/article/Share-OneDrive-files-and-folders-9fcc2f7d-de0c-4cec-93b0-a82024800c07

It will automatically collect these files: msinfo32, dxdiag, mini dumps, drivers hosts, install, uninstall, services, startup, event viewer files, etc.

Open administrative command prompt and copy and paste the whole command:

copy %SystemRoot%\minidump\.dmp "%USERPROFILE%\Desktop\&dxdiag /t %Temp%\dxdiag.txt&copy %Temp%\dxdiag.txt "%USERPROFILE%\Desktop\SFdebugFiles\&type %SystemRoot%\System32\drivers\etc\hosts >> "%USERPROFILE%\Desktop\hosts.txt"&systeminfo > "%USERPROFILE%\Desktop\systeminfo.txt"&driverquery /v > "%USERPROFILE%\Desktop\drivers.txt" &msinfo32 /nfo "%USERPROFILE%\Desktop\msinfo32.nfo"&wevtutil qe System /f:text > "%USERPROFILE%\Desktop\eventlog.txt"&reg export HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall "%USERPROFILE%\Desktop\uninstall.txt"&reg export "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Active Setup\Installed Components" "%USERPROFILE%\Desktop\installed.txt"&net start > "%USERPROFILE%\Desktop\services.txt"&REM wmic startup list full /format:htable >"%USERPROFILE%\Desktop\startup.html"&wmic STARTUP GET Caption, Command, User >"%USERPROFILE%\Desktop\startup.txt"

Sometimes the dxdiag file needs to be found and saved manually: In the left lower corner search type: dxdiag > When the DirectX Diagnostic Tool opens click on the next page button so that each tab is opened > click on save all information > save to desktop > post one drive or drop box share link into the thread

Open disk management > widen status and volume columns so that the contents of each row is in full view and nothing is cutoff > post an image into the thread using a one drive or drop box share link.

Download and install Mini Tool partition wizard: http://download.cnet.com/MiniTool-Partition-Wizard-Free-Edition/3000-2094_4-10962200.html

Post an image into the thread using one drive or drop box share links.

Open the website for the computer or motherboard manufacturer > enter the product or serial number or model > select the operating system > view drivers > post a URL or hyperlink into the thread

_{Thursday, February 8, 2018 2:37 AM}

Microsoft's post on this said they don't need any extra detail and that they've seen this before (read Karen_Hu (MSFT CSG)'s response above)

Thanks for the attempt dddrive200, but the device in question doesn't have any extra memory card readers, SD Card readers, or anything. I was also already aware of the memory card issue as well.

Adam Marshall, MCSE: Security
http://www.adamj.org
Microsoft MVP - Windows and Devices for IT

_{Thursday, February 15, 2018 9:25 PM}

Microsoft's recommended solution was to apply the latest cumulative update to the wim.

Download the 2018-01 update for Windows 10 1709 x86 (http://catalog.update.microsoft.com/v7/site/Search.aspx?q=4058258)
Copy the WinPE.wim from C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\en-us to a new directory (C:\copied_WIM)
Create a mounting directory (example: c:\mount)
Mount WinPE.wim: From an administrative command DISM /Mount-Image /ImageFile:"C:\Copied_WIM\winpe.wim" /Index:1 /MountDir:C:\Mount
Expand and install the update
1. Create a temp folder (example: C:\temp\4058258)
2. From an administrative command prompt run Expand -F:* C:\users\Username\desktop\KB4058258\AMD64_X86-all-windows10.0-kb4058258-x86_c22631f5fd747b49d553316049c02eccffd3af1d.msu C:\temp\4058258
3. From an administrative command prompt run DISM /Image:C:\Mount /Add-Package /PackagePath:C:\Temp\4058258\Windows10.0-KB4058258-x86.cab
Unmount WinPE.wim: From an administrative command prompt run DISM /Unmount-Image /MountDir:C:\Mount /Commit
Import the WinPE.wim into SCCM and test deployment of a Windows 7 32-bit OS to a device with an NVMe drive

_{Tuesday, March 13, 2018 6:21 PM}

Hi Luke0369,

I don't have SCCM, I'm using iso media.

I've extracted the iso and mounted the boot.wim (.\sources\boot.wim); applied the patch you mentioned, and tried running it via setup.exe and I get the same issue.

Microsoft Windows [Version 10.0.16299.248]
(c) 2017 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>cd \temp

C:\Temp>dism /mount-image /imagefile:C:\Temp\sources\boot.wim /index:1 /mountdir:C:\Temp\Mount

Deployment Image Servicing and Management tool
Version: 10.0.16299.15

Mounting image
[==========================100.0%==========================]
The operation completed successfully.

C:\Temp>cd a

C:\Temp\a>expand -F:* windows10.0-kb4058258-x86_c22631f5fd747b49d553316049c02eccffd3af1d.msu .
Microsoft (R) File Expansion Utility
Copyright (c) Microsoft Corporation. All rights reserved.

Adding .\WSUSSCAN.cab to Extraction Queue
Adding .\Windows10.0-KB4058258-x86.cab to Extraction Queue
Adding .\Windows10.0-KB4058258-x86-pkgProperties.txt to Extraction Queue
Adding .\Windows10.0-KB4058258-x86.xml to Extraction Queue

Expanding Files ....

Expanding Files Complete ...
4 files total.

C:\Temp\a>dism /image:C:\Temp\Mount /Add-package /packagepath:C:\Temp\a\Windows10.0-KB4058258-x86.cab

Deployment Image Servicing and Management tool
Version: 10.0.16299.15

Image Version: 10.0.16299.15

Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~x86~~16299.214.1.17
[==========================100.0%==========================]
The operation completed successfully.

C:\Temp\a>dism /unmount-image /mountdir:C:\Temp\Mount /commit

Deployment Image Servicing and Management tool
Version: 10.0.16299.15

Saving image
[==========================100.0%==========================]
Unmounting image
[==========================100.0%==========================]
The operation completed successfully.

I took it a step further - not only did I do it to boot.wim, I extracted the install.wim from the install.esd for JUST my version (pro), applied the patch, deleted the esd and re-compressed the wim back into ESD.

Tried through setup.exe - again failure.

I'm going to wait until 1803 comes out. It's just around the corner now.

Adam Marshall, MCSE: Security
http://www.adamj.org
Microsoft MVP - Windows and Devices for IT

_{Tuesday, March 13, 2018 6:43 PM}

There may be another automatic upgrade attempt before the next build upgrade.

If there is another failure please post these files for troubleshooting:

msinfo32, dxdiag, drivers, mini dumps, users, uninstall, install, setuperr.log, setupact.log, event viewer, etc.

Using 7zip will keep the files organized.

Open administrative command prompt and copy and paste this whole command:

The command should collect the files and place them on the desktop. setuperr.log and setupact.log need to be collected manually. By default they may be hidden. When using file explorer click view > check hidden items.

Use 7zip to keep the files organized.

https://docs.microsoft.com/en-us/windows/deployment/upgrade/resolve-windows-10-upgrade-errors

_{Friday, April 6, 2018 3:23 AM}

try switching the BIOS back to Intel RAID mode for the installation then switch it back to AHCI afterward. To do this:

1. Open System Configuration and select SAFE mode.

2. Reboot the computer and enter BIOS setup.

3. Change configuration from AHCI to Intel RAID.

4. Exit and boot the computer into SAFE mode. (This loads the Intel RAID drivers)

5. Open System Configuration select normal boot.

6. Restart computer then attempt the update.

7. After completion, go through steps 1 through 5 again, this time switching back to AHCI from Intel RAID.

_{Friday, June 22, 2018 9:44 AM}

Thanks for your sharing your experience and solution here. It will be very beneficial to others who have similar problems.

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

_{Wednesday, January 30, 2019 8:35 PM}

But why did you use Legacy Boot mode in the first place? Especially with an M.2 NVMe?

_{Thursday, January 31, 2019 3:07 AM}

Trust me, I didn't want to. Booting from UEFI into 32bit mode caused a black-screen error saying it couldn't load a file (don't remember what file) almost immediately and wouldn't go further. Booting from Legacy mode worked fine. USB media was fine - tested UEFI mode, 32 bit in another system and I got to the Install Windows screen.

Adam Marshall, MCSE: Security
https://www.ajtek.ca
Microsoft MVP - Windows and Devices for IT

_{Thursday, January 31, 2019 3:08 AM}

Also tested UEFI mode on both 1709, 1803 media, 32bit, so it had nothing to do with the version of Windows Media.

Adam Marshall, MCSE: Security
https://www.ajtek.ca
Microsoft MVP - Windows and Devices for IT

Share via

Windows 10 1709 32 bit Fails to upgrade with error 0xC1900101 - 0x20017

Question

All replies (16)

Additional resources