Troubleshoot Dell Dock WD19TBS

[Divine_Barakah]

Briefly explain your current issue(s)

Dell Wd19TBS

Steps taken to resolve, but have been unsuccessful

- thunderbolt is disabled in bios
- disabled VT in bios
- ran the firmware silently using CMD to force it.

Your current Antivirus

Bitdefender

I spent hours trying to update the firmware of the dock. All attempts failed

This dock is Thunderbolt 3
My laptop, Dell Latitude 5340, is Thunderbolt 4

Now when I try to update the dock firmware I get an error "timeout" or "target could not be detected"

With the help of Gemini, I disabled all protection from Bios, everything under intel VT and the firmware managed to update three components but not the NVM component.

The problem is I cannot connect my external monitor as it does not receive signal from the dock.

Is this due to the outdated firmware or sth else?

 

[Bot]

I spent hours trying to update the firmware of the dock. All attempts failed

This dock is Thunderbolt 3
My laptop, Dell Latitude 5340, is Thunderbolt 4

Now when I try to update the dock firmware I get an error "timeout" or "target could not be detected"

With the help of Gemini, I disabled all protection from Bios, everything under intel VT and the firmware managed to update three components but not the NVM component.

The problem is I cannot connect my external monitor as it does not receive signal from the dock.

Is this due to the outdated firmware or sth else?

This kind of symptom usually points to a Thunderbolt/firmware or hardware issue with the dock itself, but from the outside it’s impossible to say 100% if it’s “just” outdated firmware or a partially bricked NVM.

From what you describe (three components updated, NVM failed, now no video and “target could not be detected” errors), the NVM on the dock’s Thunderbolt controller is currently the main suspect.

A few things to check and try.

1. Basic checks (to rule out simple stuff)

• Confirm the monitor and cable are OK:
  • Connect the monitor directly to the laptop (HDMI/USB‑C/DP). If it works, the monitor and cable are fine.
• Check if anything on the dock works:
  • Do USB ports work (mouse/keyboard/USB stick)?
  • Does Ethernet on the dock work?
  • Does the dock charge the laptop (if it’s a power‑delivery dock)?
• If another laptop with Thunderbolt 3/4 is available, test the dock there:
  • If the second laptop also doesn’t see displays and can’t update firmware, that strongly suggests a dock-side issue.

If the dock isn’t enumerating properly as a Thunderbolt device, you normally lose video first because that depends on Thunderbolt/DP tunneling.

2. Check if Windows actually sees the dock as a Thunderbolt device

On Windows 10/11:

• Install or open Thunderbolt Control Center from the Microsoft Store.
• Connect the dock and wait a few seconds.
• See if the dock appears under connected Thunderbolt devices.

If it does not appear there at all:

• The Thunderbolt controller in the dock may not be talking to the laptop – which fits with a failed NVM update.
• That would also explain the firmware updater throwing “target could not be detected”.

If it does appear, but video still doesn’t work, then it could still be firmware, but also drivers or configuration.

3. Make sure the laptop side is fully up to date first

For your Dell Latitude 5340:

• Update to the latest BIOS from Dell’s support page.
• Install the latest Thunderbolt driver and (if available) Thunderbolt controller firmware for the Latitude 5340.
• Reboot after each update.

Thunderbolt 4 is backward‑compatible with Thunderbolt 3, but Dell often fixes dock compatibility issues via:

• System BIOS
• System Thunderbolt firmware
• Dock firmware

If the laptop side is outdated, dock updates can fail or behave weirdly.

4. Re‑check BIOS Thunderbolt/security settings

Since you changed BIOS settings:

• Make sure Thunderbolt is enabled.
• Thunderbolt Security Level: set it to No Security or User Authorization (not completely disabled).
• You can re‑enable Intel VT/virtualization – that’s not required to be off for firmware updates in normal circumstances.

If Thunderbolt is disabled or locked down too aggressively, firmware tools can’t see the dock and will timeout.

5. Retry the dock firmware update in the “cleanest” way possible

When everything above is updated:

• Download the exact firmware package for your dock model from Dell (e.g. WD19TB, TB16, WD22TB4, etc.).
• Connect:
  • Dock power adapter
  • Dock to laptop via Thunderbolt cable
  • If possible, no other USB devices or monitors at first
• Run the firmware tool as Administrator.
• If there are multiple components listed (NVM, PD controller, etc.), run the full update.

If NVM still consistently fails with “timeout” or “target could not be detected” while other components pass, that’s very suggestive that:

• The NVM on the dock’s TB controller is in a bad state (partially programmed or corrupted), or
• The Thunderbolt controller on the dock is no longer responding properly.

6. What this likely means in your situation

Given:

• Thunderbolt 3 dock + Thunderbolt 4 laptop (should be compatible in principle).
• Firmware update only partially completed.
• Now no display output and NVM won’t update / target not detected.

It’s very plausible this is due to a bad or incomplete NVM firmware state on the dock, not just “old firmware”. Outdated firmware usually still lets the dock be detected and work partially; a corrupted NVM can prevent proper enumeration and break video completely.

Unfortunately, if the NVM region on the dock’s controller is corrupted and the official Dell updater can’t see it anymore, there is usually no safe end‑user method to recover it. At that point it’s essentially a hardware failure from the user’s perspective.

7. Practical next steps

• Post the exact dock model and OS version in your thread – the precise Dell model matters a lot.
• Try the dock with another TB3/TB4 machine if you can, just to confirm it behaves the same.
• If the dock is still under warranty (or bought as a Dell bundle with the laptop), contact Dell support and:
  • Explain that the official firmware tool updated 3 components but NVM now fails with timeouts and the dock no longer outputs video.
  • Ask about dock replacement – on their side this is often treated as a dock hardware issue.
• If out of warranty and multiple attempts (with updated laptop BIOS/TB drivers) still give “target could not be detected”, replacing the dock is usually the realistic fix.

Summary

It’s not just “because the firmware is old”; the symptoms strongly point to a failed or incomplete firmware (NVM) state on the dock’s Thunderbolt controller. If the laptop BIOS and TB drivers are current and the Dell updater still can’t reach NVM, then the dock is likely in a state that can’t be recovered by normal tools, and you’re looking at RMA/replacement rather than a simple software fix.

If you share the dock’s exact model and what OS you’re on, I can suggest more model‑specific steps or Dell links to check.

 

[Divine_Barakah]

This kind of symptom usually points to a Thunderbolt/firmware or hardware issue with the dock itself, but from the outside it’s impossible to say 100% if it’s “just” outdated firmware or a partially bricked NVM.

From what you describe (three components updated, NVM failed, now no video and “target could not be detected” errors), the NVM on the dock’s Thunderbolt controller is currently the main suspect.

A few things to check and try.

1. Basic checks (to rule out simple stuff)

• Confirm the monitor and cable are OK:
  • Connect the monitor directly to the laptop (HDMI/USB‑C/DP). If it works, the monitor and cable are fine.
• Check if anythingon the dock works:
  • Do USB ports work (mouse/keyboard/USB stick)?
  • Does Ethernet on the dock work?
  • Does the dock charge the laptop (if it’s a power‑delivery dock)?
• If another laptop with Thunderbolt 3/4 is available, test the dock there:
  • If the second laptop also doesn’t see displays and can’t update firmware, that strongly suggests a dock-side issue.

If the dock isn’t enumerating properly as a Thunderbolt device, you normally lose video first because that depends on Thunderbolt/DP tunneling.

2. Check if Windows actually sees the dock as a Thunderbolt device

On Windows 10/11:

• Install or open Thunderbolt Control Center from the Microsoft Store.
• Connect the dock and wait a few seconds.
• See if the dock appears under connected Thunderbolt devices.

If it does not appear there at all:

• The Thunderbolt controller in the dock may not be talking to the laptop – which fits with a failed NVM update.
• That would also explain the firmware updater throwing “target could not be detected”.

If it does appear, but video still doesn’t work, then it could still be firmware, but also drivers or configuration.

3. Make sure the laptop side is fully up to date first

For your Dell Latitude 5340:

• Update to the latest BIOS from Dell’s support page.
• Install the latest Thunderbolt driver and (if available) Thunderbolt controller firmware for the Latitude 5340.
• Reboot after each update.

Thunderbolt 4 is backward‑compatible with Thunderbolt 3, but Dell often fixes dock compatibility issues via:

• System BIOS
• System Thunderbolt firmware
• Dock firmware

If the laptop side is outdated, dock updates can fail or behave weirdly.

4. Re‑check BIOS Thunderbolt/security settings

Since you changed BIOS settings:

• Make sure Thunderbolt is enabled.
• Thunderbolt Security Level: set it to No Security or User Authorization (not completely disabled).
• You can re‑enable Intel VT/virtualization – that’s not required to be off for firmware updates in normal circumstances.

If Thunderbolt is disabled or locked down too aggressively, firmware tools can’t see the dock and will timeout.

5. Retry the dock firmware update in the “cleanest” way possible

When everything above is updated:

• Download the exact firmware package for your dock model from Dell (e.g. WD19TB, TB16, WD22TB4, etc.).
• Connect:
  • Dock power adapter
  • Dock to laptop via Thunderbolt cable
  • If possible, no other USB devices or monitors at first
• Run the firmware tool as Administrator.
• If there are multiple components listed (NVM, PD controller, etc.), run the full update.

If NVM still consistently fails with “timeout” or “target could not be detected” while other components pass, that’s very suggestive that:

• The NVM on the dock’s TB controller is in a bad state (partially programmed or corrupted), or
• The Thunderbolt controller on the dock is no longer responding properly.

6. What this likely means in your situation

Given:

• Thunderbolt 3 dock + Thunderbolt 4 laptop (should be compatible in principle).
• Firmware update only partially completed.
• Now no display output and NVM won’t update / target not detected.

It’s very plausible this is due to a bad or incomplete NVM firmware state on the dock, not just “old firmware”. Outdated firmware usually still lets the dock be detected and work partially; a corrupted NVM can prevent proper enumeration and break video completely.

Unfortunately, if the NVM region on the dock’s controller is corrupted and the official Dell updater can’t see it anymore, there is usually no safe end‑user method to recover it. At that point it’s essentially a hardware failure from the user’s perspective.

7. Practical next steps

• Post the exact dock model and OS version in your thread – the precise Dell model matters a lot.
• Try the dock with another TB3/TB4 machine if you can, just to confirm it behaves the same.
• If the dock is still under warranty (or bought as a Dell bundle with the laptop), contact Dell support and:
  • Explain that the official firmware tool updated 3 components but NVM now fails with timeouts and the dock no longer outputs video.
  • Ask about dock replacement – on their side this is often treated as a dock hardware issue.
• If out of warranty and multiple attempts (with updated laptop BIOS/TB drivers) still give “target could not be detected”, replacing the dock is usually the realistic fix.

Summary

It’s not just “because the firmware is old”; the symptoms strongly point to a failed or incomplete firmware (NVM) state on the dock’s Thunderbolt controller. If the laptop BIOS and TB drivers are current and the Dell updater still can’t reach NVM, then the dock is likely in a state that can’t be recovered by normal tools, and you’re looking at RMA/replacement rather than a simple software fix.

If you share the dock’s exact model and what OS you’re on, I can suggest more model‑specific steps or Dell links to check.

Just Connected the dock to my Acer spin 714 Chromebook and it worked flawlessly

 

[Bot]

Just Connected the dock to my Acer spin 714 Chromebook and it worked flawlessly

That test is very useful: if the dock works flawlessly on the Acer Spin 714 (including video), then the dock hardware and its NVM firmware are very likely fine.

This means the problem is almost certainly on the Dell Latitude 5340 side (drivers, Thunderbolt security, or compatibility), not a “dead” dock.

So to your question:
It’s probably not simply “outdated dock firmware”. It’s more likely:

• Thunderbolt settings / security on the Dell
• Missing or outdated Dell Thunderbolt / chipset / GPU drivers
• A compatibility quirk between that Dell model and that specific dock firmware

Here’s what I’d do next on the Dell.

1. Check what actually works on the Dell via the dock

When the dock is connected to the Dell, not the Chromebook:

• Do USB ports on the dock work (mouse, keyboard, flash drive)?
• Does Ethernet from the dock work?
• Does the dock charge the laptop (if it’s a PD dock)?

This tells us if the dock is at least partially enumerating as a Thunderbolt/USB‑C device on the Dell, or if nothing works.

2. Thunderbolt Control Center on the Dell

On the Dell (Windows 10/11):

• Install or open Thunderbolt Control Center from Microsoft Store.
• Connect the dock and wait a few seconds.
• See if the dock appears as a Thunderbolt device.
• If it appears, authorize it and set it to Always Connect.

If the dock does not appear at all there, the Dell’s Thunderbolt stack is not talking to it properly. That would also explain why the Dell firmware updater says “target could not be detected”.

3. Update everything on the Dell from Dell’s own site

Go to Dell Support, enter your Latitude 5340 service tag, then:

• Update BIOS to the latest version.
• Install latest Chipset drivers.
• Install Intel Thunderbolt driver (and Thunderbolt firmware, if there is a separate package).
• Install the latest Intel Graphics driver from Dell (not Intel’s generic one, if you can avoid it).
• Reboot after each important step (BIOS, TB, GPU).

Do not rely on Windows Update only – Dell’s own packages are important for dock compatibility.

4. Re‑check Dell BIOS Thunderbolt settings

Since you changed BIOS options earlier, on the Latitude 5340:

• Make sure Thunderbolt is enabled.
• Set Thunderbolt Security Level to User Authorization or No Security (for testing).
• Ensure “Allow PCIe tunneling” / similar options are enabled.
• You can safely re‑enable Intel VT/virtualization – that’s not what blocks docks.
• If there is an option to restore BIOS to factory defaults, you can do that, then re‑enable Thunderbolt explicitly.

Then boot back into Windows, connect the dock, and check both:

• Thunderbolt Control Center (for device authorization)
• Device Manager (any USB hubs / network / audio appearing when the dock is plugged in)

5. About the NVM firmware update

Since the dock works perfectly on the Chromebook:

• The NVM is not completely corrupted, or the dock would not pass Thunderbolt/video at all.
• The Dell updater failing on the NVM part is more likely due to how the Dell sees the dock (driver/permission issue) than a totally “bricked” dock.
• NVM doesn’t have to be the very latest version to function; sometimes the update is just for compatibility fixes with specific Dell systems.

Once the Dell Thunderbolt stack is healthy and the dock is shown and authorized in Thunderbolt Control Center, you can retry the dock firmware update one more time. If NVM still refuses while the dock otherwise works, I would stop forcing it – at that point the risk outweighs the benefit.

6. Check model compatibility

Please also post (or check) the exact dock model (e.g. WD19TB, WD22TB4, TB16, WD15, etc.).

Dell is picky: some older TB3 docks are not officially supported on newer Latitudes, even though they may work on other brands (like your Acer). If your dock is in that “not supported” list for Latitude 5340, you may get:

• Hit‑and‑miss video
• Failed Dell firmware tools
• Weird detection problems

Dell’s compatibility matrix on their support site will say which docks are tested/approved for the Latitude 5340.

Summary

• Because the dock works flawlessly on the Acer Chromebook, the dock hardware and NVM are almost certainly fine.
• Your issue is almost definitely on the Dell side: Thunderbolt drivers/firmware, BIOS settings, or model compatibility.
• Update all Dell drivers/BIOS, ensure Thunderbolt is enabled and the dock is authorized in Thunderbolt Control Center, then retry.

If you share:

• Exact dock model
• Windows version on the Dell
• Whether USB/Ethernet work from the dock on the Dell

I can give a more targeted sequence (and, if possible, link you to the right Dell driver/firmware pages to check).

 

[Divine_Barakah]

That test is very useful: if the dock works flawlessly on the Acer Spin 714 (including video), then the dock hardware and its NVM firmware are very likely fine.

This means the problem is almost certainly on the Dell Latitude 5340 side (drivers, Thunderbolt security, or compatibility), not a “dead” dock.

So to your question:
It’s probably not simply “outdated dock firmware”. It’s more likely:

• Thunderbolt settings / security on the Dell
• Missing or outdated Dell Thunderbolt / chipset / GPU drivers
• A compatibility quirk between that Dell model and that specific dock firmware

Here’s what I’d do next on the Dell.

1. Check what actually works on the Dell via the dock

When the dock is connected to the Dell, not the Chromebook:

• Do USB ports on the dock work (mouse, keyboard, flash drive)?
• Does Ethernet from the dock work?
• Does the dock charge the laptop (if it’s a PD dock)?

This tells us if the dock is at least partially enumerating as a Thunderbolt/USB‑C device on the Dell, or if nothing works.

2. Thunderbolt Control Center on the Dell

On the Dell (Windows 10/11):

• Install or open Thunderbolt Control Center from Microsoft Store.
• Connect the dock and wait a few seconds.
• See if the dock appears as a Thunderbolt device.
• If it appears, authorize it and set it to Always Connect.

If the dock does not appear at all there, the Dell’s Thunderbolt stack is not talking to it properly. That would also explain why the Dell firmware updater says “target could not be detected”.

3. Update everything on the Dell from Dell’s own site

Go to Dell Support, enter your Latitude 5340 service tag, then:

• Update BIOS to the latest version.
• Install latest Chipset drivers.
• Install Intel Thunderbolt driver (and Thunderbolt firmware, if there is a separate package).
• Install the latest Intel Graphics driver from Dell (not Intel’s generic one, if you can avoid it).
• Reboot after each important step (BIOS, TB, GPU).

Do not rely on Windows Update only – Dell’s own packages are important for dock compatibility.

4. Re‑check Dell BIOS Thunderbolt settings

Since you changed BIOS options earlier, on the Latitude 5340:

• Make sure Thunderbolt is enabled.
• Set Thunderbolt Security Level to User Authorization or No Security (for testing).
• Ensure “Allow PCIe tunneling” / similar options are enabled.
• You can safely re‑enable Intel VT/virtualization – that’s not what blocks docks.
• If there is an option to restore BIOS to factory defaults, you can do that, then re‑enable Thunderbolt explicitly.

Then boot back into Windows, connect the dock, and check both:

• Thunderbolt Control Center (for device authorization)
• Device Manager (any USB hubs / network / audio appearing when the dock is plugged in)

5. About the NVM firmware update

Since the dock works perfectly on the Chromebook:

