Windows 10: Shortcut to Device Manager/Network Adapters/. . .

I'd like to make a shortcut to Device Manager/Network Adapters/Nvidia nforce networking controller.
Or, better still, a batch command to disallow the device from waking the computer.
The problem is that it frequently reverts to allowing wake, thus making it impossible to keep the computer asleep. Apparently this results from Nvidia driver updates.

:)

 

Network adapters show up in device manager but not network connections

OK,

So no idea why I didn't think of this before. SYSTEM RESTORE.

Did a system restore to a few weeks ago and now everything is working fine. It would be nice to understand what the underlying bug in windows 10 is that causes this, but at least I have a working internet connection again. I will report the bug through the
windows 10 feedback system.

Thanks for all the suggestions.

 

Network adapters show up in device manager but not network connections

Can you establish a wired internet connection if you restart the computer in "Safe Mode with Networking" ?

 

You can use this to setup the shortcuts:
CLSID Key (GUID) Shortcuts List for Windows 10 - Windows 10 Forums

 

It cannot be done. Anything that triggers an IRQ to wake up the system from S3 state, is going to happen when you want to do something. There is no way around it. As for it going back to sleep, it should be going back after the system gets no more IRQ requests.

Your only thing would be to place it back into S3 sleep state by using Task Manager.

 

topgundcp, thanks for the reference.

bro67, I'll need to look up "s3" sleep. Is that the usual sleep state? The problem is, when the Nvidia network device has permission to wake the computer it will keep doing so about a minute after the system returns to sleep, presumably to reset the system time as a time reset usually follows the wakeup. So I have to manually reset the driver to remove permission to wake the computer. I don't know why there are so many time reset calls.

 

S3 is the normal sleep state that computers go into. It is a low wattage state, that keeps the CPU in just enough of a listening state, that it only wakes up all other devices when something triggers the IRQ to bring it back up.

Recheck your power settings, you can also use PowerCfg to run reports on last sleep state, etc.. If you use something like RealVNC or RDP to connect, I would maybe set a Task to look for the logging out to place it back into Sleep, or place a shortcut on the desktop or taskbar to put it to sleep, before logging out.

Once it goes into sleep, the remote software will tell you that it lost its connection.

 

'Preciate the advice. Resetting the driver fixes the problem, at least until the next update, so I'll stay with that for now.

 

Set Windows to not update Device Drivers. That should fix the problem. It is screwing with the Task for some reason.