Kaspersky Not Working, Updating or Scanning? Diagnose It Safely

Capture the symptom before changing Kaspersky

Open Task Manager and the Kaspersky main window if possible. Record the installed product and version, protection color, database date, active scan or update, process name, CPU, memory, disk use and how long the behavior lasts. A screenshot of those facts is more useful than “Kaspersky is slow.”

A first full scan can legitimately consume CPU and disk. A database update can create a brief network and processing burst. Windows itself may be indexing or updating at the same time. Watch for ten minutes, note whether progress changes and compare the same process after the task completes.

Restart once. Don't open a game, benchmark and three repair tools immediately after sign-in. Let Windows and Kaspersky settle, then reproduce the single action. If the issue doesn't return, verify protection and monitor rather than applying speculative fixes.

Community reports use names such as “Kaspersky Lab Launcher high CPU,” “scan stuck” and “Premium slows the mouse.” Those are useful symptom labels, not proof that one product-wide bug exists. A recent r/KasperskyLabs case that looked like Premium slowdown was eventually traced by the user to a connected hard drive. Hardware remains in the decision tree.

In the United States, failed updates require migration—not repair

Kaspersky’s US service statement says signature and codebase updates and Kaspersky Security Network operation stopped after September 29, 2024. An app that still opens can't be restored to full current US protection by changing DNS, reinstalling or buying a foreign code.

If the device is permanently used in the US, follow the US migration guide. Inventory Kaspersky and UltraAV, settle billing, choose a supported provider, remove the old app and verify Windows Security.

The remaining troubleshooting steps apply to supported markets with an active subscription and legitimate update path.

Kaspersky won't open or closes immediately

Kaspersky’s home-app launch article describes the interface appearing briefly and then closing after Windows updates or an operating-system malfunction. Its first instruction is a restart. If that fails, the documented path is a supported current reinstall, not a random DLL download.

1. Restart Windows and test once after startup settles.
2. Open Windows Security and see whether Kaspersky is still registered as the antivirus provider.
3. Check Installed apps for another third-party real-time antivirus or incomplete security trial.
4. Install pending stable Windows updates and restart.
5. Preserve the Kaspersky subscription and download the current installer from My Kaspersky.
6. If the interface still won't open, perform a normal uninstall, restart and official reinstall.

Don't end every Kaspersky service repeatedly in Task Manager or delete its folders. Self-Defense can block the action, and a half-removed driver is harder to repair. If an uninstall password appears on a work device, stop and contact the administrator.

Database update failed: read the error before resetting anything

Open Security → Anti-Virus Database Update or the equivalent, click the Failed status and read the report. Kaspersky’s March 2025 general update troubleshooting starts with performance settings, metered-connection limits, proxy, system date and time, DNS and access to Kaspersky’s update servers.

1. Confirm the subscription is active and the country is supported.
2. Correct Windows date, time and time zone, then retry once.
3. Check whether Windows marks the connection as metered and whether Kaspersky limits traffic there.
4. Disable an unintended proxy; don't disable the firewall or TLS protection globally.
5. Test DNS and ordinary access to the official update-server list.
6. Open Reports and save the named update error and time.

An interrupted update, caching proxy or third-party conflict can produce “Error verifying application databases and modules.” Kaspersky’s verification-error page says retry once, then reinstall if the same error returns. Repeatedly downloading unofficial database packages isn't a supported consumer fix.

My Kaspersky can also initiate database updates for some older supported products, according to its January 2026 remote update guide. That's a useful cross-check, not a substitute for repairing local connectivity.

A scan freezes or stops: find the object and the bottleneck

First decide whether the scan is frozen. A percentage can remain still while a large archive, disk image, virtual machine or slow external drive is inspected. Watch the scanned-object count, current path, disk activity and elapsed time. Record the last path before stopping the task.

Kaspersky’s scan task freezes or stops article covers Standard, Plus and Premium and names insufficient system resources and disabled iChecker/iSwift optimization as possible causes. Keep those technologies enabled unless support is testing a specific failure.

1. Retry a quick scan. If it works, the engine isn't universally broken.
2. Run a selective scan on the parent folder before the exact problematic object.
3. Check the target drive’s free space, SMART/health status and connection.
4. Close backup, sync and archive tools competing for the same files.
5. Update databases, restart and retry once.
6. If the same object always stalls, record it for support instead of broadly excluding its whole drive.

A scan that completes after many hours can still be impractical. Schedule full scans for powered idle time and use real-time protection plus targeted scans for routine work. Don't run a full scan every day just to prove the product is active.

High CPU, memory or disk: separate a task from a fault

Use Task Manager’s Details tab to identify the process and sort by CPU and disk. Then correlate it with Kaspersky Reports. High activity during installation, module update, first full scan or a newly connected drive is expected to be time-bounded. A process consuming resources for hours after every task finished is the real troubleshooting case.

