Ghost clone win 7 seconds on, and win 10 stuck to the mouse. What's wrong with that
A few days ago, with the old flash drive into the pe, ghost would do the usual -- pick the source disk, pick the target disk, start the cloning, and win7 would be edged and plugged in. A win10 mirror was tested and turned on the black screen, an arrow cursor was active, the pass code was not working, the task manager was unable to open and even the ctrl+alt+del was stuck. It's either blue screen, it's wrong or it's not moving。
Check it out. The computer is for 2016 hp prodesk, uefi and legacy. I chose legacy at 10 a. M., and the division manually deleted the mbr of gpt reconstruction, theoretically the same as win7. But as soon as ghost runs, the system is dead. It was not a hardware problem, ssd changed two pieces and pe changed three versions, and the results were the same。
Later on, looking at the forum, looking at microsoft documents, and taking diskgenius's own division structure, it became clear that win10 was not able to run "move windows folders" at all. It's got a bunch of things that win7 doesn't have at all: a small partition called esp, which is full of . Efi files; a blank partition called msr, which is cleaned first when the bios starts; and the bcd configuration form, which says not "c drive" but a bunch of uid+ paths, which ghost would never change at all。
I tried bootrec/fixmbr, no use; try bootrec/rebuldbcd again, hinting to "successfully add a windows installation", but restarting is still black screen. Then it turns out that the bcd item, device and osdevice, still pointed at the original hard drive on the d-disc (i cloned the former system on the d-disc) and that the new system was installed on the c-disc, but it didn't recognize it. The use of bcdedit was changed three times to the top。
There's another pit: pe has to start legacy. Once i went into the pe in uefi mode and ran ghost again, as a result of which there was an efi folder in the cloned system, the bios jumped directly to the bootmgfw. Efi when it was restarted, but the path inside was completely wrong and it was flat. Diskgenius clears first, first diskpart clean, then coNvert mbr, not light-deducted partition. Gpt head might still be there。
The dumbest one was the cloning of the pe, looking at the diskpart list vol, the system volume label was e: but i thought it was c: and the result was c:, the bcdedit was all on c: written, and only when the restart was found — there was no match. Go back to the pe, list vol confirmed to be c: and change the bcd to really get up。
Macrum reflect free, picks "clone this dissk" and next step, it automatically detects esp sub-divisions (although i don't share them), automatically rebuilds the bcd, and even bypasses the signatures of winload. Exe. A success. It's not that it's so cowy, it knows what win10 wants to start. Ghost's only in the fan zone, it's in the context。
It was said that the ghost version was too old for symantec ghost 12 or not; it was said that winpe3 had little to do with the pe version, but the key was to start mode + partition structure + bcd triads. You missed one, it's stuck。
I'll write down every step: pe into legacy, disskpart clean, coNvert mbr, ghost clone, restart into pe, diskpart list vol, bootrec/rebuldbcd, bcdidit manual check three lines, rebootrec/fixboot. One less step, you have to start over。
When the win10 installation program was installed itself, it did dozens of things: building esps, writing guidance documents, registering bcds, checking signatures, setting start variables. Ghost did only one: copying sectors. It's not broken, it's not designed to do the rest of the work。
Ghost is still there, but win10 has changed a set of starting languages. You say something new in the old words, it doesn't understand。
Now that i am clone win10, it would take more than 10 minutes to confirm the solidware pattern, then confirm the partition table, then confirm the disc, and then make the last point of cloning。
It's never hardware, it's a uud, a disc, an unrewritten efi file path。
Fix it。
