Serious issues in Windows 7 after Bootcamp Migration

I have macOS 10.12.6, and I did a volume to volume clone of a Windows 7 partition to a new hard drive. Upon installing my ssd into a new computer and starting the Bootcamp partition I have been having some serious issues that I have not been able to resolve or find elsewhere on the web.

First, when I boot up, it brings me to a screen that is completely gray and says

Windows 7
Build 7601
This copy of Windows is not Genuine

in the bottom right hand corner. This is all that appears, no start bar, no desktop icons, etc. I have to open the task manager using control + alt + delete and say “new task” “explorer.exe” just to get my start bar to appear.

At this point I have my start bar. I can click on “My Computer” or “My Documents” but the error message “No Such interface is supported” comes up. When I click on “Control Panel” the error message

::{26EE0668-A00A-44D7-9371-BEB064C98683}
No such interface supported

comes up. When I click okay, another “No such interface supported” message comes up. This a problem because a good amount of the recommended trouble shooting online starts with “Go to the Control Panel…”

When I run the generic Command prompt I am not an administrator. I have to use the task manager to run an elevated prompt using “new task” “cmd.exe”.

Nothing I have been able to find online has been able to help. A lot of the commands I have typed in cannot be found by my computer, leaving me pretty stuck. For example typing in mmc.exe to the command prompt gets me a message "Windows cannot find ‘D:\Windows\system32\mmc.exe’ ".

Also, this is a genuine copy of Windows 7. I have the product key, if only I was prompted to enter it.

Please help, I am at a loss…

It sounds like the clone was not completed. I would recommend running CHKDSK on the original, then saving an image. Then restore that image to the new drive.

tim

That is odd, because I got a process is complete message after the volume to volume cloning was finished.

So when I did the volume to volume clone it pretty much wiped the original partition. When I go to boot the original partition I get the message “This is not a bootable partition…”. This makes sense because when looking at the storage in my macOS partition it says the bootcamp partition is virtually empty, but is still there.

I have an image of my bootcamp partition before all of this went down. I restored the image to the now empty original partition… and the it looked like it was going to boot up, then flashed the old school blue computer screen and pushed me back into a macOS boot. At this point I have two non fully functioning bootcamp partitions. I followed all of Winclone’s pre imaging instructions, CHKDSK, restarts, etc. the best I could. Is there any hope for the partition that does boot but does not seem to have full clearances?

Did you see the error that flashes?

tim

No it flashes too quickly. I tried to boot it normally and in safe mode, no luck.

A couple of things to try:

1. Find the Blue Screen log. It is usually at the top level of the drive or in the Windows folder.
2. Try switching between legacy and efi:

tim

1. I could not find the blue screen log but I found the lxcf.log. Below is what it contains:

2019/04/13-19:37:43.137 ComClient LcsGetClientId() exception=10106
2019/04/13-19:37:43.152 ComClient LcsGetClientId() exception=10106
2019/04/13-19:50:07.868 ComClient LcsGetClientId() exception=10106
2019/04/13-20:02:45.779 ComClient LcsGetClientId() exception=10106
2019/04/13-20:03:05.931 ComClient LcsGetClientId() exception=10106
2019/04/13-20:04:55.927 ComClient LcsGetClientId() exception=10106
2019/04/13-20:06:16.986 ComClient LcsGetClientId() exception=10106
2019/04/13-20:06:36.365 ComClient LcsGetClientId() exception=10106
2019/04/13-20:06:36.365 ComClient LcsGetClientId() exception=10106
2019/04/13-20:11:53.498 ComClient LcsGetClientId() exception=10106
2019/04/13-20:22:57.704 ComClient LcsGetClientId() exception=10106
2019/04/14-00:47:27.707 ComClient LcsGetClientId() exception=10106
2019/04/14-05:53:11.594 ComClient LcsGetClientId() exception=10106
2019/04/14-05:53:11.594 ComClient LcsGetClientId() exception=10106
2019/04/14-17:11:33.389 ComClient LcsGetClientId() exception=10106
2019/04/14-17:11:33.389 ComClient LcsGetClientId() exception=10106
2019/04/14-17:52:02.854 ComClient LcsGetClientId() exception=10106
2019/04/14-19:35:47.861 ComClient LcsGetClientId() exception=10106
2019/04/14-20:00:32.866 ComClient LcsGetClientId() exception=10106
2019/04/14-22:02:02.861 ComClient LcsGetClientId() exception=10106
2019/04/15-00:45:02.861 ComClient LcsGetClientId() exception=10106
2019/04/15-06:45:06.451 ComClient LcsGetClientId() exception=10106
2019/04/16-06:40:50.897 ComClient LcsGetClientId() exception=10106
2019/04/16-06:40:50.897 ComClient LcsGetClientId() exception=10106
2019/04/16-06:50:54.720 ComClient LcsGetClientId() exception=10106
2019/04/16-12:50:59.514 ComClient LcsGetClientId() exception=10106
2019/04/22-02:59:24.951 ComClient LcsGetClientId() exception=10106
2019/04/22-02:59:24.951 ComClient LcsGetClientId() exception=10106
2019/04/26-00:47:26.343 ComClient LcsGetClientId() exception=10106
2019/04/26-00:47:26.358 ComClient LcsGetClientId() exception=10106

2. How do I make it to the Make EFI Bootable window?

Also, I think the disk the was restored from the image is completely bad, judging by the fact that it is missing “Windows” and “Users” folders when looking at it from the macOS partition. I think the original migrated partition is the only hope at this point. Any pointers? If not, I’m just going to try and salvage what I can.

I don’t recognize the error messages. Did you try and follow the link above to set EFI bootable?

tim

Hi, I am having exactly the same problem. Was there a final resolution for this case?
Thanks,
Andrew T.

By the way, I noticed that the issue requester mentioned about the bootcamp windows 7 has D:\Windows\sytems32. Mine is mapped to G:\Windows.

How come it’s not on c:? Is there a way I can assign the bootcamp volume to c: drive? I already tried using Safe Mode with DOS command prompt and DISKPART command, but it was denied. So, I’m stuck.

there was a posting earlier about removing the mounted volume registry entry. I suspect that will resolve the D versus C, though I am not sure it will matter for booting.

It matters to my case and, I believe, to this thread of issue/resolution. I logged in thru Windows 7 Safe Mode, used task manager to open regedit.exe. Then rename the mounted device to C:\ (from G). Rebooted bootcamp Windows and everything worked smoothly.

That is great to know. thank you for posting back. I love it when I am wrong and I learn something!

tim