Difficulty upgrading to Windows 10 from Windows 7

[Sass10]

Dear team,
Am attempting to upgrade Windows 7 to Windows 10.

PC: Packard Bell imedia S2870 desktop
OS: Windows 7, 64-bit Home Premium
Ram: 8GB
HDD: 500GB, (split into separate C and D drives)

All attempts to date have failed. Error message continuously appearing at 90% of the second part of the install from a Windows 7 upgrade CD is "0xC1900101 - 0x4000D The installation failed at the SECOND_BOOT phase with an error during Migrate_Data operation". So from this, in simpler terms, can you advise next steps please? Have enough HDD space, have removed antivirus, what else is required. Is there not a program devised that can search for files/codes relating to the error message, then repair them? Or is this too simplistic? This whole thing is soo frustrating!!

Have come across scfexe. file as a possible solution to this additional error message - "...Windows Resource Protection unable to fix some of the files"... Any help appreciated for both these error messages .

 

[SIW2]

"...Windows Resource Protection unable to fix some of the files"

Have you got a list of those files? if it is just a few you could possibly replace them manually.

Otherwise, you could do a repair install of win7, then "upgrade" to win10.

Or you could install win10 onto a separate partition and do the gatherosstate dance to activate it.

Then you can transfer files and programs from win7 to win10 at your leisure.

 

[Bree]

Dear team,
Am attempting to upgrade Windows 7 to Windows 10....


...All attempts to date have failed. Error message ... "0xC1900101 - 0x4000D The installation failed at the SECOND_BOOT phase with an error during Migrate_Data operation".

Most likely cause, an incompatible driver.

Code
0xC1900101 - 0x4000D

Cause
A rollback occurred due to a driver configuration issue.
Installation failed during the second boot phase while attempting the MIGRATE_DATA operation.
This can occur because of incompatible drivers.

Mitigation
Check supplemental rollback logs for a setupmem.dmp file, or event logs for any unexpected reboots or errors.
Review the rollback log and determine the stop code.
The rollback log is located in the $Windows.~BT\Sources\Rollback folder. An example analysis is shown below. This example is not representative of all cases:

Info SP     Crash 0x0000007E detected
Info SP       Module name           :
Info SP       Bugcheck parameter 1  : 0xFFFFFFFFC0000005
Info SP       Bugcheck parameter 2  : 0xFFFFF8015BC0036A
Info SP       Bugcheck parameter 3  : 0xFFFFD000E5D23728
Info SP       Bugcheck parameter 4  : 0xFFFFD000E5D22F40
Info SP     Cannot recover the system.
Info SP     Rollback: Showing splash window with restoring text: Restoring your previous version of Windows.

Typically, there is a dump file for the crash to analyze. If you are not equipped to debug the dump, then attempt the following basic troubleshooting procedures:

• Make sure you have enough disk space.
• If a driver is identified in the bug check message, disable the driver or check with the manufacturer for driver updates.
• Try changing video adapters.
• Check with your hardware vendor for any BIOS updates.
• Disable BIOS memory options such as caching or shadowing.

Resolution procedures - Windows IT Pro - Windows Deployment | Microsoft Docs

 

[Sass10]

Have attached zip file of CBS log.

 

[Sass10]

Hello Bree,

Can you define in simple straightforward steps - how to:
1) Check supplemental rollback logs for a setupmem.dmp file, or event logs
2) Find rollback logs

 

[Bree]

Hello Bree,

Can you define in simple straightforward steps - how to....

No, not in simple terms I'm afraid. The guide I linked to is intended for IT professionals. The introduction and index page for the article is here:


Resolve Windows 10 upgrade errors - Windows IT Pro - Windows Deployment | Microsoft Docs


The section on Log Files is rated as 'Level 400: Advanced'. It does however tell you where to find all the log files, how they are structured and includes a worked example of analysis.

 

[torchwood]

Hi

The error in the CBS log is pointing at an Enterprise N hash mismatch, can you run this tool copy/paste the output

https://go.microsoft.com/fwlink/?LinkID=56062

Roy

 

[Sass10]

Hello Roy,

Output below:
Diagnostic Report (1.9.0027.0):
-----------------------------------------
Windows Validation Data-->

Validation Code: 0
Cached Online Validation Code: 0x0
Windows Product Key: *****-*****-WJ2H8-R6B6D-7QJB7
Windows Product Key Hash: ckKNc+BBPDWmo1LUlOkraNjlQ34=
Windows Product ID: 00359-OEM-8992687-00006
Windows Product ID Type: 2
Windows License Type: OEM SLP
Windows OS version: 6.1.7601.2.00010300.1.0.003
ID: {D7C69357-019D-4FF1-A41C-1ACAB90CDF0F}(3)
Is Admin: Yes
TestCab: 0x0
LegitcheckControl ActiveX: N/A, hr = 0x80070002
Signed By: N/A, hr = 0x80070002
Product Name: Windows 7 Home Premium
Architecture: 0x00000009
Build lab: 7601.win7sp1_ldr_escrow.200102-1707
TTS Error:
Validation Diagnostic:
Resolution Status: N/A