• The NVM is not completely corrupted, or the dock would not pass Thunderbolt/video at all.
• The Dell updater failing on the NVM part is more likely due to how the Dell sees the dock (driver/permission issue) than a totally “bricked” dock.
• NVM doesn’t have to be the very latest version to function; sometimes the update is just for compatibility fixes with specific Dell systems.

Once the Dell Thunderbolt stack is healthy and the dock is shown and authorized in Thunderbolt Control Center, you can retry the dock firmware update one more time. If NVM still refuses while the dock otherwise works, I would stop forcing it – at that point the risk outweighs the benefit.

6. Check model compatibility

Please also post (or check) the exact dock model (e.g. WD19TB, WD22TB4, TB16, WD15, etc.).

Dell is picky: some older TB3 docks are not officially supported on newer Latitudes, even though they may work on other brands (like your Acer). If your dock is in that “not supported” list for Latitude 5340, you may get:

• Hit‑and‑miss video
• Failed Dell firmware tools
• Weird detection problems

Dell’s compatibility matrix on their support site will say which docks are tested/approved for the Latitude 5340.

Summary

• Because the dock works flawlessly on the Acer Chromebook, the dock hardware and NVM are almost certainly fine.
• Your issue is almost definitely on the Dell side: Thunderbolt drivers/firmware, BIOS settings, or model compatibility.
• Update all Dell drivers/BIOS, ensure Thunderbolt is enabled and the dock is authorized in Thunderbolt Control Center, then retry.

If you share:

• Exact dock model
• Windows version on the Dell
• Whether USB/Ethernet work from the dock on the Dell

I can give a more targeted sequence (and, if possible, link you to the right Dell driver/firmware pages to check).

The exact model is WD19TBS.

My Latitude 5340 is up to date

It seems I need an older laptop to update the Dock's firmware and I hope that fixes the issue.

 

[Bot]

The exact model is WD19TBS.

My Latitude 5340 is up to date

It seems I need an older laptop to update the Dock's firmware and I hope that fixes the issue.

If the WD19TBS works perfectly on the Chromebook, the dock itself (including its NVM) is almost certainly OK. That points much more to a Dell host‑side problem than a “bad” dock.

Using an older Windows laptop to finish the firmware update can help, but it’s not guaranteed to fix the Latitude 5340 issue. I’d treat it as one of several steps, not the only solution.

1. Confirm what works on the Dell via the dock

With the WD19TBS connected to the Latitude 5340:

• Do USB ports on the dock work (mouse, keyboard, USB stick)?
• Does Ethernet from the dock work?
• Does audio from the dock work (headphone jack)?

If these work but only video fails, that’s usually host‑side Thunderbolt/graphics config or a firmware mismatch, not a dead dock.

2. Double‑check Thunderbolt side on the Latitude 5340

On the Dell (Windows 10/11):

• Install/open Thunderbolt Control Center (Microsoft Store).
• Connect the WD19TBS and wait.
• If the dock appears, authorize it and set to Always Connect.

In the BIOS of the 5340:

• Make sure Thunderbolt is enabled.
• Set Thunderbolt Security (if present) to User Authorization or No Security for testing.
• Ensure PCIe/DisplayPort tunneling (or similar wording) is enabled.
• You can re‑enable Intel VT; it normally doesn’t affect docks.

Then in Windows:

• Use Dell’s site (with your service tag) and reinstall:
  • Latest Thunderbolt driver/firmware
  • Latest chipset driver
  • Latest Intel graphics driver from Dell
• Reboot after each important update.

3. About updating the dock on an “older” laptop

If you have access to another Windows laptop with Thunderbolt 3/4:

• Install Dell’s official WD19TBS Firmware Update Utility on that machine.
• Connect the WD19TBS with its own Dell power supply and original TB cable.
• Run the updater as Administrator and let it finish all components (including NVM) if it will.

That may:

• Bring the dock NVM to the latest version (which might improve compatibility with the 5340’s TB4 controller).
• Avoid whatever driver/security issue is blocking the update on the 5340.

But note:

• The fact that it already works on the Chromebook means the firmware is at least functional.
• If, after a successful full update on another laptop, the 5340 still can’t output video through the dock, the problem is almost certainly on the 5340 side (Thunderbolt stack, BIOS, or even a subtle hardware fault on the 5340’s TB/USB‑C port).

4. When to involve Dell support

If you:

• Verify the dock works on another Windows machine and your Chromebook,
• Confirm the WD19TBS firmware is fully up to date on that other machine,
• Have the Latitude 5340 fully updated (BIOS, TB, chipset, GPU, Windows),
• And the dock still doesn’t output video on the 5340 only,

then it’s time to contact Dell support with those facts. They can:

• Check for any known issues with Latitude 5340 + WD19TBS.
• Run hardware diagnostics on the 5340’s Thunderbolt/USB‑C port.
• Offer repair or replacement if it’s a host‑side hardware issue.

Summary

• Yes, using another (older) laptop to complete the WD19TBS firmware update is a reasonable step and might improve compatibility.
• However, since the dock already works flawlessly on your Chromebook, the root problem is more likely on the Latitude 5340 side (Thunderbolt/BIOS/driver/compatibility).
• If, after a successful dock firmware update on another PC, the 5340 still fails, you’re almost certainly dealing with a Dell‑side issue that needs Dell support.

If you can confirm whether USB/Ethernet from the dock work on the 5340, that will narrow it down further.

 

[Divine_Barakah]

@Bot

I had to return the Dock.
I used Fedora live iso to update the Dock's firmware as dell offered a .cab driver for Linux and to my surprise FWupmgr confirmed the Dock's firmware is up to date.

As I mentioned before the dock worked perfectly on my Acer Spin. 714 Chromebook.

I did everything in bios. I disabled Thunderbolt to force the laptop to mimic what my Chromebook does with the Dock and it did not work. I then reenabled Thunderbolt in bios and also boot support. Unfortunately, there was no setting in bios to change thunderbolt security, so I went and disabled VT and related settings.

That caused the USB ports in the Dock to start working but never the hdmi port.

So today I went to the store and we tested the dock on multiple Dell laptops. The newest was a Latitude with Intel Gen 12th CPU and the dock worked flawlessly, but never on my laptop.

So we grabbed an older dell laptop and we updated the Dock's firmware there but it did not work on my laptop.

I have tried every single solution on my laptop but to no avail. I updated the drivers even installed Thunderbolt Center, but the Dock was not detected. It seems my laptop is blocking transferring the video through Thunderbolt port.

So finally I gave up and returned the Dock.

 

[Bot]

@Bot

I had to return the Dock.
I used Fedora live iso to update the Dock's firmware as dell offered a .cab driver for Linux and to my surprise FWupmgr confirmed the Dock's firmware is up to date.

As I mentioned before the dock worked perfectly on my Acer Spin. 714 Chromebook.

I did everything in bios. I disabled Thunderbolt to force the laptop to mimic what my Chromebook does with the Dock and it did not work. I then reenabled Thunderbolt in bios and also boot support. Unfortunately, there was no setting in bios to change thunderbolt security, so I went and disabled VT and related settings.

That caused the USB ports in the Dock to start working but never the hdmi port.

So today I went to the store and we tested the dock on multiple Dell laptops. The newest was a Latitude with Intel Gen 12th CPU and the dock worked flawlessly, but never on my laptop.

So we grabbed an older dell laptop and we updated the Dock's firmware there but it did not work on my laptop.

I have tried every single solution on my laptop but to no avail. I updated the drivers even installed Thunderbolt Center, but the Dock was not detected. It seems my laptop is blocking transferring the video through Thunderbolt port.

So finally I gave up and returned the Dock.

Given everything you’ve tried and the tests you did at the store, returning the dock was a completely reasonable decision. You did more troubleshooting than most people (and more than Dell support usually asks for).

What your testing actually shows

From your description:

• WD19TBS worked:
  • On your Acer Spin 714 Chromebook
  • On multiple Dell laptops at the store (including a 12th‑gen Latitude)
  • Firmware verified up to date via Fedora/.cab + fwupdmgr
• On your Latitude 5340:
  • Thunderbolt Control Center did not see the dock
  • USB on the dock only started working after BIOS tweaks
  • HDMI/video never worked
  • Dock firmware update on an older Dell (to latest) still didn’t help

That combination strongly points to an issue specific to your Latitude 5340’s Thunderbolt/USB‑C implementation, not the dock:

• The dock is clearly fine (works on other systems, up‑to‑date firmware).
• Other Dells with Thunderbolt recognize and fully use the dock.
• Your 5340 never enumerates it properly as a Thunderbolt device, and doesn’t pass DP/alt‑mode video through, even when USB starts working.

I can’t say with certainty whether that’s:

• A firmware/BIOS bug on the 5340, or
• A hardware fault on the 5340’s TB4/USB‑C port (especially the DP/Thunderbolt side), or
• Some weird, as‑yet‑unfixed compatibility quirk between 5340 + WD19TBS.

But from your steps, you essentially ruled out “user misconfiguration” and “bad dock”.

What I would do next (if you still care about docks on this laptop)

Since you’ve already returned the WD19TBS:

• Open a support case with Dell, describe exactly what you did:
  • WD19TBS works on Chromebook + multiple other Dells
  • Fully updated dock firmware from Linux and another Dell
  • Your 5340 is fully up to date (BIOS, drivers)
  • Dock never detected in Thunderbolt Control Center on 5340, no video, only partial USB after BIOS changes
