New
#470
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.
Thanks. It worked on CMD. It read the following:
Does it mean UsoClient.exe cannot be run anymore?Code:C:\Windows\system32>takeown /f "%WINDIR%\System32\UsoClient.exe" /a SUCCESS: The file (or folder): "C:\Windows\System32\UsoClient.exe" now owned by the administrators group. C:\Windows\system32>icacls "%WINDIR%\System32\UsoClient.exe" /remove "Administrators" "Authenticated Users" "Users" "System" processed file: C:\Windows\System32\UsoClient.exe Successfully processed 1 files; Failed processing 0 files
It seems, that I have forgotten to remove inheritance, last time I did it manually, so it did not occur to me.
Re-checked, the task fails to run and exe as well. Manual checking works fine.Code:takeown /f "%WINDIR%\System32\UsoClient.exe" /a icacls "%WINDIR%\System32\UsoClient.exe" /inheritance:r /remove "Administrators" "Authenticated Users" "Users" "System"
In a word, auto-checking for updates will not happen, but manual checking can be performed.
Is that correct?
In the future, if I want the auto-checking back, what should I do?