EdmServer.exe in SOLIDWORKS PDM: What It Is and High CPU Fixes

EdmServer.exe is a background process installed with the SOLIDWORKS PDM client. It is not a server in the SQL or archive server sense, despite the name: it runs on every workstation that has the PDM client and handles vault communication tasks in the background, such as notifications, login sessions and local cache work, so that Windows Explorer and SOLIDWORKS do not have to. It is safe and expected to see it in Task Manager. When EdmServer.exe uses high CPU or memory for a long time, the cause is almost always an add-in, a security product, a very large local cache or a connection problem, and all of those can be fixed. This article explains what normal looks like and how we troubleshoot it.

What is EdmServer.exe?

When you install the SOLIDWORKS PDM client (Professional or Standard), the setup places EdmServer.exe in the client installation folder, which by default is under Program Files in a SOLIDWORKS PDM folder. It starts with your Windows session and keeps running in the background.

Think of it as the client’s helper process. Explorer, the PDM integration in SOLIDWORKS and other client tools rely on it for work that should continue even when no vault window is open. In practice, administrators associate it with:

• Vault login sessions for the logged in Windows user.
• Notifications that pop up when a file changes state or is checked in.
• Background communication with the database and archive servers.
• Local cache housekeeping for the local vault view.

We deliberately keep this description at the level you can observe. The internal split of responsibilities between EdmServer.exe, Explorer and the other client processes is not publicly documented in detail, and it has changed over releases.

Is EdmServer.exe a virus?

The genuine file lives in the SOLIDWORKS PDM client installation folder, and its file properties should show a Dassault Systemes digital signature. If you find a file with that name somewhere else, for example in a temp or user profile folder, treat it as suspicious and involve your IT security team. On a normal PDM workstation, it is legitimate.

What normal EdmServer.exe behavior looks like

On a healthy client, EdmServer.exe sits near zero CPU most of the time. You will see short spikes when you:

• Log in to a vault.
• Browse into a folder with many files for the first time.
• Check in or get large assemblies.
• Receive a batch of notifications.

Memory use grows somewhat over a long session and should stay stable. What is not normal: sustained high CPU for many minutes with nobody working in the vault, memory that keeps climbing until the machine slows down, or Explorer freezing whenever you open the vault view.

Symptoms of an EdmServer.exe problem

The usual reports from users look like this:

Symptom	What users notice	Typical cause
High CPU	Fans spin, laptop slows, EdmServer.exe at the top of Task Manager	Antivirus scanning the vault view or cache, a looping add-in, a huge folder
High memory	Memory climbs through the day	An add-in leaking objects, very large result sets
Hangs	Vault view stops responding, then recovers	Slow or lost connection to the database or archive server
Stuck add-ins	Add-in menu items missing or add-in error dialogs	Add-in failed to load or is waiting on something
Explorer freezes	Windows Explorer stops responding in any folder	The PDM shell extension waiting on the client process

Safe troubleshooting steps

Work through these in order. The first steps are harmless and fix most cases. Save and check in your work before you start.

1. Log out of the vault and back in

Use the PDM icon in the Windows notification area, or the vault view, to log out of the vault, then log in again. This resets the session without killing anything. If the CPU spike stops here, it was likely a transient network or login issue.

2. End the process and let it restart

Close SOLIDWORKS and any Explorer windows showing the vault. Open Task Manager, select EdmServer.exe on the Details tab and choose End task. The client starts it again when you next browse the vault. If it does not come back, sign out of Windows and back in, or reboot. This clears a stuck state but does not fix a recurring cause, so if the problem returns within minutes, keep going.

3. Check add-ins in the Administration tool

Add-ins are the most common reason for EdmServer.exe misbehaving, because add-in code runs inside client processes and receives vault events. A badly written add-in that loops on a notification or holds COM objects can drive CPU and memory up.

In the Administration tool, expand the vault and open the Add-ins node. Look at what is installed, which versions and when each was added. Questions to ask:

• Did the problem start when an add-in was added or updated?
• Does it happen only for users in groups that trigger a particular add-in?
• Do users see add-in error dialogs or menu commands that do nothing?

