Cannot change Critical Battery level- stuck at 98%
I've searched google and several forums, but can't seem to find this particular problem posted anywhere. I've got my desktop plugged into an APC Backups 550 ES. I had a power dip the other day and my computer immediately went into hibernate mode. Normally, I get 5-10 minutes before that happens. After waking the machine up, I checked the advanced power settings. Low Battery level was set to 99% with an action of 'Do Nothing' Critical Battery level was set to 98% with an action of 'Hibernate' (these are the 'On Battery' settings) . These are normally a low number like 5-10%. I can change the value of the Low Battery setting, but not the critical battery setting. I put in a new value, but it is immediately changed back to 98% when I hit apply. Has anyone else seen or heard of this issue? I've tried creating a custom power profile, but get the same problem. No new hardware has been added and this feature was fine on Vista x64. Here's some specs: Windows 7 x64 RC build 7100 (clean install) Intel E8200 4 GB ram Thanks
May 15th, 2009 11:13am

That's very strange. Duplicating and changing different power profiles doesn't work? Have you done more research into your problem? Do you still need help? -Nick
Free Windows Admin Tool Kit Click here and download it now
June 19th, 2009 11:21am

I'm also having this problem with Windows 7 build 7100. I didn't have this problem with Vista at all. It's kind of ironic how they have the default set to 98%. Most battery's conditions are hardly 98% ever. So any under voltage or power off causes it to hibernate. I'm about to unplug the USB from my UPS so it doesn't shut down my blasted computer every time there's under voltage.
June 22nd, 2009 8:34am

It sounds as though Windows 7 is misreading the functionality of your UPS devices. Because these don't normally install driver software within Windows, I doubt that there's much that APC could do if alerted to the issue, and I'd instead recommend posting this to our comments thread where it has a better chance of being considered by the developers prior to Windows 7's release.-Alex
Free Windows Admin Tool Kit Click here and download it now
June 22nd, 2009 11:11am

I'm also having this problem with Windows 7 build 7100.I didn't have this problem with Vista at all. It's kind of ironic how they have the default set to 98%. Most battery's conditions are hardly 98% ever. So any under voltage or power off causes it to hibernate. I'm about to unplug the USB from my UPS so it doesn't shut down my blasted computer every time there's under voltage. I, too, am having the EXACT SAME PROBLEM and I've looked and looked for a solution. Last week I found a reference to running POWERCFG.EXE from an Elevated Command Prompt (run as administrator), and that DID fix the issue, however after I re-installed Win 7 x64 releas 7100, no bueno. And to top things off, I neglected to get the powerfg.exe parameters copied down, so I can't duplicate the fix.
October 3rd, 2009 11:56am

I had the same problem. Again.I tried changing the power plan, creating a new one, reinstalling the UPS, etc, etc.I found out is something related with permissions in the registry. For some reason, they get screwed up.This is what I did to fix it. I don't take any responsability, of course. ;)1. Go to HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Power\User\PowerSchemes2. Edit the permissions for HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Power\User\PowerSchemes. Go to Advanced -> Owner, and check "Replace owner on subcontainers and objects". Click ok.3. Go to Advanced again, check "Replace all child object permissions with inheritable permissions from this object". Click ok.4. Now you should be able to change the values without problem from Power Options.Cheers.
Free Windows Admin Tool Kit Click here and download it now
January 1st, 2010 2:51pm

I highly doubt that. I had the same problem, and the workaround involves finding out the unique string of guids to be typed into the command line, in a format like this: powercfg.exe -setdcvalueindex 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c e73a048d-bf27-4f12-9731-8b2076e8891f 9a66d8d7-4ff7-4ef9-b5a2-5a326ca2a469 20 The actual way of obtaining the actual string you need to type for your system involves learning to read the output of powercfg.exe /QUERY, then you pick out the guids you need to set, and compose a string like the one above. This must all be run from a command prompt with elevated priveleges (click on the start button, type command, right click on the command prompt startup-shortcut, and Run As Administrator). wp
January 12th, 2010 9:47am

That registry permission thing seems reasonable, but it didn't work for me. I needed to use powercfg.exewp
Free Windows Admin Tool Kit Click here and download it now
January 12th, 2010 9:48am

I had to use powercfg.exe method as well. This 98% issue is major flaw for those of us using UPS. If I wanted computer to turn off on every power sag, I would not have UPS to begin with!
February 18th, 2010 8:34am

I had the same problem as well with my new APC UPS, but Windows 7 was ignoring the setting I set with powercfg. Even though the Critical Battery Level was forced to 33% and Critical Battery Action was forced to "Do Nothing" with powercfg, the system was still shutting down as soon as a power sag occured and the UPS to switch to battery mode. Often the shutdown was started while the battery was still reporting 100%, 2% more then the 98% it was stuck at. For me it appears as if the issue is a result of using PowerChute while still using the "HID UPS Battery" driver instead of the "APC Battery BackUP" driver that is provided with PowerChute. The "APC Battery BackUP" driver disables WMI (Win32_battery) access for some applications that I use. When I rolled back to the "HID UPS Battery" driver, PowerChute complained several times that it was unable to communicate with the battery, and I found I was unable to manually change the Critical Battery Level of 98%. I then uninstalled PowerChute, but the damage was already done. I tried everything I could think of to get around this, and even opened a support ticket with APC. I gave them all the info above, but got no resolution. Thinking it a problem with Windows 7, I attempted to reinstall Windows. The Critical Battery Level was defaulted to 98% in the new install as well, but I was able to change it. Though Windows 7 Power Management was still ignoring the settings, so I then figured it was something with the battery. However, everything worked properly when PowerChute was re-installed and using the "APC Battery BackUP" driver. When I uninstalled the PowerChute software a second time, and rolled back to the "HID UPS Battery" driver, I was once again unable to change the Critical Battery Level which had reverted back to 98% and Windows 7 was again shutting down the moment a power sag occured. So instead of the battery, I figured it may be a hidden setting in the UPS hardware/firmware that PowerChute set and Windows Power Management is being stubborn about. I was able to get it back in working order with the following steps. (follow them at your own risk) 1. I uninstalled PowerChute and then the "APC Battery BackUP" driver that it leaves behind (ie. Uninstalled the UPS device from Device Manager with the delete driver option checked) 2. Scanned for Hardware changes and ensured the UPS was using the Windows default "HID UPS Battery" driver. 3. Turned off my PC and disconnected it from the UPS. 4. Turned off the UPS and disconnected it from the mains power. 5. Disconnected the battery from the UPS. 6. Powered on the UPS while it is w/o battery and mains power. The unit powered on, switched to battery, and powered off lacking any available power, thus draining any power left stored in it's internal circuitry, and hopefully clearing any internal memory. (I left it like this for a few minutes for good measure) 7. Reconnected the battery and all power connections. 8. Restarted system, reset all battery levels to preferred values, tested, and found everything to be in working order. 9. Shredded PowerChute CD, and deleted any downloads. I'm not sure if I'm entirely correct about my theory, but I'm not gonna mess with it any further. Microsoft and APC need to get together on this one.
Free Windows Admin Tool Kit Click here and download it now
March 30th, 2010 10:00pm

please give a demo to that in a cmd picture show all the written words because i was unable execute the following command powercfg -setdcvalueindex 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c e73a048d-bf27-4f12-9731-8b2076e8891f 9a66d8d7-4ff7-4ef9-b5a2-5a326ca2a469 20please help
April 14th, 2012 11:32am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics