Your keyboard and mouse work perfectly after Windows starts.

You can type documents, move the cursor, and use every USB device connected through your USB-C dock.

Then you restart the computer.

At the BIOS screen, nothing happens.

You cannot enter setup.

You cannot type your BitLocker PIN.

Your keyboard appears completely disconnected.

This situation is confusing because the same dock and the same keyboard worked only seconds earlier inside Windows.

The reason is simple:

Windows USB support and pre-boot USB support are not the same environment.

Before Windows loads, the computer is not using the full operating system drivers.

At this stage, keyboard and mouse support depends on:

• BIOS/UEFI firmware;
• USB controller initialization;
• dock compatibility;
• security settings;
• USB legacy support.

A USB-C dock can therefore work perfectly after login but fail during the boot process.

Windows Working Does Not Prove BIOS Compatibility

Many users test a dock like this:

Laptop → USB-C Dock → Keyboard

Windows loads.

Keyboard works.

Conclusion:

“The dock is compatible.”

For normal desktop use, that may be true.

But boot-time compatibility is a separate test.

The computer has two different stages:

Stage 1: Pre-Boot Environment

Before Windows loads:

• BIOS setup;
• UEFI firmware;
• BitLocker recovery screen;
• boot selection menu.

At this stage, the system depends on firmware-level USB support.

Stage 2: Operating System Environment

After Windows starts:

• USB drivers load;
• dock drivers initialize;
• full device management becomes available.

A device can pass Stage 2 while failing Stage 1.

That is why:

Keyboard works in Windows

does not automatically mean:

Keyboard works in BIOS through the dock

What Happens During Boot?

When you press the power button, the computer performs hardware initialization.

The firmware must discover:

• internal storage;
• display output;
• USB controllers;
• keyboards;
• mice;
• boot devices.

A directly connected USB keyboard is usually simple for firmware to recognize.

A USB-C dock is more complex.

The path becomes:

Keyboard

↓

USB-C Dock

↓

USB-C Port

↓

Laptop USB Controller

↓

BIOS/UEFI Firmware

Each layer must support pre-boot communication.

If the firmware cannot initialize the dock's USB hub controller before Windows loads, the keyboard will appear missing.

First Question: Does the Keyboard Work Directly?

Before changing BIOS settings, remove the dock.

Connect:

Keyboard → Laptop USB Port

Restart the computer.

Test:

• BIOS entry;
• BitLocker PIN input;
• boot menu navigation.

If Direct Connection Works

Your keyboard is fine.

The issue is likely related to:

• dock firmware;
• USB-C pre-boot support;
• BIOS compatibility;
• port initialization.

If Direct Connection Also Fails

The problem is not the dock.

Check:

• keyboard itself;
• BIOS USB settings;
• laptop firmware;
• USB ports.

This simple comparison avoids troubleshooting the wrong device.

Check BIOS Settings Related to USB

Different laptop manufacturers use different names, but common settings include:

• USB Legacy Support;
• USB Keyboard Support;
• External USB Port Enable;
• Thunderbolt Pre-Boot Support;
• USB Boot Support;
• Always Enable USB.

If USB keyboard support is disabled in firmware, Windows can still work normally because Windows loads its own drivers later.

That creates exactly this symptom:

Works after login, fails before login.

Enable relevant USB support options, save changes, and test again.

BitLocker Adds Another Layer

BitLocker is different from normal Windows login.

When BitLocker asks for a PIN before Windows starts, the operating system has not loaded yet.

The computer is still operating in a pre-boot environment.

Microsoft explains that BitLocker authentication occurs before Windows starts and relies on the system firmware and Trusted Platform Module (TPM) environment to validate startup conditions.

Therefore:

A keyboard that works inside Windows does not automatically prove it will work during BitLocker authentication.

If your company uses:

• BitLocker PIN;
• startup authentication;
• recovery keys;
• BIOS passwords;

pre-boot keyboard testing should be part of hardware deployment.

Why Some USB-C Docks Fail Before Windows

A USB-C dock may include:

• USB hub controller;
• Ethernet controller;
• card reader;
• audio controller;
• display adapter;
• additional USB devices.

During Windows operation, drivers handle these components.

During BIOS startup, firmware support is much more limited.

Common failure scenarios include:

Scenario 1: Simple USB Keyboard

Works directly.

Works through dock after Windows.

Fails in BIOS.

Possible cause:

Dock USB hub is not initialized during pre-boot.

Scenario 2: Keyboard Works, Mouse Does Not

Possible cause:

Different USB device initialization behavior.

Some firmware environments prioritize basic HID keyboard support but handle other USB devices differently.

Scenario 3: Works on One Laptop, Fails on Another

