The installation Failed is SAFE_OS Phase 0xc1900101-0x20017

Hi all,

I am out of ideas here on how to upgrade from 1803 to 1903, I have been googling and trying things almost all night to no avail. I learned this is some sort of driver that is outdated, what is the best way to find which driver it is? Are driver update programs like SDI safe to use?

I tried to update both via the Windows 10 update assistant as well as the media creation tool. I always just get the installation Failed is SAFE_OS Phase 0xc1900101-0x20017.

- Removed all USB devices as well as extra HDDs and peripherals
- Ran various chkdsk and dism /online /remove-package /package as well as various other commands that repaired some errors.
- Tried the windows update troubleshooter
- Tried a clean boot

Any other ideas? I am thinking I may be stuck doing a fresh install of windows. If you need any other information please let me know and thanks!

There are log collectors used in another forum room.
Run both V2 and DM and upload results into this thread:
BSOD - Posting Instructions

Current options are:
reset save files, reset save files equivalent, clean install, troubleshoot
They each take time and can be compared to decide the next step.

If you choose to troubleshoot:

1) Open administrative command prompt and type or copy and paste:
2) sfc /scannow
3) dism /online /cleanup-image /restorehealth
4) chkdsk /scan
5) wmic recoveros set autoreboot = false
6) bcdedit /enum {badmemory}
7) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

8) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings

a) > on the advanced tab under startup and recovery > click settings > post an image of the startup and recovery window into the thread

b) > on the advanced tab under performance > click on settings > on the performance options window > click on the advanced tab > under virtual memory > click on change > post an image of the virtual memory window into the thread

9) Open disk management > by default some columns are compressed > widen each Status and Volume > make sure the contents within the parenthesis are in full view and that none of the characters are cutoff > view disk 0 > widen this row as needed so that all of the characters are in full view > post an image into the thread
Disk Management - How to Post a Screenshot of

10) List and uninstall all non-Microsoft antivirus software
(This includes always on and manual software.)
(This includes running the applicable antivirus uninstall tools for any AV that could have been incompletely unistalled)

11) List and uninstall all non-Microsoft firewall software

12) List all Microsoft and non-Microsoft drive encryption software.
Uninstall all non-Microsoft disk encryption software

Microsoft Windows [Version 10.0.17134.915]
(c) 2018 Microsoft Corporation. All rights reserved.

C:\Windows\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\Windows\system32>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.17134.1

Image Version: 10.0.17134.915

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

C:\Windows\system32>chkdsk /scan
The type of the file system is NTFS.

Stage 1: Examining basic file system structure ...
596480 file records processed.
File verification completed.
18212 large file records processed.
0 bad file records processed.

Stage 2: Examining file name linkage ...
875 reparse records processed.
757514 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered to lost and found.
875 reparse records processed.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
80518 data files processed.
CHKDSK is verifying Usn Journal...
40095520 USN bytes processed.
Usn Journal verification completed.

Windows has scanned the file system and found no problems.
No further action is required.

249427967 KB total disk space.
115857212 KB in 355145 files.
253052 KB in 80519 indexes.
0 KB in bad sectors.
717403 KB in use by the system.
65536 KB occupied by the log file.
132600300 KB available on disk.

4096 bytes in each allocation unit.
62356991 total allocation units on disk.
33150075 allocation units available on disk.

C:\Windows\system32>wmic recoveros set autoreboot = false
Updating property(s) of '\\DESKTOP-30F2GC8\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\Windows|\\Device\\Harddisk5\\Partition4"'
Property(s) update successful.

C:\Windows\system32>bcdedit /enum {badmemory}

RAM Defects
-----------
identifier {badmemory}

Attachment 242768

Attachment 242769

Attachment 242770

Have no non-MS AV/firewall/encryption

- - - Updated - - -

OS Build is 17134.915

Looks like the DM and LC scripts ran into a few snags, if anything is missing let me know. :)

Question on 4, I ran it and crashed with Driver Verifier iomanger violation for HIDCLASS.sys and I used my restore point to get back into windows. Should there be a crash dump file somewhere to identify which driver caused that specifically?

I attached the files I could find from your list. Seems for some reason I have Panther, then NewOs with Panther in it (that's what I attached), then a folder called Rollback, I assume from my restore point.

- - - Updated - - -

Nevermind, it was one of these applications that were blocking it!
amtrucks.exe
corsairlink4.service.exe
Intel rapid storage technology

Thank you very much zbook!

When using Windows driver verifier there may be decreased performance and slow boot.

There are three commands/methods that are commonly used after a windows driver verifier BSOD to turn off or recover fro using the tool.

The commands should be used in order, only advancing to the next command when the prior command fails.




a) verifier /reset
b) verifier /bootmode resetonbootfail
c) system restore

System restore should only be used last as often the system restore results in the loss of dump files.
Without dump files little progress can be made in the troubleshooting.

For any BSOD:

a) run the V2 log collector to collect new log files

b) open file explorer> this PC > C: > in the right upper corner search for: C:\Windows\memory.dmp
> if the file size is < 1.5 GB then zip > post a separate share link into the thread using one drive, drop box, or google drive

zbook said:

Was the upgrade successful?
If so that's great.
You are welcome.

Yes it was, I am not sure which of those 3 programs were to blame... something tells me Corsair link... I don't think I would have found it without your help so thanks again!

That's terrific.
You are very welcome.