Jump to content

Recommended Posts

Posted (edited)

Hi there

I don't why but I can't turn on Kaspersky hardware virtualization although I followed all the steps and did everything (I also enabled it in bios). I even turned off Windows Hyper-V and core isolation options (As they're visible in the attached images) and reinstalled Kaspersky but they didn't work neither. I assume that there's conflict or incompatible with new Windows 11 24h2 build. There wasn't any problem with 23h2 but again any solution for this?

1.png

3.png

2024-10-14_220116.png

2024-10-14_220525.png

Edited by karkas20
  • Like 1
Posted
1 hour ago, harlan4096 said:

 

Thank you

I read it,but doesn't work🫠

KasperskyUser13
Posted

Hi @karkas20 did you find a solution to this issue because i have the same problem.

Posted
11 hours ago, KasperskyUser13 said:

Hi @karkas20 did you find a solution to this issue because i have the same problem.

Hi

No

  • Thanks 1
Vitalik93
Posted

This problem has been around for many years... Here is decision:

1) Disable Self-Defense in Kaspersky settings.

2) Right-click the application icon in taskbar and click "Exit".

3) Find this registry key starting with "klhk" and change the "FailSafeMode" value there to 1 (see my screenshot).

4) Restart your PC and don't forget to turn on Self-Defense later!

 

 

Снимок экрана 2024-10-22 103957.JPG

Posted

Hello

Thank you

But doesn't work🫠

Igor Kurzin
Posted

Hi @karkas20, do you mind submitting a ticket to technical support via https://support.kaspersky.com/b2c and letting me know the incident number? We would like to collect some information for analysis. 

  • Thanks 1
Posted
8 hours ago, Igor Kurzin said:

Hi @karkas20, do you mind submitting a ticket to technical support via https://support.kaspersky.com/b2c and letting me know the incident number? We would like to collect some information for analysis. 

Hello There

My before ticket is number : INC000016921012

Posted
8 hours ago, Igor Kurzin said:

Hi @karkas20, do you mind submitting a ticket to technical support via https://support.kaspersky.com/b2c and letting me know the incident number? We would like to collect some information for analysis. 

BTW, I today install Kaspersky Standard and i do disable " Memory Integrity " and restart windows and Good works.

OS PC : Windows 11 21H2

Posted (edited)

Hello @karkas20

It sounds like you've done a thorough job of troubleshooting the issue with Kaspersky hardware virtualization. Since you suspect there may be a conflict with the new Windows 11 24H2 build, it's possible that either the new build is introducing compatibility issues, or another feature is interfering with virtualization.

Here are some additional steps to try in case any were missed:

1. Check Windows Security Core Isolation (Memory Integrity) Again

Sometimes, even after disabling the memory integrity feature, the change doesn't fully apply. Make sure:

  • Memory Integrity is still off in Device Security > Core Isolation Details.
  • Restart your system again after disabling to ensure changes are applied.

2. BIOS Settings

Since you have enabled virtualization in BIOS, make sure the following are configured properly:

  • Intel VT-x/AMD-V is enabled.
  • Intel VT-d (if present) is enabled.
  • Secure Boot is disabled temporarily, as sometimes it causes conflicts with hypervisor-based software.

3. Disable Hyper-V Completely Using Command Prompt

Even after turning it off from the UI, Hyper-V can still leave residual components that interfere with other virtualization technologies. To disable Hyper-V completely, run the following command in an elevated Command Prompt:

Copy code
bcdedit /set hypervisorlaunchtype off

After running the command, reboot your computer and try enabling hardware virtualization in Kaspersky again.

4. Disable Windows Sandbox or Windows Subsystem for Linux (WSL)

If you have Windows Sandbox or WSL enabled, they might conflict with hardware virtualization. To check and disable them:

5. Try Kaspersky's Technical Support With A Ticket

If all of the above steps don’t resolve the issue, it may indeed be related to an incompatibility with the new Windows version. Contacting Kaspersky technical support could help, especially if they have a patch or workaround for the issue.

By ensuring all possible conflicting services are disabled and confirming with Kaspersky about 24H2 compatibility, you should be able to get hardware virtualization working again. Let me know how it goes!

Thank you

Edited by KarDip
Kaspersky is compatible with 24H2
  • Like 1
  • Thanks 1
Igor Kurzin
Posted
14 hours ago, karkas20 said:

Hello There

My before ticket is number : INC000016921012

@karkas20

Thank you for the provided information, we are on it. Will keep you posted of the progress.

@KarDip

Kaspersky for Windows is compatible with 24H2. The issue with virtualization is treated as a high priority bug, not a compatibility issue. 

