You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi!
Have you got an idea, what could be the reason for the Ring0 file remained open after the app exit on some PC's ?
Thanks!
PS: Here's a way to reproduce this, using ZenTimings as an example, just to illustrate what some users came across:
Run ZenTimings
Search for the winring0 handle in a Process Explorer (from Sysinternals)
Close found handle
After you close ZenTimings, the file ZenStates-Core.sys is still in the app folder. The issue is that the WinRing0 handle no longer exists, and yet the explorer says the file ZenStates-Core.sys is opened elsewhere when you try to delete it.
I also couldn't find out the lock source, as no tool (system or 3rd-party) I tried were able to identify it.
My guess is this can be caused by the Ring0 driver crash on the user’s PC
The text was updated successfully, but these errors were encountered:
Hi!
Have you got an idea, what could be the reason for the Ring0 file remained open after the app exit on some PC's ?
Thanks!
PS: Here's a way to reproduce this, using ZenTimings as an example, just to illustrate what some users came across:
After you close ZenTimings, the file ZenStates-Core.sys is still in the app folder. The issue is that the WinRing0 handle no longer exists, and yet the explorer says the file ZenStates-Core.sys is opened elsewhere when you try to delete it.
I also couldn't find out the lock source, as no tool (system or 3rd-party) I tried were able to identify it.
My guess is this can be caused by the Ring0 driver crash on the user’s PC
The text was updated successfully, but these errors were encountered: