Hi, the problem isn't related to any lack of elevation (assuming Pro is run that way, which it is by default, and as you obviously expect that, I assume it still is).
If you use the Test button in Programs-Before, you should get a 'file not found' error (that's the clue). The problem is that the manage-bde
program you are asking Pro to call lives in \System32\ folder and because of this syndrome
, Windows is redirecting Pro's call from \system32\ to \SysWOW64\ instead (where manage-bde
doesn't exist - thus, the 'not found' error).
If you use the \sysnative\ path alias mentioned in the KB article, e.g.
Code: Select all
C:\windows\sysnative\manage-bde -unlock g: -rp 0123456-0123456-138952-233849
(likewise for the lock command), you should find it works. I just tried it & both commands work fine for me, but fail if I don't use the path alias.