A more economic way is probably have a way to track all these patches, and have some sort of interface to allow quick and easy access to them.
Luckily, Microsoft maintains a list of all the patches in an Excel file that you can download here:
There are a lot of ways your exploit can fail, a bad gadget due to a change by a system update is easily one of them.
If this update occurred at a pretty early stage, chances are your exploit will fail a lot, too.
Checking patch levels is an important task for vulnerability research or exploit development.
This is typically done using a digital signature or some form of checksum.
These verification techniques ensure the patch hasn't been modified since the signature was applied or since the checksum count was calculated. Unfortunately, Microsoft occasionally releases unsigned code updates, and you may run into problems when using the automatic download and installation services of WSUS (Windows Server Update Services), Microsoft's patch management system for Windows Server 2000, Windows Server 2003 and Windows XP operating systems.
id=36982 If you prefer some sort of GUI for searching, you can use Security Tech Center's My Security Bulletins Dashboard.
Before installing any patch, verify its source and integrity.
By default, client computers check in with WSUS every 22 hours, but this is configurable.