Regardless of the virtualization problem, also please note, that Location Services need to be enabled for Smart Home Monitor to function correctly. More information: 

https://support.kaspersky.com/help/Kaspersky/Win21.19/en-US/283105.htm

  • Like 1
Posted
8 hours ago, KarDip said:

Hello @karkas20

It sounds like you've done a thorough job of troubleshooting the issue with Kaspersky hardware virtualization. Since you suspect there may be a conflict with the new Windows 11 24H2 build, it's possible that either the new build is introducing compatibility issues, or another feature is interfering with virtualization.

Here are some additional steps to try in case any were missed:

1. Check Windows Security Core Isolation (Memory Integrity) Again

Sometimes, even after disabling the memory integrity feature, the change doesn't fully apply. Make sure:

  • Memory Integrity is still off in Device Security > Core Isolation Details.
  • Restart your system again after disabling to ensure changes are applied.

2. BIOS Settings

Since you have enabled virtualization in BIOS, make sure the following are configured properly:

  • Intel VT-x/AMD-V is enabled.
  • Intel VT-d (if present) is enabled.
  • Secure Boot is disabled temporarily, as sometimes it causes conflicts with hypervisor-based software.

3. Disable Hyper-V Completely Using Command Prompt

Even after turning it off from the UI, Hyper-V can still leave residual components that interfere with other virtualization technologies. To disable Hyper-V completely, run the following command in an elevated Command Prompt:

Copy code
bcdedit /set hypervisorlaunchtype off

After running the command, reboot your computer and try enabling hardware virtualization in Kaspersky again.

4. Disable Windows Sandbox or Windows Subsystem for Linux (WSL)

If you have Windows Sandbox or WSL enabled, they might conflict with hardware virtualization. To check and disable them:

5. Try Kaspersky's Technical Support With A Ticket

If all of the above steps don’t resolve the issue, it may indeed be related to an incompatibility with the new Windows version. Contacting Kaspersky technical support could help, especially if they have a patch or workaround for the issue.

By ensuring all possible conflicting services are disabled and confirming with Kaspersky about 24H2 compatibility, you should be able to get hardware virtualization working again. Let me know how it goes!

Thank you

Thank you for help,But doesn't work

3 hours ago, Igor Kurzin said:

@karkas20

Thank you for the provided information, we are on it. Will keep you posted of the progress.

@KarDip

Kaspersky for Windows is compatible with 24H2. The issue with virtualization is treated as a high priority bug, not a compatibility issue. 

Regardless of the virtualization problem, also please note, that Location Services need to be enabled for Smart Home Monitor to function correctly. More information: 

https://support.kaspersky.com/help/Kaspersky/Win21.19/en-US/283105.htm

Thank you

  • Thanks 1
Posted (edited)
17 hours ago, karkas20 said:

Thank you for help,But doesn't work

Thank you

 

17 hours ago, karkas20 said:

Thank you for help,But doesn't work

Thank you

Hello @karkas20

Okay try this also.

If enabling Location Services didn't solve the issue with Kaspersky's Smart Home Monitor or hardware virtualization, let’s try some additional steps to narrow down the problem. 


1. Ensure No Hypervisor is Running

Even if Hyper-V appears off, virtualization features might still be blocked. Let’s ensure no hypervisor or virtual components are running.

  • Open Command Prompt (as Administrator) and run:
    Copy code
    systeminfo | findstr /i "hyper-v"
     
    If the result shows Hyper-V requirements are enabled, it indicates a hypervisor is still active. If so, run:
    Copy code
    dism /online /disable-feature /featurename:Microsoft-Hyper-V-All /norestart
    Reboot your system.

2. Disable Virtualization Conflicts via Group Policy

  1. Open the Local Group Policy Editor by typing gpedit.msc in the Start menu.
  2. Navigate to:
    Copy code
    Computer Configuration > Administrative Templates > System > Device Guard
  3. Disable:
    • Turn On Virtualization Based Security
  4. Reboot your system and try again.

3. Check for Hidden Virtualization Software (VMWare/VirtualBox)

  • If you’ve ever installed VMWare, VirtualBox, or other virtual machine software, ensure they are uninstalled or disabled as they can conflict with Kaspersky's virtualization.

4. Reinstall Kaspersky with Clean Install

  1. Uninstall Kaspersky using Kaspersky Removal Tool to ensure no leftover files or settings remain:
  2. After rebooting, download the latest version of Kaspersky and install it again.
  3. Check for any pending updates in Kaspersky after installation

Let me know if anything improves!

Thank you

Edited by KarDip
correction
  • Like 1
  • Thanks 1
shadowtabby144
Posted
On 10/23/2024 at 5:37 AM, karkas20 said:

