Justintoxicated
[H]F Junkie
- Joined
- Apr 10, 2002
- Messages
- 14,519
So my hard drive was dying in my laptop, so I backed it up and replaced the dying intel SSD with a new Samsung SSD.
I then thought I would test my home backup solution by restoring from WSE.
It went really smooth, replaced the drive, plugged in an ethernet cable and booted off the WSE2012R2 server on the network.
Or so I thought, one the recovery finished I'm getting an error in windows 10.
It boots to recovery with code 0x000000e File\\Windows\system32\winload.exe
then tells me I will need recovery tools etc.
Not really sure what to do now? Did I trip some kind of security mechanism by changing hard drives? That seems a bit ridiculous so I'm guessing it is another problem. My Windows 10 was the free windows 7 upgrade. I have a lot of development work on this machine so I don't really want to clean install.
I then thought I would test my home backup solution by restoring from WSE.
It went really smooth, replaced the drive, plugged in an ethernet cable and booted off the WSE2012R2 server on the network.
Or so I thought, one the recovery finished I'm getting an error in windows 10.
It boots to recovery with code 0x000000e File\\Windows\system32\winload.exe
then tells me I will need recovery tools etc.
Not really sure what to do now? Did I trip some kind of security mechanism by changing hard drives? That seems a bit ridiculous so I'm guessing it is another problem. My Windows 10 was the free windows 7 upgrade. I have a lot of development work on this machine so I don't really want to clean install.