Search the Community

Hello everyone, I’d like to report a reproducible issue with Kaspersky VPN Secure Connection (App Store version 3.5.0, build 30500.79.14444486) on macOS 26.0.1 (Tahoe). The application freezes immediately upon launch and remains unresponsive until forcibly terminated. Observed behaviour After launching, the ksec_app process becomes stuck in a waiting state, as seen in macOS diagnostic reports: This means the app is attempting to connect to a non-existent or unresponsive XPC helper service (com.kaspersky.ksec.bl.resolver), resulting in a permanent hang. Technical background The App Store build registers an internal XPC service com.kaspersky.ksec.bl.resolver. On macOS 26 (Tahoe), Apple introduced persistent sandbox XPC restoration. Even if the related container or plist is deleted, launchd automatically restores the entry at next boot. Since the restored service no longer responds, the VPN UI (ksec_app) hangs on the XPC handshake stage and never completes initialisation. Workaround (confirmed functional) Quit the app completely: Remove the stuck resolver: Delete the sandbox containers: In Finder → Go → Go to Folder… → ~/Library/Containers/ Delete the folder com.kaspersky.ksec.bl.resolver manually, then empty the Trash. Relaunch the VPN. It starts and connects normally after that. (Optional: to prevent macOS from recreating the broken resolver after reboot, create an empty dummy file /Library/LaunchDaemons/com.kaspersky.ksec.bl.resolver.plist with no permissions.) Expected behaviour VPN should initialise its XPC connection dynamically on launch, without relying on persistent system registration that may be invalidated by macOS sandbox changes. Environment Component Version macOS 26.0.1 (Tahoe, build 25A362) Hardware MacBook Pro 16,1 – Intel i9 VPN 3.5.0 (App Store build) Distribution Mac App Store Reproducible Always, after restart Summary This appears to be a compatibility issue between the App Store build and macOS 26’s updated XPC sandbox behaviour. Manual cleanup and deregistration of com.kaspersky.ksec.bl.resolver restores normal functionality. Please forward this to the Mac development team for verification and patching. Best regards, M. Kurzdym, PhD (UK)

Hello everyone, I would like to report a reproducible issue with Kaspersky Password Manager (App Store version 10.3.1) on macOS 26.0.1 (Tahoe, build 25A362). The application freezes immediately upon launch, showing no UI response until forcibly terminated. Observed behaviour After launching, the process kpm_app becomes stuck waiting for a blocked XPC port: This indicates that the app is trying to connect to an unresponsive or missing XPC helper service (com.kaspersky.kpm.bl.resolver), which never responds — resulting in a total freeze. Technical background The App Store build registers an internal XPC service com.kaspersky.kpm.bl.resolver. In macOS 26 (Tahoe), Apple introduced persistent sandbox XPC restoration: even after an uninstall or container cleanup, launchd automatically recreates the service entry on reboot. When that restored service doesn’t respond, kpm_app waits indefinitely on an XPC handshake during initialisation. Workaround (confirmed functional) Quit the app completely: Remove the broken resolver service: Delete the sandbox containers: In Finder → Go → Go to Folder… → ~/Library/Containers/ Delete the folder com.kaspersky.kpm.bl.resolver manually, then empty the Trash. Relaunch Kaspersky Password Manager. The app now starts and synchronises correctly. (Optional: create an empty file /Library/LaunchDaemons/com.kaspersky.kpm.bl.resolver.plist with zero permissions to prevent macOS from resurrecting the broken helper on next boot.) Expected behaviour The application should initialise its XPC connection dynamically during launch instead of relying on a persistent launchd registration that can become invalid in new macOS sandbox environments. Environment Component Version macOS 26.0.1 (Tahoe, build 25A362) Hardware MacBook Pro 16,1 – Intel i9 Password Manager 10.3.1 (App Store build) Distribution Mac App Store Reproducible Always, especially after restart Summary This appears to be a compatibility issue between the App Store sandbox and macOS 26’s updated XPC system. Removing or resetting the com.kaspersky.kpm.bl.resolver endpoint resolves the problem entirely. Please forward this to the macOS development team for validation and patching in the next release. Best regards, M. Kurzdym, PhD (UK)

Hi. First time using kaspersky premium and I am still learning the ins and outs. How do I disable the feature of where kaspersky keep asking me for permission to allow apps to access registry? While I appreciate the security tightness, it get very tedious to click allow every time I boot my pc or launch an app that I know and trusted. Cheers! :D Picture below.

I'm trying to recover my keyboard, mouse, speakers, which aren't working after uninstalling kapersky. So i booted with kapersky rescue tool. But the tools option is just not showing I'm running windows 11 Please help, I've spent hours and hours on this with no luck this is 2024 kapersky rescue tool, the 2018 version was showing black screen on my laptop

While my computer is running, whenever I launch Kaspersky, within 5–10 minutes my screen turns black and then comes back after about 2 seconds. I tested this many times and confirmed that Kaspersky is the cause. The issue happens even if I am idle on the desktop, without running any other applications. System details: -Operating System: Windows 10 Home, Version 22H2 (OS Build 19045.6216) -Kaspersky version: 21.22.7.466(a) -GPU: NVIDIA GeForce GTX 1060 6GB -Driver version tested: Latest driver 581.15 WHQL, also tested older versions with DDU clean install = issue persists -I don't use any other security software -Kaspersky settings: Default -Background apps: None (to minimize conflicts, I closed all unnecessary apps) Here are the troubleshooting steps I've already tried: -Updated GPU drivers (tested both latest and older versions) -Used DDU to perform clean driver reinstallations -Verified Windows is fully updated -Verified system integrity with: . "sfc /scannow" . "DISM /Online /Cleanup-Image /RestoreHealth" . "chkdsk C: /f /r" -Hardware has been tested and confirmed working normally I'm attaching a screenshot of the Windows Event Viewer section related to the error. Although this part is in Turkish, I've added an English version below. Here: "The description for Event ID 153 from source nvlddmkm cannot be found. The component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer. If the event originated on another computer, the display information had to be saved with the event. The following information was included with the event: \Device\0000007f Error occurred on GPUID: 100 The message resource is present but the message is not found in the message table." Thank you for your attention and support.

I would like to thank Kaspersky team for the lightning quick reaction! The problem is solved, apparently it was a minor glitch and many other users were impacted. Thank you Berny! This topic can be locked now.

Dear Community We have a requirements on Kaspersky Embedded System Security for Windows When Application Control policy is applied: -- Group policy access should be denied -- Power-shell disable / no one can access power-shell. -- Registry & Control Panel access denied -- Portable application block *Please share the extension list which will be blocked by KESS (like, .exe, .bat etc) When Device Control policy is applied: Block all USB drive except keyboard & mouse & SATA drive except preinstalled HDD & DVD (if any). We want to know are these requirements can be complied by KESS and if complied how can we do that , how can we do the configuration any support articles available. Regards Ahnaf Tahmeed

Did you find a solution? I have the same problem. Clients receive a critical alert because KES is not working, and when trying to launch the application through KES, this error appears. When the client computer is restarted, the problem is resolved. However, I would like to resolve the issue causing KES to fail and stop. As shown in the attached image, out of almost 200 computers, four are experiencing the same problem. This occurs daily on different computers. If I restart these four computers now, tomorrow there will be other computers with the same problem.

Hello, Since two days ago I have seen that I can not start up the Battle.net application when Kaspersky is enabled. This has happened to other programs before, so I would usually add Battle.net to "Specify Trusted Applications" but this is where the second part of the issue happens. When I add the Battle.net launcher to the list, my Kaspersky would immediately crash. I have sent in a crash report when it happened, but I doubt that would help me with my immediate issue. I have run Windows update, Networking driver check and Kaspersky update but none have seemed to help. Could you please advise on what I can do to mitigate either part of this issue? Thank you.

How hard is it to give us an option to disable that very annoying popup? Your users have been suffering for years and have been asking for a way to get rid of the secure keyboard input popup while still having the feature ENABLED and working in the background, but things are the same even with your latest editions (Kaspersky Plus). I think whoever thought it was a smart idea to remind the user about it every single time shouldn't have the power to manage and develop your software. Im a paying customer since 2006 and I had to turn off this feature and live without it whenever it came out (it's definitely been 5+ years). I just moved to a new computer and I've been configuring my settings and guess I will still need to disable it and live without that feature for many years to come...

