05-04-2012 01:30 AM - edited 05-04-2012 03:33 AM
I've installed the current version on my ThinkPad X220 but unfortunately there is a bug by creating new power plans via Power Manager.
I can start to create a new plan but after the finish the system hasn't create a new power plan.
Does anyone also detected this phenomen?
Thanks for your feedback,
05-05-2012 05:32 AM
Got the same issue in my X220T. Can't import/export profiles, couldn't modify them. After confirming changes it seems like Lenovo power manager accepted the changes, and after reopening it all changes are lost... Anybody any idea.
Things I already tried:
- Checking for conflicts with: Avast, Avira, Spybot
- Checking for problems with registry
- Bios Update
- Update .net-Framework
05-05-2012 05:55 AM
Power Manager now is working again. Went back to 3.66. It seems to be the only option right now.
Use the download-link at the bottom of the page.
05-05-2012 08:49 AM - edited 05-05-2012 09:32 AM
I also downgrade to version 3.67 and now it works fine so far.
@All: Does anyone know a possibility do configure the battery charge level without the ThinkVantage Power Manager, because only that why I need it.
Thanks for your feedback
05-05-2012 10:58 AM
On my R500 I upgraded Power Manager and subsequently found when I launched Rescue and Recovery to make a backup I got an all black window and maxed processor. On a hunch I down-levelled Power Manager to 3.66 and voila R&R launches properly again.
05-05-2012 01:27 PM
I think Power Manager 6.07 has some major issues. It was a fail in my 2 machines (T61 & E420) and now I read about others with different ThinkPads having isues as well. My solution was to go back to 3.66 which works as advertised.
05-20-2012 07:27 AM
With the new Power Manager, waking up from standby causes disk thrashing... As if the RAM cache is dumped.
Anyone else experienced the same issue...?
I haven't seen that, but tell me more. Does this always happen? Or does it matter how the system entered standby? For example does this only happen with the system enters standby due to timer, or does it also happen when putting the system to standby manually (by closing the lid or Fn-F4)?