[SOLVED] Upgrade from Windows 7 to Windows 10 fails with 0x8007001F - 0x20006 code

G

greenchili2021

Member
Joined
Jul 5, 2021
Posts
9
Hello,

I've been trying to upgrade my Windows 7 Pro to the Windows 10 with Media Creation Tool. I need to keep my aps and settings so I don't want to make a clean install.
Unfortunately every time I try to upgrade it fails and rolls back with the following error: "0x8007001F - 0x20006 The installation was not successful. Error in Phase SAFE_OS during REPLICATE_OC."

I've spend plenty of time searching the net and trying all fixes I could find like deleting unnecessary software and files, starting Windows "clean", turning off my antivirus software, remove all old USB devices, run a disc clean up an so on. I also tried running the upgrade from USB and DVD but it ended the same. Thank you in advance!

SFC scan found an problem and SFCFix was unable to fix the corrupt files. SFCFix log is as follows and CBS log is attached:

SFCFix version 3.0.2.1 by niemiro.
Start time: 2021-07-05 17:07:35.621
Microsoft Windows 7 Service Pack 1 - amd64
Not using a script file.




AutoAnalysis::
CORRUPT: C:\Windows\winsxs\amd64_mscorlib_b77a5c561934e089_6.1.7601.24424_none_3d9909fc83291222\mscorlib.dll
CORRUPT: C:\Windows\winsxs\x86_mscorlib_b77a5c561934e089_6.1.7601.24424_none_854640d397a53b28\mscorlib.dll


SUMMARY: Some corruptions could not be fixed automatically. Seek advice from helper or sysnative.com.
CBS & SFC total detected corruption count: 2
CBS & SFC total unimportant corruption count: 0
CBS & SFC total fixed corruption count: 0
SURT total detected corruption count: 0
SURT total unimportant corruption count: 0
SURT total fixed corruption count: 0
AutoAnalysis:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 1 datablocks.
Finish time: 2021-07-05 17:09:15.219
----------------------EOF-----------------------
 

Attachments

Hello and welcome,

Follow the instructions below please.

WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.
  • Download the attachment SFCFix.zip and save it on your desktop.
  • Save any work you have open, and close all programs.
  • Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
    1p8eDnI.gif
  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt.
  • Open the file, then copy and paste its content in your next reply.
 

Attachments

PeterJ, THank you for the quick response. It appears the script was able to successfuly fix the 2 errors with mscorlib. Please see the SFCFix text below. Should I now go back through and run SFCScan and if it's clean, run the Sytem Update Readiness Tool?

Thanks,
Brian

SFCFix version 3.0.2.1 by niemiro.
Start time: 2021-07-06 17:28:43.824
Microsoft Windows 7 Service Pack 1 - amd64
Using .zip script file at C:\Users\Brian\Desktop\SFCFix.zip [0]




PowerCopy::
Successfully took permissions for file or folder C:\Windows\winsxs\x86_mscorlib_b77a5c561934e089_6.1.7601.24424_none_854640d397a53b28\mscorlib.dll
Successfully took permissions for file or folder C:\Windows\winsxs\amd64_mscorlib_b77a5c561934e089_6.1.7601.24424_none_3d9909fc83291222

Successfully copied file C:\Users\Brian\AppData\Local\niemiro\Archive\x86_mscorlib_b77a5c561934e089_6.1.7601.24424_none_854640d397a53b28\mscorlib.dll to C:\Windows\winsxs\x86_mscorlib_b77a5c561934e089_6.1.7601.24424_none_854640d397a53b28\mscorlib.dll.
Successfully copied file C:\Users\Brian\AppData\Local\niemiro\Archive\amd64_mscorlib_b77a5c561934e089_6.1.7601.24424_none_3d9909fc83291222\mscorlib.dll to C:\Windows\winsxs\amd64_mscorlib_b77a5c561934e089_6.1.7601.24424_none_3d9909fc83291222\mscorlib.dll.

