1) Check the Troubleshooting section to see if any similar problems are described there.
2) Log in to the computer either locally or with remote desktop, and launch 0patch Console via the Start button. If you're on an enterprise account, click on SYNC NOW in the LAST SERVER SYNC box to make sure the next sync will not occur for 60 minutes, as that will revert any local changes you make to 0patch settings back to your settings in 0patch Central.
3) Disable 0patch Agent on the computer. Use the switch in the AGENT STATUS box of 0patch Console to disable the agent. Then try to reproduce the problem: if the problem is no longer there, re-enable 0patch Agent to make sure the problem is back. If this test confirms a connection between 0patch and the problem, continue to step 3.1, otherwise continue to step 4.
3.1) Identify the problematic patch. Disabling 0patch Agent effectively disables all patches, but it's probably just one that is causing the problem. In 0patch Console, open PATCHES -> RELEVANT PATCHES and disable the most recent one (the one with the highest ID), then see if the problem is still there. If this patch doesn't seem to affect the presence of the problem, keep it disabled and disable the next one - and so on until the problem has been resolved. At this point, keep the last patch disabled and start re-enabling other disabled patches while testing for the problem. You will end up with one or more patches than need to be disabled in order to resolve the problem.
3.2) Disable identified patches in 0patch Central (Enterprise users only). If you're on an enterprise account, login to 0patch Central and open the group with the affected computer. Under PATCHES for that group, disable the identified patch(es) to make sure they won't get re-enabled upon next sync. If you don't want to disable these patches for the entire group, create a temporary subgroup, move the affected computer to the new group, and disable patches in that group only.
3.3) Report the issue to email@example.com, explaining the problem and citing the patches you have identified. Note that we will want to reproduce the problem locally in our lab, so version numbers, download links (if possible), and system information will be appreciated. Do not perform any other steps listed below.
4) Remove 0patch from running processes. Even if you disable 0patch, 0patch library remains injected in running processes. To see if this is causing the problem (confirmed with some games and applications that use anti-tampering), temporarily uninstall 0patch Agent from the computer and see if the problem was resolved, then re-install and re-register 0patch Agent. (No computer restart will be needed for either.) If the problem was not resolved by uninstalling 0patch Agent, then 0patch can't be causing it. Otherwise continue to the next step.
4.1) Report the issue to firstname.lastname@example.org, explaining the problem in as much detail as you can. Note that we will want to reproduce the problem locally in our lab, so version numbers, download links (if possible), and system information will be appreciated.