• Ask them specifically:
  • Whether there is a known issue with Latitude 5340 + WD19TBS / TB4 docks
  • If they can provide a newer Thunderbolt firmware/BIOS, or
  • If they suspect a hardware fault in the TB4/USB‑C port and are willing to repair/replace the laptop under warranty.

Even though you’ve returned the dock, this is still relevant: if the 5340 has a TB/DP‑alt‑mode fault, it may also fail with other docks or USB‑C monitors.

Alternatives if you want a dock again later

Depending on what Dell says and what you need:

• USB‑C “display only” dock/adapter (DP Alt Mode)
  If your 5340’s USB‑C can do simple DP Alt Mode reliably (you’d want to test with a basic USB‑C to HDMI/DP adapter), a non‑Thunderbolt USB‑C dock could be enough.
• DisplayLink‑based dock
  These use a USB graphics chip and usually work even when Thunderbolt/Alt Mode is finicky, as long as:
  • You install the DisplayLink driver on Windows
  • You’re OK with video being compressed over USB (fine for office use, less ideal for gaming/color‑critical work)

Bottom line

You absolutely didn’t do anything “wrong” here:

• You verified the dock works elsewhere and is up to date.
• You exhaustively tested BIOS options, OS, and firmware.
• You even tried a different machine to update the dock.

Given all that, returning the WD19TBS was a sensible choice. If you still want docking on this Latitude, I’d focus now on:

• Getting Dell to check the 5340’s Thunderbolt/USB‑C hardware and firmware, and
• Considering a USB‑C or DisplayLink dock as a workaround if Dell can’t resolve it quickly.

If you later decide on another dock model, feel free to post the exact model and how you plan to use it (number of monitors, resolution, etc.), and I can help you judge whether it’s likely to avoid the same issues.

 

[Divine_Barakah]

A hardware fault on the 5340’s TB4/USB‑C port (especially the DP/Thunderbolt side)

I thought about this too, but running a hardware scan using Dell SupportAssist did not throw any workings so?

 

[Bot]

I thought about this too, but running a hardware scan using Dell SupportAssist did not throw any workings so?

SupportAssist passing unfortunately doesn’t rule this out. Dell’s built‑in tests and SupportAssist are quite limited when it comes to Thunderbolt and USB‑C display/Alt‑Mode issues.

What SupportAssist actually checks (roughly)

In very simplified terms, SupportAssist / ePSA usually test things like:

• Whether the Thunderbolt/USB‑C controller is present on the PCIe bus
• Basic USB functionality (if at all)
• Power delivery to some extent

They do not reliably test:

• DisplayPort Alt Mode over USB‑C (the “video” part)
• Thunderbolt tunneling of PCIe/DP, authorization, and security policies
• Subtle firmware bugs where a specific device (like WD19TBS) fails but others work

So you can have:

• A port that enumerates fine and passes basic diagnostics
• But still has:
  • Broken DP Alt‑Mode paths
  • A TB firmware issue
  • A mux/switch problem that only shows up when trying to send video

SupportAssist will often happily say “all good” in those cases.

The key test now: direct USB‑C video

The best way to narrow this down is a simple, direct test, independent of any dock:

• Get a basic USB‑C to HDMI or USB‑C to DisplayPort adapter (non‑Thunderbolt, just a simple DP Alt‑Mode adapter).
• Plug it into the same USB‑C/Thunderbolt port on your Latitude 5340.
• Connect your external monitor.

Then see what happens:

• Scenario A – External display works
  -> DP Alt‑Mode and the USB‑C video path are functional.
  -> This points much more to a very specific Thunderbolt/firmware/compatibility issue between your 5340 and WD19TBS, not a dead port.
• Scenario B – External display does not work, but USB devices through a simple USB‑C hub do
  -> Power + USB data work, but the DP lanes / Alt‑Mode path look suspicious.
  -> This is where a hardware or low‑level firmware fault in the port or its DP mux is quite plausible, even if SupportAssist is clean.
• Scenario C – Even basic USB over that port is flaky or dead
  -> Then it’s almost certainly a hardware fault in the port / controller despite “passed” diagnostics.

Why your WD19TBS results still point away from the dock

You already have very strong evidence:

• WD19TBS worked:
  • On your Acer Spin 714 Chromebook
  • On multiple Dell laptops in the store (including a 12th‑gen Latitude)
  • With firmware confirmed up‑to‑date via fwupdmgr on Fedora
• On your 5340:
  • Thunderbolt Control Center never saw it
  • Only USB on the dock started working after BIOS changes
  • HDMI/video never worked

Those are classic signs of either:

• A bug or incompatibility in the 5340’s Thunderbolt/firmware stack, or
• A physical issue in the TB4/USB‑C port’s DP/Alt‑Mode path

Neither of those is something SupportAssist is good at catching.

What I’d suggest now

Since you already returned the dock:

• Do the USB‑C to HDMI/DP direct adapter test if you can.
• Based on the result:
  • If the adapter also fails for video, show that to Dell support. That’s a simple, reproducible external monitor failure via USB‑C that they can’t really dismiss as “dock issue”.
  • If the adapter works fine, tell Dell support that:
    • The port does DP Alt‑Mode OK.
    • WD19TBS + multiple other laptops works.
    • Only Latitude 5340 + WD19TBS fails.
    This strengthens the case for a firmware/compatibility problem on their side.

Summary

• SupportAssist “all good” does not prove your TB4/USB‑C video path is fine.
• Your testing so far still strongly suggests an issue on the Latitude 5340 side (firmware or hardware), not with the dock.
• A simple USB‑C → HDMI/DP adapter test is the best next step to confirm whether the port can output video at all, and gives you clear evidence to take to Dell.

If you do that adapter test and share the result, it’s much easier to say “this is almost surely hardware” vs “this is almost surely firmware/compatibility.”

 

[Divine_Barakah]

SupportAssist passing unfortunately doesn’t rule this out. Dell’s built‑in tests and SupportAssist are quite limited when it comes to Thunderbolt and USB‑C display/Alt‑Mode issues.

What SupportAssist actually checks (roughly)

In very simplified terms, SupportAssist / ePSA usually test things like:

• Whether the Thunderbolt/USB‑C controller is present on the PCIe bus
• Basic USB functionality (if at all)
• Power delivery to some extent

They do not reliably test:

• DisplayPort Alt Mode over USB‑C (the “video” part)
• Thunderbolt tunneling of PCIe/DP, authorization, and security policies
• Subtle firmware bugs where a specific device (like WD19TBS) fails but others work

So you can have:

• A port that enumerates fine and passes basic diagnostics
• But still has:
  • Broken DP Alt‑Mode paths
  • A TB firmware issue
  • A mux/switch problem that only shows up when trying to send video

SupportAssist will often happily say “all good” in those cases.

The key test now: direct USB‑C video

The best way to narrow this down is a simple, direct test, independent of any dock:

• Get a basic USB‑C to HDMI or USB‑C to DisplayPort adapter (non‑Thunderbolt, just a simple DP Alt‑Mode adapter).
• Plug it into the same USB‑C/Thunderbolt port on your Latitude 5340.
• Connect your external monitor.

Then see what happens:

• Scenario A – External display works
  -> DP Alt‑Mode and the USB‑C video path are functional.
  -> This points much more to a very specific Thunderbolt/firmware/compatibility issue between your 5340 and WD19TBS, not a dead port.
• Scenario B – External display does not work, but USB devices through a simple USB‑C hub do
  -> Power + USB data work, but the DP lanes / Alt‑Mode path look suspicious.
  -> This is where a hardware or low‑level firmware fault in the port or its DP mux is quite plausible, even if SupportAssist is clean.
• Scenario C – Even basic USB over that port is flaky or dead
  -> Then it’s almost certainly a hardware fault in the port / controller despite “passed” diagnostics.

Why your WD19TBS results still point away from the dock

You already have very strong evidence:

• WD19TBS worked:
  • On your Acer Spin 714 Chromebook
  • On multiple Dell laptops in the store (including a 12th‑gen Latitude)
  • With firmware confirmed up‑to‑date via fwupdmgr on Fedora
• On your 5340:
  • Thunderbolt Control Center never saw it
  • Only USB on the dock started working after BIOS changes
  • HDMI/video never worked

Those are classic signs of either:

• A bug or incompatibility in the 5340’s Thunderbolt/firmware stack, or
• A physical issue in the TB4/USB‑C port’s DP/Alt‑Mode path

Neither of those is something SupportAssist is good at catching.

What I’d suggest now

Since you already returned the dock:

• Do the USB‑C to HDMI/DP direct adapter test if you can.
• Based on the result:
  • If the adapter also fails for video, show that to Dell support. That’s a simple, reproducible external monitor failure via USB‑C that they can’t really dismiss as “dock issue”.
  • If the adapter works fine, tell Dell support that:
    • The port does DP Alt‑Mode OK.
    • WD19TBS + multiple other laptops works.
    • Only Latitude 5340 + WD19TBS fails.
    This strengthens the case for a firmware/compatibility problem on their side.

Summary

• SupportAssist “all good” does not prove your TB4/USB‑C video path is fine.
• Your testing so far still strongly suggests an issue on the Latitude 5340 side (firmware or hardware), not with the dock.
• A simple USB‑C → HDMI/DP adapter test is the best next step to confirm whether the port can output video at all, and gives you clear evidence to take to Dell.

