H
HimalayanPeak
Guest
bcdedit alleviated command fails in windows 7 when set parameter is involved. Is this a limitation and is there any updates to remove this limitation?
This is my situation: I have built a PC with with dual booting either Windows 10 or Wnodows 7 Enterprise. Each OS is installed on a separate SSD, windows 10 on a GPT partition and Windows 7 with MBR partition.
I can see the boot menu in classical text menu. When i issued bcdedit /set menudiplaypolicy standard, it fails in windows 7 and works fine in windows 10. However when issued in Windows 10, boot menu, it does not show windows 7 choice and boots straight into windows 10 as if it doesn't recognize Windows 7. But when I issued the "bcdedit /set menudisplaypolicy legacy in Windows 10, I get text-based menu with the choice of both Windows 10 and 7.
The point is these /set parameters are not executed in Windows 7. Is there any remedy to correct the situation?
Thank you.
More...
This is my situation: I have built a PC with with dual booting either Windows 10 or Wnodows 7 Enterprise. Each OS is installed on a separate SSD, windows 10 on a GPT partition and Windows 7 with MBR partition.
I can see the boot menu in classical text menu. When i issued bcdedit /set menudiplaypolicy standard, it fails in windows 7 and works fine in windows 10. However when issued in Windows 10, boot menu, it does not show windows 7 choice and boots straight into windows 10 as if it doesn't recognize Windows 7. But when I issued the "bcdedit /set menudisplaypolicy legacy in Windows 10, I get text-based menu with the choice of both Windows 10 and 7.
The point is these /set parameters are not executed in Windows 7. Is there any remedy to correct the situation?
Thank you.
More...