Windows not Booting

[maxmbg]

I got a new m.2 ssd for Christmas and transferred data from my hard drive. I wanted to use this hard drive as extra storage space, so I used CMD to clear it. I wiped the drive, and then after it was wiped I tried to reset my computer and it would not boot. This is the drive that originally had windows installed on it, but after I transferred that to the m.2 I thought it would be okay. When I turn on my computer it says "your computer needs repairing" and I get code 0xc00000e. Anybody know how I could fix this? I tried using the Windows automatic repair tool and rebuilding the bcd already but neither seemed to work

[PwnyTheTiger]

It more than likely didn't transfer the boot record, and/or the system partitions necessary for Windows. What did you use exactly to transfer it all over? Going from a HDD to a SSD can also have odd caveats as well. When I transferred my Windows install from my old M.2 to my new one, I used AOMEI(paid) and make sure it copied it sector for sector over, especially since the drive capacities were different. At this point, you more than likely will need to completely reinstall Windows unfortunately. 

[maxmbg]

5 minutes ago, PwnyTheTiger said:

It more than likely didn't transfer the boot record, and/or the system partitions necessary for Windows. What did you use exactly to transfer it all over? Going from a HDD to a SSD can also have odd caveats as well. When I transferred my Windows install from my old M.2 to my new one, I used AOMEI(paid) and make sure it copied it sector for sector over, especially since the drive capacities were different. At this point, you more than likely will need to completely reinstall Windows unfortunately. 

I used macrium reflect v8. I looked on the app and it seemed to copy over every partition that the old drive had. Both drives are 1tb. If I reinstall, will I lose all of my data? 

[maxmbg]

14 minutes ago, PwnyTheTiger said:

It more than likely didn't transfer the boot record, and/or the system partitions necessary for Windows. What did you use exactly to transfer it all over? Going from a HDD to a SSD can also have odd caveats as well. When I transferred my Windows install from my old M.2 to my new one, I used AOMEI(paid) and make sure it copied it sector for sector over, especially since the drive capacities were different. At this point, you more than likely will need to completely reinstall Windows unfortunately. 

I also changed the boot priority in my bios to make sure that it was booting from the m.2 and not the hdd.

[PwnyTheTiger]

Have you tried clearing the CMOS? Also you mentioned trying to rebuild the BCD, you use the /bootrec commands? 

 

bootrec /FixMbr
bootrec /FixBoot
bootrec /ScanOs
bootrec /RebuildBcd

Could also be that the drive isn't marked as active, if you weren't on UEFI, which can be corrected via diskpart in a command prompt. Do you have the original drive plugged in? If so, try removing it completely before doing any fixes. If worse comes to worse there are ways to "upgrade" a Windows install here. This is exactly why you never wipe your source drive before you know the new drive actually works, and exactly why I waited until I knew my new drive was booting before I did the same. Let it be a lesson for the future.

[maxmbg]

3 minutes ago, PwnyTheTiger said:

Have you tried clearing the CMOS? Also you mentioned trying to rebuild the BCD, you use the /bootrec commands? 

 

bootrec /FixMbr
bootrec /FixBoot
bootrec /ScanOs
bootrec /RebuildBcd

Could also be that the drive isn't marked as active, if you weren't on UEFI, which can be corrected via diskpart in a command prompt. Do you have the original drive plugged in? If so, try removing it completely before doing any fixes. If worse comes to worse there are ways to "upgrade" a Windows install here

When I use the bootrec /FixBoot it outputs "access is denied".

[PwnyTheTiger]

