P2723QE, Latitude 5530, DDM 2.3 not launching properly
P2723QE monitor and Dell Latitude 5530 laptop. A few months ago the DDM stopped launching properly. The problem occurred on Windows 10 and persists on Windows 11 after recent upgrade.
As admin and regular user, I tried un/reinstalling both 2.3 versions listed here
Double clicking DDM.exe shows Display Manager in Task Manager for a couple seconds and then it disappears
Starting DDM.exe from command line behaves the same as double click. No additional output is shown on console
No errors appear in the install.log (DDM.exe does not launch following installation either)
What else can I try here? I can't find and exit code/message anywhere.
They are connected using a USB-C cable only. There are two USB-C ports on the Latitude 5530 and I've tried them both. I just tried going back (uninstalling first) to 2.2.0.43 and the behavior is the same; I can see DDM for about 1 second in Task Manager and then it disappears.
I guess it could be something is detecting and ending the DDM process. I will follow up with local IT (this is a work machine) to see if this software needs to be approved somewhere. That possibility would make sense, considering it just stopped working a couple months ago.
IT says no monitoring they have would kill a process, just reports violations. I made my way into the Windows event log and found this:
Application: DDM.exe CoreCLR Version: 6.0.3124.26714 .NET Version: 6.0.31 Description: The process was terminated due to an unhandled exception. Exception Info: System.Exception: C:\Program Files\Dell\Dell Display Manager 2\Newtonsoft.Json.dll is not signed with trusted CA at DDM2._0_UX.App..ctor() at DDM2._0_UX.App.Main()
An expired certificate would also line up with it abruptly stopping recently
The untrusted cert issue has various posts on the web suggesting manual installation work-arounds. Since that isn't the best choice for a work machine, I found that reverting all the way back to 2.1.0.45 seems to work.
At some point recently there was an auto-update and that broke things for me. It's entirely possible that I opted to update the Display Manager and didn't notice it stopped working until later since I do not use it every day.
Either way - there's something wrong with the certificates in versions >2.1.0.45
I am having the same problem on my work computer. I call install, but not run DDM because the ddm.dll is not signed.
I can use the older version provided and it will run, but it does not have the KVM features I need.
Initially I installed DDM version 2.3.x. But it would not launch. I see that the security policies prevented the launch of the application (and rightfully so) because the DLL was not signed.
I can successfully run 2.1.0.45, but again it does not have the KVM features.
Happened to me again. IT pushed a windows update which finds a newer version of DDM. I again reverted back to 2.1.045 (still had it in Downloads). This time I went into DDM and clicked the little gear for the Apps "Update" settings. There I UNchecked "Automatically notify when update is available", maybe that will keep it out of the drag net of window's update-all.
sundaymtn
1 Rookie
•
6 Posts
•
2 Points
0
1
Posted July 3rd, 2024 14:05
also tried to interact at the CLI level
no visible response from any of these commands