Monitors will not time out after 2004

I recently forced the 2004 update on my gaming desktop (Windows 10 Pro 64bit).
After doing so I have noticed that my monitors (2 of them) will no longer turn off after a set amount of inactivity. Previously they were set to turn off after 10 minutes of inactivity. All systems said that they should turn off after 10 minutes of inactivity, but they do not. Seriously, I can go watch a Star Wars movie and when I come back to my computer they are still on.

Power & Sleep Settings is set to turn them off after 10 minutes.
Power Settings: Balanced Plan is set to turn them off after 10 minutes.
Balanced Plan's advanced settings: Display is set to turn them off after 10 minutes.

These settings were not synchronized, because I was messing with them. I have now synchronized them. However, that did not solve the problem. Resetting the power plan, or changing the power plan to a different plan did not fix the problem either.
Then I thought maybe it was a screen saver issue, so I activated a blank screen saver to come on after 10 minutes of inactivity. That doesn't work either.
I have tried all of the suggestions on this FAQ: Fixed: Windows 10 Screensaver Not Working | SoftwareKeep.
That also did not work.
Please Help.
Thanks for your time and effort in advance.

dalchina said:

This might be of interest: not specifically 2004. No guarantees.
Windows 10 Display Won't Turn Off After the Specified Time | Alexander's Blog


A different example- consider other peripherals.
Screens Won't Timeout

thanks for trying, if you looked at the article I tried: Fixed: Windows 10 Screensaver Not Working | SoftwareKeep
It offers 8 supposed solutions to the problem. The possible solutions in your post were already included in the article I used and have been tried.

dalchina said:

Sorry I don't have time to compare articles- that's something you are free to do. Help is given in volunteers' free time- not paid for.

As far as I know your problem is not a known issue.

Have you considered the other idea?

Feel free to research on tenforums with suitable searches.

My apologies, I did not mean to come off as rude.
My only other idea, is that there might be something (either on my end or on windows end) that is forcibly keeping the system in an active state, so that it never is seen as inactive to activate those properties.....
Im a grad student, and I have been so busy with summer classes to throw this bad boy into safe mode and find out...

- - - Updated - - -

Had time (or rather made time) to throw it into safe mode last night.
Turned all the metrics down to 1 minute and let it idle, no change.
I turned all the metrics up to 10 minutes and let it idle, no change.
The monitors just do not shut off.
Maybe windows is forcing the activity....
open to suggestions....

Not really sure what I did that made my monitors start working again.
I took a long hard look at some of the old stale background processes of my PC.
I noticed a couple of things that were running that should not have been running.
For one I found teamviewer (a remote support software, that I use to help others with their computer problems), I noticed it had a linked service that started automatically, I stopped it and put it on manual.
I also noticed some softwares that were bundled with my ASUS mobo (now like 5+ years old), AIChargerPlus which is supposed to be able to determine automatically if the charging device will fast charge and then adjust power accordingly (never noticed if it actually worked, I have wall warts for charging needs), and WiFi GO! File Transfer (my PC does not have wifi, so...), I ended them and disabled their ability to start up.
I am pretty sure that there was at least one other service item I noticed was attached to a program that was running, but I cannot for the life of me remember what it was, anyway I stopped it and turned it to manual startup as well.

Anyway monitor sleep functionality restored! YAY!

Aggravatingly, just after rebooting, the problem returned.
I spent several days diagnosing just about everything I could to no avail.
I decided to try systematically forcing the machine to turn off the screens by remapping screen off to the power button in power settings.
Every time I turned it off it came back on, so frustrating.
I decided to diagnose my hardware.
I ran in powershell: powercfg -devicequery wake_armed
This told me that all of my external hardware (razer blackwidow ultimate, razer deathadder, and razer tartarus) were allowed to wake the computer.
So, by removing each individually and forcing the computer to sleep each time I found out it was my tartarus causing the issue.
After a quick google, I found this article: https://answers.microsoft.com/en-us/...8-51c25e8b062a
Basically, it says that sometimes there is an issue with the tartarus' joystick being detected by windows. When this happens windows will activate the driver HID-compliant game controller. Apparently, this will conflict with the tartarus driver, and as a result leave the computer in a waking state.
Solution – Disable HID-compliant game controller