Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[tuneup]

I am having the same problem on 2 Windows 7 Pro computers, an Intel i7 Toshiba and an Intel i5 Dell (the first is 1 year old and the 2nd is brand new). The computers will shut down, despite having the correct power settings, which are as follows:

Power Plan: High Performance

Never Sleep on AC power and battery

Do Nothing when lid closes

In addition, Windows keeps changing the power plan from High Performance to Balanced, where I have the same Never Sleep and lid closing settings. This is despite clicking Apply where necessary and restarting the computers. I had my IT guy check the settings and he basically just changed it back to High Performance, turned some of the other settings off and back on and restarted the computer a few times after making various settings changes. After the first 2 restarts, it went back to Balanced, but after the 3rd restart it stayed on High Performance. By the next day, it went back to Balanced by itself and also shut down by itself, both with the lid open and the lid closed. I need some help here. Is there some hidden setting(s) that I am missing? Is Microsoft taking over computers subversively? (I am not a fan of conspiracy theories.)

[fooze]

Any manufacturer's software on there that could be messing with the power settings?

[tuneup]

Thanks fooze. Iolo System Mechanic has an alternative choice for the power plan called Ultra Performance, which runs all CPU cores at maximum clock speed. But I haven't selected it so I don't think the program is doing anything, but I will try to research that possibility.

[tuneup]

On second thought fooze, I doubt that it is System Mechanic because it isn't in the other laptop, which I set up as a music server dedicated unit at a client's home with only enough software to run JRiver MC.

[fooze]

Bet you there's a program, driver or service installed somewhere that's making these changes. So annoying.

Give the workaround in this thread a go: http://www.sevenforums.com/general-discussion/21260-power-options-keep-reverting.html

[tuneup]

fooze, you may well be right and there is a lot of interesting stuff in the posts you directed me to, but I'm not sure I've got the smarts to figure it out without risking making things worse. I am an a/v specialist, not at all a computer expert. I may turn to my IT guy once again.

Is this the workaround you are recommending?
 
"I gave up on it and put commandline options like

C:\Windows\System32\powercfg.exe -x -disk-timeout-ac 0
C:\Windows\System32\powercfg.exe -x -disk-timeout-dc 0
C:\Windows\System32\powercfg.exe -x -hibernate-timeout-ac 0
C:\Windows\System32\powercfg.exe -x -hibernate-timeout-dc 0
C:\Windows\System32\powercfg.exe -x -monitor-timeout-ac 0
C:\Windows\System32\powercfg.exe -x -monitor-timeout-dc 0
C:\Windows\System32\powercfg.exe -x -standby-timeout-ac 0
C:\Windows\System32\powercfg.exe -x -standby-timeout-dc 0"

I looked up "System32" because I thought it meant his computer was 32-bit. See what I mean about being computer ignorant. Anyway, I found a lot of conflicting info on the System32 folder, some warning you not to remove it and others telling you to remove it because "system32.exe is not essential for Windows 10/8/7/XP and will often cause problems." I realize it is just part of a path in this workaround so I won't be messing it up.

Is Sleep the same as standby?

If I want the computer to run MC20 as soon as you click on Play, do I want to use all the "never" commands above, except for the monitor, which can certainly go to sleep when the lid closes (since all control is coming from JRemote on an iPad)?

[JimH]

Do not remove Windows\System32.  It is an essential part of the OS.

[tuneup]

Thanks Jim. I wasn't planning to, but was curious to see an opinion I could trust.

[fooze]

Holy moly I hope you didn't delete anything from inside system32!

C:\Windows\System32\powercfg.exe -x -disk-timeout-ac 0       ; how long to wait before turning off disks while plugged in
C:\Windows\System32\powercfg.exe -x -disk-timeout-dc 0       ; how long to wait before turning off disks while on battery
C:\Windows\System32\powercfg.exe -x -hibernate-timeout-ac 0 ; how long to wait before sleeping (plugged in)
C:\Windows\System32\powercfg.exe -x -hibernate-timeout-dc 0 ; how long to wait before sleeping (on battery)
C:\Windows\System32\powercfg.exe -x -monitor-timeout-ac 0   ; wait to turn off screen
C:\Windows\System32\powercfg.exe -x -monitor-timeout-dc 0   
C:\Windows\System32\powercfg.exe -x -standby-timeout-ac 0   ; how long to wait before shutdown
C:\Windows\System32\powercfg.exe -x -standby-timeout-dc 0

A timeout of zero means "never".

Documentation for the powercfg.exe tool: https://technet.microsoft.com/en-us/library/cc748940%28v=ws.10%29.aspx?f=255&MSPPError=-2147217396

Documentation for Windows Task Scheduler: http://windows.microsoft.com/en-au/windows/schedule-task#1TC=windows-7

I guess the best thing to do is familiarise yourself with these things before making any changes. This is a hack though.

These instructions might be helpful: https://support.microsoft.com/en-us/kb/929135 especially the part about "How to determine what is causing the problem by performing a clean boot"

If it was me I'd look for the offending software for a couple of hours, and if I had no luck I'd flatten and reinstall windows. I couldn't stand having software, that wasn't obvious, changing power settings on its own. Who knows what else it is doing.

Sorry for your frustrations.

[tuneup]

Thanks fooze. I understood that zero was never and as I said to Jim, I had no intention of deleting any part of System32. I really think this depth of computer work is beyond my abilities, but I will look at the links you provided. I also think that it would be better to switch to the Linux Id, which will cost less than getting my IT guy involved any further, because Windows is likely to come up with some other nightmare after this one is resolved. I will start a separate post re the Id.

[tuneup]

Hi Fooze, after changing the monitor timeout to 2 minutes I sent the commandline instructions to my IT guy and had him make a .bat file. This morning I installed the .bat file in the Startup folder and also set it to run once every hour indefinitely in the Scheduler. I will let you know in a week or two if my client's laptop has stopped shutting down.

I was shocked to find that Windows had changed my update setting from "...let me decide when to download and install..." to "Install updates automatically." So I changed it to "Never check for updates." where they "promise" to do nothing automatically and to not even announce updates, although I trust them about as far as I could throw a Mitsubishi 40" CRT TV.

I also uninstalled anti-virus and anti-malware programs.

[fooze]

Cool, sounds like it should alleviate the symptoms.

Turning off updates and running no antivirus on Windows 7 is a little concerning. I wouldn't do this personally on a computer that's connected to the internet.

[tuneup]

Understood, Fooze. I didn't spell out my whole plan. Once I have confirmed that the system is now stable, I will visit the site on a regular basis and manually look at Windows Updates to download & install only those that are not dealing with Win 10 installs or any other sales push by MS. I will also reinstall anti-virus program to see if it messes with anything. If all stays stable for a few more weeks, I will reinstall anti-malware program and see if it messes with anything. One variable at a time is always best.

For my own server system, I have ordered an Id Classic, as I have no spare computer to dedicate to the server system.