Windows 10: Monitor/display will not turn off

Same principles apply here, too. If it works on Safe Mode, you will need to start disabling devices (starting again from Human Interface ones) and testing if you can turn the monitor off.

 

Disabling this "HID-compliant game controller, 10.0.10240.16384, Microsoft, 6/21/2006" , solved my problem.

 

ScreenOff works but disabling Human Interface devices and usb drives and still have problem.

Again for reiteration if I make my power options plan to turn off display after 1 minute this never happens.

All help appreciated.

Thank you.

 

I'm also having this issue but it seems related to plugging my dualshock 4 controller in via usb. If I remove all the HID devices from my device manager my computer sleeps normally but as soon as I connect the ds4 controller it stops working again. I've gone through every one of the devices and made sure that it has the proper power settings and can't wake the computer but nothing seems to work for me aside from manually removing everything. Obviously, from a practical standpoint that is not a good solution.

 

Same thing here, never noticed it before but plugged in my PS4 controller yesterday and suddenly the screen will no longer turn off after the expected 10 mins. As soon as I unplugged the controller, 10 mins later the screen goes off fine.

 

Same problem with my computer Will, I also have a HP Pavilion 23, If I find a solution I will let you know, I hope you can help me too *Biggrin

 

Latest update for Windows 10 sorted my problem out.

 

In my case it was the Interlink Elite Controller for my RealFlight 7 Radio Control Flight Simulator. I tried it first since it was in the uppermost USB slot. Just a lucky choice. Next was going to be my Logitech Attack 3 Joystick, but it is not blocking the shutdown. Apparently it is not maintaining a running dialog with the computer.

*MadUnfortunately...... The screen saver was also affected by this. In the meantime the screen on our Dell E173FP took a hit where a particular image sat for long periods during the day (and, often, during the night since W10 loves to awaken our computers from Hibernation in the middle of the night). Others report success fixing stuck pixels with JScreenFix. I can't say if it is snake-oil or not, but I tried it for half an hour with no noticeable change in the "burn".

 

After a lot of tinkering found that disabling USB composite device in Device Manager solved the issue for me. Now I can turn the display off manually using the power buttons and/or using the power option menu to turn off the display after a specified time.

This was driving me crazy! Really unhappy with Microsoft Support. Absolutely no help whatsoever!

EDIT: Doing this breaks touch screen functionality. Basically my touch screen Pavilion 23 is rendered useless if I choose to fix the display issue. *Mad

 

All was working OK for about 5 days all by itself but suddenly yesterday I got same problem again.

I have set power options to turn off screen after 20 minutes.

Any ideas what could be causing this

I tried command powercfg -requests and get None on all results.

All help appreciated.

Thank you.

 

Okay, I made an account to respond to this, because I was curious about something. Do you happen to use Bitdefender? I'm getting this problem a lot too, but just today I took a look at my antivirus. I have Bitdefender, and it's usually the issue with just about every problem I have. I looked through, and Bitdefender has a series of profiles in the tools menu.

When in autopilot, bitdefender changes between these profiles at will, and both the Movie and Game profiles have a configuration that is on by default which states that it adjusts power plan settings on its own. That could be a solution, but I'm not sure what bitdefender does to accomplish this, if it would do exactly what you're describing.

 

Sorry I do not use bitdefender.

Problem is sporadic. Some days it works some days I have problems.

All help appreciated.

Thank you.

 

No sign of a fix yet from Microsoft...

 

Thanks for this. This did the trick for me.

 

Same problem here on an Acer v3-772g laptop.