0patch is a true gentleman and knows its place. When a Windows update is applied that brings an official fix for a vulnerability which was previously fixed with our micropatch, the micropatch automatically stops getting applied. Windows update typically replaces the vulnerable module with a corrected executable that has a different cryptographic hash - and because of that, the micropatch won't get applied to that module anymore. (There are exceptions, like our BlueKeep micropatch.)
In other words, Windows Updates are unaffected by 0patch, and the user doesn't have to do anything before or after applying Windows Updates.
This is also true for updating other Windows applications. For instance, if there's a micropatch for a vulnerability in the latest version of Adobe Reader and Adobe issues a new, fixed version of Reader, you simply apply that update and our micropatch will automatically become obsolete on your computer. In case you later re-install the vulnerable Reader version for any reason, the micropatch will just as automatically start getting applied again.