Yes, we are running on a license server and are all on the same version of SolidWorks (2022 SP5).
We do use a library of components (screws and various parts) accessible to everyone on the server.
For your information, 1h10 have passed since the beginning of the opening of the file:
It loads virtual parts well:
I'm repeating myself but => This Library also needs to be updated! Without forgetting to reload all the configurations if they exist, before saving in the new version of Solidworks (and... Yes, for each file.).
Ps: Is it normal that the names of your virtual parts in the temporary directory are called Copy(1), Copy(2), Copy(3) ...?
The library elements have been converted (all the configs).
For the copie(1), copy(2), copy (3) files of my assembly it is an assembly with several parts that come from the same base part.
Each part is virtualized during insertion. So SolidWorks names them copy(1), copy(2), ... in the construction tree
Hello
Small question but SWUtilities2016, wouldn't there be a ball in the installation?
SW puts them everywhere, don't you have two versions of SW installed on the same workstation?
On the workstation in question, there was SW 2018 which was uninstalled in 2022 to install SW 2021 and then SW 2021 was uninstalled in August to install SW 2022.
On the other hand, the file in question was made under SW 2021
Hello
Given the problem which seems complicated to solve (identification of the problem), I will go more on a formatting of the workstation and complete reinstallation.
At least it starts again on a totally clean configuration.
Uninstalling SW is never perfectly clean, even if only at the registry level. It can generate bugs all over the place and depending on how you went from Windows 10 to 11 it could also make SW unstable.
Otherwise I'm thinking of one last thing about Windows 11, it's a nutty bug that makes the computer not start at full power (CPU usage at barely 5% of its clock speed and suddenly SW lags like not allowed).
For my part I was forced to restart the workstation to have the right setting of the power options, so I ended up formatting the workstation and since then no more problems (I can tell you that a processor that caps at 1Ghz on SW is a horror)