I found myself without a working keyboard or mouse after installing Kaspersky Free. LUCKILY, the mouse worked when I unplugged it since it's wired and wireless. I scoured the internet for a solution to my problem and quickly learned that has been an issue with Kaspersky since as early as 2016!? I saw that while keyboard input seemed, blocked, I was still able to communicate between PC and keyboard adjusting volume and opening calculator, for example. Moving forward, I tried uninstalling the devices multiple times and reinstalling them (after system restart), I tried modifying the registry, I tried running several different scans... ZERO luck. Then I thought, "Maybe disable Kaspersky?" Still nothing. I uninstalled, restarted, nothing. Windows troubleshoot was unable to fix my "driver error". I caved and called Kaspersky - this seemed promising since the rep sounded friendly! Alas, they told me the problem was not due to Kaspersky (I KNOW it was since that was the only significant change I made to my system), they could not help me and that I might need to contact Microsoft (ROFL, no)... Solution: Hold the shift key and restart the PC. Select a restore point from before installing Kaspersky. Wait about 10 minutes (will vary by system). Thanks for nothing, rep! ZERO effort. I hope you are shown this and not reprimanded, but at least LEARN to apply yourself to help customers. Call Ref #: 14316475

Advice and Solutions (Community Knowledgebase) Disclaimer. Read before using materials. This article is about Kaspersky Endpoint Security for Windows (KES for Windows) Description FDE precheck is a utility used for advanced Full Disk Encryption compatibility testing. It contains latest drivers which will be implemented in future KES releases. FDE precheck also collects diagnostic data used to fix compatibility issues. Inability to use laptop keyboard and\or touch-pad is one of the most frequently met issues. Using FDE precheck you can understand if compatibility issue was already fixed and will be included in next release or it should be addressed. You can download latest FDE precheck utility using following links: For KES 12+ - https://support.kaspersky.com/14328 System requirements Single operating system should be installed on the test machine, FDE Precheck can't properly function on a host with multiple operating systems. Use administrative account to run the utility. Read before proceeding Decrypt the test host and remove Kaspersky Endpoint Security and AES module. Do a backup of the critical data on the test machine. Follow the test sequence exactly as stated below. Do not manually stop the execution of the utility. The system will automatically restart several times, it is an expected behavior. Plug in laptop. Do not run test on battery. Failure to comply with steps above may lead to unpredictable consequences. Test sequence Make sure machine decrypted does not have KES or AES module installed not running any KL drivers has no critical data plugged in Reboot. Copy and unpack fde_precheck.zip archive. Run elevated fde_precheck.exe (either by right-clicking and choosing Run as administrator or by starting it from an elevated command prompt). If the program will not find any incompatibilities the following message box will appear: Press Yes, to initiate installation of the encryption drivers and initiation of the test. Wait for the automatic reboot, then login using the administrative user as was done earlier. Press OK on the pop-up that will appear shortly after the reboot: Press Yes in the UAC window if it will appear shortly after. Wait for several minutes (up to 10-15 minutes) until next automatic reboot will occur. Do not initiate reboot manually! It will be done automatically. Manual reboot at this stage may result in corruption of the OS. All preparations are run in background, it is normal that there will be no indication of activity on the desktop. After automatic reboot you will see the preboot agent, and it will require human presence to complete those tests. If possible, record the whole process on a camera of smartphone. You will be asked to enter random keystrokes using the keyboard and mouse. In case of successful keystroke registration you will see something like that: Just follow the instructions that will appear on the screen and press "NEXT >" when done with each test. In case FDE Precheck Preboot agent will fail booting or will freeze at some point, please take photo of the error message, or record the whole process on a camera and reboot the machine if necessary. OS will boot either way. Login using the administrative account that was used earlier. At this point drivers will be removed in the background and host will be rebooted one last time automatically. Wait for several minutes (up to 10-15 minutes) until next automatic reboot will occur. Do not initiate reboot manually! It will be done automatically. Manual reboot at this stage may result in corruption of the OS. All preparations are run in background, it is normal that there will be no indication of activity on desktop. The following three files are always created. All three files are mandatory to provide for analysis. fde_precheck_report.txt fde_precheck.log (will be located in the folder with fde_precheck.exe) Description of what have happened during tests (with screenshots and video if possible).

