Thanks for the update and I hope the clean install helps.
If you consider the thread is now solved, please let the mods know by clicking the green button at the bottonm of the thread.
Don't hesitate to post back in a new thread if you encounter a fresh problem.
Hi! I know this thread is old, but I have a very simple solution to this problem. I had the same issue because I used Runtime Soft DriveImage XML to copy my OS to a new SSD. Of course the new partition was E: and not C:, as the latter was still in use. I rebooted successfully to the new partition - I had this 100 MB Windows System Reserved partition from an earlier installation on that drive. But my system was a mess: shortcuts weren't working and most of the Windows features were unavailable. Of course, DriveImage XML was still installed and I could start it from command line. Under "Tools" in the menu bar, it contains an option to reset the drive ID. With a new drive ID, Windows assigns a new drive letter as well. Of course, my system partition was rendered unbootable by that method. But I could recover Windows boot with the System Repair option from a Windows installation medium. All in all it took me less than 10 minutes to have my newly placed OS working. And for all who don't have DriveImage XML already installed, there is a boot CD on their webiste. And I believe it is integrated in some emergency and system preparation distributions like BartPE etc. So don't despair!
I am sorry, I just noticed that I posted this in the wrong forum (a little tired here). It was the perfect solution to my problem but does not apply here. I had sereveral tabs in my browser open and chose the wrong one. Apologies! Hopefully, this helps someone with my (former) problem ending up here as well. Over and out!
Quote