T400 power manager crashing

We have an unattended install of xp on T400's which for the most part is working well except that when the powermanager is launched it crashes. Power manager is installed silently (after dotnet 3).  I have tried version 1 ,2, and 3 of dotnet fx, and changing the power manager install package with a new download all with the same results. I have even reinstalled the C++ runtimes. Still no joy. Here is what I get in the event manager when the application unexpectedly quits. Source: Runtime 2.0 error, EventID 1000, Description: Faulting application pwmuiaux.exe, version 1.0.0.0, stamp 49c6f31e, faulting module kernel32.dll..... any ideas?
T400 2767-Rq9
Windows xp pro (2GB of RAM)
Solved!
Go to Solution.

Hello parise,
please tell us your operating system and used powermanager version.
That´ll help us, to help you.
Follow @LenovoForums on Twitter! Try the forum search, before first posting: Forum Search Option
Please insert your type, model (not S/N) number and used OS in your posts.
I´m a volunteer here using New X1 Carbon, ThinkPad Yoga, Yoga 11s, Yoga 13, T430s,T510, X220t, IdeaCentre B540.
TIP: If your computer runs satisfactorily now, it may not be necessary to update the system.
 English Community       Deutsche Community       Comunidad en Español

Similar Messages

  • Power manager crashes after returning from standby mode.

    I have a T400 2767 WU6 running Windows 7 Pro-64bit.. After returning from standby mode, power manager crashes (version 3). All the software installed is supposed to be compatible with win7 pro 64bit.
    Any help would be greatly appreciated.

    Does this issue appear from the beginning?
    Possibly the OS was installed several time ago and now the registry entries are corrupt.
    Therefore the system busy egg timer could appear.
    Im not 100% sure it will help but possibly you should reinstall the whole OS
    On the fresh installed OS all should works much faster

  • T450 - Power Manager crashes after Sysprep

    After Sysprepping a T450 with a clean Windows 7 64 bit Professional custom build, Lenovo Power Manager crashes with "An error occurred while loading resource DLL".   Followed by "There was a problem starting C:\Program Files (x86)\ThinkPad\Utilities\PWMTR64V.DLL The Power Manager toolbar on the taskbar also will not load. Reinstalling Power Manager (latest version 6.67.5) resolves issue.  Reinstalling it immediately prior to Sysprep does NOT resolve the issue. Anyone else seen this?  

    Probably because the tools aren't added to the taskbar in "Default" user. Did you added the tools to the taskbar in Audit mode?
    Though sysprep will not keep some settings. You may need to use `unattended.xml` to configure scripts to add those tools to the taskbar.
    Just another question: does the PM tool appears in its factory state?

  • Power Manager crash with with Explorer searches

    Hi,
    I had the same problem with ver. 6.07 repeating over and over again during last few days. It started when I switched the Explorer file search parameter from "search file names only" to "search file names and content" (Tools > Folder Options > Search > ...).
    This morning I switched back to "search file names only" and  no crashes so far...

    The steps to reproduce the error are those I outlined above; the issue reproduces on my equipment 100% of the time.  With the system booted and running normally:
    1)  Click the taskbar's 'Start' button.
    2)  In the 'Search programs and files' textbox, enter any two characters (e.g. 'ab')
    3)  A Power Manager dialog is displayed stating that "Power Manager has stopped working...To search for an update that will resolve this issue, click Next..."      
    4)  Click 'Next'.  A Power Manager dialog is displayed stating "No update exists to resolve this problem."       
    5)  Click 'OK'.  A Power Manager dialog is displayed stating, "Lenovo is constantly working to improve driver and software quality.  Unfortunately, we did not identify a solution to this issue at this time.  It is recommended to send an Error Report to Microsoft to help track the resolution to this problem.  Click Next to report this problem    
    6)  Click 'Next'.  A Windows Explorer dialog is displayed offering three options: a) 'Check online for a solution and restart the program', b) 'Restart the program', and c) 'Debug the program'.  There is also a 'View problem details' button.    
    7)  Clicking the 'View problem details' button yields the following
    Problem signature:
      Problem Event Name:                        APPCRASH
      Application Name:                             explorer.exe
      Application Version:                           6.1.7601.17567
      Application Timestamp:                     4d672ee4
      Fault Module Name:                          ntdll.dll
      Fault Module Version:                        6.1.7601.17725
      Fault Module Timestamp:                  4ec4aa8e
      Exception Code:                                  c0000005
      Exception Offset:                                000000000002b1ed
      OS Version:                                          6.1.7601.2.1.0.256.48
      Locale ID:                                             1033
      Additional Information 1:                  85ea
      Additional Information 2:                  85ea31b15d038786abb000c0d9d9269c
      Additional Information 3:                  b4bd
      Additional Information 4:                  b4bd3537dddea6bb1063e81566f4d641
    Clicking the 'Check online for a solution and restart the program' yields no solution; it simply restarts Windows Exporer.
    If you want someone to 'provide a crash dump', you'd be wise not to assume they have the requisite knowledge to perform such a task.

  • Power Manager 3.0 on X220

    One of the most usefull features, having Power Manager to display the remaining battery charge on the task bar, disappeared when I installed Power Manager 3.0.0114 (or something).
    Before I upgraded it worked great! Well, Power Manager crashed horribly, but the battery charge display as a toolbar on the taskbar did!
    Is there anything I can do to make the Toolbar display work again?

    Same problem here, the only workaround is ALT+F2 and r. Not always works. My graphic card is:
    koven@koven:~$ lspci | grep -i nvidia
    01:00.0 VGA compatible controller: nVidia Corporation G98M [Quadro NVS 160M] (rev a1)
    Mu driver nvidia version is
    Name : nvidia
    Version : 270.41.06-1
    URL : http://www.nvidia.com/
    Licenses : custom
    Groups : None
    Provides : None
    Depends On : kernel26>=2.6.38 kernel26<2.6.39 nvidia-utils=270.41.06
    Optional Deps : None
    Required By : None
    Conflicts With : nvidia-96xx nvidia-173xx
    Replaces : None
    Installed Size : 3944.00 K
    Packager : Ionut Biru <[email protected]>
    Architecture : x86_64
    Build Date : Wed 20 Apr 2011 01:11:09 PM COT
    Install Date : Sun 01 May 2011 08:01:37 PM COT
    Install Reason : Explicitly installed
    Install Script : Yes
    Description : NVIDIA drivers for kernel26.
    I see nouveau driver will kill my battery so I think I'll not suspend for a while. Let's wait until this issue  be resolved.
    BR
    Last edited by Koven (2011-05-12 13:37:10)

  • Power Manager claims "Battery not installed"

    System info:  T530, Windows 7 SP1, Power Manger 6.36, Power Managment driver 1.66
    Following a suggestion in another thread (to solve a Power Manager/Windows Explorer crash), I upgraded to Power Manager 6.36/driver 1.66.  Now Power Manager claims (via taskbar icon and within the Power Manager app itself) "Battery not installed"
    Solution, please.

    I'll try the download but I have a couple of concerns.  First, I upgraded to 6.32 in order to try and resolve another problem - Power Manager crashed when I tried execute a Windows Explorer "search"; it subsequently caused Windows Explorer to crash.  I'm not eager to just trade one problem for another.  Second, I need you to pass a message back up the management chain.
    As a customer, it frustrates me immensely to have to try test-and-debug procedures which ought to be done by Lenovo QA personnel.  I would feel a bit more positive if I could be certain that Lenovo QA had configured a machine like mine and tried to reproduce the problem themselves.  It's bad enough that I'm spending hours - of "vacation", time, no less - to try and resolve Lenovo product defects, but worse, I'm not getting paid for it.  (And yes, I do happen to know what qualified senior QA engineers get paid.)

  • Power manager with my T400

    latest T400, vista 64bit
    every time I start the computer, windows tells me, the power manager stop working.
    I already update the power manager to the latest version.

    thanks for being the very first one to reply! that's a very good question you ask, but unfortunately, the answer is no.
    to clarify, a power gauge does appear when the computer is on battery, but it is not the thinkvantage power gauge; it is just the one that comes with windows xp. when i pull the power, i see only a blue battery bar in my system tray. the battery gauge i'm talking about is a green battery gauge that sits not in the system tray, but in the task bar (to the left of the system tray).
    no windows xp update spoiled the functionality; i know this because i did not update windows xp at all between the time the gauge last showed up and the time it disappeared. what i did do was install a program called "shadowuser". i found it was causing problems, so i uninstalled it, but it seems the damage had been done. after uninstalling it, i uninstalled and reinstalled  thinkpad power management driver and thinkpad power manager, but the power gauge never came back. the other possible cause of the problem is that shortly after getting rid of shadowuser, i had to force reboot my computer by holding the power button. this is something i rarely have to do, but i had to do it in this case. i did a bit of searching and found that the power gauge disappears for some users if explorer.exe crashes, so this may be the problem. but if uninstalling and reinstalling won't fix the problem, what will? all my other programs (even those that shadowuser messed up) are working fine after shadowuser was uninstalled, or at least after the programs themselves were uninstalled and reinstalled. right now, i'm deeply regretting not imaging my hard drive while everything was working flawlessly. but must i pay the heavy price of reinstalling windows and all the other programs on my laptop because i mistakenly installed the trial of one program?

  • Power Manager 2.37 crash on Login (with callstack)

    I recently installed Power Manager 2.37 on my Thinkoad T400 (running Vista x64) and am now seeing the following crash whenever someone logs into Windows. Anyone else seeing this?
    System.Windows.Markup.XamlParseException was unhandled
      Message=" Unable to cast object of type 'System.Windows.Controls.StackPanel' to type 'System.Windows.Controls.Image'.  Error at object 'System.Windows.Controls.StackPanel' in markup file 'PWMUIAux;component/sliderpanel.xaml'."
      Source="PresentationFramework"
      LineNumber=0
      LinePosition=0
      NameContext="Header"
      UidContext="MenuItem_3"
      StackTrace:
           at System.Windows.Markup.XamlParseException.ThrowException(String message, Exception innerException, Int32 lineNumber, Int32 linePosition, Uri baseUri, XamlObjectIds currentXamlObjectIds, XamlObjectIds contextXamlObjectIds, Type objectType)
           at System.Windows.Markup.XamlParseException.ThrowException(ParserContext parserContext, Int32 lineNumber, Int32 linePosition, String message, Exception innerException)
           at System.Windows.Markup.BamlRecordReader.ThrowExceptionWithLine(String message, Exception innerException)
           at System.Windows.Markup.BamlRecordReader.CreateInstanceFromType(Type type, Int16 typeId, Boolean throwOnFail)
           at System.Windows.Markup.BamlRecordReader.GetElementAndFlags(BamlElementStartRecord bamlElementStartRecord, Object& element, ReaderFlags& flags, Type& delayCreatedType, Int16& delayCreatedTypeId)
           at System.Windows.Markup.BamlRecordReader.BaseReadElementStartRecord(BamlElementStartRecord bamlElementRecord)
           at System.Windows.Markup.BamlRecordReader.ReadElementStartRecord(BamlElementStartRecord bamlElementRecord)
           at System.Windows.Markup.BamlRecordReader.ReadRecord(BamlRecord bamlRecord)
           at System.Windows.Markup.BamlRecordReader.Read(Boolean singleRecord)
           at System.Windows.Markup.TreeBuilderBamlTranslator.ParseFragment()
           at System.Windows.Markup.TreeBuilder.Parse()
           at System.Windows.Markup.XamlReader.LoadBaml(Stream stream, ParserContext parserContext, Object parent, Boolean closeStream)
           at System.Windows.Application.LoadComponent(Object component, Uri resourceLocator)
           at PWMUIAux.TaskTrayMenu.InitializeComponent()
           at PWMUIAux.TaskTrayMenu..ctor()
           at PWMUIAux.MainWindow..ctor()
           at PWMUIAux.App.GetMainWindowHandle()
           at PWMUIAux.App.App_Startup(Object sender, StartupEventArgs e)
           at System.Windows.Application.OnStartup(StartupEventArgs e)
           at System.Windows.Application.<.ctor>b__0(Object unused)
           at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Boolean isSingleParameter)
           at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Boolean isSingleParameter, Delegate catchHandler)
           at System.Windows.Threading.Dispatcher.WrappedInvoke(Delegate callback, Object args, Boolean isSingleParameter, Delegate catchHandler)
           at System.Windows.Threading.DispatcherOperation.InvokeImpl()
           at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(Object state)
           at System.Threading.ExecutionContext.runTryCode(Object userData)
           at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
           at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
           at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
           at System.Windows.Threading.DispatcherOperation.Invoke()
           at System.Windows.Threading.Dispatcher.ProcessQueue()
           at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
           at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
           at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
           at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Boolean isSingleParameter)
           at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Boolean isSingleParameter, Delegate catchHandler)
           at System.Windows.Threading.Dispatcher.WrappedInvoke(Delegate callback, Object args, Boolean isSingleParameter, Delegate catchHandler)
           at System.Windows.Threading.Dispatcher.InvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Boolean isSingleParameter)
           at System.Windows.Threading.Dispatcher.Invoke(DispatcherPriority priority, Delegate method, Object arg)
           at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)
           at MS.Win32.UnsafeNativeMethods.DispatchMessage(MSG& msg)
           at System.Windows.Threading.Dispatcher.PushFrameImpl(DispatcherFrame frame)
           at System.Windows.Threading.Dispatcher.PushFrame(DispatcherFrame frame)
           at System.Windows.Threading.Dispatcher.Run()
           at System.Windows.Application.RunDispatcher(Object ignore)
           at System.Windows.Application.RunInternal(Window window)
           at System.Windows.Application.Run(Window window)
           at System.Windows.Application.Run()
           at PWMUIAux.App.Main()
      InnerException: System.InvalidCastException
           Message="Unable to cast object of type 'System.Windows.Controls.StackPanel' to type 'System.Windows.Controls.Image'."
           Source="PWMUIAux"
           StackTrace:
                at PWMUIAux.SliderPanel.System.Windows.Markup.IComponentConnector.Connect(Int32 connectionId, Object target)
                at System.Windows.Markup.BamlRecordReader.ReadConnectionId(BamlConnectionIdRecord bamlConnectionIdRecord)
                at System.Windows.Markup.BamlRecordReader.ReadRecord(BamlRecord bamlRecord)
           InnerException:
    Solved!
    Go to Solution.

    There are newer Power Manager versions available, the latest I think is 2.50. You should try installing a new one, to see if that solves the problem.

  • ThinkVantage Access Connections, Power Manager, and Toolbox all crash on startup

    I have a SL 500 with factory Vista , updated to SP2 and the current versions of the thinkvantage components.
    Access Connections has always been very buggy of this machine (I guess the battery monitor has been as well), When I attempted to update them this is where I ended up.
    Also just installed new .net framework 4 as well.
    thanks for any help 
    ian
    Description:
      Stopped working
    Problem signature:
      Problem Event Name: CLR20r3
      Problem Signature 01: pcdrcui.exe
      Problem Signature 02: 6.0.5514.59
      Problem Signature 03: 4c0eb0cb
      Problem Signature 04: wpfview
      Problem Signature 05: 6.0.5514.59
      Problem Signature 06: 4c0eb0cb
      Problem Signature 07: f8
      Problem Signature 08: 9c
      Problem Signature 09: System.IO.FileNotFoundException
      OS Version: 6.0.6002.2.2.0.256.6
      Locale ID: 1033
    Description:  Stopped working
    Problem signature:  Problem Event Name: CLR20r3  Problem Signature 01: pcdrcui.exe  Problem Signature 02: 6.0.5514.59  Problem Signature 03: 4c0eb0cb  Problem Signature 04: wpfview  Problem Signature 05: 6.0.5514.59  Problem Signature 06: 4c0eb0cb  Problem Signature 07: f8  Problem Signature 08: 9c  Problem Signature 09: System.IO.FileNotFoundException  OS Version: 6.0.6002.2.2.0.256.6  Locale ID: 1033
    Description:
      Stopped working
    Problem signature:
      Problem Event Name: APPCRASH
      Application Name: PWMUI.EXE
      Application Version: 1.0.0.0
      Application Timestamp: 4bea35c2
      Fault Module Name: KERNEL32.dll
      Fault Module Version: 6.0.6002.18005
      Fault Module Timestamp: 49e037dd
      Exception Code: e0434f4d
      Exception Offset: 0003fbae
      OS Version: 6.0.6002.2.2.0.256.6
      Locale ID: 1033
    Description:
      Stopped working
    Problem signature:
      Problem Event Name: APPCRASH
      Application Name: Access Connections.exe
      Application Version: 5.3.0.0
      Application Timestamp: 4bcff8d0
      Fault Module Name: KERNEL32.dll
      Fault Module Version: 6.0.6002.18005
      Fault Module Timestamp: 49e037dd
      Exception Code: e0434f4d
      Exception Offset: 0003fbae
      OS Version: 6.0.6002.2.2.0.256.6
      Locale ID: 1033

    Hi...
    I too have  got the same problem...
    i dont know when it started as it was running fine....earlier..
    In Access Connections the 'right click' menu on the taskbar runs just fine ..but the Access Connections program crashes on opening..
    The wireless status also runs fine
    Same is the case with Power Manager
    Shows the right battery status and the right click menu runs fine..but the Power Manager application crashes
    Like by the Lenovo toolbox too crashes
    I am using Lenovo X100e with win 7 starter edition
    i had .net framework 2 installed ...3.5 doesnt install and.net framework 4 installed after the problems started ...but still the problem hasnt stopped

  • Power Manager and Access Connections crash, neither help nor solution from Lenovo!?!

    Hello
    I've already posted here on the forum several weeks ago about the obvious problem that Lenovo has with the latest version of the Power Manager and the Access Connections which both crash either on startup or while tryibg to open it.
    So far there has been neither an update, nor a solution nor an official statement from Lenovo about that problem that consists rightnow for over two month!
    When searching the forum I see the same all over again: Unanswered threads, solutions that don't solve anything at all and so on...
    And just if someone here comes up with comments like:
    "work's here" or "just rollback to the old version", what is the point of writing software that doesn't work?? And why not giving ANY SUPPORT AT ALL???!!!
     I really would at least like to see an official statement saying "we work on it". After buying one of the most expensive notebooks on the market (and in my opinion still one of the best) hat would be the least one could expect form a "award wining" company like Lenovo...
    Regards
    Martin Pauli

    Hello, I am a Help Desk Consultant at Rensselaer Polytechnic Institute and currently, we've had many problems with access connections, 4965 agn wireless card, and its drivers.
    Symptoms:
    1) Wireless card is detected my windows device manager
    2) Wireless card is NOT detected by access connections, intel wireless utilities/tests/etc
    Other related information:
    1)  Events with ID 7036 + source: NETw#v## (the # stand for numbers, I can't quiet remember which ones but the one after the v is a 5
    2) Rollback driver is NEVER an abailable option
    3) Every failure case with same symptoms came in starting mid September
    4) If you select "show hidden devices" in device manager, there is a huge number of devices, most of which seem to be repeats
    After many hours of debugging and fustrated complaints, I have determined that it could be one of many problems:
    1) Teredo tunnelling: Apparently, atheros/intel/access connections won't find the wireless card if teredo has been enabled or something
    2) Power management: A default setting is "let windows turn the wireless off it there's not enough power" in wireless properties>configure>power management
    3) Driver update combination conflict: between a update on 9/21 and present time, there's something horribly gone wrong
    If anyone has a definitie solution to this, please post. 

  • Thinkpad Power manager causing problems in Vista

    Hi,
    We have been having problems with the Thinkpad power manager (all versions that we've tried) on Vista with T400, T500, and T60 series laptops.  These problems range from the program crashing to blue screens and reboots.  If we remove the software and use Vista's built in power manager, the battery life gets cut in half but we do not have any problems. Has anyone else had these problems?  Is there a way to reliably increase the battery life using Vista's built in power manager?  If not, how can we get the thinkpad power manager working correctly?
    Thank you,
    Brandon

    Hello Brandon,
    please tell us which version of PM and OS 32 or 64 do you use.
    That´ll help us to help you.
    Follow @LenovoForums on Twitter! Try the forum search, before first posting: Forum Search Option
    Please insert your type, model (not S/N) number and used OS in your posts.
    I´m a volunteer here using New X1 Carbon, ThinkPad Yoga, Yoga 11s, Yoga 13, T430s,T510, X220t, IdeaCentre B540.
    TIP: If your computer runs satisfactorily now, it may not be necessary to update the system.
     English Community       Deutsche Community       Comunidad en Español

  • BUG: Power Manager fails to autostart

    Alright, this topic is a continuation of my conversation with Lenovo support on Twitter, as it has been a while and we were unable to resolve this problem.
    Until recently I had Windows 7 x86 running perfectly normal with a number of ThinkVantage tools such as Power Manager, HDAPS protection, HotKey integration, etc. - all the bare necessities, though not the latest versions.
    Recently I've formatted everything and installed Windows 7 SP1 x64. Immediately after installation I've installed the latest versions of Power Manager, etc. from Lenovo Support website (i.e. not through System Update). Upon installation, the Power Manager gave me this error: 
    Every time I rebooted my computer, the same thing showed up and the Power Gauge was not showing in the taskbar. After a bit of looking around, I have found that in the following registry entry:  HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\Curren​tVersion\Run in the value rundll32 "C:\Program Files (x86)\ThinkPad\UTILIT~1\PWMTR64V.DLL",PwrMgrBkGndM​onitor the quotes were missing. Once I put them in, the Power Gauge started to show up during start up, however the message did not disappear.
    Then I tried installing the APS protection which gave me a couple of the very same messages during installation. When the installation finished, I tried running the APS protection from the Control Panel, but it crashed every time.
    Highly dissatisfied with all this, I've formatted the hard drive again, installed the same version of Windows and installed the Power Manager the very minute it finished installing, to be sure no other applications intervene. The result was the same.
    From @lenovo on Twitter I've received an advice to uninstall the Power Manager and try installing it from System Update, however the same error message prevents me from uninstalling the Power Manager. I have also tried using the System Update to install the HDAPS (which I haven't installed this time), but it failed.
    So there's my story. Any help would be very appreciated, as never before have I had a single issue with Lenovo tools.
    Thanks!
    Solved!
    Go to Solution.

    All right, I've gone through some experiments in the VMWare. Installing my modified image and then the Power Manager gave the same errors I am experiencing. However, when I used the untouched image, everything worked fine.
    So I would like to thank everyone who contributed to this topic and apologize to @Lenovo for taking their time with this issue.
    Yet I am very interested in what it is with the modified image that makes the Power Manager installation use paths like C:\Program Files (x86)\... instead of C:\Progra~2 like it happens with the normal image, which I just verified comparing registry entries. And also why the ThinkVantage tools are the only ones affected by this.
    But in any case, thanks to everyone again and I will accept this solution now.

  • Windows 7 RTM x64 Power Manager and switchable graphics not working

    Installed Windows 7 RTM x64 on my T400. After windows update and installing Lenovo's drivers, everything is accounted for. ATI graphics works fine, and I can see the Intel graphics on the shortcut menu. I just cannot manually switch to the built-in graphics, nor did I see the Power Manager. What do I need to do? I have installed the drivers for the power management, even though on the list of driver on lenovo's webpage it says it's only for SL models.
    Help would be appreciated.
    Specs:
    T400
    LED
    ATI/Intel switchable graphics
    4Gb

    Have you installed the Power manager http://www-307.ibm.com/pc/support/site.wss/WIN7-BE​TA.html#powm ?
    And after that, make sure you have installed the right driver (the one for switchable graphics): http://www-307.ibm.com/pc/support/site.wss/WIN7-BE​TA.html#m8xswitch
    Hope that helps.
    I also have Windows 7 Professional x64 on my T400 and everything works fine (i only uses programs and driver from here: http://www-307.ibm.com/pc/support/site.wss/WIN7-BE​TA.html
    T400 2767-AG8
    Windows 7 Professional 64bit

  • Can't get R&R or Power Manager to work under upgraded Win7 on X61

    I recently upgraded my X61 from Win Vista Business to Win7 Pro. While doing so I installed the new and supposedly Windows 7 compatible versions of R&R and Power Manager. However, I can't seem to get either to work - I can't even start the applications. Both immediately crash and tell me that "Lenovo Application has stopped working" (R&R) and "Power Manager has stopped working." I do get the power gauge in the task bar, but I cannot click it (same error/crash). 
    I followed the instructions and have therefore updated all the applicable drivers etc, e.g. the new version of CSS for R&R and the Power Management Driver for Power Manager, but it still doesn't work. I've also tried reinstalling (both uninstall followed by install and repair/reinstall). Does anybody know what's going on? What could be wrong?
    Is anybody else experiencing the same [kind of] problem? Are there any solutions?
    Thanks!
    Per Bylund
    Solved!
    Go to Solution.

    I believe I've found the reason for the problem I had with both R&R and the Power Manager (also discussed here): I did not have .NET framework 3.5.1 SP 1 installed. It is obviously disabled by default on Win7, so one will have to enable it through Control Panel -> Uninstall a program -> Turn Windows features on or off (and then make sure to check the Microsoft .NET Framework 3.5.1 check box).
    The strange thing is that I have not found the information that .NET framework is required anywhere - Lenovo obviously didn't think of supplying it. I just happened to find the solution when installing the upgrade for the Lenovo Toolbox, which could not be finished without first installing the framework (and the Toolbox installation program told me this was required). 
    So make sure you have the .NET framework enabled if you want to run a bunch of the ThinkVantage applications!
    Per Bylund

  • Power Manager 4.42 Not Working T61p Vista 64-bit

    ThinkVantage Power Manager is not working on my machine.  I first noticed this after System Update added several new ThinkVantage programs, including PM version 4.41a several weeks ago, but I can't point with any certainty a specific cause or beginning to the problem. 
    PM now stops working every time during initial (power-on) machine boot-up showing message: "Power Manager Stopped Working".  This seems to happen whenver it is installed by system update.  When I have tried installing PM manually, it simply refuses to install, giving a short message saying it cannot run on my system.  Earlier versions ran OK before.  Microsoft Problem Reports and Solutions is of course clueless about this (and most other crashes).
    I have tried uninstalling, rebooting, and reinstalling both PM and the latest PM driver in several different sequences, but nothing seems to work.  I was hopeful that a recent upgrade to PM version 4.42 (via System Update) might solve the problem, but same thing happens and manually installation still doesn't work.  I also uninstalling Access Connections (which has given me other problems), rebooted, and tried loading both PM and PM Driver, but with the same results.  Something funny going on...
    I have ThinkPad 61p (6459-CTO) with 4GB RAM, running Vista Ultimate 64-bit with NIS 2009.  I have installed the most recent BIOS and have other up-to-date Lenovo software via System Update. 
    Any suggestions?
    Thanks

    I have tried several more things, including upgrading to Visual C++ 2008 in an attempt to get my system to install TV Power Manager 4.42 (or earlier versions).  I still get the same message when I attempt to install manually: "cannot run on this system". Same thing happens when trying to load an older version 4.20a that I found through the forum.
    I have been successful in loading the version that came pre-installed on my computer (found in SWTools folder), and that seems to work, though with very basic functionality.  It appears to be Version 2.11.
    I would really like to find a way to install a newer version (preferably 4.42), as it seems this is needed to run later versions of other TV software.  I have T61p (6459-CTO) running Vista Ultimate 64-bit, and the BIOS and drivers are all up to date, as per Lenovo site.
    Thanks for any advice.

Maybe you are looking for