Possible cause:

Different:

• BIOS version;
• USB-C implementation;
• Thunderbolt settings;
• firmware support.

This is why enterprise IT teams should test:

Laptop + Dock + Firmware

as a complete configuration.

Thunderbolt and USB-C Security Settings Can Matter

Business laptops often include security controls for external devices.

Examples:

• Thunderbolt Security Level;
• External Device Authorization;
• Pre-Boot ACL;
• DMA protection.

A dock may work after Windows because the operating system authorizes the device.

But before Windows loads, firmware may block or limit it.

For Thunderbolt systems, check manufacturer firmware settings and whether external devices require approval before boot.

Do not assume:

USB-C port = unrestricted pre-boot access

Test Different USB-C Ports

Some laptops have multiple USB-C ports with different capabilities.

One port may support:

• Thunderbolt;
• charging;
• display output;

while another supports only:

• USB data.

Even when Windows works, firmware behavior may differ between ports.

Test:

Dock → USB-C Port A

and:

Dock → USB-C Port B

Record:

This type of information is exactly what should be captured in an enterprise USB-C compatibility matrix.

For larger deployments, see our guide on creating a USB-C hub compatibility matrix for IT teams.

Simplify the Dock Setup During Testing

Do not test BIOS compatibility with a fully loaded workstation first.

Remove:

• external SSD;
• webcam;
• Ethernet;
• audio devices;
• card readers.

Start with:

Laptop → Dock → Keyboard only

Then add devices back.

Why?

Because every additional USB function increases firmware initialization complexity.

A dock that works with:

Keyboard

may behave differently when it also has:

Ethernet + storage + audio + webcam

connected.

Choosing a Dock for Enterprise Pre-Boot Testing

For IT teams, the most important question is not:

“How many ports does this dock have?”

The better question is:

“Does this dock pass our required workflow on our approved laptop fleet?”

For a basic office profile requiring:

• keyboard;
• mouse;
• HDMI display;
• Ethernet;
• USB devices;

a compact configuration such as the LENTION USB-C hub with Gigabit Ethernet, HDMI, and USB 3.0 ports can be included as a candidate device for compatibility testing.

It provides:

• Gigabit Ethernet;
• HDMI output;
• three USB 3.0 ports.

For a permanent workstation deployment requiring:

• multiple USB devices;
• Ethernet;
• display output;
• charging;
• audio;

a full docking station such as the LENTION USB-C docking station with 4K@60Hz HDMI, Gigabit Ethernet, USB ports, audio, and PD pass-through is a more appropriate enterprise test profile.

However, neither USB-C hub nor docking station should be considered automatically compatible with BIOS or BitLocker environments.

Pre-boot support must be tested with:

Laptop model

BIOS version

Dock firmware

Security configuration

IT Deployment Checklist

Before approving a USB-C dock for company-wide use, test:

Windows Environment

✓ Keyboard works after login
✓ Mouse works after login
✓ External display works
✓ Ethernet works
✓ USB storage works

Pre-Boot Environment

✓ BIOS keyboard input
✓ Boot menu navigation
✓ BitLocker PIN input
✓ Recovery key input

Security Environment

✓ Thunderbolt authorization
✓ BIOS USB settings
✓ Firmware updates
✓ Corporate security policies

Recovery Scenario

✓ Dock reconnects after restart
✓ Dock works after firmware update
✓ User can complete recovery without removing the dock

Quick Answers

Why does my keyboard work in Windows but not BIOS through a USB-C dock?

Because Windows uses full USB drivers after startup, while BIOS relies on firmware-level USB support.

Can a USB-C dock prevent BitLocker PIN entry?

Yes. If the dock's USB path is not available during pre-boot, the keyboard connected through it may not work before Windows loads.

Will buying a powered USB-C dock fix BIOS keyboard problems?

Not necessarily. Power can help device stability, but pre-boot support depends mainly on firmware and USB initialization.

Why does the same dock work on one laptop but not another?

Different laptops may have different:

• BIOS support;
• USB-C controllers;
• Thunderbolt settings;
• firmware behavior.

Final Takeaway

A USB-C dock passing Windows testing does not automatically mean it passes pre-boot testing.

For BIOS, UEFI, and BitLocker scenarios, the important question is:

Can the laptop firmware communicate with the dock before Windows loads?

The reliable troubleshooting path is:

Direct keyboard test

→ BIOS USB settings

→ Different USB-C ports

→ Dock simplification

→ Firmware/security settings

For business environments, pre-boot compatibility should be treated as a separate requirement—not assumed from normal Windows operation.

A dock is truly enterprise-ready only when it works where users need it most:

before login, during recovery, and during everyday work.