Laptop (Asus) not waking from sleep..

hdmi said:

If input suppression is enabled, then when the laptop is on battery power, to wake the laptop from sleep you need to press the power button. This is to assure that the laptop doesn't get woken up accidentally inside a laptop bag or backback. If input suppression is disabled, then when the laptop is on battery power, the laptop can wake up accidentally if something accidentally slides between the keyboard and the lid e.g. as a result of shaking/swinging the laptop bag or backback around.

Click to expand...

I get that, but I can wake the laptop by pressing any key when on battery so does this mean this Input Suppresion is disabled on my system? How do I enable/disable it, I found 4 keys in my registry with InputSuppression (see attached)

FrankW said:

I get that, but I can wake the laptop by pressing any key when on battery so does this mean this Input Suppresion is disabled on my system? How do I enable/disable it, I found 4 keys in my registry with InputSuppression (see attached)

Click to expand...

To check whether input suppression is enabled:
reg query HKLM\SYSTEM\CurrentControlSet\Control\Power /v EnableInputSuppression
0x1 = enabled (default), 0x0 = disabled

To enable it:
reg add HKLM\SYSTEM\CurrentControlSet\Control\Power /v EnableInputSuppression /t REG_DWORD /d 1 /f
Reboot for changes to apply.

To disable it:
reg add HKLM\SYSTEM\CurrentControlSet\Control\Power /v EnableInputSuppression /t REG_DWORD /d 0 /f
Reboot for changes to apply.

As for the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PolicyManager\current\device\knobs registry key. That one is for centralized management and/or (remote) system administration through Intune MDM policies:

EDIT: ControlSet001 and ControlSet002 are alternating backups of CurrentControlSet and you don't need to modify them. What are Control Sets? What is CurrentControlSet?

hdmi said:

To check whether input suppression is enabled:
reg query HKLM\SYSTEM\CurrentControlSet\Control\Power /v EnableInputSuppression
0x1 = enabled (default), 0x0 = disabled

To enable it:
reg add HKLM\SYSTEM\CurrentControlSet\Control\Power /v EnableInputSuppression /t REG_DWORD /d 1 /f
Reboot for changes to apply.

To disable it:
reg add HKLM\SYSTEM\CurrentControlSet\Control\Power /v EnableInputSuppression /t REG_DWORD /d 0 /f
Reboot for changes to apply.

Click to expand...

Thanks, I disabled it and will check now if that works with the lid.
It worked, on battery, no warnings after closing and opening the lid while in Sleep mode. I woke with the power button, but I thinks any button will wake too. I will let you know if this is the fix or if the warnings come back.
Still OK, I believe this is the fix.

Okay, I just checked on my new Lenovo laptop. This is my first system with Modern Standby and I've only had it a few weeks now, so I've been doing testing with Modern Standby.

As far as I can tell, Modern Standby is working flawlessly on my system, but I am also getting the even 700 and 701 messages. As best as I can tell, this is 100% normal.

Out of curiosity, what led you chasing these events? It would seem to me that these are 100% normal to see. Is it possible that we are chasing ghosts here?

My apologies for needing to wait until now to test this. I was testing a hidden powercfg setting to extend the amount of time that the system would stay in Modern Standby so I had to leave the system in Standby to test that.

hsehestedt said:

chasing ghosts

Click to expand...

hsehestedt said:

Okay, I just checked on my new Lenovo laptop. This is my first system with Modern Standby and I've only had it a few weeks now, so I've been doing testing with Modern Standby.

As far as I can tell, Modern Standby is working flawlessly on my system, but I am also getting the even 700 and 701 messages. As best as I can tell, this is 100% normal.

Out of curiosity, what led you chasing these events? It would seem to me that these are 100% normal to see. Is it possible that we are chasing ghosts here?

My apologies for needing to wait until now to test this. I was testing a hidden powercfg setting to extend the amount of time that the system would stay in Modern Standby so I had to leave the system in Standby to test that.

Click to expand...

Some ignore warnings or all Event logs, some don't, they are there for a good reason and 700/701 warnings are triggered by inputSuppression so you have to turn that off on my system if you don't want to get these warnings. Thank you both for helping me with this "ghost".

Frank, my point is that some "warnings" are 100% normal and expected in normal operation.

In fact, this is a common tactic of scammers. They will share your screen and one of the first things they like to do is open Event Viewer and show you warning messages in order to assert that your system has been compromised.

In the meantime, I restored my original factory fresh Lenovo installation, and those events are there even on the factory fresh installation.

Bottom line: Ignore it. This is normal!

If you are seeing abnormal behavior, that's a different story.

<Now restoring laptop to most recent configuration>. It's 7:30 in the morning and already I'm pushing around the poor laptop

hsehestedt, I got your point that this "warning" is pure Info, that the lid action on battery was suppressed. Power users expect getting hundreds of prompts daily in diagnostic logs, casual users, like me, prefer blank Event View and Reliability History screens as most of these warnings do indicate (often minor) issues. I appreciate you guys explained functionality of Modern Standby with InputSuppression, all very new to me.

Another thing I can ignore but obsessed as I am it bothers me: I have 5 identical Device firmware drivers in my Device Manager probably from Asus updating bloatware that I have not yet disabled. Can I at least delete 4 of them (see attached)?

Darn good question, Frank. I'm not sure why you have multiple occurrences, but I do have a theory. I wonder if this firmware is possibly for some device that has multiple "channels", ports, etc. so this firmware shows up for each occurrence.

So, let's take a look at the details of the firmware to see if we can figure out what this is.

On the properties screen that you showed, go to the Details tab. Work your way down the path to see if there is any unique info that will tell us what this is. In particular, take a look at options like "Device instance path" to see if there is a unique value for each instance.

