Keyboard and displays don't work when using a KVM on a computer with bitlocker

[Talkar]

Hi,
When I try to boot up my laptop (a lenovo p52), my displays don’t render anything.
And I’m fairly certain that my keyboard isn’t outputting anything to the laptop either.

My keyboard is a Mountain Everest, and my display is a Samsung CRG9.
My KVM is connected to a docking station, and the docking station is connected to the laptop.
So I tried taking the USB cable going from the KVM to the docking station, and plugging it into the laptop directly.
I then disconnected the display port cables, so that the boot screen would render on my laptops screen.
This was done to test the keyboard specifically.

What happens then, when I turn on the laptop, is that the boot screen is rendered, and then I arrive at bitlocker, asking for its password.
Here I discovered, I can’t use the keyboard
Nothing happens when I enter anything on the keyboard.
If I use the laptops built in keyboard, everything works fine.

If I connect everything as I want it, through the KVM, and enter my bitlocker password using the laptops built in keyboard, then everything works fine, once booted into windows.

So it seems to me, that bitlocker does not like the KVM. Any idea on how to enable my keyboard during boot?
I don’t really care about the displays that much, as I can just wait X time, and estimate that the computer is waiting for a bitlocker password, and enter it.
But not having a functioning keyboard in bitlocker, is tricky.

[Talkar]

Hello again,
I got it working!

So, there were a couple of issues, that obfuscated the problem .
Firstly, I had to change the boot mode from “Diagnostic” to “Quick”, and also set my boot display option to “USB-C”, which means the dock.
The second issue, was that my keyboard was plugged into the port on the KVM with a keyboard symbol.
Instead, I moved it to the front USB that doesn’t say “HID”.
I also had to unplug all of my USB and power cable from the KVM, and then reconnect it all.
But now everything seems to be working!

I’m replying and leaving the solution here, in case another user experiences the same issues, even though I reckon the chance is small, since it seems a configuration, that is specific to my setup, was at primary fault.