Windows 10 BCDEdit - How to change {bootmgr} path?

So basically, I'm trying to install rEFInd. I've gotten everything to go successfully besides this part:

Type bcdedit /set {bootmgr} path \EFI\refind\refind_x64.efi to set rEFInd as the default EFI boot program. Note that {bootmgr} is entered as such; that's not a notation for a variable. Also, change refind_x64.efi to refind_ia32.efi on systems with 32-bit EFIs. Such computers are rare, and most of them are tablets. Check your Windows bit depth to determine which binary you should use.

I get this:

The parameter is incorrect.

The exact line I enter is

bcdedit /set {bootmgr} path \EFI\refind\refind_x64.efi

I recall this working in earlier versions of Windows, but not here. What should I do?

Please note that EasyUEFI and VisualBCD are both screwing up. Here is a full output of my current BCD:

TheForgottenArchitect

Posted 2015-09-29T14:11:22.497

Reputation: 53

Answers

You can create a separate boot entry in NVRAM for rEFInd and set it as default (first boot choice) if this is the desired result. This should be possible using your UEFI firmware functionality for setting/creating new UEFI boot entry.

If this is not possible using firmware functionality:

I just changed "ApplicationPath" for {bootmgr} object using Visual BCD Editor in Windows 10 - 10240.

You have to map EFI System partition(ESP) to drive Z: for example (use diskpart.exe or mountvol.exe) and later use search button when editing ApplicationPath element to select rEFInd executable on ESP - "\EFI\refind\refind_x64.efi".
("ApplicationDevice" should show Z: or else you will get application exception)

snayob

Posted 2015-09-29T14:11:22.497

Reputation: 4 044

I opened up Visual BCD, and selected Windows Boot Manager under Loaders. From here, I tried double clicking ApplicationPath, entering the proper path, and clicking OK. However, the value field did not update. Using the search button and selecting the rEFInd .efi file that way didn't work either. – TheForgottenArchitect – 2015-09-29T16:41:13.957

Map ESP to Z:. 2. Select {bootmgr} and edit its ApplicationPath.

< – snayob – 2015-09-29T16:48:59.680

That's what I did. I'll get you some screenshots, give me a second. – TheForgottenArchitect – 2015-09-29T16:50:35.407

Before: http://vgy.me/ZYh7J9.png

– TheForgottenArchitect – 2015-09-29T16:51:25.913

Right before hitting "OK": http://vgy.me/A6s3e9.png

– TheForgottenArchitect – 2015-09-29T16:52:16.407

After: http://vgy.me/7jiN01.png

– TheForgottenArchitect – 2015-09-29T16:52:29.330

DO NOT EDIT Windows Boot Manager BUT {bootmgr}. – snayob – 2015-09-29T17:06:46.377

Editing {bootmgr} gives the same issue: Nothing happens after I click OK. – TheForgottenArchitect – 2015-09-29T17:17:02.937

It looks like this both before and after editing: http://vgy.me/nwbps1.png

– TheForgottenArchitect – 2015-09-29T17:18:00.860

MOUNTVOL Z: /S (on admin command prompt) 2. OPEN VISUAL BCD EDITOR 3. Set {bootmgr} ApplicationDevice to Z: 4.EDIT "ApplicationPath". .....................SEE POSTED IMAGE.

< – snayob – 2015-09-29T17:26:17.707

Attempting to change the ApplicationDevice to Z: results in this error: http://vgy.me/qYYJgM.png

– TheForgottenArchitect – 2015-09-29T17:46:06.203

Bcdedit /set {bootmgr} device partition=Z: – snayob – 2015-09-29T17:52:12.323

And? Is question solved? – snayob – 2015-09-29T19:11:06.870

Yes, I have marked it as solved and given reputation for your answer. The key was setting the device partition. – TheForgottenArchitect – 2015-09-29T20:32:10.057

Thanks for rep. Visual BCD Editor should be updated to fix "Unknown Device" as this only means that some utility has written nonsense in this BCD element (which is a true object/complex data structure). – snayob – 2015-09-30T14:28:00.550

In Windows 10 you have to quote {bootmgr}. The new line is

bcdedit /set '{bootmgr}' path \EFI\refind\refind_x64.efi

Marcel Krüger

Posted 2015-09-29T14:11:22.497

Reputation: 241

4Or use CMD instead of PowerShell. – Martín Coll – 2016-12-19T01:36:03.387

3@MartínColl You should post that as an answer, since that is THE answer. Quotes will fail in cmd.exe but are needed in Powershell. – Adam Plocher – 2017-01-02T13:31:40.357

If you're using PowerShell you need to quote as answered by @zauguin.

Another option would be to use CMD, which is the terminal that the rEFInd author used when writing the guide.

Martín Coll

Posted 2015-09-29T14:11:22.497

Reputation: 171