While installing Xmanager I get an "Error 1935: An error occurred during the installation of assembly"

Owned by Support
Last updated: May 21, 2018
2 min read

While installing Xmanager Power Suite, you may see the following error: "Error 1603: An error occurred during the installation of assembly."

The 1935 error is not an Xmanager Power Suite error nor is it exclusive to Xmanager Power Suite. It mostly occurs during the installation of the Microsoft Visual C++ Redistributable package.


First, try rebooting Windows and then reinstalling Xmanager Power Suite. If that fails, the reason for the error may be one of the following:


  • The Microsoft Visual C++ Redistributable package file is deleted, corrupted, or improperly installed
    In this case, you'll need to reinstall the package. You can download the package directly from Microsoft here:
    https://www.microsoft.com/en-us/download/details.aspx?id=53840

  • Installation files corrupted by Antivirus Software
    Your antivirus software may flag Xmanager Power Suite installation files during installation therefore making it impossible to install Xmanager Power Suite. You'll need to turn off real-time scanning and try installing Xmanager Power Suite again.

    Note

    Xmanager Power Suite does not contain a virus. Certain antivirus programs are overly aggressive as a precaution.

  • Part of the WIndows File System or the Transaction Log is corrupted
    You'll need to run the command prompt as an administrator and then enter the following:

    fsutil resource setautoreset true C:\
    (Change C:\ to your installation drive as necessary)

    You can also check the system files by entering the following command:

    sfc /scannow

    Once the scan is complete, restart Windows and try installing Xmanager Power Suite again.



Most 1935 errors will fall into one of the above categories. However, other various circumstances can also cause users to see this error. If you've tried all the solutions listed above, the issue may be related to one of the issues below:
  • The Windows Event Viewer service is down
    If the Windows Event Log is not running, open the "Run" window and type "services.msc" and hit Ok. This will open the Services tool. Locate the Windows Event Log service and start it.

  • Adware causing a 1935 error
    Certain adware programs may cause a 1935 error. You'll need to either force quit the adware program or remove it altogether. Permanently removing adware is always recommended. After the adware program is removed, try installing Xmanager Power Suite again.