Enable or Disable Windows Update Automatic Updates in Windows 10  

Matthew Wai said:

I just ran the above on PowerShell (Admin) and got the following error:
Attachment 166536

Environment variables are different in PS ... use Cmd rather.

or change it to
[System.Environment]::ExpandEnvironmentVariables("%WINDIR%")

or..

$env:windir

for C:\Windows

Superfly said:

Environment variables are different in PS ... use Cmd rather.

or change it to
[System.Environment]::ExpandEnvironmentVariables("%WINDIR%")

or..

$env:windir

for C:\Windows

On another forum, I got all sorts of abuse from some people when I said powershell was not 100% compatible with command, with comments referring to speaking out of a different orifice!

It would be nice if powershell was clever enough to recognise cmds command and warn you even if automatically converting to powershell was too difficult.

It does not even need to be perfect e.g. This looks like a CMD command. Try executing in a legacy command prompt.

Matthew Wai said:

Does it mean UsoClient.exe cannot be run anymore?

It seems, that I have forgotten to remove inheritance, last time I did it manually, so it did not occur to me.

Code:

takeown /f "%WINDIR%\System32\UsoClient.exe" /a
icacls "%WINDIR%\System32\UsoClient.exe" /inheritance:r /remove "Administrators" "Authenticated Users" "Users" "System"

Re-checked, the task fails to run and exe as well. Manual checking works fine.

Matthew Wai said:

Do you mean UsoClient.exe cannot be run automatically by Task Scheduler but can be run manually by the user?

It can be run only by trusted installer and app packages.

Matthew Wai said:

In a word, auto-checking for updates will not happen, but manual checking can be performed.

Is that correct?

Yes

Matthew Wai said:

In the future, if I want the auto-checking back, what should I do?

Code:

icacls "%WINDIR%\System32\UsoClient.exe" /reset