Win7 Ultimate SP1 to Win10 upgrade "Error: 0x8007001F-0x20006", SURT shows missing KB2952664 MUMs

C

CoffinDodger

Member
Joined
Jan 20, 2020
Posts
19
Hi good folks,

Another one of these, I've come here after 12 hours of attempts over the weekend to upgrade my Win7 Ultimate to Win 10, following many of the suggestions from this site and the googleverse.

The Windows 10 upgrade eventually rolls back with:

"Error: 0x8007001F-0x20006 the installation failed in the safe_os phase with an error during replicate oc operation"

I've removed Microsoft Security Essentials AV, and NordVPN, and USB devices like webcams and external storage.

The Win10 update is written to USB stick using the app MediaCreationTool1909.exe, I run this in place from within Windows to get the upgrade started. I got the same results running a local upgrade from MediaCreationTool1909 - however this just downloads the entire Win10 every single time, which takes forever on my lowly broadband. The USB stick at least progresses a bit faster due to less download.

PC build is home built:
ASUS MB with integrated SoundMax HD Audio
Integrated Marvell 61xx RAID Controller
8GB ram
Intel Q6700 CPU
NVIDIA GeForce GTS 450
Fresco Logic xHCI (USB3) Controller FL1100 Series

The log files below indicate missing parts from a single KB update. I have tried removing and reinstalling KB2952664, which has not changed the result.


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

SFC Scan = "Windows Resource Protection did not find any integrity violations"

------------------------------------------------
SFCFix version 3.0.2.1 by niemiro.
Start time: 2020-01-18 23:24:03.458
Microsoft Windows 7 Service Pack 1 - amd64
Not using a script file.

AutoAnalysis::
SUMMARY: Some corruptions could not be fixed automatically. Seek advice from helper or sysnative.com.
CBS & SFC total detected corruption count: 0
CBS & SFC total unimportant corruption count: 0
CBS & SFC total fixed corruption count: 0
SURT total detected corruption count: 4
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 0 datablocks.
Finish time: 2020-01-18 23:27:16.010
----------------------EOF-----------------------


I got the SURT version Windows6.1-KB947821-v34-x64.msu

The CBS log folder is compressed on a google drive share. It's 500MB uncompressed, 100MB compressed.

SURT share - Google Drive



The CheckSUR.log follows. I note that the missing files it lists have "amd64" in their name, but I have an Intel Q6700 CPU in the machine???


=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2020-01-18 22:20

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs

Checking Package Watchlist

Checking Component Watchlist

Checking Packages
(f) CBS MUM Missing 0x00000002 servicing\Packages\Package_1_for_KB2952664~31bf3856ad364e35~amd64~~6.1.9.6.mum
(f) CBS MUM Missing 0x00000002 servicing\Packages\Package_3_for_KB2952664~31bf3856ad364e35~amd64~~6.1.9.6.mum
(f) CBS MUM Missing 0x00000002 servicing\Packages\Package_for_KB2952664_SP1~31bf3856ad364e35~amd64~~6.1.9.6.mum
(f) CBS MUM Missing 0x00000002 servicing\Packages\Package_for_KB2952664~31bf3856ad364e35~amd64~~6.1.9.6.mum

Checking Component Store

Summary:
Seconds executed: 1139
Found 4 errors
CBS MUM Missing Total count: 4

Unavailable repair files:
servicing\packages\Package_1_for_KB2952664~31bf3856ad364e35~amd64~~6.1.9.6.mum
servicing\packages\Package_3_for_KB2952664~31bf3856ad364e35~amd64~~6.1.9.6.mum
servicing\packages\Package_for_KB2952664_SP1~31bf3856ad364e35~amd64~~6.1.9.6.mum
servicing\packages\Package_for_KB2952664~31bf3856ad364e35~amd64~~6.1.9.6.mum
servicing\packages\Package_1_for_KB2952664~31bf3856ad364e35~amd64~~6.1.9.6.cat
servicing\packages\Package_3_for_KB2952664~31bf3856ad364e35~amd64~~6.1.9.6.cat
servicing\packages\Package_for_KB2952664_SP1~31bf3856ad364e35~amd64~~6.1.9.6.cat
servicing\packages\Package_for_KB2952664~31bf3856ad364e35~amd64~~6.1.9.6.cat
 