If you do that adapter test and share the result, it’s much easier to say “this is almost surely hardware” vs “this is almost surely firmware/compatibility.”

I have a usb c hub from Ivanky and it has an HDMI port, so I connected that to the Dell U2422H Monitor and it did not work. So I'm not sure what is causing all of this, but I suspect it has sth to do with either BIOS security settings or Windows security. I even did the registry hack to prevent compressing the signal sent to the external monitor and it did not work.


So now in USB4 info it shows like this

Manufacturer name INTEL

Model name Gen12

Domain ID 0x4d0001

Device instance ID PCI\VEN_8086&DEV_A73E&SUBSYS_0C031028&REV_01&USB4_MS_CM\3&115836598086A

Topology ID 0:0:0:0:0:0:0


Silicon vendor ID 0x8087

Silicon product ID Oxa73e

Silicon revision 1

Firmware version 23.3


USB4 version 1.0


Total DP IN adaptors 2

Tunneled DP IN adaptors 0

Unavailable DP IN adaptors 0

 

[Bot]

I have a usb c hub from Ivanky and it has an HDMI port, so I connected that to the Dell U2422H Monitor and it did not work. So I'm not sure what is causing all of this, but I suspect it has sth to do with either BIOS security settings or Windows security. I even did the registry hack to prevent compressing the signal sent to the external monitor and it did not work.


So now in USB4 info it shows like this

Manufacturer name INTEL

Model name Gen12

Domain ID 0x4d0001

Device instance ID PCI\VEN_8086&DEV_A73E&SUBSYS_0C031028&REV_01&USB4_MS_CM\3&115836598086A

Topology ID 0:0:0:0:0:0:0


Silicon vendor ID 0x8087

Silicon product ID Oxa73e

Silicon revision 1

Firmware version 23.3


USB4 version 1.0


Total DP IN adaptors 2

Tunneled DP IN adaptors 0

Unavailable DP IN adaptors 0

The behavior with the iVanky hub basically confirms that this is not just a WD19TBS problem – your Latitude’s USB‑C/TB4 port is currently not outputting any video (DP Alt Mode), even to a simple USB‑C hub.

That makes “Windows security” or a registry tweak very unlikely as the main cause.

1. What your current tests really show

You now have:

• WD19TBS dock:
  • Works on Acer Spin 714 Chromebook
  • Works on multiple other Dell laptops (including 12th‑gen Latitude)
  • Firmware up to date (confirmed via fwupdmgr on Fedora + older Dell)
• iVanky USB‑C hub with HDMI:
  • Connected to Dell U2422H from the Latitude 5340 → no signal
  • (Assuming it works on other devices – if not, it’s worth confirming)
• SupportAssist hardware test → passes
• Thunderbolt Control Center → dock was never detected on your 5340
• USB ports on dock only started working after BIOS tweaks; HDMI never did

So:

• Basic USB over USB‑C: seems to work (at least with the dock after tweaks).
• DisplayPort Alt Mode / Thunderbolt tunneling (video): does not work on your 5340.

The iVanky hub is likely not a Thunderbolt device – it’s a simple USB‑C DP Alt‑Mode adapter. That path is below Windows‑level things like Defender, SmartScreen, etc. If even that fails, it is almost never caused by Windows security.

2. Interpreting the USB4 info you posted

The USB4 info:

• Manufacturer: Intel, Gen12
• Firmware version: 23.3
• USB4 version: 1.0
• Total DP IN adaptors: 2
• Tunneled DP IN adaptors: 0

In plain terms:

• The USB4/TB4 controller itself is there and has firmware 23.3.
• “Total DP IN adaptors 2” = the controller can receive up to two DisplayPort inputs from the GPU.
• “Tunneled DP IN adaptors 0” = right now, no DP signal is actually being tunneled through USB4/TB – i.e. no active DP Alt‑Mode / TB display stream.

If you captured this while the iVanky hub + monitor were already plugged in and active, that suggests the DP/Alt‑Mode negotiation isn’t happening on this machine. Either:

• The port isn’t wired/enabled for DP Alt Mode correctly on this system, or
• There’s a low‑level firmware/BIOS issue, or
• There’s a hardware fault in the DP path/mux to the USB‑C port.

This is exactly the sort of thing SupportAssist typically doesn’t catch.

3. A couple of sanity checks (if you haven’t done them yet)

• Confirm the iVanky hub + cable + monitor work on another device
  Just to be 100% sure:
  • Use the same iVanky hub + same USB‑C cable + same Dell U2422H
  • Test on your Chromebook or another laptop
  If it works there, then we know the entire chain (hub + cable + monitor) is good.
  
• Make sure you’re using a full‑feature USB‑C cable
  Some C cables are power/USB‑2‑only. If the iVanky hub came with its own cable, use that exact cable.
  
• Try outside of Windows
  Since you already used a Fedora live ISO:
  • Boot into Fedora live again.
  • Plug in the iVanky hub + HDMI monitor.
  • See if Fedora detects the external display (Display settings).
  If Linux also sees no external display, that’s very strong evidence this is not a Windows or driver/security issue.
  
• Try to get video at boot time
  With the hub + monitor connected:
  • Turn the laptop completely off.
  • Power it on and immediately enter BIOS (F2) or the one‑time boot menu (F12).
  • See if the BIOS/boot menu appears on the external monitor.
  If you never get a picture even at BIOS level, again it points strongly to hardware/firmware on the laptop – Windows isn’t even involved yet.

4. Why BIOS/Windows “security” is unlikely to be the real blocker

Some points:

• Thunderbolt security level (SL0/SL1/SL2, etc.) affects Thunderbolt devices (like WD19TBS) and PCIe tunneling.
• Your iVanky hub is just a USB‑C DP Alt‑Mode adapter – it normally does not need Thunderbolt at all and should work even if TB is disabled, as long as DP Alt‑Mode is supported and working.
• Windows features (Defender, Core Isolation, etc.) do not selectively block DP Alt‑Mode; they operate at a much higher layer.
• That registry hack about “signal compression” would only matter once a display is actually recognized; it won’t fix a total lack of DP link.

Because even the simple USB‑C → HDMI hub is failing, the root cause is almost certainly at or below:

• GPU → USB4/TB controller DP wiring
• USB‑C DP mux/switch
• USB4/TB firmware/BIOS level
• Physical fault in the port or mainboard traces

5. What I’d do with Dell support now

At this point you have very strong evidence:

• Multiple docks/adapters and monitors tested
• Everything works on other laptops (Dell + Chromebook)
• Nothing outputs video on the Latitude 5340’s USB‑C, even simple USB‑C → HDMI
• SupportAssist passes, but USB4 info shows 0 tunneled DP even with devices attached

I’d contact Dell support and present it like this:

• “My Latitude 5340’s USB‑C/TB4 port does not output video at all.”
• “A WD19TBS dock works perfectly on other Dells and a Chromebook, but never shows up in Thunderbolt Control Center on this 5340.”
• “A simple USB‑C hub with HDMI (Ivanky) also fails to output video to a Dell U2422H, but works on other machines.”
• “SupportAssist passes, but USB4 info shows ‘Total DP IN adaptors 2’ and ‘Tunneled DP IN adaptors 0’ even when a USB‑C video device is attached.”
• “I have already updated BIOS, chipset, GPU, Thunderbolt drivers, and tested under a Linux live ISO – no video from USB‑C.” (if Linux test also fails).

Then ask clearly:

• To treat this as a suspected hardware or low‑level firmware issue with the USB‑C/TB4 port / DP path.
• For a mainboard repair/replacement or at least escalation to an engineering‑level check for known issues with DP Alt‑Mode on the Latitude 5340.

Summary

• The failure of both WD19TBS and a simple iVanky USB‑C HDMI hub on the 5340, while they work elsewhere, points strongly to an issue with the 5340’s USB‑C/TB4 display path – not Windows security or the dock itself.
• Your USB4 info (0 tunneled DP IN) is consistent with “no DP Alt‑Mode / tunneling happening at all”.
• Next concrete steps:
  • Verify the iVanky hub + cable work on another device.
  • Test USB‑C video under Linux live and at BIOS/boot if you can.
  • Use that evidence to push Dell to treat this as a hardware/firmware fault rather than a software misconfiguration.

If you run the Linux/BIOS test and let me know whether the external display shows anything there, I can help you phrase an even more precise description for Dell support.

 

[Divine_Barakah]

The behavior with the iVanky hub basically confirms that this is not just a WD19TBS problem – your Latitude’s USB‑C/TB4 port is currently not outputting any video (DP Alt Mode), even to a simple USB‑C hub.

That makes “Windows security” or a registry tweak very unlikely as the main cause.

1. What your current tests really show

You now have:

• WD19TBS dock:
  • Works on Acer Spin 714 Chromebook
  • Works on multiple other Dell laptops (including 12th‑gen Latitude)
  • Firmware up to date (confirmed via fwupdmgr on Fedora + older Dell)
• iVanky USB‑C hub with HDMI:
  • Connected to Dell U2422H from the Latitude 5340 → no signal
  • (Assuming it works on other devices – if not, it’s worth confirming)
• SupportAssist hardware test → passes
• Thunderbolt Control Center → dock was never detected on your 5340
• USB ports on dock only started working after BIOS tweaks; HDMI never did

So:

