Antivirus sometimes gets in the way of SOLIDWORKS Connected, read below to find out the exceptions that should be made for a successful install!
When should you implement exceptions to the antivirus?
Generally, it's a good idea to implement these exceptions before any installs occur. There are a lot of common issues we see involving installation-based errors that stem from the antivirus. For example, "Unable to retrieve install data" is the most common. Others may say "Failed to Install" or something similar. The tricky part here is most antivirus does not report killing or blocking these executables, so the simplest test is to just try to turn off the antivirus first, if it succeeds, then we know that the antivirus is the source of the issue.
However, we don't want to leave the antivirus off! We can add in exceptions step by step to see what works. There are some standard exceptions which are pretty much implemented on all users. There is also a list of advanced exceptions if these standard ones are not enough and you continue to be blocked after they are implemented.
Standard Exceptions
Any anti-virus that users install on their machines must not block 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".
They will also need to make an exception for this file location:
- C:\Program Files\SOLIDWORKS Corp
Advanced Antivirus Exceptions
If these exceptions are not enough, this is a further list of items that need to be allowed. The aforementioned exceptions are also listed here:
3DEXPERIENCELauncher.exe
- "C:\Program Files\Dassault Systemes\3DEXPERIENCE Launcher\3DEXPERIENCELauncher.exe"
3DEXPERIENCELauncherBackbone.exe
- "C:\Program Files\Dassault Systemes\3DEXPERIENCE Launcher\3DEXPERIENCELauncherBackbone.exe"
Necessary Executables for Connected/SOLIDWORKS UES ("Connector"):
- "C:\Program Files\Dassault Systemes\3DEXPERIENCE Launcher\3DEXPERIENCELauncherSysTray.exe"
- 'C:\Program Files\Dassault Systemes\SOLIDWORKS 3DEXPERIENCE\win_b64\USWC' or if UES: "C:\Program Files\Dassault Systemes\SOLIDWORKS 3DEXPERIENCE\win_b64\USWC\EdmServerV6.exe"
PLM Services:
- ENOPLMCSAClient.exe ("C:\Program Files\Dassault Systemes\SOLIDWORKS 3DEXPERIENCE\win_b64\code\bin\ENOPLMCSAClient.exe")
- ENOUSWCStart.exe ("C:\Program Files\Dassault Systemes\SOLIDWORKS 3DEXPERIENCE\win_b64\code\bin\ENOUSWCStart.exe")
- ENOUSWCStart2.exe ("C:\Program Files\Dassault Systemes\SOLIDWORKS 3DEXPERIENCE\win_b64\code\bin\ENOUSWCStart2.exe")
- CATSTART.exe ("C:\Program Files\Dassault Systemes\SOLIDWORKS 3DEXPERIENCE\win_b64\code\bin\CATSTART.exe")
Please also add an exception to this file location:
- 'C:\Program Files\Dassault Systemes\SOLIDWORKS 3DEXPERIENCE\win_b64\code\bin\.'
Add the following exceptions in trusted sites.
- dslauncher.3ds.com
- *.software.3ds.com
- *.3dexperience.3ds.com
- *.outscale.com
- *.3ds.com
Special Cases:
Below cases are not necessary to implement if you do not plan on utilizing this part of the software.
If you are installing Derived Output Converter:
- 'C:\Program Files\Dassault Systemes\B426DerivedFormatConverter\win_b64\code\bin'
- DOBatchLauncher.exe
Final Notes
We have an extended list of more advanced antivirus exceptions, but please reach out to us to confirm that you have attempted all of these first. Remember that there may be more than just the antivirus blocking these sites/executables, please check any software that may deny permissions to the user or block executables from running. If you are utilizing Active Directory, make sure that there is not a Group Policy blocking these as well.