New
#11
When you are booted into Windows 10, what drive letter does the Windows 7 partition have?
When you are booted into Windows 10, what drive letter does the Windows 7 partition have?
thanks so if i'm in Window 10, my Win 7 drive is E, my commands would look like this correct?:
bcdedit /export e:\oldstore
bcdedit /createstore e:\emptystore
bcdedit /import e:\emptystore /clean
bcdboot e:\windows
Would I need to repeat the similar step when i'm logged into my Win 7 HDD?
yes, E
The command you want is:
Code:bcdboot E:\Windows /d /addlast
No that is NOT correctthanks so if i'm in Window 10, my Win 7 drive is E, my commands would look like this correct?:
bcdedit /export e:\oldstore
bcdedit /createstore e:\emptystore
bcdedit /import e:\emptystore /clean
bcdboot e:\windows
Please read again my post detailing the cmds as here
You boot into 10
you then open a cmd prompt with admin rights
you then issue these cmds
bcdedit /export c:\oldstore
bcdedit /createstore c:\emptystore
bcdedit /import c:\emptystore /clean
bcdboot c:\windows
Those are the cmds if when in 10 the drive with 10 installed is lettered C
as you have a dual boot the extra cmd if as you say when in 10 - 7 is lettered E
is
bcdboot e:\Windows
or as I said whatever letter is 7 whilst booted into 10
Everything seems to be working as intended now!
When I did the bcdedit and bcdboot commands on my Windows 10 (bcdboot E:\Windows /d /addlast didn't seem to register in cmd), I wasn't able to boot to Win 10 anymore as it keeps booting into Win 7, even when I chose to boot from Win 10 drive.
I boot into Win 7 to do the similar bcdedit and bcdboot command to fix my Win 10. Win 10 started giving me bcd errors, was able to fix this by doing bootrec /rebuildbcd and bootrec /fixmbr.
fingers cross, hope everything is ok as I keep monitor the next week or so.
bcdboot E:\Windows /d /addlast didn't seem to register in cmd)
I did not suggest that. It was another post
My cmd was
bcdboot e:\Windows
which I can assure you, adds that to the newly configured boot configuration data and I am sure would have worked perfectly.
I used it only two days ago on a dual boot I was repairing for someone.
I do not know how technically interested you are but here is the tech doc
https://docs.microsoft.com/en-us/win...ons-techref-di
the add last will not work for a dual boot on MBR as it changes the position of the entry so that you end up, only being able to boot into the add last - entry
If you have an external drive of the right capacity to take both images I would make a Macrium image of each drive - on the external drive.
If you do that - it will serve you well
NOT a clone - as that formats the drive and only then has the clone
An image of each of the disks on the computer
If you need help I will guide you.
Pleased to have assisted you.
"bcdboot X:\Windows /d /addlast" is the standard command used to establish dual booting. Below is a dual drive system with Windows 10 installed on disk 0 and Windows 7 installed on disk 1. Both disks will boot independently into their respective OS and it is currently booted into Windows 10:
The single bcdboot E:\Windows /d /addlast command has the following result:
This is the result:Code:Microsoft Windows [Version 10.0.19042.746] (c) 2020 Microsoft Corporation. All rights reserved. C:\Windows\system32>bcdedit Windows Boot Manager -------------------- identifier {bootmgr} device partition=\Device\HarddiskVolume1 description Windows Boot Manager locale en-US inherit {globalsettings} default {current} resumeobject {b48085ed-812f-11eb-b097-ea000bb970ef} displayorder {current} toolsdisplayorder {memdiag} timeout 30 Windows Boot Loader ------------------- identifier {current} device partition=C: path \Windows\system32\winload.exe description Windows 10 locale en-US inherit {bootloadersettings} recoverysequence {b48085ef-812f-11eb-b097-ea000bb970ef} displaymessageoverride Recovery recoveryenabled Yes allowedinmemorysettings 0x15000075 osdevice partition=C: systemroot \Windows resumeobject {b48085ed-812f-11eb-b097-ea000bb970ef} nx OptIn bootmenupolicy Standard C:\Windows\system32>bcdboot E:\Windows /d /addlast Boot files successfully created. C:\Windows\system32>bcdedit Windows Boot Manager -------------------- identifier {bootmgr} device partition=\Device\HarddiskVolume1 description Windows Boot Manager locale en-us inherit {globalsettings} default {current} resumeobject {b48085f1-812f-11eb-b097-ea000bb970ef} displayorder {b48085f2-812f-11eb-b097-ea000bb970ef} {current} toolsdisplayorder {memdiag} timeout 30 Windows Boot Loader ------------------- identifier {b48085f2-812f-11eb-b097-ea000bb970ef} device partition=E: path \Windows\system32\winload.exe description Windows 7 locale en-us inherit {bootloadersettings} osdevice partition=E: systemroot \Windows resumeobject {b48085f1-812f-11eb-b097-ea000bb970ef} nx OptIn detecthal Yes Windows Boot Loader ------------------- identifier {current} device partition=C: path \Windows\system32\winload.exe description Windows 10 locale en-US inherit {bootloadersettings} recoverysequence {b48085ef-812f-11eb-b097-ea000bb970ef} displaymessageoverride Recovery recoveryenabled Yes allowedinmemorysettings 0x15000075 osdevice partition=C: systemroot \Windows resumeobject {b48085ed-812f-11eb-b097-ea000bb970ef} nx OptIn bootmenupolicy Standard C:\Windows\system32>
And upon rebooting:
This is a computer system booting normally in legacy BIOS mode. It works exactly the same way on UEFI systems.
As a side note, in the hundreds of times I have used this command to set up multiple booting, the /addlast switch has never seemed to have any affect. The newly added OS still gets added to the top of the new boot menu list.
NavyLCDR
Well all I can say is - I have never used it
However as you clearly have please accept my apologies - if necessary
I use the system I posted and have never had a problem
This computer is dual boot 10 and 7 on MBR
My Windows boot manager shows the same as yours and as I said I have never issued the
/d
or the
/add last
I follow the procedure here
https://docs.microsoft.com/en-us/win...a-dual-boot-pc
which as shown once you have established the clean store for the BCD and added the 10 on C you then simply use the cmd shown in the link
However as I said - I am not familiar with the need to use the d - preserve and the add last - position cmdsAdd boot options for a Windows operating system.
Bcdboot D:\Windows
Reboot the PC. Now, the boot menu will show both menu options.