Forum Discussion
Device Manager - Windows changes settings without my permission
I'm getting no traction from Dell, Microsoft, or any other support sites so I am posting here.
I have a major problem with my settings in Device Manager. I have a brand new Dell laptop.
I have drivers that control the touchpad on my laptop. I have set the "Allow the computer to turn off the device to save power" setting unchecked on all of my touchpad drivers.
Windows will randomly enable this setting without my permission. The result is that sometimes when I wake my laptop from Sleep, the touchpad is not working.
How do I stop Windows from changing this setting? The change is happening automatically and I want it to stop.
Before one of the idiot Microsoft employees or independent advisors jumps on here:
- This is a brand new computer, have had it for 1 week
- This happens with the factory drivers and the updated recent drivers directly from Microsoft and Intel
- The touchpad has already been replaced with a new touchpad, behavior still occurs
- My user account is an Administrator account
- I already have all of the newest Dell updates and Windows updates, including Bios updates
3 Replies
Do a factory reset and see if the problem was solved.
I will not be factory resetting the device but thanks for the option.
I'm experiencing the same issue. I'm running a Dell XPS15 laptop. The drive in question seems to be "Intel(R) Serial IO I2C Host Controller - A369." When the computer wakes up, the touchpad requires something like 4-5 seconds of my finger moving on the touchpad before I have control of the mouse. When I remove my finger, the 4-5 seconds resets. It's annoying as hell. The only solution I've come across that works is disabling "Allow the computer to turn off this device to save power," under the power management tab. Unfortunately, when Windows performs an update, it resets this driver setting and my mouse breaks again after the computer wakes up from a period of sleep.
If anyone has any suggestions, please share them. I've tried upgrading the firmware, but the issue persists.
