search authority

Step‑by‑Step Guide to Disable Kaspersky Security Cloud in a Virtual Machine

By Elena Carter4 min read 316 views
Featured image for Step‑by‑Step Guide to Disable Kaspersky Security Cloud in a Virtual Machine
Step‑by‑Step Guide to Disable Kaspersky Security Cloud in a Virtual Machine

Why You Might Want to Disable Kaspersky Security Cloud in a VM

Running Kaspersky Security Cloud inside a virtual machine (VM) can be useful for testing, development, or isolating potentially unsafe software. However, there are scenarios where you need to disable it: performance testing without AV overhead, compatibility with certain development tools, or when the VM is used as a clean sandbox for malware analysis where the host's protection is sufficient.

More from this site

Keep reading the latest coverage

Browse latest →

Prerequisites Before You Begin

Make sure you have the following before attempting to disable Kaspersky:

  • Administrative rights on the virtual machine.
  • Access to the Kaspersky Security Cloud user interface.
  • A backup point or snapshot of the VM in case you need to revert changes.

Method 1: Disable via the Kaspersky Tray Icon

Step 1 – Open the Kaspersky UI

Locate the Kaspersky icon in the Windows taskbar (usually near the clock). Right‑click the icon and select Open Kaspersky Security Cloud.

Step 2 – Turn off real‑time protection

In the main window, click the Protection tab. Find the Real‑time protection toggle and switch it to Off. Confirm any prompts that ask for administrator permission.

Step 3 – Disable additional modules (optional)

If you need a completely silent environment, also turn off the following modules from the same Protection page:

  • Network Attack Protection
  • Web Anti‑phishing
  • Application Control

Each toggle works the same way—click to disable and confirm.

Method 2: Use the Settings Menu for a Persistent Disable

Step 1 – Access Settings

From the main window, click the gear icon (Settings) in the lower‑left corner.

Step 2 – Navigate to "Additional

In the Settings sidebar, select Additional → Self‑defence. Uncheck Enable self‑defence to allow other software to stop Kaspersky services.

Step 3 – Stop the Kaspersky Services

Open services.msc (press Win+R, type services.msc, press Enter). Locate the following services and set each to Disabled:

  • Kaspersky Security Cloud Service
  • Kaspersky Anti‑Virus Service
  • Kaspersky Endpoint Security Service

Right‑click each service, choose Properties**, set *Startup type* to *Disabled*, and click **Stop** if the service is running.

Method 3: Command‑Line Approach (PowerShell)

For automation or when the UI is unavailable, you can stop and disable the services via PowerShell:

Stop-Service -Name "klnagnt" -Force Set-Service -Name "klnagnt" -StartupType Disabled Stop-Service -Name "avp" -Force Set-Service -Name "avp" -StartupType Disabled

Replace klnagnt and avp with the exact service names displayed in services.msc for your version.

Verification: Confirm Kaspersky Is Disabled

After completing any method, verify that protection is off:

  • Return to the Kaspersky UI – the status bar should read "Protection is disabled".
  • Run Get-Service in PowerShell and ensure the relevant services show Stopped and Disabled.

If the VM still reports protection, repeat the steps or check for leftover scheduled tasks that reactivate the service.

Troubleshooting Common Issues

Service Restarts After Reboot

Some enterprise policies force Kaspersky to re‑enable on boot. Open Local Group Policy Editor (gpedit.msc) and navigate to Computer Configuration → Administrative Templates → Kaspersky. Set policies that prevent auto‑start, or remove the policy if you control the VM image.

Unable to Access Settings

If the UI is locked, boot the VM into Safe Mode (press F8 during startup). In Safe Mode, most security services are disabled, allowing you to change settings or uninstall Kaspersky entirely.

When to Re‑Enable Kaspersky

Even in a VM, leaving it unprotected can expose the host if the VM's network is bridged. Re‑enable Kaspersky before connecting the VM to external networks, or after completing performance‑critical testing.

Quick Comparison: UI vs. CLI Disable Methods

MethodProsCons
Tray Icon/UIVisual, easy for beginnersManual, not scriptable
Settings → ServicesPersistent across rebootsRequires admin rights
PowerShell CLIAutomatable, works on headless VMsNeeds exact service names
",

Editor's pick

Keep exploring our latest stories

Fresh reads, picked daily.

Browse latest
Share: