Since switching to Windows 11, I have noticed that auto login does not work the same way as it did under Windows 10.
Under Windows 10, when a user logged into their client, the BlueBerry icon appeared in the lower right corner after a few seconds, and immediately afterwards, a window opened in the middle of the screen showing the progress of the local cache update.
In W11, the BlueBerry icon only appears after the user has clicked on a file in the vault. Or, in our case, when they have started SWX, because we have stored some of the SWX settings in PDM.
But actually, the cache with the SWX system settings should already be updated before SWX is started. This worked in W10.
Has anyone else noticed this behavior since switching to W11? How can the behavior be forced to be the same as in W10?
I have already spent several hours on the phone with support, but have not found the cause of the behavior.
what version of win11 are you running? we saw no blueberry icon for a while on 24H2 before january windows update deployment, now it works.
there is a BR open that basically states it randomly happens due to multiple reasons. one of them is the explorer process running in an elevated state.
Try this (I am not at work so I am not 100% sure of the procedure I used to reproduce the issue when I reported to my VAR) :
ă»start windows and login
ă»wait for everything to load, if pdm dialog comes out close it
ă»open task manager and kill the edmserver.exe process and explorer.exe
ă»start explorer.exe again
ă»open the pdm install folder in program files and run edmserver.exe from there.
We have Win 11 Business 25 H2; operating system build 26200.7623 and Windows Feature Experience Pack 1000.26100.2750.
I think my problem is different from yours. I donât have the problem that the blue berry is not displayed. As soon as I open a file in the vault, the blue berry is displayed immediately. But only after I have accessed a file in the vault and not directly after logging in to the client.
win11 made a lot of changes in the explorer.exe process that pdm is based on.
It lead to multiple known issues that sw fixed client side with PDM patches and workarounds, but be aware that 2023 is going to be phased out support and you should not expect further fixes from DS. A bug that sometimes resurfaces was the current path in the explorer window truncated at the vault root. It was addressed with a hot fix, but since then we had some minor annoyances here and there, basically depending on the windows update mood⊠quite tragic.
That said we basically dropped AD logins, autologins, and login dialog suppression since they broke something in PDM.
dialog suppression was a new option in 2023, and it happens everytime since they do not test properly the software, it was bugged and blocked the cache synchronization as well.
I reported it and had an exchange with tor iveroth from pdm dev team that confirmed the bug and told us to just avoid using that option.
I am currently testing 2025 and some new pdm options are broken. Those errors are so blandant that I suspect nobody even tested them once. Old bugs seems fixed so far, but I am tired to play this hunt-a-bug game every single time we upgrade our systems.
Would you mind elaborating on the â2025 and some new PDM options are brokenâ comment? I am just starting the process of looking at upgrading to 2025 and would be curious to what you have found.
I have a post named sw2025 confirmed bugs on this forum.
Since I cannot access this site from my job, I have to update it when I have gathered all the info and I have time.
At the moment I am waiting for DS to release a BR so the post is still old. I am stuck at the preliminary test phase and found some minor annoyances, and it was only casual testing nothing too stressful, but enough to say DS did not care to even look at their new features onceâŠ
In SW2025 PDM, DS introduced a new pdm tab in the command manager: it is not customizable and it does not allow to be disabled from the UI. I manage our settings with the registry and that new feature just ignore the settings and reset itself every time sw is closed and reopened. Confirmed with a BR opened.
Another new feature broken is on the pdm addin, the lower part of the task pane on the right, where they put the latest revision version and another version variable showing by default, there is a setting to turn them off in the pdm option, but it just reset every time you close SW. I confirmed with my VAR that the entries in the registry are also ignored and forcing those parameters visualization off is not even possible.
Minor annoyances, but since we do not manage them in our vault they could be potentially confusing for our users.
The add or rename file and add or rename folder permissions has been splitted in two different settings: that is good, in theory, but I have to figure out how a new folder can be created without the rename permission, since the operation gave me an permission error when I tried to set a name for a folder I just createdâŠ
The answer is to not allow users to create folders except in places where creating them wonât cause problems. This may not be possible for your vault/users but if you can do it, it eliminates a lot of headaches. I have a distinct split in my vault. Project folders have a âWork In Processâ (WIP) folder and files have a WIP state. Inside that folder and in that state users can do whatever they like Add/rename/move/delete. Outside that, they can do almost nothing. Or the processes are automated to the point that they donât realize what they can do outside of WIP because they have no need to.
The project folder and all its subfolders (including the WIP folder) is created by a PDM template.
I am not in disagreement with you, but I inherited a folder structure with multiple engineering teams working on different kind of machineries. I was able to put some order, but there are some complicationsâŠ
At least I wanted to lock the root folders, but I have to set the folder creation permissions on every subfolder inside them.
templates could be handy, but they are not practical since there is not a shortcut in the toolbar and the template itself is not intuitive, especially for our engineering user group, because their data folders are located according to their design group and there is like a dozen of them.
GR-A-
GR-B-
GR-C-
and every group has a different approach in organizing their data in their sub folders.
They make completely different kind of things, for very different engineering fields, different design logic, and barely share catalog market parts and hardware in our vault.