Hi!

FRST Registry Search
1. Click your Start button and type in cmd.
2.After you find the Command Prompt, right click on it and select Run as Administrator.
3. Copy and paste the following into the Command Prompt:

reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS

4. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
5. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
6. Copy and paste KB2952664 into the Search box and click the Search Registry button.
7. When the scan is complete a notepad window will open with the results. Please attach this to your next reply. It is saved on your desktop named SearchReg.txt.
 
Thank you. You caught me just about to go away until tomorrow night. However I'd already downloaded FRST64 in anticipation of a reply, so this was quick to run.

Hope the attached will help - I'll be able to pick up responses over the weekend, just won't have access to the troubled machine till late Saturday.
 

Attachments

Step#1 - FRST Fix
NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system
1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
2. Download the attached fixlist.txt and save it to the Desktop.
Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
4. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.
 

Attachments

We've made progress, but got to the next hurdle.

After a looooong timeout on one of the reboots, it eventually rolled back again.

0xC1900101 - 0x30018
The installation failed in the FIRST_BOOT phase with an error during SYSPREP_SPECIALIZE operation.

I've just started to do some of my own research, but I won't change anythign until I've heard back from you.

Thanks.
 
Please do the following:

Step#1 - FRST Scan

1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
2. Right-click FRST64.exe and click Run as Administrator to run it as administrator. When the tool opens, click Yes to disclaimer.
3. Please ensure you place a check mark in the Addition.txt check box at the bottom of the form before running (if not already checked).
4. Press Scan button.
5. It will produce a log called FRST.txt in the same directory the tool is run from (which should now be the desktop)
6. Please attach the log back here.
7. Another log (Addition.txt - also located in the same directory as FRST64.exe) will be generated Please also attach that along with the FRST.txt in your reply.


Thanks.
 
Please uninstall this and disconnect the related devices from the machine if possible.

Broadcom 802.11 Wireless LAN Adapter
CanoScan LiDE 110 Scanner Driver
Registry First Aid 10
Samsung CLP-410 Series (and all of the utilities)
Secure Print@Home

Also, please do the following:

Step#1 - FRST Fix
NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system
1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
2. Download the attached fixlist.txt and save it to the Desktop.
Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
4. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.
 

Attachments

Workign on it. The last of the uninstalls has taken some finding. It appears to be a user-local install of some coupon software which is not in add/remove progs for admin. However I've found it now so should be rid of it soon
 
These are unistalled:

Broadcom 802.11 Wireless LAN Adapter
CanoScan LiDE 110 Scanner Driver
Registry First Aid 10
Samsung CLP-410 Series (and all of the utilities)

This is not uninstalled:

Secure Print@Home

- It was installed locally for one user under C:\Users\[username]\AppData\Roaming\Valassis
- There is no entry in Add / Remove programs for Admin or the user. There is no start menu shortcut or uninstall exe on disk.
- The installed version is 3.7.1394.0, which is old (folder date is 07/02/2015)
- Online advice for manual removal does not cover versions this old.

I have run the fix script. Much of the time was spent deleteing user temporary files for the two main users of this manchin
A reboot was asked for and completed.

Fixlog attached.
 

Attachments

Thank you for the info:

SFCFixScript.txt

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the attached file, SFCFixScript.txt, and save this to your Desktop. Ensure that this file is named SFCFixScript.txt - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFixScript.txt.
  5. Drag the file SFCFixScript.txt onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a log should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.[/list]
 

Attachments

Here's the output.

Note that numbers 12 & 13 were some copies I took after last night's attempt to install. I left the originals in place when I made the copies.

