You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Disable startup check for latest virus and spyware security intelligence (signature)
Promises to disable the signature update during startup, while the script has done it wrong.
In this line: PowerShell -ExecutionPolicy Unrestricted -Command "reg add 'HKLM\Software\Policies\Microsoft\Windows Defender\Signature Updates' /v 'UpdateOnStartUp' /t 'REG_DWORD' /d '1' /f"
The correct data for value UpdateOnStartUp should be "0" instead of "1", as mentioned on the admx.help itself (the script on privacy.sexy uses this link as reference): Reference link used in privacy.sexy
If you disable this setting or do not configure this setting, a check for new security intelligence will not occur after service startup.
How can the bug be recreated?
ANSWER FROM GPT
Steps to Reproduce:
Open a PowerShell window with administrative privileges.
Execute the following command to create a registry entry that should disable the signature update at startup:
powershell
PowerShell -ExecutionPolicy Unrestricted -Command "reg add 'HKLM\Software\Policies\Microsoft\Windows Defender\Signature Updates' /v 'UpdateOnStartUp' /t 'REG_DWORD' /d '1' /f"
Verify the registry value by navigating to the registry path HKLM\Software\Policies\Microsoft\Windows Defender\Signature Updates and checking the UpdateOnStartUp value.
Note the value is set to 1 and confirm that a signature update check occurs at startup.
According to the documentation and reference link provided, this value should be 0 to disable the update check.
Expected Result:
The UpdateOnStartUp registry value should be set to 0 to disable signature update checks at startup.
Actual Result:
The UpdateOnStartUp registry value is set to 1, which incorrectly enables the update check at startup.
Description
The title
Promises to disable the signature update during startup, while the script has done it wrong.
In this line:
PowerShell -ExecutionPolicy Unrestricted -Command "reg add 'HKLM\Software\Policies\Microsoft\Windows Defender\Signature Updates' /v 'UpdateOnStartUp' /t 'REG_DWORD' /d '1' /f"
The correct data for value
UpdateOnStartUp
should be "0
" instead of "1
", as mentioned on the admx.help itself (the script on privacy.sexy uses this link as reference):Reference link used in privacy.sexy
How can the bug be recreated?
ANSWER FROM GPT
Steps to Reproduce:
Expected Result:
The UpdateOnStartUp registry value should be set to 0 to disable signature update checks at startup.
Actual Result:
The UpdateOnStartUp registry value is set to 1, which incorrectly enables the update check at startup.
Operating system
This script affects Windows users.
Script file
https://gist.github.com/femdiya/4cf86b54d3c3604b0267912fc9d92f2e
Screenshots
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: