New
#1
How to clean up mess with multiple BCD stores on multiple drives
Hi. In my computer I have 3 drives, 1 M.2 and 2 HDDs and 2 OS: Windows 10 on WD M.2 and Windows 7 on Toshiba HDD. After some messing around with switching drives, moving partitions, restoring bootloaders and so on, I ended with funny situation.
My MSI motherboard has standard boot device selector (by pressing F11 at boot), which automatically detect UEFI bootloaders on EFI partition (in my setup there is only one on M.2 WD drive), but also allow to choose boot drive without recognized EFI bootloader, in which case it load OS in legacy mode. I guess proper CSM BCD configuration is stored on M.2 drive, because when I choose M.2 drive 2 OS entries are listed and both of them working fine. However Windows bootmanager screen is showing for other 2 drives also. For Toshiba HDD it showing 2 Windows entries (both work), and for HGST HDD 2 Windows 10 entries and one for Windows 7 (non working properly - problem with detecting winload).
So I guessed that other drives also containing old BCD stores, and maybe it isn't huge problem, but I really want to clean up that mess.
I know that I could load these stores with command:
bcdedit /store <patch> /enum.
But really haven't idea how <patch> parameter should look like and where on partition BCDs are stored.
Any help?