Reply to thread

Message

<blockquote data-quote="cofer123" data-source="post: 1034619" data-attributes="member: 92976">I had this happen many times before, not sure what&#039;s the cause.What usually happens is that when booting up, Windows hangs with a black screen right before showing the login screen. Only a reset solves it. After that, Windows boots normally, but then Kaspersky displays that message. If you reboot after that it usually works again.It happens randomly from what I could tell, sometimes working perfectly fine for months without issues (I shutdown my computer every day), but then there would be times when every day Windows would fail to boot because of that for like a week, only to later fix itself without my intervention.I would say this is Kaspersky&#039;s fault with its hypervisor. Something doesn&#039;t play nice with some driver or whatever, and it fails to initialize properly. After each failure, Kaspersky disables the hypervisor for the next boot, and shows that message. In fact, I don&#039;t really understand what&#039;s the point of Kaspersky Hardware Virtualization feature to being with. Kaspersky is vague on what benefits running their own hypervisor offers in terms of security, and since it doesn&#039;t even work if you have hyper-v enabled (something anyone running WSL2 has) then what&#039;s the point?</blockquote>

[QUOTE="cofer123, post: 1034619, member: 92976"] I had this happen many times before, not sure what's the cause. What usually happens is that when booting up, Windows hangs with a black screen right before showing the login screen. Only a reset solves it. After that, Windows boots normally, but then Kaspersky displays that message. If you reboot after that it usually works again. It happens randomly from what I could tell, sometimes working perfectly fine for months without issues (I shutdown my computer every day), but then there would be times when every day Windows would fail to boot because of that for like a week, only to later fix itself without my intervention. I would say this is Kaspersky's fault with its hypervisor. Something doesn't play nice with some driver or whatever, and it fails to initialize properly. After each failure, Kaspersky disables the hypervisor for the next boot, and shows that message. In fact, I don't really understand what's the point of Kaspersky Hardware Virtualization feature to being with. Kaspersky is vague on what benefits running their own hypervisor offers in terms of security, and since it doesn't even work if you have hyper-v enabled (something anyone running WSL2 has) then what's the point? [/QUOTE]

Verification