Windows 10 Anniversary Build 1607 False Positive Finding

I've been working on pushing out the Windows 10 1607 build to some of our PCs. Because Microsoft has been having issues with 1607 and the cumulative updates, they've had to create multiple variations of those cumulative updates each month. In September and October I've noticed on our PCs with 1607 that I receive false positives after the newer CU is applied. Example:

KB111111 is released and applied to a PC.

Desktop Central scans the PC and all is well.

KB111112 is released to fix an issue with KB111111 and applied to PC.

Desktop Central scans the PC and reports that KB111111 is missing and that the PC is highly vulnerable.

Yet I can see in the PC history that KB111111 was applied successfully, but it's been superseded by Microsoft with the newer KB111112.

I'm currently using build 92113 of Desktop Central. Also, I update our patch database in Desktop Central every day, once in the morning and once in the afternoon.

Just an interesting, yet slightly frustrating, issue I've come across that requires me to manually check each PC to be absolutely certain everything is installed and secure as it should be.

Thank you,

Jennifer