Search results

I'm pretty sure it's two Ds (DDISABLE) I had to put in my case but whatever, glad you solved it :)

@erictheluminant Thanks, glad I could help :) @babylorv Well, there's people in this forum more capable of helping you than me but basically my problem was that I had a BCD setup on Windows 7 which was altered to allow some stuff to work (unsigned drivers) and was not compatible with...

yes, every time I meant the guid, sorry for not stating it clearly. Also bcdedit can be used as you pointed out, instead of win7 install/recovery option, but it was simpler for me to let the tool do the work (probably the combo bootrec /rebuildbcd and bootrec /fixboot could also have worked to...

Ok, I finally solved it, here is how: a) Forget about dual letter issues. There are none at all, when using bcdedit just work with the current letter assignment whatever it is (I guess internally the volume id is what's stored, so when you run bcdedit /enum it will always list the...

Ok, First of all I solved the signature issue disabling x64 driver signature checking (I guess this was necessary due to some device encription drives (freeotfe) I had installed on win7, which required to disable the driver checking which was somehow reenabled when I tried to restore windows...

No luck, keeps saying something about winload.exe signature cannot be verified. Worst than that. I realized I have two BCD: one in my "new" c: drive for win8 with win7 and win8 entries and another in my d: drive (previously c:) with win7 entry. I guess the one active is windows 8, but since...

Hi guys, I've got a problem with my dual boot setup: I've installed win8, selected an empty partition, booted it, everything peachy. The only surprising thing was that driver letters where switched: my windows 7 install and data was now in D: drive and windows 8 install appropiated C: letter...