Hello, Thank You for Your reply. The article You’ve shared refers only to hardware and software requirements for macOS versions up to 15, while this report concerns a confirmed reproducible issue on macOS 26.0.1 (Tahoe, build 25A362). After detailed analysis, I’ve identified the exact cause — the new XPC handling in macOS 26 interferes with the com.kaspersky.kpm.bl.resolver endpoint. This results in Kaspersky Password Manager freezing immediately after launch. Removing or resetting that endpoint restores full functionality and stability. I would kindly ask You to forward this finding to the macOS development team so that it can be validated and patched in an upcoming release. Including this fix or a related note in the official documentation could also help other users who may experience the same issue.

Hi, I have Kaspersky VPN set to split tunnelling and to only work on Firefox. That's great, it works fine. However if I try and launch warcraft the game fails to connect. Why is this? It seems to imply as if split tunnelling is applying outside of just firefox. As soon as I close the VPN wow loads fine. Wow does not care about VPNs, other VPNs work fine on it so im a bit confused.

In certain cases, ‘Install updates and fix vulnerabilities’ task might fail with some error. Below example contains ‘Error verifying file signature’ error but you may use mentioned keywords and overall approach for investigation of other errors met while running ‘Install updates and fix vulnerabilities’ task. Here are some steps to investigate such problems: First of all view list of updates aimed at installation on client. For this purpose in network agent trace file search for ‘Update to install:’ without quotes. You will get results similar to: etc. Some of found updates are skipped by filters so pay attention to skipped updates and to overall number of updates that should be installed. Some updates might already be downloaded to the target system so at the second step identify which update files are already downloaded and which should be downloaded. In network agent trace file search for ‘is already downloaded’ and ‘needs to be downloaded’ without quotes. In our sample traces results are: Match code of update which needs to be downloaded (79ae03df-d6eb-4de2-b59f-37e963d7a69e) with results detected at step 1 and you will see that KB907417 needs to be downloaded. Open MS Update catalog and search for KB907417. In search results click ‘Download’ button and observe window with results: Name of archive containing required update KB907417 is: otkloadr_c87e2fe94dd873224afa65e2af2473ca3e307a37.cab Search for c87e2fe94dd873224afa65e2af2473ca3e307a37.cab in WindowsUpdate.log from client machine. Pay attention to the found lines: Search for otkloadr_c87e2fe94dd873224afa65e2af2473ca3e307a37.cab in administration server trace file to find URL used by administration server to download required update from MS servers: Now once we know the name of problem update you may offer the customer to temporarily exclude KB907417 from update installation task to let other updates to be installed. Then proceed with investigation. On Administration server use web browser to download problem update from the link identified at step 6 and make sure that its signature is valid. It should look like on below screenshots In case if Digital Signatures tab is not present in properties of this file or signature is invalid then try to re-download with disabled AV solution. If this does not help then make sure that no proxy/firewall affect this issue. Verify that MS certificates are up to date on KSC server. In MMC console / Software updates node right click on KB907417 and ‘Delete update files’. Try to launch updates installation task again. On client machine use web browser to download problem update using link identified at step 5. Verify its signature and proceed same way as in step 8. Additionally compare downloaded file with C:\WINDOWS\SoftwareDistribution\Download\48ec39650764ea7a46ebe67ecf3b6f47\OTKLOADR.CAB. Verify diginal signature of OTKLOADR.CAB You may use signtool.exe to verify signature of .cab files on server and client: signtool.exe verify /pa otkloadr_c87e2fe94dd873224afa65e2af2473ca3e307a37.cab The utility signtool.exe goes as part of Windows SDK. It is available at C:\<Path to Windows SDK>\<version>\bin\<build number>\x64\signtool.exe In case if digital signature appears to be correct then use standard recommendations for resetting WUA: net stop wuauserv net stop cryptSvc net stop bits net stop msiserver Rename folders Del "%ALLUSERSPROFILE%\Application Data\Microsoft\Network\Downloader\qmgr*.dat" net start wuauserv net start cryptSvc net start bits net start msiserver After resetting WUA launch ‘Find updates and critical vulnerabilities’ task. It might fail several times because WUA cache was cleared. So after getting error just re-launch task again. Once 'find updates' task completes successfully launch task to install updates and fix vulnerabilities (problem update should be included in task scope this time). Observe the results.

Hi, After installing Kaspersky I used quick scan after it my pc went black for 2/3 mins. Idk exactly. After that my pc restarted, but my mouse cursor disappeared even tho my mouse is on and same with my keyboard they both have rgb so I know that they are on, but aren't working. I can press any button, but it's not going to work. My mouse is Model O and the keyboard is Genesis Thor 150 After I saw this problem I thought maybe taking mouse usb and keyboards wire and putting them in would work, but nothing. Now I don't know what to do because I can't do anything I have another office mouse with a wire I put it in and still nothing the cursor just won't appear. I downloaded the best version of Kaspersky free trial please help me

