New
#1
Failed boot into Windows 7 after converting from dynamic to basic disk
This is my first post, but I've been a long time lurker on the Seven forums; and they've provided a great deal of help. I googled for hours and could not find a solution to my specific problem. Wiping and re-installing is my last resort option, but I understand that it's entirely doable.
So I have what I believe is quite a unique situation. I got my new Crucial M4 64gb ssd a few days ago, installed windows to it, updates, etc. Prior to that I had Windows 7 Professional x64 installed to my Seagate Barracuda 1tb drive. Given the limited capacity of my ssd, I had partitioned 50gb of space (named it G:\) on my Seagate through the original install for the purpose of installing programs to it for the new Windows installation on my SSD. After getting the SSD all set up, I quickly noticed that 50gb was not enough space.
Before this mess occurred, dual booting was not a problem with the multiple partitions and whatnot.
So after taking a nap, I tiredly booted into the SSD and shrunk what was the C: volume on the other installation (and was now E or something) with the intent of extending the G partition into the unallocated space. Upon trying to extend it, Windows popped up warning me that it needed to convert the disk to a dynamic one (even though it didn't do this while in the Windows install from the Seagate, before I had the ssd) and that I'd lose the ability to boot from it. So I decided to cancel it. Then, since I had just woken up, I stupidly decided to re-attempt it and figured I'd just hit yes, forgetting that I had a Widnows install on that HDD.
So it converted it to dynamic, and I noticed the greenish-brownish bar across the top of all the partitions which instantly woke me up, questioning what I had just done. Sure enough, I was no longer able to boot into the HDD as it would simply BSOD. I googled a little bit to see how to convert a dynamic disk back into a basic disk without data loss and landed on EaseUS' Partition master Home edition. So I installed that to the windows on my SSD, used it to convert E and G back to a basic disk, rebooted to finish. So at this point I thought I had fixed it.
However, I did not notice that under Disk management, the System Reserved 100mb partition had stayed as a primary basic disk, but E and G were both sub-partitions in an extended partition (basic disk) due to EaseUS' handling of the conversion...until later. So I tried to boot from the HDD once again, with no luck. I popped in my Windows 7 Pro disk to launch the recovery utility, and it said it found problems and whatnot to fix. Still no luck. I booted back into the SSD, and found that the partitions were extended, so I switched E to primary using the EaseUS software, forgetting about G. I booted back into the HDD, this time it went into my lock screen (which looked normal with a custom background I had applied) and typed in my password to log in.
"Preparing your desktop" followed for a few minutes. Finally, it finished and basically took me to a light blue screen with nothing on it other than "version of Windows is not genuine" and "Version 7601" in the bottom right corner. It reminds me of safe mode, but it isn't. I hit ctrl-shift-esc to open Task manager, and ran explorer.exe. I got a start menu after a while but I couldn't do much. I couldn't run programs, or open folders with the error saying "No such interface is supported." I booted into the Windows 7 disk, ran the recovery, it said it found and fixed problems. Yet somehow, after the windows recovery utitility ran, it had associated the G partition as my Program files (or C drive) and installed the basic Windows programs (Like Windows NT, Internet Explorer, etc) to it, rather than running the programs off the actual C drive.
I booted back into my SSD, uninstalled my programs from the G partition, formatted it, and merged it with the E (original C) drive, in an attempt to reverse that association. No luck still, still a light blue screen background. I popped in my disk again while in that weird semi-safe mode OS and navigated to it using Task Manager's run command. I hoped that I could just run my W7 Pro upgrade off the setup disk so I'd keep my programs and files and it would re-install the OS. No luck, it came up saying that my Program files, page file, user files, etc. all had to be on the same partition (which should've been C). But they weren't. This made me find out after running diskmgmt.msc that my C drive had apparently become D now, and I had no C drive; where obviously my whole registry pointed to for all my programs. So I thought that was the problem.
I booted again from the repair disc, opened command prompt, ran diskpart and re-assigned the System Reserved (which was C there) to D, and Local Disk from D back to C. Exited, closed it, rebooted. Still no luck, I got the same light blue background screen. I ran chkdisk from the recovery utility, it fixed problems that it found, but didn't help. I ran sfc /scannow multiple times, fixed problems, no luck. I ran the startup repair, which sometimes found problems and sometimes didn't, no luck. One time my HDD failed to boot saying that bootmgr.exe was missing, but I ran Startup recovery yet again and it fixed that. But I went back into the light blue screen semi-safe mode thing.
Then I found out that under the Windows recovery utility, it listed my partitions as C and D the way I had labelled them, but under the semi safe mode after running diskmgmt.msc it still showed Local Disk as D and System reserved as no drive letter.
So this is where I am currently. Sorry for the huge post, but I tried to be as specific as possible and even then I may have missed a few things of what I did since it's been going on for the last 2 days. I know I could just wipe the HDD and be done with it, but it's got MS office installed to it as well as Autocad and a bunch of games and other programs that would be hard to replace if I wiped it.
Thanks, and I really appreciate any help you guys could give me out there. If you need any more info, let me know. Also, sorry for any typos i didn't catch, this is quite a long post.