Measure at idle for ten minutes after a restart, then reproduce one workload. Note CPU range, disk throughput, whether the laptop is on battery and whether the slowdown affects input, network or storage. A single one-second 80% peak is different from a sustained 30% that blocks work.

Kaspersky documents a performance option that postpones scan tasks when CPU and disk load are high. Its PC resource consumption guide places it under Settings → Performance settings → PC resource consumption in that generation. Menu labels can move, so search settings for “postpone” or “resources” rather than following an old screenshot blindly.

If the load begins when a particular drive is attached, test the drive. If it begins with a developer build folder, identify whether thousands of generated files are being rewritten. If it begins only in one browser, use the separate web and SSL troubleshooting guide.

Check antivirus overlap, storage and Windows before blaming one process

Open Installed apps for another third-party antivirus, web shield, corporate endpoint agent or incomplete trial. Two real-time engines can repeatedly rescan the same file or intercept each other’s network traffic. Keep one primary consumer antivirus.

Check Windows Update, Search indexing, cloud sync and backup activity. Task Manager can show the resource, Resource Monitor can show the file path. A failing HDD can make every security scan look like high CPU because the whole system waits on I/O.

Don't turn off Microsoft Defender through registry scripts. When Kaspersky is properly registered, Windows manages provider status. An unresolved warning in Windows Security is a signal to inspect the registration, not permission to disable the dashboard.

Compare performance expectations with the current independent results in our Kaspersky review. Lab scores describe controlled workloads; they don't prove that a particular disk, driver or application conflict can't exist.

Use safe performance settings before removing protection

Enable the “postpone scan tasks when CPU and disk systems are at high load” option if available. Schedule full scans for a time when the PC is powered and idle. Keep automatic database updates; postponing a heavy scan isn't a reason to age threat intelligence.

Use Gaming or Do Not Disturb behavior for presentation and full-screen periods, but verify it suppresses notifications rather than disabling protection. Pause a scan task when urgent work needs the disk, then resume it later. Don't leave File Anti-Virus, Web Anti-Virus, firewall or encrypted-connection scanning disabled.

Change one setting, reproduce the workload and record the result. Toggling six components at once can make the symptom disappear without revealing which security layer was lost.

A broad exclusion is usually the wrong high-CPU fix

An exclusion trades performance for inspection coverage. Never exclude Downloads, the whole user profile, browser data, temporary folders or an entire drive just because scans are busy. Malware also chooses those locations.

Use an exclusion only after you identify a known safe application or generated-data folder, reproduce the conflict and check the software vendor’s documentation. Make the path and process rule as narrow as possible, set a review date and remove it when the underlying issue is fixed.

For a suspected false positive, submit the file or hash through Kaspersky’s official OpenTIP portal and preserve quarantine. Don't restore a detected file merely because a second scanner was silent.

Reinstall only after preserving the subscription and evidence

Download the current installer from My Kaspersky before removing the existing app. Save the account-linked subscription and export settings only if they aren't suspected of causing the issue. Take screenshots of the error and Reports first; reinstalling erases useful local context.

Use normal uninstall, restart and reinstall from the official package. The complete uninstall guide reserves kavremover for failed standard removal because the tool deletes local license data and settings. A routine performance complaint isn't a reason to start with it.

After reinstalling, update databases and run a quick scan before importing settings. Test the original workload with defaults. If it works, reintroduce custom settings one group at a time.

What useful evidence looks like when you contact support

Provide product and version, Windows build, hardware, subscription region, exact time, process name, Task Manager screenshot, active Kaspersky task, report error, reproduction steps and every change already tested. State whether the issue survives a restart and a default-settings reinstall.

Kaspersky’s support center can request diagnostic reports or traces. Read the privacy disclosure and upload only through the official case. Don't send logs to a stranger in a forum or install a remote-control tool from an unsolicited reply.

A concise case is actionable: “21.xx on Windows 11, update fails at 10:42 with database verification error after retry; clock, DNS and proxy checked” beats “it never works.” Community discussion can help name a symptom, but only reproducible evidence can establish your cause.

Finish by proving protection and normal performance

Open Kaspersky and confirm green status, current database date and no failed task. Run a quick scan. In Windows Security, confirm Kaspersky is the single registered third-party antivirus provider. Restart once and repeat the checks.

Repeat the workload that originally exposed the issue and compare the same ten-minute measurement. Check browser, email, local printer and any VPN. If protection works but VPN alone is unstable, use the Kaspersky VPN review and troubleshooting section rather than reinstalling the antivirus again.

If the product remains unreliable, use the Kaspersky alternatives guide and cancel renewal through the merchant-first billing guide. A safe fix preserves protection; a safe exit replaces it before the old provider is removed.