DEP invalid paramater

I try to modify DEP settings for a x64 WIndows 7 Pro workstation with the following command

Code:

bcdedit.exe /set {current} nx AlwaysOn

But it fails : invalid parameter

The same command works perfectly on another machine

What's wrong ?

Thanks

Hello cobra02,

Safe Boot needs to be disabled in BIOS (if applicable) and the command needs to be run from an elevated command prompt.

thanks iko22 but safe boot disabled and elevated command prompt used and still same issue !

Okay. The error means that the BCD store is unable to work with one or both command line arguments.

Try typing these three commands, and see if they are executed correctly:
1.

Code:

bcdedit /enum {current} /v

2.

Code:

wmic OS Get DataExecutionPrevention_SupportPolicy

3.

Code:

bcdedit.exe /set {current} nx OptIn

So this is what I get:

Command 1:

Code:

  Chargeur de démarrage Windows
-----------------------------
identificateur          {c33452e9-6035-11e7-9590-e88ff9790913}
device                  partition=C:
path                    \windows\system32\winload.efi
description             Windows 7
locale                  fr-FR
inherit                 {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
recoverysequence        {c33452ea-6035-11e7-9590-e88ff9790913}
recoveryenabled         Yes
osdevice                partition=C:
systemroot              \windows
resumeobject            {c33452e8-6035-11e7-9590-e88ff9790913}
nx                      OptIn
ParamŠtre incorrect.

Command 2

Code:

DataExecutionPrevention_SupportPolicy  
1

Command 3

Code:

Paramètre incorrect.

Are you using cmd.exe to type the command or are you typing the commands in PowerShell?

If you use PowerShell, the {current} GUID must be enclosed inbetween quotes, like this: "{current}".

cmd.exe is used

I have no more explanation to offer you. I am out of further suggestions.
Unless one thing is a problem. Is {current} recognised in your system locale (fr-FR)? Do both your computers have the same system locale?
You could try substituting {current} with the correct OS loader GUID Identifier. So, do the following commands succeed in their execution:
4.

Code:

bcdedit /enum {c33452e9-6035-11e7-9590-e88ff9790913} /v

5.

Code:

bcdedit.exe /set nx AlwaysOn

6.

Code:

bcdedit.exe /set {c33452e9-6035-11e7-9590-e88ff9790913} nx AlwaysOn

?

still the same... returns bad parameter

Is anybody else has a suggestion ?