Classic KAV Module - 7 Steps To Troubleshoot Installation Failures


1)    Check to see if the install was successful but script timed out before verification

  •  After a failed install check the end point for the avp.exe process and the Kaspersky Service.  Sometimes the install script will time out and show a failure when the install was actually successful.  If you find KAV process and service present run the Install> Verify Install and see if it shows as installed.

2)    Remove any previously installed (or failed installs) AV products

  • The new version of KAV now has an uninstall option – Install> Install> Advanced Options – “Uninstall prior A/V”. Kaspersky will try to uninstall any other anti-virus software that it finds”.  If the install fails and won’t verify, check to make sure all components of previous AV are removed. Look for log “avpsetup.rpu” in C:\kworking\kav\”.  Open file with text editor and see if it names any conflicting AV software. (i.e. “Kaspersky Endpoint Security 10 for Windows Setup cannot be performed, because some third-party application is already installed on the host: McAfee Anti-Virus File System Filter Driver. To run the installation please remove third-party software using Microsoft Windows tools”)
  • If removing locally with Add/Remove Programs does not work try the vendor provided removal tool.  Many are listed here:
  • Components of a failed KAV install can prevent a new install attempt.  This includes old KAV files if this is a reinstall. It may be necessary to run the Kaspersky removal tools here:  Also make sure the working directory KAV folder (usually C:\kworking\KAV and the C:\Program Files\Kaspersky Lab folder is deleted

3)   Run agent updater then attempt new KAV install

  • Before attempting another install make sure the Kaseya agent is up to date by running the agent updater with the force enabled (Agent> Upgrade Version> Update Agent then check the box “Force update even if agent is at version –” and run it.)

4)    Check to see if there are any stuck scripts

  • Check to see if any stuck scripts are preventing the KAV install script from running.  Agent procedures are run in order and stuck scripts will prevent new scripts from running (Agent Procedure> Manage Procedures> Agent Procedure Status or KLC> Agent Data> Pending Procedures) Cancel any stuck agent procedures. Reboot machine then run the agent updater first before you reschedule the scripts.

5)   Is KAV asking for a reboot?

  • See if KAV is asking for a reboot (Anti Virus> Show> Machine at top Column Sets> Reboot Required).   Unfortunately if KAV is asking for a reboot, the flag can only be reset if the machine is rebooted through KAV – (Anti Virus> Show> Machine at top Actions> Reboot).

6)    Are your credentials set?

  • Check the credentials (if added) on the Agent> Configure Agents> Set Credentialspage.  Make sure the Test will result in Passed. By default the agent will use the system account for credentials. This is often enough for the agent to function.  However if incorrect credentials are added, nothing will run.

7)  Test Installer Manually

  • If you still cannot get the install to work try running the install file(C:\kworking\KAV\kes10win_x64.msi or _x86 if 32-bit) manually.  If you can’t complete the install manually, this will let you know if the Installer is working – i.e. “Windows Installer service could not be accessed”.
  • If KAV successfully installs, try to use the Connect Install or Repair install to get it to show in the Kaseya portal, and if those fail, try a new Install/Update (reboots will probably be required).
  • Note: Manual KAV Installations are not supported by the VSA.

8)  If still unsuccessful gather any relevant data (log, GSI report) and open a support ticket

  • Finally open a ticket with support.  Include what you have done and attached the KAV log (C:\kworking\KAV\ kav_install.log).  Run the GSI report


Have more questions?

Contact us

Was this article helpful?
2 out of 3 found this helpful

Provide feedback for the Documentation team!

Browse this section