Solved bcdedit fails in Powershell works in cmd


jimbo45

Well-known member
Power User
VIP
Local time
8:02 AM
Posts
1,461
Location
Hafnarfjörður IS
OS
Windows XP,7,10,11 Linux Arch Linux
Hi folks
Not sure if this is a recent change in W11 but if I run bcdedit /delete {Identifier} from powereshell I get error not valid and a prompt to run bcdedit /? and the delete command is shown exactly how I did it.

However run the same thing from the command line it works perfectly (bot were run in admin mode).
Is this new in W11 as I prefer in general to use powershell than the standard command processor.

Cheers
jimbo
 

My Computer

System One

  • OS
    Windows XP,7,10,11 Linux Arch Linux
    Computer type
    PC/Desktop
    CPU
    2 X Intel i7

cereberus

Well-known member
Power User
VIP
Local time
9:02 AM
Posts
1,669
OS
Windows 10 Pro + others in VHDs
Hi folks
Not sure if this is a recent change in W11 but if I run bcdedit /delete {Identifier} from powereshell I get error not valid and a prompt to run bcdedit /? and the delete command is shown exactly how I did it.

However run the same thing from the command line it works perfectly (bot were run in admin mode).
Is this new in W11 as I prefer in general to use powershell than the standard command processor.

Cheers
jimbo
This is nothing new. When you run a command line file in powershell, powershell is using aliases (not native ps commands) and whilst they are generally compatible, not all commands are fully compatible (bcdedit being a prime example).

I once had a guy slagging me off saying that was bullshit. I screen dumped some examples in reply, and he then accused me of photoshop editing screen dumps LOL!

Simplest solution is whilst in powershell, type cmd to jump to a command shell to run command, then type exit to get back to powershell.
 

My Computer

System One

  • OS
    Windows 10 Pro + others in VHDs
    Computer type
    Laptop
    Manufacturer/Model
    ASUS Vivobook 14
    CPU
    I7
    Motherboard
    Yep, Laptop has one.
    Memory
    16 GB
    Graphics Card(s)
    Integrated Intel Iris XE
    Sound Card
    Realtek built in
    Monitor(s) Displays
    N/A
    Screen Resolution
    1920x1080
    Hard Drives
    1 TB Optane NVME SSD, 1 TB NVME SSD
    PSU
    Yep, got one
    Case
    Yep, got one
    Cooling
    Stella Artois
    Keyboard
    Built in
    Mouse
    Bluetooth , wired
    Internet Speed
    72 Mb/s :-(
    Browser
    Edge mostly
    Antivirus
    Defender
    Other Info
    TPM 2.0

jimbo45

Well-known member
Power User
VIP
Thread Starter
Local time
8:02 AM
Posts
1,461
Location
Hafnarfjörður IS
OS
Windows XP,7,10,11 Linux Arch Linux
This is nothing new. When you run a command line file in powershell, powershell is using aliases (not native ps commands) and whilst they are generally compatible, not all commands are fully compatible (bcdedit being a prime example).

I once had a guy slagging me off saying that was bullshit. I screen dumped some examples in reply, and he then accused me of photoshop editing screen dumps LOL!

Simplest solution is whilst in powershell, type cmd to jump to a command shell to run command, then type exit to get back to powershell.
Thanks
I rarely use the cmd console as I prefer Powershell. Your suggestion is great.
Will mark as solved now.

Can't believe how stupid some people are -- why on earth would one want to "Photoshop" a screen dump !!!!! --Well I suppose it takes all sorts. !!

Cheers
jimbo
 

My Computer

System One

  • OS
    Windows XP,7,10,11 Linux Arch Linux
    Computer type
    PC/Desktop
    CPU
    2 X Intel i7

SIW2

Active member
Member
VIP
Local time
9:02 AM
Posts
233
bcdedit /delete "{Identifier}"


quote the squigly brackets. It will then accept what is inside the quotes literally. Otherwise it passes only Identifier to bcdedit without the squiglies.

So you will get error message parameter is incorrect or words to that effect.
 
Last edited:

My Computer

Top Bottom