mirror of
https://github.com/amidaware/community-scripts.git
synced 2026-04-26 06:25:54 +03:00
[GH-ISSUE #268] Win_Antivirus_Verify.ps1 may falsly detect AV as disabled or not up to date if multipe instances of the same AV are installed. #319
Labels
No labels
enhancement
good first issue
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/community-scripts#319
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @SpookOz on GitHub (Feb 28, 2025).
Original GitHub issue: https://github.com/amidaware/community-scripts/issues/268
I've found that often when an AV updates itself, it leaves the old instance in the the security center. So often there are 2 instances with the same name displayName, pathToSignedProductExe and pathToSignedReportingExe but different instanceGuid. In these cases, this script seems to occassionally report one instance as being active, but the other as having updated defs. Therefor, it gives an error saying "There do not seem to be any active and / or up-to-date Antivirus! Please check the installed AV for issues."
May I propose an alternative script that combines instances with the same displayName and pulls the status from both?
@bbrendon commented on GitHub (Feb 28, 2025):
I don't think i've seen two from the same brand, but I know I've removed webroot and it still appears. What I've done is just wipe the AV center and reboot. It rebuilds itself.
@SpookOz commented on GitHub (Mar 3, 2025):
Yeah I've seen it with BitDefender and Vipre. Rebuilding sounds like a good method. How do you wipe the AV center?