Vista WgaER Data-->
ThreatID(s): N/A, hr = 0x80070002
Version: N/A, hr = 0x80070002

Windows XP Notifications Data-->
Cached Result: N/A, hr = 0x80070002
File Exists: No
Version: N/A, hr = 0x80070002
WgaTray.exe Signed By: N/A, hr = 0x80070002
WgaLogon.dll Signed By: N/A, hr = 0x80070002

OGA Notifications Data-->
Cached Result: N/A, hr = 0x80070002
Version: N/A, hr = 0x80070002
OGAExec.exe Signed By: N/A, hr = 0x80070002
OGAAddin.dll Signed By: N/A, hr = 0x80070002

OGA Data-->
Office Status: 109 N/A
OGA Version: N/A, 0x80070002
Signed By: N/A, hr = 0x80070002
Office Diagnostics: 025D1FF3-364-80041010_025D1FF3-229-80041010_025D1FF3-230-1_025D1FF3-517-80040154_025D1FF3-237-80040154_025D1FF3-238-2_025D1FF3-244-80070002_025D1FF3-258-3

Browser Data-->
Proxy settings: N/A
User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)
Default Browser: C:\Program Files (x86)\Google\Chrome\Application\chrome.exe
Download signed ActiveX controls: Prompt
Download unsigned ActiveX controls: Disabled
Run ActiveX controls and plug-ins: Allowed
Initialize and script ActiveX controls not marked as safe: Disabled
Allow scripting of Internet Explorer Webbrowser control: Disabled
Active scripting: Allowed
Script ActiveX controls marked as safe for scripting: Allowed

File Scan Data-->

Other data-->
Office Details: <GenuineResults><MachineData><UGUID>{D7C69357-019D-4FF1-A41C-1ACAB90CDF0F}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010300.1.0.003</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-7QJB7</PKey><PID>00359-OEM-8992687-00006</PID><PIDType>2</PIDType><SID>S-1-5-21-259000744-805150807-1604811156</SID><SYSTEM><Manufacturer>Packard Bell</Manufacturer><Model>imedia S2870</Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>P01-A1 </Version><SMBIOSVersion major="2" minor="7"/><Date>20120518000000.000000+000</Date></BIOS><HWID>99393407018400FE</HWID><UserLCID>0809</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>GMT Standard Time(GMT+00:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>ACRSYS</OEMID><OEMTableID>ACRPRDCT</OEMTableID></OEM><GANotification/></MachineData><Software><Office><Result>109</Result><Products/><Applications/></Office></Software></GenuineResults>

Spsys.log Content: 0x80070002

Licensing Data-->
Software licensing service version: 6.1.7601.17514

Name: Windows(R) 7, HomePremium edition
Description: Windows Operating System - Windows(R) 7, OEM_SLP channel
Activation ID: d2c04e90-c3dd-4260-b0f3-f845f5d27d64
Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
Extended PID: 00359-00178-926-800006-02-1033-7601.0000-0892012
Installation ID: 007471774314182283116600870745716381216496286003790832
Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88338
Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88339
Use License URL: http://go.microsoft.com/fwlink/?LinkID=88341
Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88340
Partial Product Key: 7QJB7
License Status: Licensed
Remaining Windows rearm count: 2
Trusted time: 05/02/2020 06:54:00

Windows Activation Technologies-->
HrOffline: 0x00000000
HrOnline: N/A
HealthStatus: 0x0000000000000000
Event Time Stamp: N/A
ActiveX: Registered, Version: 7.1.7600.16395
Admin Service: Registered, Version: 7.1.7600.16395
HealthStatus Bitmask Output:


HWID Data-->
HWID Hash Current: LgAAAAEAAQABAAEAAAABAAAAAwABAAEAln2SJj4lMhsko4LVCE4s5gDhOIYucw==

OEM Activation 1.0 Data-->
N/A

OEM Activation 2.0 Data-->
BIOS valid for OA 2.0: yes
Windows marker version: 0x20001
OEMID and OEMTableID Consistent: yes
BIOS Information:
ACPI Table Name OEMID Value OEMTableID Value
APIC ACRSYS ACRPRDCT
FACP ACRSYS ACRPRDCT
HPET ACRSYS ACRPRDCT
MCFG ACRSYS ACRPRDCT
ASF! INTEL HCG
SLIC ACRSYS ACRPRDCT
SSDT SataRe SataTabl
SSDT SataRe SataTabl
SSDT SataRe SataTabl

 

[Sass10]

Problems solved

Have now updated to Windows 10 via a clean install. All files retrieved via system restore. The upgrade option never worked for whatever reason. nevertheless it's all good now.

 

[flavallee]

A "clean" install of Windows 10 is preferable over an "upgrade" install from Windows 7 to Windows 10 because it doesn't carry over the issues and debris from Windows 7 into Windows 10.

It's more work and requires a few more hours to set up and install everything, but it gives a computer a clean, fresh start.

And an "upgrade" install isn't always successful because there are too many things that can go wrong.

I personally have seen a failure rate of about 40% when doing an "upgrade" install.

 

[Megahertz07]

Please mark this thread as solved