SW2025 SP5 Confirmed bugs

I decided to skip SW2024 and jump to SSW2025 from our current SW2023.

SW2023 had some very annoying issues with PDM administration and our db apparently, also some very basic stuff in 2024 seemed quite broken the first time I tested it.

Now I started to do some very basic test before deploying 2025 and I will post here my findings, one reply one issue. If I found a solution I will edit the reply accordingly.


The first issue, happened almost immediately. I made a compressed admin image from scratch, around 6GB with the essential stuff we use (PMD, CAD, Simulation, Flow, Edrawings) , and when I started SW a “Login Manager error” popup welcomed me at the home screen in sw: pushing OK closes SW, ignoring the dialog and keeping it opened just works…

The issue is described below and seems related with SW connected (I think it is the current name of that thing) and 3DX. But we use a on premise PDM and I do not want to install 3DX components. To my surprise SOLIDWORKS Login Manager was installed along SW and PDM, but it is not in the software list of the administrative image and I tried to uninstall it but the error kept coming. Concerning that a client with an 3DX unrelated license Serial Number is installed 3DX ready(?) and it does not even works apparently. I looked into the KB, but no luck at the moment.

First confirmed bug.

The SOLIDWORKS PDM tab in the command manager cannot be edited or disabled and it is reset and activated every time SW is started if the PDM plugin is used.

BR10000401030

Closed (with SW2026…and thank you for your attention on the matter!)

SOLIDWORKS PDM Command bar always load as active tab and reloads in a new SOLIDWORKS Session after it has been disabled from the Command Manager
Portfolio / Domain: SOLIDWORKS Desktop / E-Apps
Product: SOLIDWORKS PDM
OS: Windows 10 64 bits
Detected level(s): SOLIDWORKS 2025 SP2
Platform: n/a
Description

Seen with SOLIDWORKS PDM 2025 SP0, Windows 11

Issue1: Command bar for SOLIDWORKS PDM always comes back and cannot be disabled.

1. Open SOLIDWORKS and load SOLIDWORKS PDM Add-In on startup and Create a new Part, assy or drawing.
2. Right Click on Tab on SOLIDWORKS Command Manager
3. Disable SOLIDWORKS PDM Tab
4. Close SW and reopen SW and create a new Part
5. Notice that SOLIDWORKS PDM Tab will still be active

Issue2: The Command bar for SOLIDWORKS PDM always shows as active tab, even if other tab is set active.

1. Open SOLIDWORKS and load SOLIDWORKS PDM Add-In on startup and Create or open a Part, assy or drawing.
2. Make a different command bar tab active, for example “Layout”.

3. Close the file, leaving Sw running.

4. Open another file, the previously “active” tab remains selected. OK.
5. Close SW session and start a new session.

6. Load file again - the SOLIDWORKS PDM command bar tab becomes the active tab again. NOT OK.

It should remember what tab was previously active.

Closure Information

Fixed in SOLIDWORKS PDM 2026 SP1. Fix is client side.

It has been a long time since last update. I have a quite a bunch of bugs and odd things happening.

I will make some placeholders here to keep track of the problems and update them later.

excerpt

When I use the SOLIDWORKS® PDM 2025 SP5 or 2026 SP0 software, what can cause the change state operation to remove the read-only flag on the locally cached file?
Portfolio / Domain: SOLIDWORKS Desktop / GOVERNANCE
Product: SOLIDWORKS PDM Professional CAD Editor Network
Platform: On Premise
Question

When I use the SOLIDWORKS® PDM 2025 SP5 or 2026 SP0 software, what can cause the change state operation to remove the read-only flag on the locally cached file?

Answer

In SOLIDWORKS® PDM 2025 SP5 and 2026 SP0, change state can leave checked in local files writable.

This issue occurs when a transition updates a file data card variable through a set variable action. SOLIDWORKS PDM leaves the locally cached and checked-in copy with the read-only flag disabled. For example, after approving a file.

This problem affects clients that use the SOLIDWORKS PDM 2025 SP5 or 2026 SP0 version. The issue resolves when you upgrade the client to SOLIDWORKS PDM 2026 SP1 or later version.

A client hotfix (HF) is available for the affected versions.

…

PLACEHOLDER

Drawings

with a weight variable called inside a block inserted in the sheet format every time the drawing is opened a warning pops up in the upper part of the screen telling the user a property in an annotation was modified. it can be suppressed until SW is closed and started again…

Drawings

Since 2025 layers can be assigned to center lines: this triggers a continuous line font when inserting a center line, instead of the dotted one expected.

{LINK to cadmunity thread}

Workaround is to set the template layer to nothing and allow the centerline to show properly when created.

For already created centerlines select and move them in the “follow the standard” (or whatever is called in english) category instead of a layer, drom the layer drop down.

Drawings

With no layer selected the manually created dimensions do not obey the color setting in system option, instead they take the “driven dimension” color when if the dimension is not driven.

DImensions imported with Annotation item are not affected, smart dimensions are.

Workaround is to move the dimension to a layer with a forced color, which is quite annoying since the previous centerline bug (a new feature!) with no layer assigned triggers this bug…

Edrawings

Vulnerability with remote code execution.

eDrawings Viewer EPRT File Parsing Out-Of-Bounds Write Remote Code Execution Vulnerability.
Portfolio / Domain: SOLIDWORKS Desktop / E-Apps
Product: eDrawings
OS: Windows 11
Detected level(s): SOLIDWORKS 2025 SP4.1
Platform: n/a
Description

eDrawings Viewer EPRT File Parsing Out-Of-Bounds Write Remote Code Execution Vulnerability.
Closure Information

THIS PROBLEM WILL BE FIXED ON SOLIDWORKS eDrawings 2026 SP1.1. A SOLIDWORKS eDrawings 2026 SP0 hotfix was implemented. Refer to QA00000442322.

just want to say thanks for highlighting this!

I was troubleshooting some odd behavior with our SWPDM and it is exactly this

save me from going down into rabbit hole :slight_smile: