bcdedit commands not working


i trying use bcdedit within powershell window. powershell window launched administrator, has privileges, , other privileged commands appear work fine. seems bcdedit not working in powershell window.

ps c:\users\administrator> bcdedit /copy {current} /d new  copy command specified not valid.  run "bcdedit /?" command line assistance.  parameter incorrect.

if issue exact same command command window, works fine.

c:\windows\system32>bcdedit /copy {current} /d new  entry copied {30070d01-4e58-11e4-a80d-fc88c48f0475}.  
have same issue other bcdedit commands, not all, some, such set , delete; seems read commands work fine update don't.  there special have bcdedit work within powershell window?  have tried on windows 8.1, windows 10, windows server 2012 r2, , windows server 2016 same results.  it's not big of deal have open command window, seems little strange.


. : | : . : | : . tim

you might able around adding cmd /c command. that's how use mklink in powershell:

ps c:\> mklink mklink : term 'mklink' not recognized name of cmdlet, function, script file, or operable program. check spelling of name, or if path included, verify path correct , try again. @ line:1 char:1 + mklink + ~~~~~~     + categoryinfo          : objectnotfound: (mklink:string) [], commandnotfoundexception     + fullyqualifiederrorid : commandnotfoundexception  ps c:\> cmd /c mklink creates symbolic link.  mklink [[/d] | [/h] | [/j]] link target          /d      creates directory symbolic link.  default file                 symbolic link.         /h      creates hard link instead of symbolic link.         /j      creates directory junction.         link    specifies new symbolic link name.         target  specifies path (relative or absolute) new link                 refers to.




Windows Server  >  Windows PowerShell



Comments

Popular posts from this blog

some help on Event 540

WMI Repository 4GB limit - Win 2003 Ent Question

Event ID 1302 (error 1307) DFS replication service encountered an error while writing to the debug log file