Windows is not bootable after cloning using version 8.1.7638, tried multiple computers/SSDs but same...


Windows is not bootable after cloning using version 8.1.7638, tried...
View
Options
Author
Message
ahmad
ahmad
ahmad
posted 17 September 2023 2:19 PM HOT
Junior Member
Junior Member (70 reputation)Junior Member (70 reputation)Junior Member (70 reputation)Junior Member (70 reputation)Junior Member (70 reputation)Junior Member (70 reputation)Junior Member (70 reputation)Junior Member (70 reputation)Junior Member (70 reputation)Junior Member (70 reputation)
Group: Forum Members
Posts: 30, Visits: 609
Hello,
I've been cloning SSDs and HDDs for years with Macrium and since I updated to version 8.1.7638, the SSD/HDD isn't bootable at all and the PC doesn't see Windows at all after using the clone feature. I've tried from different computers to clone to and from. The only way for me to fix the issue is to go to a previous version (8.0.6036).
I even tried as a test to install fresh Windows (legacy CSM) on a brand new SSD and then cloned it to another SSD with version 8.1.7638 and the cloned SSD didn't boot at all. Cloning with v8.0.6036 works fine. I am not sure in which version the issue started happening since I updated directly from 8.0.6036 to 8.1.7638. The issue isn't with the PC I am using to clone as I temporarily installed 8.1.7638 on a brand new Windows and the same issue happens after cloning.

I tried on two licenses, Workstation (mine) and Server Plus (my friend's) and with both Windows doesn't boot at all after cloning using 8.1.7638.

You can easily re-produce the issue, just clone any non-UEFI SSD/HDD that has Windows 10 on it to any other empty SSD/HDD using v.8.1.7638, it won't be bootable. Just make sure the windows you're cloning is not UEFI (legacy).

Edited 17 September 2023 2:52 PM by ahmad
Reply Like 0
ahmad
ahmad
ahmad
posted 18 September 2023 10:41 AM ANSWER
Junior Member
Junior Member (70 reputation)Junior Member (70 reputation)Junior Member (70 reputation)Junior Member (70 reputation)Junior Member (70 reputation)Junior Member (70 reputation)Junior Member (70 reputation)Junior Member (70 reputation)Junior Member (70 reputation)Junior Member (70 reputation)
Group: Forum Members
Posts: 30, Visits: 609
I just let my friend test again and he's having the same issue cloning MBR Windows with 8.1.7638, it really is easy to see the issue and reproduce, no need for me to even provide any additional information for the issue; just clone any MBR disk that has Windows 7 or 10 using the clone feature within the app to any other HDD/SSD and it won't boot at all despite the partition layout is perfectly identical after the clone. Cloning any Windows UEFI with GPT works fine, only cloning MBR disks is affected.

And yes, the MR "Fix Windows boot problems" fixed it after cloning, I only had to check ""Replace the Master Boot Record", here's the log:



Looks like 8.1.7638 for some reason fails to write the MBR correctly after cloning.

Here's one of the failed clones log:

Clone ID - B4A221230A78CA09

--------------------------------------------------------------------------------
Dismounting drives


--------------------------------------------------------------------------------
Starting Clone - Sunday, September 17, 2023 4:46 PM


--------------------------------------------------------------------------------
Creating volume snapshots
Volume Snapshots Created
H:\ \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy3
J:\ \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy4


--------------------------------------------------------------------------------
Source Disk: Disk 6 MBR [6F42844D] - ASMT 2115 0 <111.80 GB>
Geometry: 14594\63\512
BPB: 255\63\512
Destination Disk: Disk 5 [00000000] - ASMT 2115 0 <476.94 GB>

Clone Type: Intelligent sector copy
Verify: Y
Delta: N
SSD Trim: Y
Power Saving: N
Email On Success: N
Email On Failure: N


--------------------------------------------------------------------------------
Operation 1 of 3
Copy Partition: 1 - System Reserved (HSmile
NTFS 30.3 MB / 50.0 MB
Destination
Start Sector: 2,048
End Sector: 104,447
Partition Type: Active


--------------------------------------------------------------------------------
Processing: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy3
Clone completed successfully


--------------------------------------------------------------------------------
Operation 2 of 3
Copy Partition: 2 - <NO NAME> (JSmile
NTFS 19.09 GB / 111.25 GB
Destination
Start Sector: 104,448
End Sector: 999,172,095
Partition Type: Primary


--------------------------------------------------------------------------------
Processing: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy4
Clone completed successfully


--------------------------------------------------------------------------------
Operation 3 of 3
Copy Partition: 3 - <NO NAME>
NTFS 426.2 MB / 508.0 MB
Destination
Start Sector: 999,172,096
End Sector: 1,000,212,479
Partition Type: Primary


--------------------------------------------------------------------------------
Processing: \\.\PHYSICALDRIVE5
Writing partition table
Using existing MBR
Clone completed successfully


--------------------------------------------------------------------------------
BCD Update - From Disk ID - 0x6F42844D, New Disk ID - 0x009F9A17
BCD Update - Success
Registry Update - No offline hive
Closing VSS. Please Wait...


--------------------------------------------------------------------------------
Clone completed in 00:03:45


Edited 18 September 2023 10:42 AM by ahmad
Reply Like 0
ahmad
ahmad
ahmad
posted 20 September 2023 11:40 AM ANSWER
Junior Member
Junior Member (70 reputation)Junior Member (70 reputation)Junior Member (70 reputation)Junior Member (70 reputation)Junior Member (70 reputation)Junior Member (70 reputation)Junior Member (70 reputation)Junior Member (70 reputation)Junior Member (70 reputation)Junior Member (70 reputation)
Group: Forum Members
Posts: 30, Visits: 609
Joe Allen sent me the dev build in the ticket and it works fine. Issue is completely fixed. He said this fix will be included in the next release. You guys are awesome Smile

Edit: Looking at the logs it looks like before and after the fix only one log line is different:

Before the fix (8.1.7638): Using existing MBR
After the fix (dev build and previous versions): Writing Master Boot Record (MBR)

So it looks like 8.1.7638 ignored something and didn't take the MBR from the source disk during cloning.

Edited 20 September 2023 12:01 PM by ahmad
Reply Like 1
GO

Merge Selected

Merge into selected topic...



Merge into merge target...



Merge into a specific topic ID...



Submit

Post Quoted Reply
Reading This Topic

Powered by InstantForum 2017-1 Final © 2023
Execution: 0.000. 3 queries. Compression Enabled.

Login

Explore
Messages
Mentions
Search