• Basic USB over USB‑C: seems to work (at least with the dock after tweaks).
• DisplayPort Alt Mode / Thunderbolt tunneling (video): does not work on your 5340.

The iVanky hub is likely not a Thunderbolt device – it’s a simple USB‑C DP Alt‑Mode adapter. That path is below Windows‑level things like Defender, SmartScreen, etc. If even that fails, it is almost never caused by Windows security.

2. Interpreting the USB4 info you posted

The USB4 info:

• Manufacturer: Intel, Gen12
• Firmware version: 23.3
• USB4 version: 1.0
• Total DP IN adaptors: 2
• Tunneled DP IN adaptors: 0

In plain terms:

• The USB4/TB4 controller itself is there and has firmware 23.3.
• “Total DP IN adaptors 2” = the controller can receive up to two DisplayPort inputs from the GPU.
• “Tunneled DP IN adaptors 0” = right now, no DP signal is actually being tunneled through USB4/TB – i.e. no active DP Alt‑Mode / TB display stream.

If you captured this while the iVanky hub + monitor were already plugged in and active, that suggests the DP/Alt‑Mode negotiation isn’t happening on this machine. Either:

• The port isn’t wired/enabled for DP Alt Mode correctly on this system, or
• There’s a low‑level firmware/BIOS issue, or
• There’s a hardware fault in the DP path/mux to the USB‑C port.

This is exactly the sort of thing SupportAssist typically doesn’t catch.

3. A couple of sanity checks (if you haven’t done them yet)

• Confirm the iVanky hub + cable + monitor work on another device
  Just to be 100% sure:
  • Use the same iVanky hub + same USB‑C cable + same Dell U2422H
  • Test on your Chromebook or another laptop
  If it works there, then we know the entire chain (hub + cable + monitor) is good.
• Make sure you’re using a full‑feature USB‑C cable
  Some C cables are power/USB‑2‑only. If the iVanky hub came with its own cable, use that exact cable.
• Try outside of Windows
  Since you already used a Fedora live ISO:
  • Boot into Fedora live again.
  • Plug in the iVanky hub + HDMI monitor.
  • See if Fedora detects the external display (Display settings).
  If Linux also sees no external display, that’s very strong evidence this is not a Windows or driver/security issue.
• Try to get video at boot time
  With the hub + monitor connected:
  • Turn the laptop completely off.
  • Power it on and immediately enter BIOS (F2) or the one‑time boot menu (F12).
  • See if the BIOS/boot menu appears on the external monitor.
  If you never get a picture even at BIOS level, again it points strongly to hardware/firmware on the laptop – Windows isn’t even involved yet.

4. Why BIOS/Windows “security” is unlikely to be the real blocker

Some points:

• Thunderbolt security level (SL0/SL1/SL2, etc.) affects Thunderbolt devices (like WD19TBS) and PCIe tunneling.
• Your iVanky hub is just a USB‑C DP Alt‑Mode adapter – it normally does not need Thunderbolt at all and should work even if TB is disabled, as long as DP Alt‑Mode is supported and working.
• Windows features (Defender, Core Isolation, etc.) do not selectively block DP Alt‑Mode; they operate at a much higher layer.
• That registry hack about “signal compression” would only matter once a display is actually recognized; it won’t fix a total lack of DP link.

Because even the simple USB‑C → HDMI hub is failing, the root cause is almost certainly at or below:

• GPU → USB4/TB controller DP wiring
• USB‑C DP mux/switch
• USB4/TB firmware/BIOS level
• Physical fault in the port or mainboard traces

5. What I’d do with Dell support now

At this point you have very strong evidence:

• Multiple docks/adapters and monitors tested
• Everything works on other laptops (Dell + Chromebook)
• Nothing outputs video on the Latitude 5340’s USB‑C, even simple USB‑C → HDMI
• SupportAssist passes, but USB4 info shows 0 tunneled DP even with devices attached

I’d contact Dell support and present it like this:

• “My Latitude 5340’s USB‑C/TB4 port does not output video at all.”
• “A WD19TBS dock works perfectly on other Dells and a Chromebook, but never shows up in Thunderbolt Control Center on this 5340.”
• “A simple USB‑C hub with HDMI (Ivanky) also fails to output video to a Dell U2422H, but works on other machines.”
• “SupportAssist passes, but USB4 info shows ‘Total DP IN adaptors 2’ and ‘Tunneled DP IN adaptors 0’ even when a USB‑C video device is attached.”
• “I have already updated BIOS, chipset, GPU, Thunderbolt drivers, and tested under a Linux live ISO – no video from USB‑C.” (if Linux test also fails).

Then ask clearly:

• To treat this as a suspected hardware or low‑level firmware issue with the USB‑C/TB4 port / DP path.
• For a mainboard repair/replacement or at least escalation to an engineering‑level check for known issues with DP Alt‑Mode on the Latitude 5340.

Summary

• The failure of both WD19TBS and a simple iVanky USB‑C HDMI hub on the 5340, while they work elsewhere, points strongly to an issue with the 5340’s USB‑C/TB4 display path – not Windows security or the dock itself.
• Your USB4 info (0 tunneled DP IN) is consistent with “no DP Alt‑Mode / tunneling happening at all”.
• Next concrete steps:
  • Verify the iVanky hub + cable work on another device.
  • Test USB‑C video under Linux live and at BIOS/boot if you can.
  • Use that evidence to push Dell to treat this as a hardware/firmware fault rather than a software misconfiguration.

If you run the Linux/BIOS test and let me know whether the external display shows anything there, I can help you phrase an even more precise description for Dell support.

I've just tested the Ivanky hub with my Chromebook and it successfully worked with my external display.

The Ivanky hub did not work with my Dell even in BiOS main screen the external screen never worked.

Now on my Dell I pressed F 12 during boot and I'm currently running a thorough hardware diagnostic scan and no issues were detected.

 

[Bot]

I've just tested the Ivanky hub with my Chromebook and it successfully worked with my external display.

The Ivanky hub did not work with my Dell even in BiOS main screen the external screen never worked.

Now on my Dell I pressed F 12 during boot and I'm currently running a thorough hardware diagnostic scan and no issues were detected.

Your latest tests basically close the case: the problem is on the Latitude 5340, not on the docks/adapters or the monitor.

What your results prove

• iVanky USB‑C hub + HDMI + U2422H:
  • Works on your Chromebook → hub, cable, and monitor are fine.
  • Does not work on your Latitude 5340, even:
    • On the BIOS screen
    • During F12 boot menu
    • In Windows
• WD19TBS:
  • Worked on multiple other Dell laptops and your Chromebook.
  • Never worked properly on the 5340 (no video, no TB detection).
• Dell diagnostics (SupportAssist / F12 thorough test) → no issues detected.

So:

• USB‑C/TB4 video output on the Latitude 5340 is not working at all.
• This failure is present before Windows loads (in BIOS), which means:
  • It is not caused by Windows settings, drivers, or security features.
  • It is very likely a hardware issue or a very low‑level firmware/BIOS bug in the USB‑C/DP path.

Dell’s built‑in diagnostics simply don’t do a proper test of DisplayPort Alt Mode over USB‑C, so it’s expected they miss this kind of fault.

What to do with Dell now

At this point, the only realistic next step is to get Dell to treat it as a warranty hardware/firmware problem.

When you contact Dell support, I’d present it clearly like this:

• “My Latitude 5340’s USB‑C/TB4 port does not output any video to external displays.”
• “A WD19TBS dock works perfectly on other Dell laptops and my Acer Spin 714 Chromebook, but on the 5340:
  • It never appears in Thunderbolt Control Center
  • It never sends video to external monitors
• “A simple iVanky USB‑C hub with HDMI does work with my Chromebook and the same Dell U2422H monitor, but does not show any image on the 5340 – not in Windows, not on the BIOS screen, not during F12 boot menu.”
• “I have:
  • Updated BIOS, chipset, GPU, and Thunderbolt drivers from Dell
  • Reset and checked BIOS options (Thunderbolt on/off, boot support, VT, etc.)
  • Tested under Linux live (Fedora ISO) – still no USB‑C video
  • Run full Dell hardware diagnostics (F12, SupportAssist) – no errors reported
• “Given that:
  • All docks/adapters and the monitor work on other machines
  • No USB‑C video works at any level on the 5340 (even BIOS)
  This looks like a hardware fault or low‑level firmware issue in the USB‑C/TB4 display path on my Latitude 5340, not a configuration issue.”

Then explicitly ask for:

• Escalation as a suspected USB‑C/TB4 display hardware issue.
• Board/port repair or a system replacement under warranty.

If the laptop is very new and you bought it from a store, you could also consider going through the retailer’s return/exchange process if that’s easier than arguing with Dell.

Summary

• You’ve done all the right tests: multiple docks, multiple machines, BIOS level, Linux, etc.
• All evidence says the Latitude 5340’s USB‑C/TB4 port cannot output video, even though diagnostics say “OK”.
• This is now in Dell’s court: it needs a warranty repair/replacement or a firmware fix from them, not more tweaking on your side.

If you want, you can paste what you plan to send/tell Dell here and I can help refine it further, but from a technical standpoint, you’ve already narrowed it down as far as you reasonably can.

 

[Divine_Barakah]

Your latest tests basically close the case: the problem is on the Latitude 5340, not on the docks/adapters or the monitor.

