Update from Win-7 pro to Win-10 pro fails with 0x8007042B-0x2000D

S

SomervilleTom

Contributor
Joined
Jan 7, 2020
Posts
21
First, let me say how impressed I am with the advice I've seen on this forum. I've already made a small donation and anticipate making at least one more.

I have been attempting to update my venerable Win-7 pro system to Win-10 pro in anticipation of the 14-January sunset date. I've been stuck at the same error since last Friday. The updater runs and all seems well until I get about 30% of the way through the Win-10 migration phase (I think that's what it's doing). At that point, the system reboots and says it is undoing its changes. It reboots to Win-7 pro. I then have to reboot it one more time to turn the sound card back on. On the second boot, it shows a complaint that says:
We couldn't install Windows 10
We've set your PC back to the way it was right before you started installing Windows 10.

0x8007042B-0x2000D
The installation failed in the SAFE_OS phase with an error during MIGRATE_DATA operation
Click to expand...

Sadly, I found this forum after several days of failed attempts to get past this issue. I followed the recipe provided in your tutorial and attached the resulting CBS.zip. There is some chance that some of the corruption it found is the result of my own failed attempts to clean up the system. I have backups (created by Acronis TrueImage) if those will help.

In case it might help, I have attached "setupact.log", the summary log from Panther (the windows update tool) and "SetupDiagResults.log", the sumamry log from SetupDiag.exe (the Microsoft tool that helps diagnose issues). I have the details of each, but I haven't uploaded them because they are quite large.

When I started all this, the complaint in "setupact.log" was a failure attempting to migrate "Comodo Internet Security" (cmdagent.exe). This was detritus from removing Comodo AV years ago. I've been using MalwareBytes premium for some time now. Since the path to that executable didn't exist, I wasn't surprised that it failed. I spent days attempting to find and remove references to Comodo from the registry, file system, and so on. None of those attempts had any effect at all until late yesterday.

The last change I made -- using "FRST64.exe", which I found here -- finally removed the "Comodo" complaints. Unfortunately, the upgrade still fails in the same place. As you can see from the two log files, it now correctly identifies MalwareBytes as my AV. The path that it is attempting to migrate exists, and so something else is causing this failure.

That's about all I can think of to help get you started.

Thanks in advance for your help!
 

Attachments

Last edited:
Hi!

Please provide me with FRST.txt and Addition.txt logs and also 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

Because of the time zone, this may have to wait until tomorrow -- I've got another job running that may take awhile before I can start this.

I appreciate your immediate response! I'll update this as soon as I have something to report.
 
I ran the "scan" first, then the "fix", attached are the three resulting files.

I also ran checkSur a few times (Windows6.1-KB947821-v34-x64.msu). Earlier this afternoon, it asked for a total of 8 missing .msu files. I downloaded those from Microsoft and put them in the appointed places (C:\windows\CheckSur\packages and C:\Windows\Temp\CheckSUR\packages). It continues to complain about 6 missing .mum and .cat packages. I've attached the most recent "CheckSUR.log".

It's 12:25AM here, so I'm going to start one more update pass to see what happens. I'll pass along any news.
 

Attachments

Please do the following:

SFCFix Script

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 file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - 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 SFCFix.zip.
  5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.

Afterwards, run System Update Readiness Tool again and attach CheckSUR.log.
 

Attachments

The update pass I attempted failed again in a similar way. The summary logs are attached as before.

Here's what I've done since then:

1. Found a copy of the apparently missing "setupmig.dll" and put it in a newly-created ".../drivers/migration/" directory. I hope this doesn't hurt, it's easy to remove if so.
2. Ran "sfc /scannow". It found some issues that it says it repaired, and I rebooted. Interestingly, I'm getting a permissions/file-not-found complaint when I attempt to zip .../Logs/CBS.
3. Found and followed your directions from above. It looks to me as though the zipfile successfully restored the missing packages.
4. Ran a FRST.exe scan and harvested frst.txt and additional.txt (attached).

I'm going to post this (with its attachments) and then attempt another upgrade pass. I'll update this thread after that attempt finishes.

SFXFix.txt contents:
Code: 
SFCFix version 3.0.2.1 by niemiro.
Start time: 2020-01-09 11:19:42.146
Microsoft Windows 7 Service Pack 1 - amd64
Using .zip script file at C:\Users\Thomas\Desktop\SFCFix.zip [0]




PowerCopy::
Successfully took permissions for file or folder C:\Windows\Temp\CheckSur\Servicing\Packages

