DisplayLink/Winwing MIP display drivers fail after update to Windows 11 24H2

[GeneralDynamics]

Hey folks, I hope everyone has been well! I am not, unfortunately, so here I am:-) 

I run the Winwing MIP panels and displays and they had been working flawlessly under Windows 11 23H2, right up until I finally gave in to Microsoft's incessant nagging and installed Windows 11 24H2.

After the 24H2 install, the following occurs:

1. Simapppro comes up fine and sets all the displays to my defined configuration.

2. I start DCS (latest version), it logs me in and initialization begins.

3. When it is time for the DCS menu panel to be displayed, the screens all flash multiple times, DCS minimizes to the task bar, and my multi-monitor configuration reverts back to the default config with all the Winwing displays set back to landscape orientation. 

I keep daily image backups, so it is easy for me to revert back to 23H2, and when I do so, everything is perfectly fine again. I've gone through this exercise several times now, and each time, 23H2 GOOD, 24H2 BAD. Sigh.

 

Errors:  

From Event Viewer - 

I see 6 critical errors in all, with 3 of these for device WINWING USB 3.0 Display 1:

 

And 3 of these for device DisplayLink USB Device:

 

From the DCS log:

2025-02-24 01:13:14.294 INFO    DXGUI_WIN_ADAPTER (Main): ChangeDisplaySettings failed! Result is -2
2025-02-24 01:13:14.342 INFO    EDCORE (Main): (dDispatcher)enterToState_:1
2025-02-24 01:13:15.311 INFO    DXGUI_WIN_ADAPTER (Main): resize main window to [0, 0]
2025-02-24 01:13:16.056 INFO    DXGUI_WIN_ADAPTER (Main): ChangeDisplaySettings failed! Result is -2
2025-02-24 01:13:16.068 INFO    DXGUI_WIN_ADAPTER (Main): resize main window to [5376, 2160]
2025-02-24 01:13:16.157 INFO    DXGUI_WIN_ADAPTER (Main): resize main window to [0, 0]
2025-02-24 01:13:16.355 INFO    DXGUI_WIN_ADAPTER (Main): ChangeDisplaySettings failed! Result is -2
2025-02-24 01:13:16.377 INFO    DXGUI_WIN_ADAPTER (Main): resize main window to [5376, 2160]
2025-02-24 01:13:16.559 INFO    DXGUI_WIN_ADAPTER (Main): resize main window to [0, 0]
2025-02-24 01:13:16.739 INFO    DXGUI_WIN_ADAPTER (Main): ChangeDisplaySettings failed! Result is -2
2025-02-24 01:13:16.753 INFO    DXGUI_WIN_ADAPTER (Main): resize main window to [5376, 2160]
2025-02-24 01:13:16.850 INFO    UIBASERENDERER (Main): Cannot load font [C:\Program Files\Eagle Dynamics\DCS World\dxgui\skins\fonts\]!
2025-02-24 01:13:16.850 INFO    UIBASERENDERER (Main): Cannot create font [C:\Program Files\Eagle Dynamics\DCS World\dxgui\skins\fonts\] size 0!
2025-02-24 01:13:17.166 INFO    DXGUI_WIN_ADAPTER (Main): resize main window to [0, 0]
 

Microsoft's suggestion:

Contact the device manufacturer for further assistance.

Doesn't sound like a very good option for Winwing, Synaptic or DisplayLink based upon what I'm seeing in their support tickets I've reviewed, none of which are an exact match of this issue that I'm experiencing. 

 

So, this is where I am at this point, and 23H2 hits end of service on Nov 11th of this year. I do have some time to get this resolved, and I will try to open support tickets with Winwing and DisplayLink/Synaptic in the meantime.

Since this issue started, I've tried the following:

1. Installed the latest available Displaylink drivers from Synaptic.

2. Reinstalled 24H2 via the Windows Update option that allows this to be done while keeping installed apps. May try a clean install from scratch later, but that's going to be a ton of work that will likely not resolve the issue.  

3. Upgraded to the latest BIOS release for my Asus Maximus Z690 Hero.

4. Ran CHKDSK, Dism and SFC scannow commands to verify file and image integrity in 24H2 - all good.  

5. Spent many hours online searching for any other occurrences of this issue, no luck.

 

All that being said, what I'm asking of the community is if anyone else has experienced this issue? I went through the first 8 pages of DCS topics returned searching on "DisplayLink 24H2" and did not see a similar problem discussed.

Many thanks in advance if anyone has experienced this and has a solution.

I will set a Group Policy to block 24H2 from installing without my permission until I can get this resolved. 

Best wishes to all!

 

 

 

Edited February 24 by GeneralDynamics
Spacing for clarity

[Wostg]

Thanks for noting this so clearly and for reporting to WW/DL.

I thought something was off but had just put it down to usual complications.

All I can tell you at this stage is a) i use DisplayFusion to keep monitor profiles of where everything is placed / deactivate the MIPs when not playing. As of yesterday it was having trouble activating and rearranging the monitors to where they should be b) loaded up the hornet on a default WW configuration and the middle display wasn't showing. Assumed a usb issue and packed up for the day.

Edited February 24 by Wostg

[MustangSally]

15 hours ago, Wostg said:

Thanks for noting this so clearly and for reporting to WW/DL.

I thought something was off but had just put it down to usual complications.

All I can tell you at this stage is a) i use DisplayFusion to keep monitor profiles of where everything is placed / deactivate the MIPs when not playing. As of yesterday it was having trouble activating and rearranging the monitors to where they should be b) loaded up the hornet on a default WW configuration and the middle display wasn't showing. Assumed a usb issue and packed up for the day.

Only had the issue if placed the monitor connections randomly on the hub. Mine are now side by side on a USB3.1 powered hub. Not one issue since.

[Wostg]

Yeah they sit in the same hub they always do (need a good labelling but) and until yesterday, DF's profile swapper (activate/deactivate 3x MIPs) was working fine. Pending further tests it seemed like OP might be onto something.