You cannot disable an add-in for a single user from the client, so test on a non-production vault or with your VAR. For the most frequent add-in errors and what they mean, see common must-know SOLIDWORKS EPDM add-in errors and why “class not registered” happens when loading PDM add-ins.

4. Add antivirus exclusions

Real-time antivirus scanning of the local vault view and the PDM client’s cache is a classic cause of high CPU in EdmServer.exe. Every time PDM writes a cached file, the scanner reads it again, and both processes fight over the disk.

Work with your security team to exclude the local vault view folder, the PDM client cache and the PDM client processes, following SOLIDWORKS guidance for your version. Some endpoint products also intercept network traffic to the archive server and slow it down. Our essential guide to configuring security software with SOLIDWORKS PDM lists what to exclude and why.

5. Look for very large folders

A single folder with tens of thousands of files makes every listing expensive, on the client and on the server. If CPU spikes only when users open specific folders, the folder is the problem, not the client. Splitting large folders into a sensible structure and keeping file listings small helps everyone. While you are reviewing structure, it is worth reading why serial numbers and folder number ranges keep your vault fast.

6. Clear the local cache

Over years, a local vault view accumulates a large number of cached files. Clearing the local cache for folders you no longer work in reduces disk activity and the work the client does on startup. Use the clear local cache command from the vault view on the folders concerned. Never delete files from the local vault view folder directly in Windows while logged in, because the client tracks what it has cached.

If the local view itself is damaged, the clean fix is to remove the local view and recreate it with the View Setup tool. Make sure nothing is checked out first, otherwise local changes are lost.

7. Check server connectivity

If EdmServer.exe hangs rather than burns CPU, it is often waiting on the network. Check:

• That the workstation can reach the archive server and the SQL Server host by name.
• VPN or Wi-Fi users, who often see long timeouts.
• That the archive server service is running and not overloaded.
• Firewall changes on either side.

When several users report the same freeze at the same time, look at the servers before touching any client.

8. Match the client to the server version

Running a client with a different service pack than the server is a recipe for strange behavior. The PDM client should match the server’s major version and service pack. After a server upgrade, plan client upgrades for every workstation, including the forgotten machines on the shop floor and in the quality lab.

Problems with notifications

Because notifications are delivered through the client’s background process, notification problems often show up alongside EdmServer.exe symptoms. If users stop receiving notifications, or receive them late, the root causes overlap with what we covered above. Our SOLIDWORKS PDM notifications troubleshooting post goes through the notification specific checks.

When to escalate to your VAR

Escalate when:

• The problem happens on many machines after a server or client update.
• You have ruled out antivirus and add-ins and it still recurs.
• Explorer crashes rather than freezes, and Windows Event Viewer shows faulting modules from the PDM client.
• You suspect database performance problems on the SQL Server side.

Bring the details your VAR will ask for: client and server versions with service packs, the list of add-ins and versions, whether the problem follows the user or the machine, and the steps that reproduce it. That turns a long support call into a short one.

If an in-house add-in turns out to be the culprit, the usual fixes are releasing COM objects promptly, avoiding work inside high frequency events and not doing heavy processing in the client at all. Long running jobs belong in a task or a scripted process on a dedicated machine. This is one reason we moved many customer automations to PDMShell scripts that run outside the user’s client session.

FAQ

Can I disable EdmServer.exe?

Not if you want the PDM client to work properly. It is part of the client installation and is needed for vault sessions and background work such as notifications. End it only to reset a stuck state.

Why does EdmServer.exe use high CPU when I am not using the vault?

The most common causes are antivirus scanning the local vault view or cache, an add-in reacting to vault events, or a background connection retrying against a slow or unreachable server.

Is it safe to end EdmServer.exe in Task Manager?

Yes, as a troubleshooting step, after saving your work and closing SOLIDWORKS. The client starts it again, and signing out of Windows or rebooting also restores it.

Does EdmServer.exe run on the PDM server?

It is a client process. If the PDM client is installed on a server (for example to run tasks), it runs there too, but it is not the database or archive server service.

Need help with this?

If EdmServer.exe problems keep coming back, or you suspect an add-in, contact us. We review add-ins, vault structure and client setup, and we can move heavy automation off user workstations with PDMShell.