I'd like to know why my CAPS lock light won't light up after a clean install of Windows 11

Question

I have a Dell Inspiron 3780 laptop and the CAPS lock light won't turn on when Windows is running (it works fine during startup). I recently did a clean install of Windows 11 (the latest Insider Preview version in the Developer channel). I'd really appreciate any thoughts on how to start troubleshooting. Thanks!

Answer 1

The cap locks is a known problem.

It is being troubleshooted by Microsoft:

"We’re working on a fix to address reports from some Insiders that the lights on their keyboards, for example for caps lock, are not working properly after upgrading to the previous build."

.
.
.
.
.

Please remember to vote and to mark the replies as answers if they help.

.
.
.
.
.

Answer 2

Make sure the chipset has been installed. The chipset allows the operating system to find and use devices integrated into the mother board.
https://www.dell.com/support/home/en-us/product-support/product/inspiron-17-3780-laptop/drivers

--please don't forget to upvote and if the reply is helpful--

Answer 3

Sounds good, you could try reverting to a known supported operating system to check the hardware. Also try asking in Dell forums for help with the hardware problems.
https://www.dell.com/community/Inspiron/bd-p/Inspiron

--please don't forget to upvote and Accept as answer if the reply is helpful--

Answer 4

See this thread:

https://www.elevenforum.com/t/kb5008400-cumulative-update-for-windows-11-insider-preview-dev-build-22499-1010-nov-12.2686/#post-54941

Known issues​
[General]
Users updating from Builds 22000.xxx, or earlier, to newer Dev Channel builds using the latest Dev Channel ISO, may receive the following warning message: The build you are trying to install is Flight Signed. To continue installing, enable flight signing. If you receive this message, press the Enable button, reboot the PC, and retry the update.
We’re investigating an issue where some PCs are unable to install new builds, or other updates. The PC may report an error code 0x80070002. If you are experiencing this issue, please reboot your PC and try again.
Some devices may bugcheck with error code 0xc1900101-0x4001c when installing this build. If you hit this, after the device rolls back to the previous build, you may want to pause updates until we release a fix.
[Start]
In some cases, you might be unable to enter text when using Search from Start or the Taskbar. If you experience the issue, press WIN + R on the keyboard to launch the Run dialog box, then close it.
[Taskbar]
The Taskbar will sometimes flicker when switching input methods.
We’re investigating an issue in this build where the clock in the Taskbar can get stuck and not updated, particularly when accessing the PC via Remote Desktop.
[Windowing]
Hovering your mouse back and forth between different desktops in Task View will result in the displayed thumbnails and content area unexpectedly shrinking.
[Input]
We’re working on a fix to address reports from some Insiders that the lights on their keyboards, for example for caps lock, are not working properly after upgrading to the previous build.
[Search]
After clicking the Search icon on the Taskbar, the Search panel may not open. If this occurs, restart the “Windows Explorer” process, and open the search panel again.
[Quick Settings]
We’re investigating reports from Insiders that the volume and brightness sliders aren’t displaying properly in Quick Settings.

.
.
.
.
.

Please remember to vote and to mark the replies as answers if they help.

.
.
.
.
.