WinRing0 cleanup, after move to PawnIO #90
-
|
So with 1.36, ZenTimings moved over to a different driver, what clean-up should we do to get rid of whatever old driver ZenTimings was using? I read the ReadMe, so is it just the InpOut64 driver that should be removed? I'm on a 64bit system, of course. Thank you. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
|
Hello, Unfortunately, the InpOut driver is still needed and used, only WinRing0 is removed and replaced with PawnIO. Previously, WinRing0 was extracted in the directory app as |
Beta Was this translation helpful? Give feedback.
-
|
You can also check if the service is still there. It can happen if more than one app is using it at the same time and the app that is closed last does not remove the service (legacy code). Open a Command Prompt as Administrator
sc query WinRing0_1_2_02 Stop the service sc stop WinRing0_1_2_03 Delete it sc delete WinRing0_1_2_0Some of these might fail if it is being used at the moment. Normally, if it had been properly cleaned up, you should not see any matches in step 1. If some of the steps fail, e.g. service can't be stopped, it is best to reboot the machine and then try again. |
Beta Was this translation helpful? Give feedback.
Hello,
Unfortunately, the InpOut driver is still needed and used, only WinRing0 is removed and replaced with PawnIO. Previously, WinRing0 was extracted in the directory app as
ZenStates-Core.sysand removed on each app close. If you still have it as a file, then you can safely remove it. You can also removesettings.enc,iv.bin,key.binfiles which were used to store AGESA version and to prevent easy manipulation. You can also removeWinRing0.LICENSE.txtor any other file that starts withWinRing.