Strange... the first critical update you mention is for every version of windows up to 7x86. there are other x86 update you list as well. Do you have win7 x64?
Do it’s definitely the 32 bit version as you can see from this screen shot
https://s32.postimg.org/wql9u2eid/Untitled3.png
edit:
ohh wait... whats this?
Windows Malicious Software Removal Tool - June 2016 (KB890830) <--- this applies to ALL version of windows. If it doesn't apply to you... I don't know what would. I wonder if it says that if its already installed.
What ??? The Windows Malicious Software Removal Tool - June 2016 (KB890830) wasn’t one of the Critical Updates or Recommended Updates that where being flagged as not applicable to my system that was simply one of the patches that appeared on windows update after I was done patching my system with Autopatcher.
I provided the list of updates that where showing up on windows update after patching with Autopatcher in case Whatacrock missed them and needed to update the windows7 patch list.
I think possibly you may have misread my post sorry if there was any confusion.
If you haven't, update AP to 6.2.6 - see releases list.
As you will see from this first screen shot I’m already running the latest version
https://s31.postimg.org/uqaho8t4r/Untitled1.png
Can you confirm kb2872339 is infact installed? If it is, can you compare the detections in the apm to your system and post your findings. Please see, after updating to 6.2.6, if AP shows kb2872339 in Blue.
As you can see from this screen shot when I run the patch installer manually windows tells me it’s installed already however the same patch is still black in the autopatcher interface so for what ever reason autopatcher isn’t detecting that its already installed.
https://s32.postimg.org/yqv09sbkl/Untitled2.png
In case you were unaware (I don't know what releases you've downloaded), there's a .NET Framework x86 release, and the Common release should have the MSRT KB890830 tool you want.
Ahh I only downloaded Autopatcher for Windows 7 sp1 (x86) didn’t realise that the updates for .NET Framework where under a separate release I though that the .NET Framework x86 release simply downloaded the redistributable for the different versions of .NET Framework.
AP does - see the top lines of the ap.log file but, this isn't always the only detail that matters with updates. There are, however, ways to make the apm(s) more precise but to do so requires so many variables. AP hopes that users will also be as proactive as possible, and know that certain updates don't apply to their system -- maybe the update targets the OS but also a software version that the user isn't running.
Again, maybe better Titles & Descriptions would help but users would need to actually highlight and read each update's info and know they can uncheck or leave unchecked certain updates.
I'm not directing this to you, this is just an observation of the difficulty with dealing with a user base whose systems are vast and unique. AP is not for the hands-off user, these users need to use MU/WU to patch their systems.
Ahh right I had though that such a thing would be relatively straightforward but obviously its not quiet so simple, as a possible alternative would it be possible to have autopatcher simply inform the user when a patch can’t be installer?
Because when you run the patch manually it tells you when it can’t install the patch and why it can’t install it aka the patch is not applicable for your system or the patch is already installed or there was some sort of error, so I’m wondering if it would be possible for autopatcher to capture and display that feed back to the inform the user if/when there is a problem.