BCDedit says: "The set command specified is not valid"

I am using Windows PowerShell (Admin).
My command line is this: "bcdedit /set {bootmgr} path \EFI\ubuntu\shimx64.efi"
I had used this exact command line before and it did work.
Now it says "The set command specified is not valid". It makes no sense.
So I am suspecting that bcdedit cannot find the shimx64.efi.
I found where exactly the shimx64.efi is found.
In the 1st partition of disk 2. It's flagged "boot, esp". Is it possible that bcdedit is only looking in its own disk (#1) ? If so, are there command line parameters that would allow me to specify on what disk to search? Or is that shimx64.efi file supposed to be in disk 1 too?
I hope this is clear enough.

Hardware: Acer Predator 710 Desktop

The command is correct. Try running it in Administrator: Command Prompt

Powershell

Code:

Windows PowerShell
Copyright (C) 2016 Microsoft Corporation. All rights reserved.

PS C:\Windows\system32> bcdedit /set {bootmgr} path \EFI\refind\refind_x64.efi
The set command specified is not valid.
Run "bcdedit /?" for command line assistance.
The parameter is incorrect.
PS C:\Windows\system32>

CMD prompt

Code:

Microsoft Windows [Version 10.0.15063]
(c) 2017 Microsoft Corporation. All rights reserved.

C:\Windows\system32>bcdedit /set {bootmgr} path \EFI\refind\refind_x64.efi
The operation completed successfully.

C:\Windows\system32>

This thread explains the parsing problems powershell has...

Adil Hindistan's Technology Blog: PowerShell Gotchas: Enabling Safemode for Windows 8.1 with Bcdedit

Yes, I am using Windows PowerShell (Admin).

Type cmd to run in command prompt instead of powershell and then re-enter bcdedit command.

It should then work OK.

Well, very much to my surprise... I did work!!!
Thank you so much for your help :)
I will update my records on this right away .

Do you know if this was due to a recent Windows 10 update, maybe the new Creator's update?

drpeppercan said:

Do you know if this was due to a recent Windows 10 update, maybe the new Creator's update?

Powershell is the same as it ever was afaik.

What changed is in the past the + X menu had the cmd prompt by default and in creators update this changed to powershell. Perhaps that was it.

Most commands work the same in both cmd and PS but some don't...