How To Upgrade SolidWorks: The Definitive Engineering Guide
Upgrading SolidWorks requires a methodical approach involving system compatibility verification, license server updates, and local client installation to prevent data corruption and downtime. Executing a clean deployment ensures your CAD environment supports new performance enhancements, enhanced drawing detailing modes, and updated file format standards without interrupting active engineering workflows.
Essential Preparation and System Requirements
Transitioning to a newer major release of SolidWorks involves significant changes to core architecture, database schemas, and graphics driver dependencies. Neglecting preliminary compatibility checks often leads to installation halts, licensing failures, and file translation errors across multi-user environments. Establishing a standardized upgrade checklist guarantees that hardware, operating systems, and network assets align with Dassault Systèmes minimum specifications before initiating setup routines.
- Essential Equipment and Software Assets: Administrator access to all target workstations, local administrative rights on the SolidNetWork License (SNL) server, valid serial numbers for the target release, and installation media or downloaded administrative image files matching your exact service pack.
- Mandatory Prerequisite Knowledge: Comprehensive understanding of local vault permissions (if utilizing SolidWorks PDM), backup protocols for customized templates, design libraries, macro folders, and familiarity with the SolidWorks Installation Manager interface.
- Estimated Budget and Duration Benchmarks: Zero direct software cost for active subscription contracts, but allocate approximately two to four hours of IT administration per server and 45 to 90 minutes per individual client workstation, depending on network speeds and local drive storage types.
Step-by-Step SolidWorks Upgrade Workflow
Step 1: Audit System Requirements and Operating System Compatibility
Verify that your workstation hardware, specifically the central processing unit (CPU), RAM capacity, and graphics processing unit (GPU), meets or exceeds the certified hardware matrix provided by Dassault Systèmes for the target year version. Navigate to your system settings and confirm that your Windows operating system build matches the supported versions for the new SolidWorks release, as unsupported Windows updates will cause the Installation Manager to block the upgrade process.
Warning: Attempting to install a new major version of SolidWorks on an uncertified graphics card or obsolete Windows build will result in viewport instability, rendering glitches, and frequent application crashes during assembly manipulation.
Step 2: Backup Custom Files, Templates, and Vault Data
Locate and back up all customized enterprise data before touching the installation media. Copy your custom drawing templates, sheet formats, weldment profiles, library features, Toolbox configurations, and design tables to a secure, isolated network directory. If your organization utilizes SolidWorks PDM, coordinate with your vault administrator to create a full SQL database backup and archive file snapshot prior to upgrading the PDM server components.
Step 3: Upgrade the SolidNetWork License (SNL) Server
If your organization utilizes floating network licenses, you must upgrade the SolidNetWork License Manager before updating any client machines. Log into the designated license server, download the latest SNL Manager utility matching your target SolidWorks version, and uninstall the legacy license manager. Install the new license manager, input your updated serial number, and activate the license over the internet or via email to ensure client workstations can check out licenses upon their respective updates.
Pro-Tip: Always upgrade the SNL server at least one full version ahead or concurrently with client machines; newer SolidWorks clients cannot pull licenses from older license managers, but older clients can temporarily pull licenses from an upgraded server during staggered rollouts.
Step 4: Execute the Client Installation via the Installation Manager
Launch the SolidWorks Installation Manager on the target client machine by running the setup executable from your administrative image or extracted media files. Select individual installation or administrative image deployment, input your upgraded serial numbers, and carefully review the product selection summary to include or exclude specific add-ons such as SolidWorks Simulation, Motion, or Electrical. Allow the Installation Manager to automatically remove older prerequisite components, install the updated core files, and prompt for a system reboot upon completion.
Step 5: Verify Post-Installation Performance and File Integrity
Reboot the workstation, launch the newly upgraded SolidWorks application, and navigate to the options menu to confirm the correct version and service pack are displayed. Open a legacy complex assembly and a detailed multi-sheet drawing to verify that external references resolve correctly, graphics hardware acceleration functions smoothly, and custom templates load without missing annotations or broken parametric links.
Help! How to properly update Keyshot scene from Solidworks? | GrabCAD ...
Hardware and Version Compatibility Matrix
| Component Category | Minimum Specification | Recommended Enterprise Standard | Upgrade Action Required |
|---|---|---|---|
| Operating System | Windows 10 (64-bit) | Windows 11 (64-bit) Pro/Enterprise | Verify OS build compatibility via hardware matrix |
| Processor (CPU) | 3.3 GHz or higher clock speed | 4.0+ GHz Intel Core i7/i9 or AMD Ryzen | Ensure single-core performance benchmarks match load |
| Graphics Card (GPU) | Dedicated CAD-certified GPU | NVIDIA RTX A4000 / AMD Radeon Pro W6600 | Update certified GPU drivers post-installation |
| System Memory (RAM) | 16 GB | 64 GB or higher ECC RAM | Expand physical RAM for large assemblies (>500 parts) |
| Storage Drive | 500 GB SATA SSD | 1 TB NVMe M.2 Solid State Drive | Maintain minimum 20% free space for virtual memory |
Common Upgrade Failures and Field Fixes
Symptom: The Installation Manager halts unexpectedly with a fatal error citing failed prerequisite installations such as Microsoft Visual C++ Redistributable or .NET Framework.
- Root Cause: Corrupted Windows Installer cache or pending operating system updates blocking prerequisite package execution.
- Actionable Fix: Clear all pending Windows updates, restart the machine, manually download and install the required Microsoft .NET and C++ runtimes from official sources, and re-run the SolidWorks Installation Manager as a local administrator.
Symptom: Client workstations launch successfully but fail to pull a license, returning a network communication timeout error.
- Root Cause: Firewall blocking TCP/IP ports 25734 and 25735, or the license server service failed to start after the SNL upgrade.
- Actionable Fix: Open the Windows Services manager on the server, ensure the SolidNetWork License Manager service is running, and configure inbound/outbound firewall rules on both the server and client to permit traffic through ports 25734 and 25735.
Symptom: Custom Toolbox parts, hole wizard standards, or design library components disappear or revert to default factory settings after the upgrade.
- Root Cause: The new installation pointed to a default local Toolbox directory instead of referencing the shared enterprise network database.
- Actionable Fix: Open SolidWorks System Options, navigate to the Hole Wizard/Toolbox configuration menu, browse to your backed-up network Toolbox folder path, and execute an upgrade on the database using the Toolbox Configuration tool.
Frequently Asked Questions
Can I run multiple versions of SolidWorks on the same computer?
Yes, Dassault Systèmes permits side-by-side installations of different major SolidWorks releases on a single workstation. This allows engineering teams to validate custom add-ons and complete active legacy projects on an older version while simultaneously testing the new release environment.
Do files saved in a newer version of SolidWorks open in older versions?
No, SolidWorks files are not backward compatible. Once a part, assembly, or drawing is saved in a newer major release, it cannot be opened in previous versions of the software. Organizations must implement strict file management and project transition cut-off dates to prevent data lockout across external supply chains.
How do I deploy SolidWorks upgrades across multiple network workstations simultaneously?
Administrators should utilize the SolidWorks Administrative Image creation tool. By configuring a centralized administrative image package on a server share, IT departments can push silent, automated installations to hundreds of client machines simultaneously via group policy objects (GPO) or enterprise deployment software.
What happens to my custom macros and user interface settings after an upgrade?
User interface customizations, keyboard shortcuts, and macro file paths may reset if the user settings migration fails during the initial setup. Always use the Copy Settings Wizard utility prior to upgrading your software to export and save all user profile preferences into a single backup file for instant restoration.
Streamline Your Enterprise CAD Deployment Today
Mastering the SolidWorks upgrade process safeguards your intellectual property, prevents costly production delays, and unlocks advanced modeling capabilities for your engineering team. Plan your deployment meticulously, back up all critical enterprise assets, and contact our technical specialists today to schedule an expert-led software migration assessment.
