-
Notifications
You must be signed in to change notification settings - Fork 270
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
call to set_hvm_event() returns not success #4
Comments
Sorry for late reply. This usually happens in three cases:
Try:
Let me know if this solves your problem. |
no other hypervisors are running. its a clean vm installation. i tried cleaning up all services etc even got a new vm installation |
Do you have any more details? Every user that reached to me on Discord that had this same error code managed to fix by following those steps. Did you make sure VT-x/AMD-v is enabled on guest? Are you using a newer version of klhk.sys? What's your Windows version? I'd like to try reproducing this issue. |
can you add me on discord so we can solve this faster if you got some time flushin#9408 |
Unfortunately I'm not adding people on Discord anymore because I've got a lot of friend requests from people that want me to sell pay-to-cheats, fix their cheats and also annoying me in general. I know that this is not your case but I prefer not adding people on Discord anymore. I tried to reproduce your issue with different Windows 10 versions but I couldn't get an error code, except when registry had wrong information. |
我也是 |
-1073741661 = set_hvm_event() |
Did you follow the same steps as I said above? |
i reinstalled my vm and followed these steps except i dont understand what you mean by cleanup registry information |
Down new sys。 it is ok |
i downloaded latest kaspersky antivirus and checked the driver timestampand its the same as the one provided in here. and same hash. its the same file so it won't make a difference edit: seems like i had the old driver sitting there and kaspersky installer didn't finish installing due to some conflicts with malwarebytes lmfao. anyways i am getting the new sys now and trying but im thinking that solution should work. |
Did it work or not? I'm curious to see the results. |
OP didn't post any updates so I'm assuming he solved his issue. I'm closing the issue now. |
Update: OP told me on Discord that he got his issue solved by getting a newer driver. |
Could you provide more info on the new driver like the sign time and version? I am also having this problem and I tried using the newest driver to no avail. |
Well I've talked to some people that had the same issue and this is what seems to work: 1- Delete KasperskyHook service (make sure registry information is properly removed) Make sure that there are no other hypervisors running and virtualization is enabled by system firmware. |
SHA256 of working driver on Win10 19044.1645: 3433F5BB9AB3B33E862AAB2C1D565115E3E4B5F2D3CB7610B109FB2502F05031 I also disabled virtualization based-security using |
I couldn't load successfully on 19045 |
You need to get the latest klhk.sys in order to make it work for your windows version. Kaspersky uses hardcoded indexes for win32k syscalls so if you have an unsupported windows version everything else is going to fail. |
i tried using the project with virtualization enabled on my vm / main pc
the kaspersky hypervisor is loaded i checked the service.
but when calling
return NT_SUCCESS( set_hvm_event() );
this returns false because set_hvm_event() doesnt return STATUS SUCCESS it returns: C00000A3 (STATUS_DEVICE_NOT_READY) sometimes returns C000090B.edit: driver is also signed i am using a cert.
https://guidedhacking.com/threads/kasperskyhook-hook-windows-system-calls.16030/post-98821
same error as this guy ^
except i have virtualization enabled
The text was updated successfully, but these errors were encountered: