Keyboard LEDs go out in seconds after using keyboard

I'm running Win10 Version 1607, Build 14393.1358 on a Dell 3650. My input devices are a Microsoft 'curvy' USB keyboard and a Logitech Wireless Trackman that has the little USB receiver plugged into another USB port.

My problem is not critical, just unusual and annoying. The green Num Lock and Caps Lock LEDs on the keyboard indicate properly while I am typing, but after about 5 seconds of keyboard inactivity, they go out. Not a big deal, but when resuming work, I can't simply glance down and see what's what... I have to hit a random key to wake them up for another 5 seconds.

Under Device Manager I see two entries under Keyboards, both are named HID Keyboard Device. One looks to be a 'standard' keyboard, the other is apparently the Logitech RF plug-in, which can accept a wireless keyboard, which I am not using, as well as the wireless trackball, which I am. Under Power Management on both, neither box is checked to save power or to wake the computer. Here's a screenshot:

This is the same USB keyboard I was using with a previous Vista system, and the LEDs worked 'normally' then. Is there something in Win10 that turns these LEDs off, and is it normal for this OS, or do I have a problem?

SOLVED! Needing instant gratification, I continued to search the Web for a reason for this situation, and found this post:
Solved: Microsoft Wired Keyboard 200 Randomly Disconnects
This guy had worse problems with a Microsoft keyboard, but among his complaints was the same business with the LEDs going out after a few seconds. So, although the Properties of that keyboard were NOT set up for power-saving under Device Manager, if instead you navigate to the keyboard through the Control Panel, there's a whole raft of additional Properties boxes and, wonder of wonders, one of them had that power-save option checked. Unchecking it did the trick and I'm stoked. So, riddle me this, Batman, what's the story with 'hidden' Properties boxes? I never would have found the stealth ones if it weren't for this guy's post.