Win 7 Pro x64 to Win 10 Upgrade: Error (0x8007042B - 0x2000D)

[illyminati]

Hi there,

I have upgraded 3 of 4 workstations from Win 7 to Win 10 so far but the 4th machine is killing me with the migration error in the title. I have not built the machine, so I don't know the history of it.

Specs: as seen in my profile.

- The system disk has (Crucial MX500 SSD) has 230 GB free space.

- The system reserved partition has sufficient space of over 500 MB - BUT: used space is only about 30 MB and the partition has a drive letter (F. The other workstations had 90 MB used space and no drive letter for the system reserved partition.

--
The steps I went through so far after numerous failed installations (always at 27% progress):

- removed every peripheral but the mouse, keyboard and 1 display
- removed the second hard drive
- removed any third party antivirus
- removed any other software that is not essential for the workstation
- resized the system reserved partition from 100 to 600 MB
- ran AMD cleanup utility (there seemed to be another GPU installed before)
- updated the Nvidia Driver
- updated the Crucial Firmware
- ran system file check in safe mode (output: Windows Resource Protection found corrupt files but was unable to fix some of them)
- ran DISM but I guess /checkhealth and /restorehealth are no Win 7 features
- resetted windows update components and renamed SoftwareDistribution / Catroot2 / Migration folders

Upgrade is executed with MediaCreationTool 1909

SURT and SetupDiag logs are attached. I can't find a solution for the errors stated in the CheckSUR log or any Visual C++ 2005 SP1 Redistributable Package that could take me a step further.

Where am I? What is time?

Thanks in advance for your help and suggestions.

 

[Megahertz07]

There is no SURT or SetupDiag logs attachments

Do the basic first. Open a CMD window as administrator and type:
chkdsk c: /f
It will say the disk is in use and if you want to schedule to next start = Yes
Restart

Back to windows, open a CMD window as administrator and type:
sfc /scannow

Report

 

[illyminati]

Hi Megahertz07,

first of all, thanks for your reply.

I remember uploading a .rar file but anyway, I followed your steps and the logs should be attached now.

 

[Megahertz07]

CheckSUR Found 11 errors and SetupDiag reports fatal migration plug-in failure.

Did you run chkdsk c: /f and sfc /scannow as instructed?

 

[illyminati]

Yes, I followed your instructions and ran chkdsk, restarted after the prompt and ran sfc. The output was still "Windows Resource Protection found corrupt files but was unable to fix some of them". The logs from 01/20/2020 are listed in the CBS.log (attached in the .rar).

I have read the CheckSUR and SetupDiag logs myself and after a deep search a Visual C++ 2005 SP1 Redistributable Package could be the solution but I am not sure if this is the case and if so, which redistributable is the right one.

 

[Megahertz07]

The CBS.log has no errors.

To the "upgrde", did you run Setup.exe on the USB drive or did you extracted the iso files to a folder and ran Setup.exe ?

 

[illyminati]

I tried to upgrade with MediaCreationTool 1909 from the desktop (in place installation) like I did on the other 3 workstations.

 

[Megahertz07]

All updates that you launch from running Windows is an in place installation. You can install downloading or download and then install. I prefer download and then install as you keep the installation disk
Lets try this.
- Create a USB boot able disk. You need a USB flash disk of 8G. It's not only for the installation but also for maintenance.
- If you don't have a a USB flash disk of 8G, download the iso, extract all files and folders to a folder and run setup (if you don't have, use 7zip) .

 

[illyminati]

Thanks for the suggestion. I'll give this a try and keep you updated.

 

[illyminati]

Megahertz07

I tried two methods via USB flash:

1. Install with drivers etc. updates
2. Install without drivers etc. updates

Both methods were unsuccessfull and the system was reverted to Windows 7 with the same migration error.

By the way, a clean install like the solution in this thread is not an option.