[SOLVED] Win7 to 10 Upgrade crashes with Error Code: 0x80070003 - 0x2000D

Please try the following.

1. Download the Media Creation Tool to your desktop. Go ahead and run this. Note: Click the Download tool now button when you are at this link.
2. Accept the license agreement
3. Keep the default which is to Upgrade your PC and click Next.
4. Go ahead and run this through and report the result.

Doing it this way will keep all your data and programs intact. As always though, make sure you have a backup of any critical data in case something unexpected happens.
 
Unfortunately, the outcome was the same as the previous times... Crash even before the 1st reboot (I attach the CBS file since you asked for it the other time, perhaps it can be useful).
 

Attachments

The cbs.log doesn't contain an error.

Provide a screenshot or photo of the error you get.
When available attach the following files also.
C:\$WINDOWS.~BT\Sources\Panther\SetupAct.log
C:\$WINDOWS.~BT\Sources\Panther\SetupErr.log
C:\WINDOWS\setupact.log
C:\WINDOWS\setuperr.log
 
Here you go, the error message is basically useless just a fail notification. I have attached the files as well (the smaller ones are from the Windows dir).
 

Attachments

How is the machine connected to the internet, wired or wireless ?
Is the machine connected to the internet when you try to upgrade ?
Did you removed/disconnected all unneeded hardware when you try to upgrade ?

Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine.
  1. Download the attachment fixlist.txt and save it to your desktop.
  2. Right-click on FRST64.exe and select "Run as administrator".
  3. Press the Fix button.
  4. The tool will now process fixlist.txt.
  5. 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.
  6. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
  7. Note: Attach the file Fixlog.txt to a private message as it contains sensitive information!
 

Attachments

The computer is connected via LAN to the net but I have a firewall that checks the programs that want to connect and prompts me for permission. I never got a pop-up during the update process though, usually, it's able to download updates and whatever it needs.
As for the fixlist.txt file, it wasnt attache to the previous message. :)
 
As for the fixlist.txt file, it wasnt attache to the previous message. :)
Click to expand...
Oops, I fixed that.

The computer is connected via LAN to the net but I have a firewall that checks the programs that want to connect and prompts me for permission.
Click to expand...
Which firewall ?
Any improvement if you disable that firewall before doing the upgrade ?
 
The firewall is called "Windows 8 Firewall Control". I think I run the update without it on one of the first times I did it but might retry it again.
Just run the fixlist-tool, will attach the log on a PM, it's kinda big I hope it fits lol
 
So I just tried an upgrade process after closing the Firewall process, unfortunately it had the same outcome :(
 
Uninstall AVG TuneUp.

Attach the file C:\windows\logs\mosetup\bluebox.log to your next reply.
 
Step 1:
Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine.
  1. Download the attachment fixlist.txt and save it to your desktop.
  2. Right-click on FRST64.exe and select "Run as administrator".
  3. Press the Fix button.
  4. The tool will now process fixlist.txt.
  5. 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.
  6. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
  7. Attach the logfile Fixlog.txt to your next reply.

Step 2:
Perform the instructions in message #42 again and report the result.
 

Attachments

Step 1:
Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine.
  1. Download the attachment fixlist.txt and save it to your desktop.
  2. Right-click on FRST64.exe and select "Run as administrator".
  3. Press the Fix button.
  4. The tool will now process fixlist.txt.
  5. 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.
  6. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
  7. Attach the logfile Fixlog.txt to your next reply.

Step 2:
Perform the instructions in message #42 again and report the result.
 

Attachments

Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine.
  1. Download the attachment fixlist.txt and save it to your desktop.
  2. Right-click on FRST64.exe and select "Run as administrator".
  3. Press the Fix button.
  4. The tool will now process fixlist.txt.
  5. 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.
  6. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
  7. Attach the logfile Fixlog.txt to your next reply.
 

Attachments

Let's rename the C:\ESD folder as a backup and recreate a new ESD folder.

Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine.
  1. Download the attachment fixlist.txt and save it to your desktop.
  2. Right-click on FRST64.exe and select "Run as administrator".
  3. Press the Fix button.
  4. The tool will now process fixlist.txt.
  5. 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.
  6. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
  7. Attach the logfile Fixlog.txt to your next reply.
 

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