|Topic Review (Newest First)|
|04-20-2019 04:21 AM|
yep, got it. that was in fact the problem. Learn as you go, more tools at my disposal in the future god forbid. Sometimes you always start chipping away at a problem from the wrong direction and do the first thing you should have done last, and it costs you SO much time
what a relief though. Shame how much little things like that can stress you out.
Now just to find out why my darn non system drives are being spun up when not being used. That may just be one of those "is what it is" situations though. Not fixable without a hacky workaround.
Proc-mon pointed to nada and it seems like its something under the hood/windows 10'ey type thing. Maintenence on said drives is off. None of them are set to be index'd. Theyre all set to power down. I dont access any directly yet they just spin up.
I have a few drives that have 7000 power on/off cycles and theyre not even 2 years old.
buuuut. I digress
spend more time getting a pc "just right" nowadays then actually enjoying it. Perhaps on some subliminal level, this IS enjoying it? yuck!
|04-19-2019 04:24 PM|
If you fixed it the great job!
You didn’t even need our help at all
|04-19-2019 03:56 PM|
i "think" i got it.
cant check for certain yet because windows search indexer decided to do its thing and is now preventing sleep lol.
My USB stick holds miscellaneous stuff. One of those items being icons for various shortcuts I use. My other running pc insta connected to that USB stick in order to use that same icon for a shortcut over the network as opposed to locally.
I "assume" thats what did it. My gosh some times these problems put you through the ringer. A normal human would just resort to putting the pc to sleep when their done with it.
Not this savage ocd animal.
|04-19-2019 02:29 PM|
found this on another forum from way back when (with no solution given) that is a different OS but describes the same exact problem with what sounds like a plausible explanation as when I ended the shared drives, it said id be booting 1 user, which would likely have been the pc next to me.
Heres the post
"Looking more into Server 2003, it looks like there is a Session being created when my Windows 7 computer connects via mapped network that doesn't get closed when not being used"
So how can one force the session(s) to terminate when not being used?
|04-19-2019 02:24 PM|
ok NOW im a little closer.
I disabled ALL my network shares, and it went to sleep. Unfortunately - disabling network shares is a fail since this pc is the main pc.
how does one get it to sleep irrespective of network shares?
|04-19-2019 01:54 PM|
worth mentioning - if i disable the nic, and use wifi instead - result is the same. If i use wifi but use my phone as a hotspot, it will sleep.
this point to anything in particular?
|04-19-2019 01:03 PM|
How to determine what network activity is preventing sleep?
So after DAAAYS of troubleshooting, i did what i should have done first.
Disabled my ethernet adapter. PC will now sleep. (it would sleep fine manually, but wouldnt go to sleep on its own).
I thought it was my nvidia shieldtv's doing something over the network that kept it awake, but i turned those both off and the pc still will only sleep when i disable the network adapter.
Turning off "allow this device to wake the computer" would be a workaround, except I need Wake on Lan to function so thats no bueno.
Plus this was never an issue until the last month or so. Something has changed.
Anybody able to point me in the right direction?