Hello

Thank you

But doesn't work🫠

 

Heyo,

 

I am having the same problem with 24H2 as well.  Clean install.

  • Thanks 1
Posted (edited)
6 hours ago, KarDip said:

 

Hello @karkas20

Okay try this also.

If enabling Location Services didn't solve the issue with Kaspersky's Smart Home Monitor or hardware virtualization, let’s try some additional steps to narrow down the problem. 


1. Ensure No Hypervisor is Running

Even if Hyper-V appears off, virtualization features might still be blocked. Let’s ensure no hypervisor or virtual components are running.

  • Open Command Prompt (as Administrator) and run:
    Copy code
    systeminfo | findstr /i "hyper-v"
     
    If the result shows Hyper-V requirements are enabled, it indicates a hypervisor is still active. If so, run:
    Copy code
    dism /online /disable-feature /featurename:Microsoft-Hyper-V-All /norestart
    Reboot your system.

2. Disable Virtualization Conflicts via Group Policy

  1. Open the Local Group Policy Editor by typing gpedit.msc in the Start menu.
  2. Navigate to:
    Copy code
    Computer Configuration > Administrative Templates > System > Device Guard
  3. Disable:
    • Turn On Virtualization Based Security
  4. Reboot your system and try again.

3. Check for Hidden Virtualization Software (VMWare/VirtualBox)

  • If you’ve ever installed VMWare, VirtualBox, or other virtual machine software, ensure they are uninstalled or disabled as they can conflict with Kaspersky's virtualization.

4. Reinstall Kaspersky with Clean Install

  1. Uninstall Kaspersky using Kaspersky Removal Tool to ensure no leftover files or settings remain:
  2. After rebooting, download the latest version of Kaspersky and install it again.
  3. Check for any pending updates in Kaspersky after installation

Let me know if anything improves!

Thank you

Thanks for the help and follow up, but it didn't work

On build 23H2 i do only disable " Memory Integrity "and kaspersky good works

4 minutes ago, shadowtabby144 said:

 

Heyo,

 

I am having the same problem with 24H2 as well.  Clean install.

I think this bug only with new build 24H2 and we can only wait for It was fixed by Kaspersky

Edited by karkas20
Posted (edited)
17 hours ago, karkas20 said:

Thanks for the help and follow up, but it didn't work

On build 23H2 i do only disable " Memory Integrity "and kaspersky good works

I think this bug only with new build 24H2 and we can only wait for It was fixed by Kaspersky

Hello @karkas20

Yes i agree you tried just about everything possible so you best wait for Kaspersky BUG fix well done.

Thank you

Edited by KarDip
Posted
17 hours ago, shadowtabby144 said:

 

Heyo,

 

I am having the same problem with 24H2 as well.  Clean install.

Hello @shadowtabby144

We know  that Kaspersky has encountered issues with hardware virtualization on Windows 11, especially with the recent 24H2 update. As you know  seems to be affecting many users, and the root of the issue likely lies in compatibility between Kaspersky’s virtualization drivers and the Windows 11 hypervisor changes or security features in the latest build.

Did you try this?

Current Workarounds for the Kaspersky Virtualization Bug on Windows 11

  1. Ensure Complete Hyper-V and Virtualization-Based Security (VBS) Shutdown

    • Disable Hyper-V using:
      Copy code
      bcdedit /set hypervisorlaunchtype off
    • Disable Virtualization-Based Security (VBS) through Group Policy:
      • Open Group Policy Editor (gpedit.msc).
      • Go to Computer Configuration > Administrative Templates > System > Device Guard.
      • Set Turn On Virtualization Based Security to Disabled.
  2. Reinstall Kaspersky in Compatibility Mode

    • Uninstall Kaspersky completely using the Kaspersky Removal Tool.
    • Reinstall the latest version but use Compatibility Mode (try Windows 10 compatibility) to mitigate any OS-specific issues.
  3. Check for Kaspersky and Windows Updates

    • Kaspersky may release updates to address this compatibility issue with 24H2, as they frequently patch critical compatibility bugs. Force an update check in Kaspersky.
    • Ensure Windows Update is set to automatic in case Microsoft releases a hotfix for this issue.

Thank you

  • Like 1
  • 4 weeks later...
shadowtabby144
Posted
On 10/25/2024 at 8:27 PM, karkas20 said:

Thanks for the help and follow up, but it didn't work

On build 23H2 i do only disable " Memory Integrity "and kaspersky good works

I think this bug only with new build 24H2 and we can only wait for It was fixed by Kaspersky

Heyo,

 

Okies thank you.

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now


×
×
  • Create New...