What your results prove

• iVanky USB‑C hub + HDMI + U2422H:
  • Works on your Chromebook → hub, cable, and monitor are fine.
  • Does notwork on your Latitude 5340, even:
    • On the BIOS screen
    • During F12 boot menu
    • In Windows
• WD19TBS:
  • Worked on multiple other Dell laptops and your Chromebook.
  • Never worked properly on the 5340 (no video, no TB detection).
• Dell diagnostics (SupportAssist / F12 thorough test) → no issues detected.

So:

• USB‑C/TB4 video output on the Latitude 5340 is not working at all.
• This failure is present beforeWindows loads (in BIOS), which means:
  • It is not caused by Windows settings, drivers, or security features.
  • It is very likely a hardware issue or a very low‑level firmware/BIOS bug in the USB‑C/DP path.

Dell’s built‑in diagnostics simply don’t do a proper test of DisplayPort Alt Mode over USB‑C, so it’s expected they miss this kind of fault.

What to do with Dell now

At this point, the only realistic next step is to get Dell to treat it as a warranty hardware/firmware problem.

When you contact Dell support, I’d present it clearly like this:

• “My Latitude 5340’s USB‑C/TB4 port does not output any video to external displays.”
• “A WD19TBS dock works perfectly on other Dell laptops and my Acer Spin 714 Chromebook, but on the 5340:
  • It never appears in Thunderbolt Control Center
  • It never sends video to external monitors
• “A simple iVanky USB‑C hub with HDMI does work with my Chromebook and the same Dell U2422H monitor, but does not show any image on the 5340 – not in Windows, not on the BIOS screen, not during F12 boot menu.”
• “I have:
  • Updated BIOS, chipset, GPU, and Thunderbolt drivers from Dell
  • Reset and checked BIOS options (Thunderbolt on/off, boot support, VT, etc.)
  • Tested under Linux live (Fedora ISO) – still no USB‑C video
  • Run full Dell hardware diagnostics (F12, SupportAssist) – no errors reported
• “Given that:
  • All docks/adapters and the monitor work on other machines
  • No USB‑C video works at any level on the 5340 (even BIOS)
  This looks like a hardware fault or low‑level firmware issue in the USB‑C/TB4 display path on my Latitude 5340, not a configuration issue.”

Then explicitly ask for:

• Escalation as a suspected USB‑C/TB4 display hardware issue.
• Board/port repair or a system replacement under warranty.

If the laptop is very new and you bought it from a store, you could also consider going through the retailer’s return/exchange process if that’s easier than arguing with Dell.

Summary

• You’ve done all the right tests: multiple docks, multiple machines, BIOS level, Linux, etc.
• All evidence says the Latitude 5340’s USB‑C/TB4 port cannot output video, even though diagnostics say “OK”.
• This is now in Dell’s court: it needs a warranty repair/replacement or a firmware fix from them, not more tweaking on your side.

If you want, you can paste what you plan to send/tell Dell here and I can help refine it further, but from a technical standpoint, you’ve already narrowed it down as far as you reasonably can.

What about BIOS security settings in my dell. They are overwhelming and this might be prevented due to security policies in the bios.

 

[Bot]

What about BIOS security settings in my dell. They are overwhelming and this might be prevented due to security policies in the bios.

Given everything you’ve tested so far, it’s very unlikely that a BIOS “security” setting alone is causing this – especially because:

• The iVanky USB‑C → HDMI hub (non‑Thunderbolt) shows no image even in BIOS.
• The same hub + cable + monitor work on your Chromebook.
• WD19TBS works on multiple other Dells, but never on your 5340.

Still, it’s worth clarifying what BIOS security can and cannot do, and what is sensible to check.

1. What BIOS security can actually block

On Dell Latitudes, BIOS “Security” / “Thunderbolt” options typically cover things like:

• Thunderbolt security level (SL0/SL1/SL2) – controls Thunderbolt PCIe tunneling and which TB devices are allowed.
• Enabling/disabling the Thunderbolt controller.
• Sometimes: External ports (ability to disable USB/Thunderbolt ports for data).
• Boot from external devices, Secure Boot, TPM, etc.

These can:

• Block Thunderbolt devices (like a WD19TBS) from being authorized.
• Block PCIe tunneling over TB (e.g. external GPUs, network cards).

They typically do not:

• Silently break basic USB‑C DP Alt‑Mode video for a simple adapter like the iVanky hub.
• Stop video output in BIOS while still letting basic USB work, across Windows and Linux.

If Thunderbolt security were the only issue, you would expect at least one of these:

• The WD19TBS would appear in Thunderbolt Control Center as a device awaiting authorization.
• A simple USB‑C DP Alt‑Mode hub (non‑TB) would still usually output video, even with Thunderbolt disabled.

In your case, neither happens.

2. BIOS settings that are worth double‑checking

On a Latitude 5340, the relevant areas are usually under:

• System Configuration
• Security → something like Thunderbolt Security / External Ports

Things to check (names may differ slightly):

• Thunderbolt (USB4) / USB‑C Port
  • Should be Enabled.
  • If there’s a per‑port setting (e.g. disable front/back USB‑C), make sure your port is on.
• Thunderbolt Adapter Configuration / Security Level
  • If present, set to the lowest security level or No Security for testing.
  • Enable “Allow PCIe tunneling” or similar if there’s a checkbox.
• External Ports
  • Some business Dells allow disabling all external ports for security.
  • Make sure “USB‑C / Thunderbolt” is not disabled here.

3. Best way to rule BIOS out: full reset + minimal config

To be 100% sure it’s not some obscure policy:

• Enter BIOS (F2 on boot).
• Use the option to Load Defaults / Factory Defaults.
• Save and reboot back into BIOS once.
• Then, if needed, re‑enable only:
  • Thunderbolt/USB‑C controller
  • Any “USB‑C docking” or “Thunderbolt boot support” options you specifically want
• Leave virtualization (VT‑x/VT‑d), Secure Boot, and other security options at default – they do not affect DP Alt‑Mode video.
• With this “clean” BIOS config, connect the iVanky hub + HDMI monitor and:
  • See if the BIOS screen or F12 boot menu appears on the external monitor.
  • Optionally boot a Linux live ISO again and check if it sees the external display.

If even after a full BIOS reset with Thunderbolt/USB‑C enabled:

• No USB‑C video in BIOS,
• No USB‑C video in Linux,
• No detection of WD19TBS in Thunderbolt Control Center,

then this stops being a “maybe security policy” scenario and is effectively:

• Either a hardware fault in the USB‑C/TB4 display path, or
• A very low‑level firmware/BIOS bug that Dell would have to fix.

4. Why your tests strongly favor hardware/firmware over security

You’ve already shown:

• iVanky hub works fine on Chromebook with the same monitor and cable.
• WD19TBS works fine on other Dells and the Chromebook.
• Nothing that uses USB‑C for video works on the 5340, at any stage (BIOS, Windows, Linux).
• You’ve updated BIOS, chipset, GPU, Thunderbolt drivers.
• SupportAssist and F12 diagnostics report no issues (but they don’t properly test DP Alt‑Mode).

This pattern is exactly what you’d expect from:

• Broken DP Alt‑Mode path (GPU → USB4/TB controller → USB‑C port), or
• A USB4/TB firmware bug that prevents DP from being tunneled/negotiated at all.

Not from a “normal” BIOS security setting.

5. What I’d do now

• Perform the BIOS defaults reset + minimal re‑enable test once, as above, just to be absolutely sure.
• If still no USB‑C video anywhere:
  • Contact Dell support.
  • Explain that:
    • Multiple docks/adapters and the monitor all work on other systems.
    • No USB‑C video works on the 5340, even in BIOS and Linux, after a BIOS reset.
    • Diagnostics pass, but the USB‑C/TB4 port doesn’t output any video.
  • Ask for the case to be treated as a suspected USB‑C/TB4 display hardware or low‑level firmware failure, and request repair or mainboard replacement.

Bottom line

BIOS security options can definitely make Thunderbolt devices annoying, but they usually don’t silently kill all USB‑C video like this, across BIOS/Windows/Linux and with simple DP Alt‑Mode adapters.

If you reset BIOS to defaults, re‑enable Thunderbolt/USB‑C, and it still can’t drive an external screen, you’re almost certainly looking at a defect that only Dell can fix.

 

[Divine_Barakah]

Given everything you’ve tested so far, it’s very unlikely that a BIOS “security” setting alone is causing this – especially because:

• The iVanky USB‑C → HDMI hub (non‑Thunderbolt) shows no image even in BIOS.
• The same hub + cable + monitor work on your Chromebook.
• WD19TBS works on multiple other Dells, but never on your 5340.

Still, it’s worth clarifying what BIOS security can and cannot do, and what is sensible to check.

1. What BIOS security can actually block

On Dell Latitudes, BIOS “Security” / “Thunderbolt” options typically cover things like:

• Thunderbolt security level (SL0/SL1/SL2) – controls Thunderbolt PCIe tunneling and which TB devices are allowed.
• Enabling/disabling the Thunderbolt controller.
• Sometimes: External ports (ability to disable USB/Thunderbolt ports for data).
• Boot from external devices, Secure Boot, TPM, etc.

These can:

• Block Thunderbolt devices (like a WD19TBS) from being authorized.
• Block PCIe tunneling over TB (e.g. external GPUs, network cards).

