Did you figure this out

This should help https://patchmypc.com/how-to-view-applicability-rules-and-troubleshoot-detection-states-for-third-party-updates. It’s about third-party updates, but the update status is the same across third-party or Microsoft updates.

i have a question maybe i want to clear, because i have an environment with a lot of computers with 5 missing updates and in fact when i check logs says me :missing update… but which the difference between not applicable or missing updates.

can you clear a little bit ?

thanks in advance
and greatly appreciate your videos..

I don’t have enough details to help here, unfortunately.

im glad finding yous pages and videos, i have a couple of questions i have an environment that i have a missing updates computers i have tried remediate it with fix update,wmi, reinstall client but at last i see on deployment logs status missing.

i deploye from primary server to 20 distribution points.

is there something that i am missing along the way?

thanks in advance

I see lot of machine under Unknown tab but they showing as

“Client Check passed/Active”
“Client Check passed/InActive”
“Client Check failed/Active”

They don’t go away, it takes them around 7 days. The machine are already reported to SCCM that this update is applied.

I’ve just gone through your videos again at a slower pace and after watching them a little more carefully I’ve managed to figure (to an extent) how they work. Thanks!

Hmm, yeah not sure I have anything that really covers using collections and WQL queries yet. Maybe this will help? https://docs.microsoft.com/en-us/sccm/core/clients/manage/collections/create-collections

Hey Frank,

Thanks for watching and the feedback! I’m hoping to get the next video recorded Thursday or this weekend at the latest. – Justin

your videos are awesome and I really learn a lot! Since this one is “already” two weeks old – any ideas when the next one will be released! Thanks in advance for creating such valuable content and keep up the good work…

Thanks Frank

That’s weird, you could try a policy reset using client center. A support case may be the best next step.

I should have added that the evaluation is not picked up as compliant after the restart and the scheduled rescan. At the rescan it sees them as still required, it reinstalls them all and restarts. The logs show this happening daily once the SW Update Deployment hits it’s installation deadline. I have run Microsoft’s latest WU Troubleshooting tool to no avail. I have also tried a complete uninstall and reinstall of client. I guess I was wondering if there was any need of ‘clearing’ WMI entries for update compliance to allow it to start fresh. Otherwise, I guess they just go in the bin for an OS refresh.

I generally see this when a restart is needed. You would need to do a restart then the next software update scan cycle should report the results back.

Sometimes, updates do install correctly but the evaluation of them does not seem to be picked up and the compliance status always remains required. Any suggestions for rectifying such a problem?