3DEXPERIENCE SOLIDWORKS Connected - Antivirus Conflicts and Exceptions

This article summarizes the exceptions needed to properly run and install SOLIDWORKS Connected

Antiviruses can be helpful and harmful at the same time. While it may keep you protected from unwanted viruses, it can sometimes protect you from the things you want to do! This article is going to be useful to help you out in the case you're having an antivirus block the files you need to run the 3DEXPERIENCE Platform.

We have seen the most common conflict with SentinelOne Antivirus blocking critical files for SOLIDWORKS and SOLIDWORKS Connected users. This guide may also apply to other antiviruses as well.

For SOLIDWORKS Connected Users

Any antivirus that users install on their machines must not block or crash the two executables below, for 3DEXPERIENCE Launcher to function successfully:

  • “C:\Program Files\Dassault Systemes\3DEXPERIENCE Launcher\3DEXPERIENCELauncherGUI.exe”
  • "C:\Program Files\Dassault Systemes\3DEXPERIENCE Launcher\3DEXPERIENCELauncherBackbone.exe".

If these are blocked, you may receive the "Unable to Retrieve Install Data" error when attempting to install SOLIDWORKS Connected.

Advanced Connected Exceptions

If the two exceptions are not sufficient and you are still receiving the "Unable to Retrieve Install Data" error, add the following exceptions to your antivirus application for C:\Program Files\Dassault Systemes\3DEXPERIENCE Launcher\. 

  • 3DEXPERIENCELauncher.exe
  • 3DEXPERIENCELauncherBackbone.exe
  • 3DEXPERIENCELauncherSysTray.exe
  • DSYCommunicationHubLauncher.exe
  • 3DEXPERIENCELauncherGUI.exe

NOTE: You must restart your machine once the exception is added.

Then, add the following exceptions in trusted sites.

For Desktop SOLIDWORKS Users

You will need to make an exception for this location:

  • "C:/Program Files/SOLIDWORKS Corp."

Please see your antivirus documentation on how to create an exception for a file path or executable.

If left blocked, you may have one or two single users crashing SOLIDWORKS. The faulting module would be "InProcessClient64.dll". This error was hard to diagnose as a network-based error due to the fact that even if you have two identical PCs on the same network; one could be affected while the other unaffected.

If you are still having issues, please place a case on our support page here: https://cadimensions.com/support.