Code: 
SFCFix version 3.0.2.1 by niemiro.
Start time: 2020-01-26 18:03:05.115
Microsoft Windows 7 Service Pack 1 - amd64
Using .txt script file at C:\_DATA\Downloads\SFCFIX\SFCFixScript.txt [0]




FileScan::
WARNING: There may be further unlisted copies of some of these files on the system.

[0: 1] C:\Windows\setupact.log
File is untraceable.
 Found: lD261ws/31kyGdMjVVgcO9C10oeyoE4bsb08R+EVCXU=
 Version number not available.
Trace not available.



[1: 1] C:\Windows\setuperr.log
File is untraceable.
 Found: Nk+a1Rvn0fUZHW6gGuDQIACr/Gs1uqdpSH8Dj3CLQwo=
 Version number not available.
Trace not available.



[2: 1] C:\Windows\Panther\setupact.log
File is untraceable.
 Found: lyY8PT6R96DaNQqBIW7BxKr1vJBM5roea+3Z2BY0Xfo=
 Version number not available.
Trace not available.



[3: 1] C:\Windows\Panther\setuperr.log
File is untraceable.
 Found: tqNmmD3jd/TK4SZhNOEpWXq5XDxNiQXsqFH2wy8mCIw=
 Version number not available.
Trace not available.



[4: 1] C:\Windows\Panther\NewOs\Panther\setupact.log
File is untraceable.
 Found: O8RFtN3EGwxl2PxzA+Rqv132r8Mso3gGhYE7LzYC5bo=
 Version number not available.
Trace not available.



[5: 1] C:\Windows\Panther\NewOs\Panther\setuperr.log
File is untraceable.
 Found: IGsX9TpmYFJyNs7XlPrNpiUphoRYBfPGu2Rs4y7KpDQ=
 Version number not available.
Trace not available.



[6: 1] C:\Windows\Panther\NewOs\Panther\UnattendGC\setupact.log
File is untraceable.
 Found: GFVhUD9uJQpETqaurdCxHKKn7Jc2C12gRELnWCsVLfY=
 Version number not available.
Trace not available.



[7: 1] C:\Windows\Panther\NewOs\Panther\UnattendGC\setuperr.log
File is untraceable.
 Found: 47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZG3hSuFU=
 Version number not available.
Trace not available.



[8: 1] C:\Windows\Panther\NewOs\Rollback\setupact.log
File is untraceable.
 Found: Ynxb9N6G9TjbATseNSq+E5OoM3cz9i3BjInDckLhckk=
 Version number not available.
Trace not available.



[9: 1] C:\Windows\Panther\NewOs\Rollback\setuperr.log
File is untraceable.
 Found: 47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZG3hSuFU=
 Version number not available.
Trace not available.



[10: 1] C:\$WINDOWS.~BT\Sources\Rollback\setuperr.log
File is untraceable.
 Found: 47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZG3hSuFU=
 Version number not available.
Trace not available.



[11: 1] C:\$WINDOWS.~BT\Sources\Rollback\setupact.log
File is untraceable.
 Found: UHYtpAv4quTrFdWqgh+fqDdX9fixR0J0cw6Dr5ZaJ2s=
 Version number not available.
Trace not available.



[12: 1] C:\_DATA\Downloads\attempt 2020-01-25a\setuperr.log
File is untraceable.
 Found: IGsX9TpmYFJyNs7XlPrNpiUphoRYBfPGu2Rs4y7KpDQ=
 Version number not available.
Trace not available.



[13: 1] C:\_DATA\Downloads\attempt 2020-01-25a\setupact.log
File is untraceable.
 Found: Ynxb9N6G9TjbATseNSq+E5OoM3cz9i3BjInDckLhckk=
 Version number not available.
Trace not available.
FileScan:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2020-01-26 18:03:49.481
Script hash: pXg+N9RsOFhulAFuO/lhUn3Em2ka7ErzNa7iX3SlHuo=
----------------------EOF-----------------------
 
I zipped the pair of files from each folder, named the zips after the folder they came from, then put these into a master zip. Hope that's not too complicated.
 

Attachments

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