Patch Policy Shows as Successful, But Nothing Was Installed
When managing devices, you might notice that a patch policy is marked as successful, even though no software or updates were installed. This can occur due to the device reporting that no updates were necessary. Below, we’ll explain why this happens, how to interpret the logs, and steps to confirm the device status.
Common Symptoms
- Activity logs show a "successful" status, but no software or updates are visible in the installation history.
- Logs include entries such as:
Couldn't find update for [ID], skipping.
Nothing left to do.
Cause
This behavior is due to the Windows Update Package Manager determining that no updates are needed. Automox relies on this feedback to report the status as successful. Common reasons include:
- Updates are already installed.
- Updates are no longer applicable.
Analyzing Logs
When reviewing logs, look for key messages:
- "response":["0"]: Indicates no errors occurred.
- "Couldn't find update for [ID], skipping.": The update is deemed unnecessary or inapplicable.
- "Nothing left to do.": Confirms the policy completed its check.
Example log:
{"args":"\"[Update IDs]\"","response":"[\"0\",\"Installing MS updates: ...\\r\\nCouldn't find update for [ID], skipping.\\r\\nNothing left to do\",null]"}
Steps to Confirm
- Validate Update Status:
- On the device, open the update history (Windows: Settings > Update & Security > View Update History) to confirm whether updates are installed.
- For macOS or Linux, use the respective package manager or logs to review update activity.
- Verify Agent Status:
- Check the Automox console for the device status.
Next Steps
If the behavior persists and you suspect an issue with the agent or console, contact Automox Support with:
- Device Name/ID.
- Relevant agent logs for analysis.