Run diskpart in the command prompt. List vol, find the 100mb FAT32 partition, select vol (volume # that partition is), followed by det par. Then please, if you could post the result from that. Also, the result of the bcdedit command would be helpful.

[maxmbg]

Just now, PwnyTheTiger said:

Run diskpart in the command prompt. List vol, find the 100mb FAT32 partition, select (volume # that partition is), followed by det par. Then please, if you could post the result from that.

This is what I got from running all of that

[PwnyTheTiger]

2 minutes ago, maxmbg said:

This is what I got from running all of that

Yeah, it isn't showing up as a system partition in info, which isn't good. In diskpart do all the same to select volume 2, then run set id=c12a7328-f81f-11d2-ba4b-00a0c93ec93b override

 

I'm not sure this will actually fix it. But what about the bcdedit command?

[maxmbg]

1 minute ago, PwnyTheTiger said:

Yeah, it isn't showing up as a system partition in info, which isn't good. In diskpart do all the same to select volume 2, then run set id=c12a7328-f81f-11d2-ba4b-00a0c93ec93b override

 

I'm not sure this will actually fix it. But what about the bcdedit command?

I ran that command and it gave me a long list of commands that I can do. What do I do now? Also, I don't know what the bcdedit command is. Sorry for having so many questions and thank you for helping.

[PwnyTheTiger]

2 minutes ago, maxmbg said:

I ran that command and it gave me a long list of commands that I can do. What do I do now? Also, I don't know what the bcdedit command is. Sorry for having so many questions and thank you for helping.

That override command should force the volume to unmount before making the change, the ID is just the GUID identifier of a EFI System Partition, which is what that partition is and should be, the hope is that it would force it to be identified as a system drive. As far as the bcdedit command, you must exit on diskpart first and run it in the command prompt normally, it will basically read the boot record and spit out info about it. You said you ran that command and it gave you a long list of commands you can do? Nothing pertaining to it actually making any changes?

[maxmbg]

1 minute ago, PwnyTheTiger said:

That override command should force the volume to unmount before making the change, the ID is just the GUID identifier of a EFI System Partition, which is what that partition is and should be, the hope is that it would force it to be identified as a system drive. As far as the bcdedit command, you must exit on diskpart first and run it in the command prompt normally, it will basically read the boot record and spit out info about it. You said you ran that command and it gave you a long list of commands you can do? Nothing pertaining to it actually making any changes?

When I ran the override command it did not seem like it did much. Just gave me a long list of commands that I can run and what they would do. I ran bcdedit and it listed a lot of stuff as well. Should I try the 

bootrec /FixMbr
bootrec /FixBoot
bootrec /ScanOs
bootrec /RebuildBcd

commands now?

[PwnyTheTiger]

If that EFI partition is showing as a system partition in the info field when you run list vol, then sure, give it another try. Otherwise, it might be too FUBAR and you may want to consider prepping a Windows install USB to do as I said above, in the hopes you can keep your old Windows files. Though I'm not sure how Windows would react to it if the boot record is shot. Could always try this also, as it is basically the issue you're having currently. I totally forgot that EFI partitions aren't considered GPT thus those bootrec commands are useless.

[maxmbg]

2 minutes ago, PwnyTheTiger said:

If that EFI partition is showing as a system partition in the info field when you run list vol, then sure, give it another try. Otherwise, it might be too FUBAR and you may want to consider prepping a Windows install USB to do as I said above, in the hopes you can keep your old Windows files.

When I run list vol it says that it is a partition just like the other 2 partitions in that drive. I tried running fixboot again and it just said access denied. I have my windows usb ready, should I just do a custom install and keep as much data as I can?

[PwnyTheTiger]

Try what was posted in the link above first, if that fails, then yes, I would start reinstalling Windows on that drive as I previously posted, in hopes you can do a custom install and keep your old stuff. But it's been a while since I've done that myself, so I'm unsure how Windows would handle it.

[maxmbg]

1 minute ago, PwnyTheTiger said:

Try what was posted in the link above first, if that fails, then yes, I would start reinstalling Windows on that drive as I previously posted, in hopes you can do a custom install and keep your old stuff. But it's been a while since I've done that myself, so I'm unsure how Windows would handle it.

Do you mean this link here? If so, when going through the install do I use the custom option or the upgrade option?

[PwnyTheTiger]

Just now, maxmbg said:

Do you mean this link here? If so, when going through the install do I use the custom option or the upgrade option?

Nope, this link right here. Try using the custom option if available, otherwise upgrade essentially is the same thing. The installer will indicate if the drive will be wiped in the event that isn't an option, so you'll at least know it's coming. Again, let it be a lesson to you and all, don't format your source drive until you know your new drive works. It sucks, but that's the way she goes.

[maxmbg]

3 minutes ago, PwnyTheTiger said:

Nope, this link right here. Try using the custom option if available, otherwise upgrade essentially is the same thing. The installer will indicate if the drive will be wiped in the event that isn't an option, so you'll at least know it's coming. Again, let it be a lesson to you and all, don't format your source drive until you know your new drive works. It sucks, but that's the way she goes.

Definitely will be a lesson for me. Nothing else seems to be working for me so I am going to try the custom install of windows. It seems like the best option at this point. I'll follow the instructions the website says and let you know what happens. Thank you for all of your help.

[PwnyTheTiger]

1 minute ago, maxmbg said:

Definitely will be a lesson for me. Nothing else seems to be working for me so I am going to try the custom install of windows. It seems like the best option at this point. I'll follow the instructions the website says and let you know what happens. Thank you for all of your help.

No worries, best of luck to you, let me know how it goes. Remember any old files, in kept will show up in a folder named windows.old

[maxmbg]

Install went great