Does anyone else get SR’s for failed patches for Google Chrome, but every time you check the machines the patch is already applied?
Question
Patch Management for Google Chrome
+4Hi there,
SysAid Copilot is here with our AI Magic!
Here is the response we thought might assist you:
SysAid Copilot is here with our AI Magic!
Here is the response we thought might assist you:
## Chrome patches show as “Failed” but are already applied
Yes—this does happen. Common causes and quick checks:
- Scan data is stale
- After a manual install or an auto-update by Chrome, Patch Management may still hold the previous scan result.
- Fix: Run a Full Patch Scan on the affected assets, then recheck the patch status.
- Assets > Asset List > Patch Management view > select devices > Full Patch Scan.
- Patch not deployed by SysAid
- If Chrome updated via its own updater or manually, SysAid may still list the patch as “missing” or mark the prior deployment as “failed.”
- Fix: Click “Apply approved patches now” once; often the items clear after the next scan.
- Agents can’t verify/download at deployment time
- You might see “agent could not locate the patch” or timeouts, but the endpoint updated later via another source.
- Fix: Ensure agents have access to vendor CDNs and GFI LanGuard sources, and that port 1070 is open if used in your setup.
- Policy/schedule out of sync
- Verify the policy includes Chrome, patches are approved, and scanning runs daily.
- Settings > Patch Management > Policies: confirm Chrome is included and the schedule is active.
- Version mismatch expectations
- SysAid’s catalog comes from GFI LanGuard. Occasionally Chrome releases outrun the catalog briefly; assets may self-update to a newer build than what the catalog expects. A rescan typically reconciles this.
Recommended workflow to clean up the noise:
1. Trigger Full Patch Scan on a few sample devices.
2. Review agent logs on one device that showed “failed”:
- C:\Program Files\SysAid\Logs\
- Look for entries around the deployment time (download errors, timeouts).
3. Confirm network egress to Chrome/GFI sources and no firewall/content filter is blocking downloads.
4. If the failures persist after rescans, enable debug logging on one device and retest, then review/upload logs.
If you want, tell me one asset name that shows “Failed” while Chrome is current, and I’ll outline exact log lines/indicators to look for and the next steps. If human assistance is needed beyond this, please open a Service Record so Support can review your logs and environment.
Yes—this does happen. Common causes and quick checks:
- Scan data is stale
- After a manual install or an auto-update by Chrome, Patch Management may still hold the previous scan result.
- Fix: Run a Full Patch Scan on the affected assets, then recheck the patch status.
- Assets > Asset List > Patch Management view > select devices > Full Patch Scan.
- Patch not deployed by SysAid
- If Chrome updated via its own updater or manually, SysAid may still list the patch as “missing” or mark the prior deployment as “failed.”
- Fix: Click “Apply approved patches now” once; often the items clear after the next scan.
- Agents can’t verify/download at deployment time
- You might see “agent could not locate the patch” or timeouts, but the endpoint updated later via another source.
- Fix: Ensure agents have access to vendor CDNs and GFI LanGuard sources, and that port 1070 is open if used in your setup.
- Policy/schedule out of sync
- Verify the policy includes Chrome, patches are approved, and scanning runs daily.
- Settings > Patch Management > Policies: confirm Chrome is included and the schedule is active.
- Version mismatch expectations
- SysAid’s catalog comes from GFI LanGuard. Occasionally Chrome releases outrun the catalog briefly; assets may self-update to a newer build than what the catalog expects. A rescan typically reconciles this.
Recommended workflow to clean up the noise:
1. Trigger Full Patch Scan on a few sample devices.
2. Review agent logs on one device that showed “failed”:
- C:\Program Files\SysAid\Logs\
- Look for entries around the deployment time (download errors, timeouts).
3. Confirm network egress to Chrome/GFI sources and no firewall/content filter is blocking downloads.
4. If the failures persist after rescans, enable debug logging on one device and retest, then review/upload logs.
If you want, tell me one asset name that shows “Failed” while Chrome is current, and I’ll outline exact log lines/indicators to look for and the next steps. If human assistance is needed beyond this, please open a Service Record so Support can review your logs and environment.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
