WIn7 fails to upgrade to Win10? 'SafeOS phase - BOOT operation' error.

Hey all - a friend of mine who is an older gentleman, but quite an established and capable photographer asked me to replace the power supply in his desktop PC after a recent power surge killed it.

Power supply is replaced and all is working well again so he asked me to do an upgrade on it from Win7 to Win10. I've done this many times before and haven't had many issues but this time during the upgrade, it fails, reverts back to Win7 and gives me the 'upgrade failed in SAFE_OS phase yada yada BOOT operation' error. I'm trying the upgrade from a Win10 USB stick created using the Media Creation Tool.

I know this can often be caused by drivers and antivirus software, so I temporarily uninstalled the version of AVAST Antivirus Premium he had installed and tried the upgrade again...same error. I don't have any external devices plugged in except for my USB keyboard, USB mouse, monitor, the Media Creation Tool flash drive, and a USB WiFi dongle.

I tried the upgrade again having run the Avast Clear tool to get rid of ANYTHING Avast left behind, and also removed the USB WiFI dongle as well...same error.

I HAVE had this error in the past and solved it with help from here, but can't remember how I went about doing so. I seem to recall user @zbook is knowledgeable about this sort of thing and my fixing it in the past involved log files (but I don't recall where the logs are located...?)

Any help is appreciated as I'd rather not do a full reinstall of Win10 as he has a LOT of high-end photography related software that would need to be put back, a lot of which he no longer has the disks for...

Thanks so much! :)

OH....I did remember to download and run the Microsoft SetupDiag tol and the log from that said it didn't find any errors that matched with known ones...?

The computer is a custom build with Win7 Home Premium 64-bit, an ASUS mobo with 2 x 320GB SATA desktop hard drives running in RAID 0 (as far as I can tell?) with an Intel Core i7 930 CPU @ 2.8Ghz, Radeon HD7800 Series video card and 12GB of RAM.

Thanks! :)

hsehestedt said:

Just to make sure I have the details correct...

The system is running Windows 7. Within Windows 7, you access the USB stick with Windows 10 and run Setup. Setup begins and eventually reboots the system. Is it very soon after the reboot that you are encountering the error?

Essentially yes - running Win7 Home, run Win10 setup from Media Creation Tool-created USB stick, go through the motions, goes to the usual blue screen for installing Win10. It gets someway through to where it would reboot to start the next step, fails there somewhere and goes to the 'reverting to the way things were before' screen and then eventually reboots back into Win7 with the error listed in my first post about the Win10 upgrade failure.

SIW2 said:

setupact.log and setuperr.log
$Windows.~BT\Sources\Panther

and

$Windows.~BT\Sources\Rollback

Thanks - logs attached in a zip file! You guys know more what you're looking for than I do...

logs.zip

- - - Updated - - -

hsehestedt said:

Take a look at this article to see if this helps at all:

Fixed – the Installation Failed in the Safe_OS Phase

From what I can see, it looks like some driver is the most likely cause of the issue. Also, it's worth mentioning that "Safe OS" is a reference to the Windows Recovery environment.

OK, good to know what Safe OS is referring to. I watched it this time - just after running setup.exe from the USB and going through that process, it goes to the blue screen where it starts counting up the % of the upgrade. It gets to 100% then reboots as normal where it would usually continue the upgrade, but I see the Win10 logo (with the spinning circle) for a few seconds, then it just reboots back into Win7 with the SafeOS/BOOT error.

Maybe there is something in the logs you guys could find that would help...sorry I don't really know what I am looking for in them

I should also mention that I've done a sfc /scannow on this machine as well and it said it 'found errors but was unable to fix SOME of them' meaning it had at least fixed some?

- - - Updated - - -

Just an update - ran the Snappy Drive tool, updated the video drivers manually and have just started the upgrade again - will see if that made any difference as it did find some drivers to update.

I'll update when I find out!

- - - Updated - - -

Another update - that didn't make any difference, same error sadly. Running a second sfc /scannow as I've been told it never hurts to do them more than once, and then going to run a chkdsk as I've not done any of those yet.

hsehestedt said:

I suspect that there is likely a driver issue.

I would suggest that however you proceed, you make sure that you have a good complete image backup of the system.

There might be some drivers that you can safely delete. As an example, the display driver can be uninstalled to just allow the system to run on the standard Windows display driver initially. If the system upgrades successfully, then you can locate suitable Windows 10 drivers for those device(s).

The drivers most likely to be causing difficulties with the upgrade are the display driver and the RAID driver.

Another way of approaching this is to start with a good system backup again. Then, perform a clean install of Win 10 just to sanity check it and make sure that Win 10 will run successfully on the system. You could take it a step further to make sure you can find good drivers for everything and then place those drivers aside for later use.

Once you know for a fact that Win 10 will run, then you at least have confidence that you can get there - it just might take a lot of persistence to get there.

Uh oh....but if the RAID driver is the cause, how can I uninstall that when the system is RUNNING in RAID? I'l try using the AMD Cleanup Tool to remove all the display drivers and give the upgrade another shot.

- - - Updated - - -

zbook said:

Before performing major upgrades it is best to make free or pay backup images and save the images to another disk drive or the cloud.

For Windows 7 it is also best to record the product ID.



These batch scripts were created by Matthew Wai.

Batch files for use in BSOD debugging

They were designed for Windows 10 and some may work on Windows 7.




For Windows upgrade failure troubleshooting run:

