NET Framework 4.5.2, install update 4020506įor the. NET Framework 3.5, install update 4020512įor the. NET Framework 4.6.2, install update 4020500įor the. NET Framework 4.6 or 4.6.1, install update 4020503įor the. NET Framework 3.5.1, install update 4020513įor the. NET Framework 4.6, install update 4020503įor the. NET Framework 4.5.2, install update 4020507įor the. NET Framework 2.0, install update 4020511įor the. To resolve this problem, install the update in the table below according to your system.įor the. Var mgmtCallResult = mgmtInst.InvokeMethod('Reboot', null, null) Ĭ('Reboot() Return Value: ', mgmtCallResult) Var mgmtClass = new ManagementClass(mgmtScope, new ManagementPath('Win32_OperatingSystem'), null) įoreach (ManagementObject mgmtInst in mgmtClass.GetInstances()) $win32OS = get-wmiobject win32_operatingsystem -computername $computername -EnableAllPrivileges IterMgmtObject.InvokeMethod('Reboot', null, null) ManagementClass mgmtObject = new ManagementClass('Win32_OperatingSystem') įoreach (ManagementObject iterMgmtObject in mgmtObject.GetInstances()) $.EnablePrivileges = $trueĮxample 2 (C# code) returns “Privilege not held” error: $win32OS = get-wmiobject win32_operatingsystem -computername $computername To work around this issue, run the following “shutdown.exe” command to execute power-down and restart operations on local or remote systems:įor more information and command help, run:Ĭustomer applications using power management methods, such as shutdown or reboot, from the Win32_OperatingSystem class and set the EnablePrivileges attribute to true, may observe the same “Privilege not held” error.Įxample 1 (PowerShell) returns “Privilege not held” error: + FullyQualifiedErrorId : StopComputerException, Workaround for Issue 1 + CategoryInfo : InvalidOperation: (:String), ManagementE

More information Symptoms for Issue 1Ĭustomers who try to turn off or restart a system, either local or remote, by using the stop-computer command on PowerShell v3.0 and later, will see the following error:

A 'Privilege not held' error message is returned. Additionally, if applications use power management methods, such as shutdown or reboot, from the Win32_OperatingSystem class and set the EnablePrivileges attribute to true, they may observe the same failure. 'Privilege not held' error with PowerShell 'stop-computer' command and power management methods in the Win32_OperatingSystem class: Workaround after April 2017 security updates from CVE-2017-0160 SummaryĪfter you apply the April 2017 security updates described in Microsoft security update guidance CVE-2017-0160, the PowerShell v3.0+ stop-computer command fails.

Cve 2017 14491 zyxel firmware download