- Jun 22, 2014
- 16
- 0
- 10,510
So I'm pretty stuck on this one.
Last night I was rendering some video, while watching another video, when everything started to lag really bad. My rendering software crashed, as did Media Player, and Windows 10 (anniversary edition) basically had a seizure. No brainer, I thought, just reset.
Lol no.
Windows wouldn't boot any more. I got endless loading loop with the windows logo, and every third attempt I got endless "preparing automatic repair" screens. I know they were endless, because I left the latter overnight and it didn't change.
For ages I thought it was something to do with the MBR, so I created a Win10 installation USB to use as a recover media. I used commands to repair the boot environment, with no success. I was able (intermittently) to boot into safe mode, but never into Windows properly.
In the end I connected a second, new SSD and did a fresh install of Windows 10 to that. This install I'm able to boot into, no problem. So from here I used EasyBCD to create a dual boot option with the old SSD.
So now I can see both Win10 installs in the boot environment, but every time I select the old install I get a "Inacessible Boot Device" blue screen, complete with a perfectly useless QR code (why Microsoft?).
I know Windows likes to share boot environment information, so I'm thinking now that this can't be an MBR/ BCD issue as I've got one working install running parallel to the one that isn't. Besides, I've tried running all the command prompt fixes in the recovery environment that I can find (‘bootrec /rebuildbcd’, then ‘bootrec /fixmbr’, then ‘bootrec /fixboot' etc) and none of them have worked.
Frankly I don't want to have to start over with a fresh install of Windows 10, I'd much rather get back into my old install.
Anybody got any advice?
Last night I was rendering some video, while watching another video, when everything started to lag really bad. My rendering software crashed, as did Media Player, and Windows 10 (anniversary edition) basically had a seizure. No brainer, I thought, just reset.
Lol no.
Windows wouldn't boot any more. I got endless loading loop with the windows logo, and every third attempt I got endless "preparing automatic repair" screens. I know they were endless, because I left the latter overnight and it didn't change.
For ages I thought it was something to do with the MBR, so I created a Win10 installation USB to use as a recover media. I used commands to repair the boot environment, with no success. I was able (intermittently) to boot into safe mode, but never into Windows properly.
In the end I connected a second, new SSD and did a fresh install of Windows 10 to that. This install I'm able to boot into, no problem. So from here I used EasyBCD to create a dual boot option with the old SSD.
So now I can see both Win10 installs in the boot environment, but every time I select the old install I get a "Inacessible Boot Device" blue screen, complete with a perfectly useless QR code (why Microsoft?).
I know Windows likes to share boot environment information, so I'm thinking now that this can't be an MBR/ BCD issue as I've got one working install running parallel to the one that isn't. Besides, I've tried running all the command prompt fixes in the recovery environment that I can find (‘bootrec /rebuildbcd’, then ‘bootrec /fixmbr’, then ‘bootrec /fixboot' etc) and none of them have worked.
Frankly I don't want to have to start over with a fresh install of Windows 10, I'd much rather get back into my old install.
Anybody got any advice?
Facebook
Twitter
Instagram