I think SecureBoot is already off but I'll check again. Issue bcdboot C:\Windows /l de-DE /s k: /f ALL (replace C:\Windows with your OS drive that has the Windows folder, de-DE to en-US if your installation is in English, ALL to UEFI if you have an UEFI installation. Reboot, and it should go straight into Windows. Issue bcdboot C:\Windows /l de-DE /s v: /f ALL (replace C:\Windows with your OS drive that has the Windows folder, de-DE to en-US if your installation is in English, ALL to UEFI if you have an UEFI installation. In case anything happens you can always rename the. Change its attributes so you can rename it with attrib BCD -s -h -r and rename it to something else as a backup with ren BCD BCD.bak and you can rebuild the BCD now. Navigate further into it (EFI\Microsoft\Boot) and when you dir again you should see the BCD file, that's your problem over there. Exit diskpart, navigate to the volume ( cd /d v:) and type dir. Now that we have mounted it on V: we can work on it. ![]() In diskpart issue these commands (confirm volume number again first): I deduce that that's Volume 2 for you, a 100-200 MB FAT32 hidden partition tagged "SYSTEM". We'll rebuild the boot configuration data manually.įirst step, mounting the EFI partition. ![]() Windows likes to nag a lot when it is pushed to the second line at boot order. That's a common problem with removing multiboots.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |