| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 143953 | 2017-05-22 04:29:00 | Multi-boot menu look | Tony (4941) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 1435616 | 2017-05-22 04:29:00 | This is a bit of a newbie question I suspect, but how do I change my multi-boot menu from this: 8059 to this: 8060 ? |
Tony (4941) | ||
| 1435617 | 2017-05-22 05:02:00 | I have used bcdedit.exe to compile a boot menu for a physical address extension boot option that looks like your second screen. These MS sites may offer some help: docs.microsoft.com docs.microsoft.com |
Terry Porritt (14) | ||
| 1435618 | 2017-05-22 05:12:00 | If you are referring to the "looks" then the top one is the old style W7 boot loader. Found the following article that says how the person fixed theirs. how-to-get-the-windows-8-dual-boot-screen (social.technet.microsoft.com) Bit of an overkill to fix, but looks like its something to do with the bootloaders. So time to keep looking to see if theres any other options -hi ho hi ho off to look we go-------- :D If you had installed W7 then that will have caused the old style menu to appear, just a suggestion, have you tried changing the Defualt Boot OS in system Config ? |
wainuitech (129) | ||
| 1435619 | 2017-05-22 05:30:00 | Haven't tried it but have a read of this ( its for W8, but should work the same in 10) www.techgainer.com | wainuitech (129) | ||
| 1435620 | 2017-05-22 06:49:00 | Haven't tried it but have a read of this ( its for W8, but should work the same in 10) www.techgainer.com the command(s) as supplied on that web page don't work in PowerShell. I've tried variations after looking up BCDEDIT, but none of them work. The suggested command is bcdedit /set {default} bootmenupolicy standard (or legacy for the text menu) |
Tony (4941) | ||
| 1435621 | 2017-05-22 10:16:00 | Which Windows 10 were you using ( as the picture) . Were you running PowerShell as Admin ? The latest Insider Preview has a bug in the CMD options, couldn't make a ISO until someone discovered how to get the commands working again. The choice command fails when run in a Command Prompt script. |
wainuitech (129) | ||
| 1435622 | 2017-05-22 10:32:00 | Which Windows 10 were you using ( as the picture) . Were you running PowerShell as Admin ?Running build 1703 with Powershell as admin. Here is the powerShell script: 8062 |
Tony (4941) | ||
| 1435623 | 2017-05-22 23:52:00 | Running build 1703 with Powershell as admin. Here is the powerShell script: 8062 The problem is you are using powershell, and not the CMD. Just tried it, and Powershell failed, CMD worked. 8064 |
wainuitech (129) | ||
| 1435624 | 2017-05-23 00:02:00 | Just tried it, and Powershell failed, CMD worked. Your right, it worked for me too. That was a trap for young players - I thought Powershell did everything CMD did and more and could be universally used instead. |
Tony (4941) | ||
| 1435625 | 2017-05-23 00:05:00 | [QUOTE=wainuitech;1261273]Just tried it, and Powershell failed, CMD worked. Your right, it worked for me too. That was a trap for young players - I thought Powershell did everything CMD did and more and could be universally used instead. That's what I thought as well. Powershell is meant to be the Powerhouse of using commands, can do anything with it. Appears we have all been lied to over the years :) |
wainuitech (129) | ||
| 1 2 | |||||