micha_nue

updated

4 years ago

Closed

M

micha_nue

4 Posts

0

24424

October 13th, 2022 05:00

U2722DE, no USB-C signal from your device, #3

Hello,

I've been using the Dell U2722DE daily for over 2 months.

It used to work both for my MacBook Air M1 and HP EliteBook without any issues via the 90W PD USB-C Port. When I switched my Laptop on today I got presented with "No USB-C signal from your device". I tried switching to the MacBook - the same issue. Both Devices did still charge but no display output. 

I updated the Firmware to the most recent version and all the drivers as well, but nothing helped.

The most likely thing I can think of is the cable being broken but is this possible if it still charges?

  • DELL-Chris M

    Community Manager

    •

    56891 Posts

    •

    232143 Points

    28913

    0

    Posted October 13th, 2022 06:00

    * Turn the U2722DE and all PC's off
    * Disconnect every cable and device from the U2722DE (including the power cable)
    * Press and hold the U2722DE power button for 8 seconds
    * Reconnect only the power cable to the U2722DE
    * On a working PC, open the online U2722DE User's Guide
    * Run the U2722DE Self-Test and Built-in Diagnostics pages 92/93. Do they pass?

     



    If still under the purchased warranty, click the "Get Help Now" icon on the right to start a live chat session.


    DELL-Chris M (old account)

    #IWork4Dell

  • micha_nue

    4 Posts

    20062

    0

    Posted October 13th, 2022 14:00

    Got a replacement, seems like the USB Port got damaged.

  • micha_nue

    4 Posts

    20080

    0

    Posted October 13th, 2022 08:00

    Hello Chris,

    in the Self-Test, exactly the same thing happens as before. The error message appears.

    The Built-in Diagnostics works fine.

    One more thing that I noticed, is when connecting it via USB C the Display Manager doesn't recognize the Monitor as supported, which it obviously is.

    Do you think it could be the cable? 

  • micha_nue

    4 Posts

    20066

    1

    Posted October 13th, 2022 12:00

    Update: It was not the Cable.

     

    After chatting with Support, they wanted me to try another Cable to I went out and bought a brand new one. Same issue.