There may be a way to dump all this information so that you can share it with us, but I'll have to research that when I get back to my main PC.

One final thought / tip:

When poking around at something like this, I like to create a disk image just before doing so. Then I am free to delete, alter, do whatever I want with the item to see what happens, knowing that no matter how big a problem I cause, I can always easily revert back using my backup.

Let me know what you see by looking at the properties.

EDIT: I should note that I would suspect this to be normal because there are no errors shown for these occurrences., but I do understand that it would be nice to know what it is.

EDIT #2: Here is a good example of what I am thinking: If you look at your Processor in Device Manager, you will see multiple entries there. This is because each core will cause another instance of the CPU to show up. In addition, if you have hyperthreading, this will cause another instance for each core that can do hyperthreading to show up. For example, if you have an 8 core CPU and each core can do hyperthreading, then 16 processors will be displayed.

FrankW said:

that this "warning" is pure Info

Click to expand...

It isn't. Had it been that, the event type would have been "Information", not "Warning".

FrankW said:

Another thing I can ignore but obsessed as I am it bothers me: I have 5 identical Device firmware drivers in my Device Manager probably from Asus updating bloatware that I have not yet disabled. Can I at least delete 4 of them (see attached)?

Click to expand...

Just because devices can have identical names in Device Manager, doesn't also mean they're duplicates of each other. Usually it just means that name is just a generic name. Simply updating the Chipset INF Utility (a lot of so-called "advanced" users mistakenly call the chipset driver, when the reality is that it isn't an actual driver) may help to improve this kind of nondescript-ness about some (but typically not all) of these names. Here's a car analogy. Deleting drivers when you don't know what they're there for is like opening the hood of your car and throwing a wrench. Lest you want to risk going on foot... don't do it!

Here's another car analogy for ya. Does the mere fact that a car engine has four identical cylinders imply that I can remove three of 'em and it will still be able to run like normal?

Agree, I was thinking of all the USB duplicate drivers in Device Manager, this may well be the way Asus boards function, never had this on Acer machines., zilch info in the property tabs (see attached) other than that the 5 Firmware versions differ: FO6C7,11207, 6C7, 41B and 1.

I once "cleaned up" my driver store (system 1) with RAPR, ended up having to reinstall all my drivers so lessons learned.

I'm not saying that Bing Chat is never wrong, but even it notes that warning in Event Viewer are often not anything to be concerned about.

I've even seen many cases where Microsoft changes messages that show up as warnings into informational messages in new releases of Windows.

Is this annoying? Heck yes! The point is simply to not get lost chasing things that turn out not to be a real problem. I don't think that I have EVER seen a system, no matter how well managed, that doesn't have warnings. On every one of my machines (all running flawlessly) I have litterary hundreds if not thousands of warnings. I even have many hundreds of flat out "Error" level messages. These affect absolutely nothing.

Basically, Lord Of The Rings' Dead Men of Dunharrow probably have a lot fewer ghosts than any version of Windows.

hdmi said:

Here's another car analogy for ya. Does the mere fact that a car engine has four identical cylinders imply that I can remove three of 'em and it will still be able to run like normal?

Click to expand...

I like your cat analogy best

hsehestedt said:

I'm not saying that Bing Chat is never wrong, but even it notes that warning in Event Viewer are often not anything to be concerned about.

I've even seen many cases where Microsoft changes messages that show up as warnings into informational messages in new releases of Windows.

Is this annoying? Heck yes! The point is simply to not get lost chasing things that turn out not to be a real problem. I don't think that I have EVER seen a system, no matter how well managed, that doesn't have warnings. On every one of my machines (all running flawlessly) I have litterary hundreds if not thousands of warnings. I even have many hundreds of flat out "Error" level messages. These affect absolutely nothing.

View attachment 67536

Click to expand...

And I have seen many purportedly "maintained" systems (Acer community) that crashed/restarted, fail to boot, BSOD, slowed down to a trickle and bricked while users/gamers were not even aware of Event Viewer logs (or Error Reports in Reliability History). Except for Security and Info, these screens are kept blank on my machines, but I have disabled some Event log channels in the registry. I also remember in W10 some Errors were depreciated to Warnings and Warnings to Info by MS but not lately. Scaring people is completely wrong but IMO minimizing Event logs ("thousands", really?) works counterproductive. Similarly, the very negative reports on W7 BU app on this forum continues to be offered by MS after 15 years and is even part now of the W11 22H2 platform, I continue using it to make full disk images and never had a botched restore job yet (but the File History part is a disaster).

It's funny. Now that I reflect back, my perspective has changed. I used to go after every little error with great zeal, intent on squashing every one of them out. Without going into detail, I'll let you read between the lines, let's just say that it was Microsoft themselves that quickly squashed that desire in a hurry!

For now, I'll just wish you a good night. Gonna try to power off and get some shuteye within the next half hour or so

@hsehestedt and @hdmi @glasskuter
Can I ask another question about my recent Asus login Audit failures?
I have Hello turned on with both PIN and Password sign-in as Local Account. Also have a MS online account. I am getting Audit Failures 4625 (see attached): Null SID, S-1-0-0, "A group with no members. This is often used when a SID value is not known". Does that mean that my account does not have a SID? It could be Edge causing it but that is logged in automatically. I don't know where to look in the registry, there is no S-1-0-0 account in security c:/ drive (attached). It only appears after I shut down, not after wake from sleep mode.
It is not the way I sign into my laptop as when I started getting the Audit failures, I had Hello turned off and used no password or pin (administrator). I hate to create a new user account on a brand-new laptop and find out I still get these Audit failures.

Update 25 August.
It was a "glitch" no more Audit Failures, according to MS this is "Information" not an Audit Failure. I disabled the Edge Core updater in Task Scheduler and that may have been the cause.