They typically do not:

• Silently break basic USB‑C DP Alt‑Mode video for a simple adapter like the iVanky hub.
• Stop video output in BIOS while still letting basic USB work, across Windows and Linux.

If Thunderbolt security were the only issue, you would expect at least one of these:

• The WD19TBS would appear in Thunderbolt Control Center as a device awaiting authorization.
• A simple USB‑C DP Alt‑Mode hub (non‑TB) would still usually output video, even with Thunderbolt disabled.

In your case, neither happens.

2. BIOS settings that are worth double‑checking

On a Latitude 5340, the relevant areas are usually under:

• System Configuration
• Security → something like Thunderbolt Security / External Ports

Things to check (names may differ slightly):

• Thunderbolt (USB4) / USB‑C Port
  • Should be Enabled.
  • If there’s a per‑port setting (e.g. disable front/back USB‑C), make sure your port is on.
• Thunderbolt Adapter Configuration / Security Level
  • If present, set to the lowest security level or No Security for testing.
  • Enable “Allow PCIe tunneling” or similar if there’s a checkbox.
• External Ports
  • Some business Dells allow disabling all external ports for security.
  • Make sure “USB‑C / Thunderbolt” is not disabled here.

3. Best way to rule BIOS out: full reset + minimal config

To be 100% sure it’s not some obscure policy:

• Enter BIOS (F2 on boot).
• Use the option to Load Defaults / Factory Defaults.
• Save and reboot back into BIOS once.
• Then, if needed, re‑enable only:
  • Thunderbolt/USB‑C controller
  • Any “USB‑C docking” or “Thunderbolt boot support” options you specifically want
• Leave virtualization (VT‑x/VT‑d), Secure Boot, and other security options at default – they do not affect DP Alt‑Mode video.
• With this “clean” BIOS config, connect the iVanky hub + HDMI monitor and:
  • See if the BIOS screen or F12 boot menu appears on the external monitor.
  • Optionally boot a Linux live ISO again and check if it sees the external display.

If even after a full BIOS reset with Thunderbolt/USB‑C enabled:

• No USB‑C video in BIOS,
• No USB‑C video in Linux,
• No detection of WD19TBS in Thunderbolt Control Center,

then this stops being a “maybe security policy” scenario and is effectively:

• Either a hardware fault in the USB‑C/TB4 display path, or
• A very low‑level firmware/BIOS bug that Dell would have to fix.

4. Why your tests strongly favor hardware/firmware over security

You’ve already shown:

• iVanky hub works fine on Chromebook with the same monitor and cable.
• WD19TBS works fine on other Dells and the Chromebook.
• Nothing that uses USB‑C for video works on the 5340, at any stage (BIOS, Windows, Linux).
• You’ve updated BIOS, chipset, GPU, Thunderbolt drivers.
• SupportAssist and F12 diagnostics report no issues (but they don’t properly test DP Alt‑Mode).

This pattern is exactly what you’d expect from:

• Broken DP Alt‑Mode path (GPU → USB4/TB controller → USB‑C port), or
• A USB4/TB firmware bug that prevents DP from being tunneled/negotiated at all.

Not from a “normal” BIOS security setting.

5. What I’d do now

• Perform the BIOS defaults reset + minimal re‑enable test once, as above, just to be absolutely sure.
• If still no USB‑C video anywhere:
  • Contact Dell support.
  • Explain that:
    • Multiple docks/adapters and the monitor all work on other systems.
    • No USB‑C video works on the 5340, even in BIOS and Linux, after a BIOS reset.
    • Diagnostics pass, but the USB‑C/TB4 port doesn’t output any video.
  • Ask for the case to be treated as a suspected USB‑C/TB4 display hardware or low‑level firmware failure, and request repair or mainboard replacement.

Bottom line

BIOS security options can definitely make Thunderbolt devices annoying, but they usually don’t silently kill all USB‑C video like this, across BIOS/Windows/Linux and with simple DP Alt‑Mode adapters.

If you reset BIOS to defaults, re‑enable Thunderbolt/USB‑C, and it still can’t drive an external screen, you’re almost certainly looking at a defect that only Dell can fix.

Would enabling Video/Power only on Type-C ports help with Ivanky Hub?

 

[Bot]

Would enabling Video/Power only on Type-C ports help with Ivanky Hub?

Enabling Video/Power only on the Type‑C port is unlikely to fix your issue, and for testing it’s actually the wrong direction to go.

What “Video/Power only” usually does

On Dell business laptops, that option typically means:

• Allowed:
  • USB‑C power (charging)
  • DisplayPort Alt‑Mode video (to a monitor/dock)
• Blocked:
  • USB data over Type‑C (flash drives, USB devices on the hub)
  • Thunderbolt / PCIe tunneling

So with Video/Power only = Enabled:

• Your iVanky hub’s HDMI output should still work if the DP Alt‑Mode path is healthy.
• The USB ports and Ethernet (if any) on the hub would stop working (no data).

But your problem is that video itself is not working at all, even:

• In BIOS
• In Windows
• With a simple USB‑C → HDMI hub that works fine on your Chromebook

That strongly suggests the DP Alt‑Mode / USB‑C display path is broken or bugged. “Video/Power only” is designed to restrict features for security, not to enable them.

For troubleshooting, you actually want:

In BIOS, for the Type‑C / Thunderbolt settings, you should aim for:

• USB‑C / Thunderbolt Enabled
• Full Video + Data + Power (not Video‑only)
• Thunderbolt Security at the lowest level or “No Security” just for testing
• External Ports not disabled

If, with that “fully open” configuration:

• The iVanky hub still shows no video in BIOS,
• Still no video in Windows or Linux,

then toggling to “Video/Power only” will not magically make it work. It would just further reduce what the port can do.

Bottom line

• For testing, do not enable “Video/Power only”. Use full Video + Data + Power instead.
• Your existing tests (no USB‑C video in BIOS, Linux, or Windows; hubs/docks work on other devices) already point much more to:
  • A hardware fault in the USB‑C/DP path, or
  • A very low‑level firmware issue Dell needs to fix.

If you’ve already tried with full features enabled and still get no video, I’d focus on pushing Dell for a repair/board replacement rather than hunting for a BIOS security toggle to fix this.

 

[Divine_Barakah]

Thunderbolt Security at the lowest level or “No Security” just for testing

There is no option to change Thunderbolt security in my Dell Latitude 5340.

 

[Bot]

There is no option to change Thunderbolt security in my Dell Latitude 5340.

On some Latitude 5340 BIOS versions it’s normal that you don’t see any Thunderbolt Security level option – Dell can lock it to a default (e.g. SL1) and simply not expose the toggle.

The key point: that does not explain your symptoms, especially:

• The iVanky USB‑C → HDMI hub (non‑Thunderbolt) shows no video even in BIOS.
• The same iVanky hub + cable + monitor work fine on your Chromebook.
• WD19TBS works on other Dell laptops but gives no video and is not detected in Thunderbolt Control Center on your 5340.

Why missing “Thunderbolt security” option is not the culprit

• The iVanky hub uses DisplayPort Alt‑Mode over USB‑C, not Thunderbolt PCIe tunneling.
• Thunderbolt security settings, even when strict, affect mainly Thunderbolt devices and PCIe tunneling – not simple DP Alt‑Mode adapters.
• If Thunderbolt security were blocking only TB docks:
  • You would still expect the WD19TBS to appear in some way (e.g. as an unauthorized device) in Thunderbolt Control Center.
  • The iVanky hub should still show video in BIOS, because BIOS‑level DP Alt‑Mode does not depend on Windows Thunderbolt policies.
• The fact that no USB‑C video works (BIOS, Windows, Linux) strongly suggests:
  • A problem in the DP Alt‑Mode path (GPU → USB4 controller → Type‑C port), or
  • A low‑level USB4/TB firmware/BIOS bug, or
  • A physical fault with the port or mainboard.

What you can still check in BIOS

Even without a Thunderbolt security toggle, you can verify:

• USB‑C / Thunderbolt / USB4 controller is Enabled.
• Any External Ports / “Port Disable” settings are not disabling the Type‑C port.
• You’ve done a Load Defaults / Restore Factory Settings in BIOS, then:
  • Re‑enabled USB‑C / Thunderbolt if needed.
  • Left the rest mostly at defaults.

If after that:

• The iVanky hub still shows no video in BIOS,
• Still no video in Windows or Linux,
• WD19TBS still isn’t visible in Thunderbolt Control Center,

then this is almost certainly not something you can fix with BIOS security options.

Next realistic step

You’ve already gathered very strong evidence for Dell:

• Multiple docks/adapters + monitor work on other machines.
• None of them produce USB‑C video on the Latitude 5340, at any stage (BIOS, Windows, Linux).
• Diagnostics pass, but DP Alt‑Mode / tunneling never actually happens.

At this point, the missing Thunderbolt Security option is just a design/firmware choice, not the root of your problem. The root issue looks like:

• A hardware fault in the USB‑C/TB4 video path, or
• A low‑level firmware/BIOS bug Dell needs to fix.

So I’d focus on pushing Dell support for:

• Escalation as a USB‑C/TB4 display failure.
• Mainboard/port repair or system replacement under warranty.

If you’d like, you can paste your full description of the issue (including what you told me) and I can help you condense it into something clear and “engineer‑friendly” to send to Dell.