a) upgrade failure info:
https://www.tenforums.com/attachment...ilure_info.bat

b) setupdiag:
https://learn.microsoft.com/en-us/wi...s/download.png

c) DM log collector:
BSOD - Posting Instructions

Open administrative command prompt and type or copy and paste:
sfc /scannow

Type:
ctrl + a
ctrl +c

Paste into this thread typing:
ctrl + v


Upgrade failure troubleshooting can take significant time and may fail.

If the user is able to backup important files they can clean install Windows 10 using gatherosstate.exe.

Clean Install Windows 10 Directly without having to Upgrade First

OK - I'll try doing an upgrade after I'va taken the display drivers a go and then start diagnosing it as per your details!

- - - Updated - - -

OK - tried to run the 'Upgrade Failure Info' batch file you had me run, but nothing is left on the desktop and something flashes up about "the term compress...is not recognized" when I try and run it?

SetupDiag logs here:
SetupDiag - Logs.zip

DM Logs here:
CUSTOMER-PC-16_03_2023__82341_66.zip

sfc scannow copy paste:

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 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 found corrupt files but was unable to fix some of th
em.
Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example
C:\Windows\Logs\CBS\CBS.log

C:\Windows\system32>

CBS Log from sfc scannow:
CBS.zip

1) Uninstall Superantispyware using the applicable uninstall tool:
SUPERAntiSpyware FAQ - How do I uninstall SUPERAntiSpyware?

2) Run the Avast uninstall tool:
Avast Removal Tool | Download Avast Clear | Avast
How to use the Avast Uninstall Tool | Avast

3) Update the progress with:
a) Before performing major upgrades it is best to make free or pay backup images and save the images to another disk drive or the cloud.

b) For Windows 7 it is also best to record the product ID.


4) Indicate whether the user is considering:
If the user is able to backup important files they can clean install Windows 10 using gatherosstate.exe.

Clean Install Windows 10 Directly without having to Upgrade First
Clean Install Windows 10 Directly without having to Upgrade First

Code:

Cannot repair member file [l:32{16}]"winsatencode.wmv" of Microsoft-Windows-WinSATMediaSamples, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2023-03-16 08:40:07, Info                  CSI    0000039e Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-winsatmediasamples_31bf3856ad364e35_6.1.7600.16385_none_0b34d0642122c1c4\winsatencode.wmv do not match actual file [l:32{16}]"winsatencode.wmv" :
  Found: {l:32 b:+1p3AfpjuS9cEwadxHCPE4rxiprmrYDMkpJcfrEId0Q=} Expected: {l:32 b:xw50XnyohqtqIhANFweVy8TeepsUO3fukfEQ8nHd5W8=}
2023-03-16 08:40:07, Info                  CSI    0000039f [SR] Cannot repair member file [l:32{16}]"winsatencode.wmv" of Microsoft-Windows-WinSATMediaSamples, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2023-03-16 08:40:07, Info                  CSI    000003a0 [SR] This component was referenced by [l:194{97}]"Microsoft-Windows-SampleContent-Music-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.MusicSamples"
2023-03-16 08:40:07, Info                  CSI    000003a1 Hashes for file member \??\C:\Windows\Performance\WinSAT\winsatencode.wmv do not match actual file [l:32{16}]"winsatencode.wmv" :
  Found: {l:32 b:+1p3AfpjuS9cEwadxHCPE4rxiprmrYDMkpJcfrEId0Q=} Expected: {l:32 b:xw50XnyohqtqIhANFweVy8TeepsUO3fukfEQ8nHd5W8=}
2023-03-16 08:40:08, Info                  CSI    000003a2 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-winsatmediasamples_31bf3856ad364e35_6.1.7600.16385_none_0b34d0642122c1c4\winsatencode.wmv do not match actual file [l:32{16}]"winsatencode.wmv" :
  Found: {l:32 b:+1p3AfpjuS9cEwadxHCPE4rxiprmrYDMkpJcfrEId0Q=} Expected: {l:32 b:xw50XnyohqtqIhANFweVy8TeepsUO3fukfEQ8nHd5W8=}
2023-03-16 08:40:08, Info                  CSI    000003a3 [SR] Could not reproject corrupted file [ml:520{260},l:66{33}]"\??\C:\Windows\Performance\WinSAT"\[l:32{16}]"winsatencode.wmv"; source file in store is also corrupted
2023-03-16 08:40:08, Info                  CSI    000003a4 Repair results create

Code:

SetupDiag was unable to match to any known failure signatures.

Code:

Event[54793]:
  Log Name: System
  Source: Microsoft-Windows-WindowsUpdateClient
  Date: 2023-03-15T09:37:40.061
  Event ID: 20
  Task: Windows Update Agent
  Level: Error
  Opcode: Installation
  Keyword: Installation,Failure
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: Customer-PC
  Description: 
Installation Failure: Windows failed to install the following update with error 0x80242016: 2020-01 Security Monthly Quality Rollup for Windows 7 for x64-based Systems (KB4534310).

Code:

Event[54105]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-Power
  Date: 2023-03-14T17:44:46.699
  Event ID: 41
  Task: N/A
  Level: Critical
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: Customer-PC
  Description: 
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Code:

Event[54136]:
  Log Name: System
  Source: EventLog
  Date: 2023-03-14T17:45:22.000
  Event ID: 6008
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Customer-PC
  Description: 
The previous system shutdown at 5:41:11 PM on ?14/?03/?2023 was unexpected.

Code:

0xC1900101, 0x20017