@denacre Try to contact the Support Team, for quick assistance use the Chat.

Thanks. I was able to find it, though it was not that easy. Searching for "launch" did not return any results. Searching for startup has given 3 results. This settings is under: Settings (gear icon) / Performance settings / PC performance optimization / PC resource consumption Turning it off set Kaspersky Service 21.22 startup type to manual. And after I exit the App (from the notification area), it also the service as well.

Problem Some devices do not have keyboards, but still are detected with BadUSB. Step-by-step guide In order to allow them work properly use BadUSB on-screen keyboard, using other onscreen keyboards or physical ones is not recommended. To open BadUSB on-screen keyboard click on the highlighted text (example for Russian localization). Note that Prohibit use of On-Screen Keyboard for authorization of USB devices option should be turned off.

i am unable to launch any game apps while the program is active. After disabling it, i can launch it again. i have tried messing with the firewall but that doesn't seem to be the issue. How can i launch games while the program remains active

Welcome to Kaspersky Community. Find an option in Your KF settings called: Launch Kaspersky at computer startup, and manually disable it. Re-enable Self Defense. To run KF again manually, just do it via its K. icon.

I am not able to use expedia with secure keyboard. I am not able to type in the destinations under flight section as the system forces me to use Kaspersky secured keyboard for some reason! and that keyboard just doesn't work! Has anyone else faced this problem? even after disabling it from kaspersky privacy settings and restarting the browser, I am still struggling with this problem. Any solutions?

Hey everyone, Tonight when I search on Google via chrome, 3 times I’ve had below pop up, I’ve never seen it before: HEUR:Trojan-Clicker Script GhostPlugin.gen It tells me it’s a Trojan type and that the object is: https://youronlinesearches.com/script/r.php?a=3201&uid=52863x0000xzzz7. ZZZZZZZZZ However Kaspersky tells me that it has blocked the download each time, this while I’m on Google via chrome, I’ve never seen this before and the only sites I go on are legit ones. I have done a quick scan and it comes back with nothing found, Kaspersky tell me: Event: Malicious object detected User: ***** (I’m not inc this for privacy) Usertype: Initiator Application name: chrome.exe Application path: C:\Program Files|Google|Chrome/Application Component: Safe Browsing Result description: Detected Type: Trojan Can anyone help?

Hello @Pandonus, Welcome back! What happened - what errors show when Kaspersky Premium fails to update anydesk? Please look in Kaspersky Reports for any anydesk events & post back? Note - please post images in English - to convert the Kaspersky Gui to English - by pressing SHIFT + F12 on the keyboard; to revert press SHIFT + F5 on the keyboard. Are (you) able to update anydesk manually? *Note* when posting images to a public forum, for *your* privacy & security - please hide all personal information - for example - email address. Please post back? Thank you🙏 Flood🐳+🐋

Problem: Create Group On Demand Scan Task of Windows Kaspersky Light Agent 5.2/Linux Kaspersky Light Agent 5.2 Launch Group On Demand Scan Task Group On Demand Scan Task of Windows Kaspersky Light Agent 5.2/Linux Kaspersky Light Agent 5.2 might detect infected object, but might not delete it. Solution: Delete created Group On Demand Scan Task of Windows Kaspersky Light Agent 5.2/Linux Kaspersky Light Agent 5.2 Delete all created Windows Kaspersky Light Agent 5.2/Linux Kaspersky Light Agent 5.2 Policies Add registry key on Kaspersky Administration Server 5_2_ksc_win_x86_fix.reg if Kaspersky Administration Server is installed on x86 operation system 5_2_ksc_win_x64_fix.reg if Kaspersky Administration Server is installed on x64 operation system Create Windows Kaspersky Light Agent 5.2/Linux Kaspersky Light Agent 5.2 Policies anew. Create Group On Demand Scan Task of Windows Kaspersky Light Agent 5.2/Linux Kaspersky Light Agent 5.2 Launch Group On Demand Scan Task of Windows Kaspersky Light Agent 5.2/Linux Kaspersky Light Agent 5.2