Cloned dual boot SSD containing Windows 7 and Window 10 partitions fails to open Windows 10

Question

To gain more operating space I recently cloned a Samsung 850 EVO 500GB SSD having two partitions (one running Windows 7, the other Windows 10; both successfully) to a 1TB Samsung 870 EVO SSD using Samsung's Data Migration Software which I ran using Windows 7 on the partition of the original SSD. After I was done cloning, the new SSD would start up on Windows 7 just fine, but Windows 10 would not. Upon choosing Windows 10, the computer would generate the blue windows symbol, the dots would circle around, and then the screen would go black. I could only get the system to respond by restarting it and picking Windows 7. I have reviewed a previous thread stating this is a problem that can be solved by switching some drive letters in the HKLM\System\Mounted Devices registry, but I couldn't make it work for me. I don't want to lose data on the Windows 10 partition so I'm looking for some help in addressing this problem. Thank you in advance for any advice you can offer!

p.s. the event logs show an error related to calling a Windows command from a path (for example, F:\Windows\System32\dwm.exe) that does not have an OS! I've included two Application crashing events below as examples:

Log Name: Application
Source: Application Error
Date: 8/1/2022 5:14:54 PM
Event ID: 1000
Task Category: Application Crashing Events
Level: Error
Keywords: Classic
User: N/A
Computer: DESKTOP-J5J61QD
Description:
Faulting application name: dwm.exe, version: 10.0.19041.746, time stamp: 0x6be51595
Faulting module name: KERNELBASE.dll, version: 10.0.19041.1826, time stamp: 0x299341e8
Exception code: 0x8000ffff
Fault offset: 0x0000000000034fd9
Faulting process id: 0x4f4
Faulting application start time: 0x01d8a5f41ff4246f
Faulting application path: F:\Windows\system32\dwm.exe
Faulting module path: F:\Windows\System32\KERNELBASE.dll
Report Id: 9da2446c-f00f-4112-bcfc-390c407f9ee7
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>100</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2022-08-01T22:14:54.396873700Z" />
<EventRecordID>41274</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>DESKTOP-J5J61QD</Computer>
<Security />
</System>
<EventData>
<Data>dwm.exe</Data>
<Data>10.0.19041.746</Data>
<Data>6be51595</Data>
<Data>KERNELBASE.dll</Data>
<Data>10.0.19041.1826</Data>
<Data>299341e8</Data>
<Data>8000ffff</Data>
<Data>0000000000034fd9</Data>
<Data>4f4</Data>
<Data>01d8a5f41ff4246f</Data>
<Data>F:\Windows\system32\dwm.exe</Data>
<Data>F:\Windows\System32\KERNELBASE.dll</Data>
<Data>9da2446c-f00f-4112-bcfc-390c407f9ee7</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>

Log Name: Application
Source: Application Error
Date: 8/1/2022 5:14:54 PM
Event ID: 1000
Task Category: Application Crashing Events
Level: Error
Keywords: Classic
User: N/A
Computer: DESKTOP-J5J61QD
Description:
Faulting application name: LogonUI.exe, version: 10.0.19041.1, time stamp: 0xc08a5452
Faulting module name: KERNELBASE.dll, version: 10.0.19041.1826, time stamp: 0x299341e8
Exception code: 0x8000ffff
Fault offset: 0x0000000000034fd9
Faulting process id: 0x4ec
Faulting application start time: 0x01d8a5f41ff406ea
Faulting application path: F:\Windows\system32\LogonUI.exe
Faulting module path: F:\Windows\System32\KERNELBASE.dll
Report Id: 33e9f4d7-4c27-404a-ab2c-d5d35ccffe09
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>100</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2022-08-01T22:14:54.396873700Z" />
<EventRecordID>41275</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>DESKTOP-J5J61QD</Computer>
<Security />
</System>
<EventData>
<Data>LogonUI.exe</Data>
<Data>10.0.19041.1</Data>
<Data>c08a5452</Data>
<Data>KERNELBASE.dll</Data>
<Data>10.0.19041.1826</Data>
<Data>299341e8</Data>
<Data>8000ffff</Data>
<Data>0000000000034fd9</Data>
<Data>4ec</Data>
<Data>01d8a5f41ff406ea</Data>
<Data>F:\Windows\system32\LogonUI.exe</Data>
<Data>F:\Windows\System32\KERNELBASE.dll</Data>
<Data>33e9f4d7-4c27-404a-ab2c-d5d35ccffe09</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>

Answer 1

Hi,

If you encounter the problem that Windows cannot be started after data migration, you can try the method of rebuilding the Boot Configuration Data (BCD).

The specific operation steps are as follows:

1. Start the computer and select win10 system.
2. Start Advanced Startup Options.
3. select Troubleshoot > Advanced options.
4. Select the Command Prompt button to start it.（Tip:Command Prompt won't start immediately. Your computer will show a "Preparing" screen for a short time while it readies the computer）.
5. At the prompt, type the bootrec /rebuildbcd, and then press Enter.

For more information refer to the article:
https://www.lifewire.com/how-to-rebuild-the-bcd-in-windows-2624508

Best Regards,
Wesley Li