Hey,
I am looking at previous machines that are having error receiving monthly windows patches via bigfix. Each month we repush the windows update because it states “Complete” in the baseline action but we still see it pop up as a vulnerability on Qualys. When we push out the patch separately to the machine it states “fixed” with the exit code 2. but we still see it pop up in Qualys stating it didn’t receive that months window patch.
Exit code 2 - Windows Encountered and Unknown Error
There are two things:
- its not BigFix generated exit code, exit code are being generated by the process whichever you are running.
- You need to locally check & fix whatever patch is failing with exit code 2
1 Like
In these situations you need to be looking at the client logs, windows event logs and, if the patches are the monthly CU then logs such as cbs.log and/or dism.log on affected machines to gain better insight into possible installation issues (e.g. was the patch running and the user powered off at the same time). The type of patch also comes into play as monthly CU (MSU type of patch) can behave differenlty and have different dependacies than .NET or Office updates. CBS corruption seems to be an issue on the increase for some but as for the root cause, now thats the real question.
1 Like