Successfully copied file C:\Users\Thomas\AppData\Local\niemiro\Archive\Packages\Package_3_for_KB3109094~31bf3856ad364e35~amd64~~6.1.1.1.cat to C:\Windows\Temp\CheckSur\Servicing\Packages\Package_3_for_KB3109094~31bf3856ad364e35~amd64~~6.1.1.1.cat.
Successfully copied file C:\Users\Thomas\AppData\Local\niemiro\Archive\Packages\Package_3_for_KB3109094~31bf3856ad364e35~amd64~~6.1.1.1.mum to C:\Windows\Temp\CheckSur\Servicing\Packages\Package_3_for_KB3109094~31bf3856ad364e35~amd64~~6.1.1.1.mum.
Successfully copied file C:\Users\Thomas\AppData\Local\niemiro\Archive\Packages\Package_3_for_KB3124280~31bf3856ad364e35~amd64~~6.1.1.1.cat to C:\Windows\Temp\CheckSur\Servicing\Packages\Package_3_for_KB3124280~31bf3856ad364e35~amd64~~6.1.1.1.cat.
Successfully copied file C:\Users\Thomas\AppData\Local\niemiro\Archive\Packages\Package_3_for_KB3124280~31bf3856ad364e35~amd64~~6.1.1.1.mum to C:\Windows\Temp\CheckSur\Servicing\Packages\Package_3_for_KB3124280~31bf3856ad364e35~amd64~~6.1.1.1.mum.
Successfully copied file C:\Users\Thomas\AppData\Local\niemiro\Archive\Packages\Package_3_for_KB3140735~31bf3856ad364e35~amd64~~6.1.1.0.cat to C:\Windows\Temp\CheckSur\Servicing\Packages\Package_3_for_KB3140735~31bf3856ad364e35~amd64~~6.1.1.0.cat.
Successfully copied file C:\Users\Thomas\AppData\Local\niemiro\Archive\Packages\Package_3_for_KB3140735~31bf3856ad364e35~amd64~~6.1.1.0.mum to C:\Windows\Temp\CheckSur\Servicing\Packages\Package_3_for_KB3140735~31bf3856ad364e35~amd64~~6.1.1.0.mum.

Successfully restored ownership for C:\Windows\Temp\CheckSur\Servicing\Packages
Successfully restored permissions on C:\Windows\Temp\CheckSur\Servicing\Packages
PowerCopy:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 1 datablocks.
Finish time: 2020-01-09 11:19:43.440
Script hash: n5dW+UV0UF6SK7iegThNkXK47PBdHOs8q/shcG8fEnQ=
----------------------EOF-----------------------
 

Attachments

Hi!

Let's see what's wrong with SFC:

SFC Scan


  1. Click on the Start button and in the search box, type Command Prompt
  2. When you see Command Prompt on the list, right-click on it and select Run as administrator
  3. When command prompt opens, copy and paste the following commands into it, press enter after each

    sfc /scannow

    Wait for this to finish before you continue

    copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
  4. This will create a file, cbs.txt on your Desktop. Please attach this to your next post.

If you can't get the log this way, please go to: C:\Windows\Logs\CBS, copy it to your Desktop and then attach CBS.log from inside of the folder.
 
Clean run of sfc ... "Windows Resource Protection did not find any integrity violations ".

cbs.txt is attached.
 

Attachments

Please do the following and zip up all the files listed by the script:

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

I'm not sure what files you'd like me to zip, there are several copies of each from both panther and setupDiag.

Here is SFCFix.txt:
Code: 
SFCFix version 3.0.2.1 by niemiro.
Start time: 2020-01-09 14:53:04.102
Microsoft Windows 7 Service Pack 1 - amd64
Using .txt script file at C:\Users\Thomas\Desktop\SFCFixScript.txt [0]




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

[0: 1] C:\Windows\setuperr.log
File is untraceable.
 Found: +yaS59xhKv27SMMLlF0rendkQMeChmaMv79M1IomNbs=
 Version number not available.
Trace not available.



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



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



[3: 1] C:\Windows\Panther\NewOs\Panther\setupact.log
File is untraceable.
 Found: 8mDvHFPqz4e8Emaz9UliwttzgtesT/Osxc6YY/c9sXg=
 Version number not available.
Trace not available.



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



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



[6: 1] C:\Windows\Panther\NewOs\Rollback\setuperr.log
File is untraceable.
 Found: C9eQdHNQ3+m1eKWf6jh+NgEL4UDVZhG26ZI1sd5oHBI=
 Version number not available.
Trace not available.



[7: 1] C:\$WINDOWS.~BT\Sources\Rollback\setuperr.log
File is untraceable.
 Found: kcAg2WRG1mYNM5WGsSzMG3FSwVr4E87xw7lDrMi/zQs=
 Version number not available.
Trace not available.



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



[9: 1] C:\Windows\setupact.log
File is untraceable.
 Found: ywe+eilWCAm1l7tG5q89MnhjSovHEqKz1M9SEAG/Wl4=
 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 1 datablocks.
Finish time: 2020-01-09 14:53:16.684
Script hash: pXg+N9RsOFhulAFuO/lhUn3Em2ka7ErzNa7iX3SlHuo=
----------------------EOF-----------------------
 
Got it.

I keep the results of SetupDiag.exe in a different directory tree (outside /windows), do you want those too?
 
Okay: I would uninstall the following:

Linksys Dual Band Wireless-AC USB Adapter
SAMSUNG USB Driver for Mobile Phones
Samsung Kies
Samsung Data Migration
marvell 91xx driver
Canon MF Toolbox 4.9.1.1.mf17
Canon MF210 Series
Logitech Options
Logitech Unifying Software 2.50
Majestic MJC8Q300


Check for updates for your chipset drivers.

If it still fails, I would recommend rebuilding the BCD.
 
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