-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
- HP Community
- Notebooks
- Notebook Video, Display and Touch
- USB-C TO Displayport no longer working SOLVED

Create an account on the HP Community to personalize your profile and ask a question
08-29-2024 05:23 PM - edited 08-29-2024 05:24 PM
I've been using my Laptop with an external Monitor for half a year now. I connected the Monitor from the USB-C out to the Displayport in. This has been working absolutely fine. 2 days go when I turn on my Laptop it suddenly no longer finds the Displayport. I bought a new cable but the issue persists. The monitor is fine and it works with the HDMI to HDMI connection. The USB-C Port is fine too because it recognized other devices.
Things I've tried:
Updating graphics drivers from AMD and Nvidia
Turning the monitor power off, replugging in and out
Latest windows update
Everything from HP is up to date as well, even the optional ones. Newest BIOS etc.
I'm forced to use my Laptop with the monitor via HDMI to HDMI now but due to the properties of the Monitor I have greatly reduced resolution and fps. Please help.
Solved! Go to Solution.
Accepted Solutions
12-06-2024
10:03 AM
- last edited on
12-06-2024
12:19 PM
by
SNicollas
So I made this thread earlier this year and had the issue since then. I now found a solution by chance.
New! Windows Update Replaced AMD Graphics Driver (1-Minute Fix) - YouTube
This video completely fixed it for me. The problem was caused by windows interfering with AMD drivers.
12-06-2024
10:03 AM
- last edited on
12-06-2024
12:19 PM
by
SNicollas
So I made this thread earlier this year and had the issue since then. I now found a solution by chance.
New! Windows Update Replaced AMD Graphics Driver (1-Minute Fix) - YouTube
This video completely fixed it for me. The problem was caused by windows interfering with AMD drivers.