New
#11
Yes, exactly. rt click it and Run it as AdministratorYour instructions are to run your program 'NT6repairEx64.EXE' (presumably from the original drive);
Select the cloned drive, and click 'FIX'
Yes, exactly. rt click it and Run it as AdministratorYour instructions are to run your program 'NT6repairEx64.EXE' (presumably from the original drive);
Select the cloned drive, and click 'FIX'
The cloned windows should then boot fine and reassign letters to any other volumes.
Rarely, it doesn't, so after booting into it you can fire up disk mgmt and add letters to other volumes manually.
Works fine on my 64-bit machine. Is there any way to get it to run on my 32-bit machine? (which rejects it now).
Looks like there are quite a few other really useful tasks your program can perform. Looking forward to researching those.
Again, a tip of my hat and a load of thanks. The computer community is amazing!
I will compile 32 bit version when I get a moment. 32 bit is more useful as it will work in both 32 and 64 bit windows. However, standard winpe is bit version specific, so that is where separate versions are needed.
If you want all the functions, you would need a copy of bootsect.exe in the path ( easiest is to put nt6repair in the same folder as bootsect.exe and create a shortcut to nt6repair.
You will get bootsect.exe included if you d/l Boyans wonderful little program VisualBCD . You can then pop nt6repair into the Program Files\Visual bcd folder.
VisualBCD 0.9.3.1
Download Visual BCD
I feel like I am back in school again; Looking forward to following your instructions. You would make a great professor.
I am running out of adequate ways to express my admiration. What you have done will be a presentation at our January Computer Club meeting. I will leave out the particulars so no one will pester you. Our 100 or so members need to know there are people like you out there. Perfect timing for the Christmas season.
Great help SIW2!
I'm still curious as to why I don't see this issue using imaging (see my post #3).
Is Acronis Imaging "smarter" than Macrium Cloning with making changes for a "different HD ID" ?
With cloning, the new and old HD must be known when the clone is performed...
With Imaging, there is no way to know what HD the backup image might be restored onto...
Am I correct with that understanding/assumptions?
Thanks and Happy New Year,
David
I am following this discussion with great interest but cannot contribute much.
I know that others often benefit from simply reading so I will tell you my ending to the original thread.
The NT6RepairEx86 ran on my 64-bit and 32-bit computers (both). The cloned drive boots fine.
One interesting note: The first time the clone ran by itself, a message appeared in the lower right corner which said something like Windows is not genuine and gave the build number and something else. This disappeared and everything worked fine. The second time the cloned drive booted, the message did not appear.
Since I don't pirate and get Windows free from work, none of that bothers me. I just don't want to spend 8 hours updating Windows if my hard drive fails. Only happened once in ten years but it can happen.
Details probably don't matter but here are some in case they do:
Gigabyte Mother, Win7 Ultimate 64-bit, Western Digital HDs cloned with Acronis True Image Free
Phoenix Mother, Win7 Ultimate 32-bit, Seagate HDs cloned with Macrium Reflect Free
I also made image files earlier but have not tried recovering with them. Let sleeping dogs lie.