Framework 16 Win 11 graphics module usb-c display out to usb-c capable monitor

[William_Winn]

Hello, I searched the community and didn’t find a solution so may I ask; Does anyone know why my USB-C display output on my graphics module will not send a signal to my USB-C capable monitor?

If I plug the USB-C cable ( USB C Monitor Display Cable [4K@144Hz/60Hz 8K@30Hz], USB C 3.2 Gen 2x2 Video Cable, 20Gbps Data Transfer, 240W) into expansion port 1 (top left) I get a clear sharp image on the external monitor (SANSUI Monitor 24 inch 100Hz USB Type-C Computer Monitor).

If I plug into the USB-C display port on the back of the graphics module I get nothing.

If I put an HDMI adapter on the end of the USB-C cable going into the monitor’s HDMI input the graphics module display port will send a display signal and I get a clear sharp image. I have tried manually selecting USB-C in the monitor’s settings but I don’t think that was ever the issue as it all works with the display port 1 on the FW16.

Operating System: Windows 11 Home 64-bit (10.0, Build 22631) (22621.ni_release.220506-1250)

System Manufacturer: Framework
System Model: Laptop 16 (AMD Ryzen 7040 Series)
BIOS: 03.05 (type: UEFI)
Processor: AMD Ryzen 7 7840HS w/ Radeon 780M Graphics (16 CPUs), ~3.8GHz
Memory: 65536MB RAM

'ppreciate y’all,
Bill

[Alex_Wilken]

EDIT: After disconnecting all peripherals and power cable, I performed a shut down cycle using the physical power button. After this, my issue is resolved. Never forget the basics
I did also update my display drivers using the AMD discovery tool from their website, but it wasn’t until the shutdown that my issue cleared. Good luck with your issue!

I just want to report I also have this problem.
I’ve been happily using my Framework 16 with a Dell Ultrasharp monitor for months, connected via a USB-C cable from the USB-C port on the back (on the dGPU.)
This has only stopped working for me this week. I can successfully output to the monitor using the same USB-C cable from the left-rear USB-C port on the side, so it’s not a cable/ monitor problem.
My only recent change was installing the Feb update for Win 11 23H2.