Successfully restored ownership for C:\Windows\winsxs\x86_mscorlib_b77a5c561934e089_6.1.7601.24424_none_854640d397a53b28\mscorlib.dll
Successfully restored permissions on C:\Windows\winsxs\x86_mscorlib_b77a5c561934e089_6.1.7601.24424_none_854640d397a53b28\mscorlib.dll
Successfully restored ownership for C:\Windows\winsxs\amd64_mscorlib_b77a5c561934e089_6.1.7601.24424_none_3d9909fc83291222
Successfully restored permissions on C:\Windows\winsxs\amd64_mscorlib_b77a5c561934e089_6.1.7601.24424_none_3d9909fc83291222
PowerCopy:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 3 datablocks.
Finish time: 2021-07-06 17:28:44.503
Script hash: nf/XhbDe5oe0Q/5FByPX7RfV5gyfaNZdEZZ0dewN6ek=
----------------------EOF-----------------------

 
Looks good. Please run the System Update Readiness Tool only.
On completion, attach the file C:\Windows\Logs\CBS\CheckSUR.log to your next reply.
 
Step 1:
WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.
  • Download the attachment SFCFix.zip and save it on your desktop.
  • Save any work you have open, and close all programs.
  • Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
    1p8eDnI.gif
  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt.
  • Attach that file to your next reply.

Step 2:
Start the System Update Readiness Tool (SURT) again.
On completion, attach the logfile C:\Windows\Logs\CBS\CheckSUR.log to your next reply.
 

Attachments

I'm not sure if we're getting closer or not!
Click to expand...
Yes we are.

Step 1:
WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.
  • Download the attachment SFCFix.zip and save it on your desktop.
  • Save any work you have open, and close all programs.
  • Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
    1p8eDnI.gif
  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt.
  • Attach that file to your next reply.

Step 2:
Start the System Update Readiness Tool (SURT) again.
On completion, attach the logfile C:\Windows\Logs\CBS\CheckSUR.log to your next reply.
 

Attachments

I downloaded and ran "checksurpackage_f3f05923c10e732ff623bbb88cbdb4846b657a7f.exe". The program asked me if I wanted run this file, I clicked yes and then... nothing. I get a quick flash that looks like it ran, it was too fast to tell. The ChuckSur log was not updated. Not sure what the issue might be. I dowloaded the SURT that I used following the link in your "Windows Update Forum Posting Instructions". The file I was using is Windows6.1-KB947821-v12-x64. The newest files that the Update Catalog had for the SURT were 2014. ¯\_(ツ)_/¯
 
PeterJ, I worked on the computer and cleaned up a couple of errors showing in the CBS.log. The SFC scan is now clean, there are no errors in the CBS.log and the SURT shows no errors either. Should I be good to attempt another Windows 10 upgrade? Or is ther something else I need to do before I attempt the upgrade? Thank you
 
I worked on the computer and cleaned up a couple of errors showing in the CBS.log. The SFC scan is now clean, there are no errors in the CBS.log and the SURT shows no errors either.
Click to expand...
Please tell us what you did in more detail.
 
Really only two things. One, CBS.log had an error regarding the Servicing Stack update file. Boiled down, I had an old version of the Servicing Stack Update which was causing the errors. I downloaded and ran the latest Servicing Stack Update (Windows6.1-KB947821-v12-x64) and this ended up clearing this error. CBS.log no longer contains any error messages.

The second thing I did was regarding an error in the CheckSur log. I had the following message:

Checking Package Manifests and Catalogs
(f) CBS MUM Corrupt 0x00000000 servicing\Packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~11.2.9412.0.mum Expected file name Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~neutral~~11.2.9412.0.mum does not match the actual file name
(f) CBS MUM Corrupt 0x00000000 servicing\Packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~11.2.9412.0.mum Expected file name Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~neutral~~11.2.9412.0.mum does not match the actual file name


Checking Package Watchlist


Checking Component Watchlist


Checking Packages


Checking Component Store


Summary:
Seconds executed: 186
Found 2 errors
CBS MUM Corrupt Total count: 2


Unavailable repair files:
servicing\packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~11.2.9412.0.mum
servicing\packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~11.2.9412.0.mum
servicing\packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~11.2.9412.0.cat
servicing\packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~11.2.9412.0.cat

I found a similar case that had the exact same message: LINK Looking at the proposed solution. I knew I could try the solution without any harm to my computer as it was only adding the packages to the CheckSur/Packages folder. SURT would only use the files if they were need. I reran SURT and it showed that the two packages were repaired with no other errors. I've rerun the SFC scan and it also shows no errors. CBS.log continues to show no errors.
 
Thanks for the feedback.
Try to upgrade this machine and report the result.
 
As a final update, I'd like you to know that the Windows 10 upgrade proceeded successfully and now I get the "fun" of setting up the OS the way I like it to be. Thank you for all your help. I plan on making a donation to the forum.
 
Your welcome. Thanks in advance for the donation.

Take care.
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top