none
Windows 10 error while loading: Resource DLL Power Manager Gauge

Answers

All replies

  • a. Click on Start button and type cmd in search box.

    b. Right-click on Command Prompt and select Run as administrator.

    c. Type the following command and hit Enter.

    sfc /scannow


    S.Sengupta, Windows Experience MVP

    Sunday, September 6, 2015 8:46 AM
  • I am having the same issue as mentioned and ran you commands.

    Result

    Windos Resource Protection found corrupt files but was unable to fix some of them details are included in the .....

    That Log file contains

    SI    000055b6 [SR] Verify complete
    2015-09-09 15:11:18, Info                  CSI    000055b7 [SR] Verifying 13 (0x000000000000000d) components
    2015-09-09 15:11:18, Info                  CSI    000055b8 [SR] Beginning Verify and Repair transaction
    2015-09-09 15:11:18, Info                  CSI    000055b9@2015/9/9:22:11:18.765 Primitive installers committed for repair
    2015-09-09 15:11:18, Info                  CSI    000055ba@2015/9/9:22:11:18.846 Primitive installers committed for repair
    2015-09-09 15:11:18, Info                  CSI    000055bb@2015/9/9:22:11:18.909 Primitive installers committed for repair
    2015-09-09 15:11:18, Info                  CSI    000055bc@2015/9/9:22:11:18.975 Primitive installers committed for repair
    2015-09-09 15:11:19, Info                  CSI    000055bd@2015/9/9:22:11:19.034 Primitive installers committed for repair
    2015-09-09 15:11:19, Info                  CSI    000055be@2015/9/9:22:11:19.091 Primitive installers committed for repair
    2015-09-09 15:11:19, Info                  CSI    000055bf@2015/9/9:22:11:19.156 Primitive installers committed for repair
    2015-09-09 15:11:19, Info                  CSI    000055c0@2015/9/9:22:11:19.206 Primitive installers committed for repair
    2015-09-09 15:11:19, Info                  CSI    000055c1@2015/9/9:22:11:19.259 Primitive installers committed for repair
    2015-09-09 15:11:19, Info                  CSI    000055c2@2015/9/9:22:11:19.352 Primitive installers committed for repair
    2015-09-09 15:11:19, Info                  CSI    000055c3@2015/9/9:22:11:19.416 Primitive installers committed for repair
    2015-09-09 15:11:19, Info                  CSI    000055c4@2015/9/9:22:11:19.465 Primitive installers committed for repair
    2015-09-09 15:11:19, Info                  CSI    000055c5@2015/9/9:22:11:19.516 Primitive installers committed for repair
    2015-09-09 15:11:19, Info                  CSI    000055c6 [SR] Verify complete
    2015-09-09 15:11:19, Info                  CSI    000055c7 [SR] Repairing 1 components
    2015-09-09 15:11:19, Info                  CSI    000055c8 [SR] Beginning Verify and Repair transaction
    2015-09-09 15:11:19, Info                  CSI    000055c9 Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10534.0_none_3de21453566a5dbf\opencl.dll do not match actual file [l:20{10}]"opencl.dll" :
      Found: {l:32 b:AB4N8DQiScfF3OdJKIVfaVDVOuAu0Ch3S1qd4OsLWmw=} Expected: {l:32 b:fHzrSo52aqKOCWJKswo4tfhU7PHsLs6OMsMnvq59gXQ=}
    2015-09-09 15:11:19, Info                  CSI    000055ca [SR] Cannot repair member file [l:20{10}]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, Version = 10.0.10534.0, pA Host= amd64 Guest= x86, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2015-09-09 15:11:19, Info                  CSI    000055cb@2015/9/9:22:11:19.580 Primitive installers committed for repair
    2015-09-09 15:11:19, Info                  CSI    000055cc Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10534.0_none_3de21453566a5dbf\opencl.dll do not match actual file [l:20{10}]"opencl.dll" :
      Found: {l:32 b:AB4N8DQiScfF3OdJKIVfaVDVOuAu0Ch3S1qd4OsLWmw=} Expected: {l:32 b:fHzrSo52aqKOCWJKswo4tfhU7PHsLs6OMsMnvq59gXQ=}
    2015-09-09 15:11:19, Info                  CSI    000055cd [SR] Cannot repair member file [l:20{10}]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, Version = 10.0.10534.0, pA Host= amd64 Guest= x86, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2015-09-09 15:11:19, Info                  CSI    000055ce [SR] This component was referenced by [l:250{125}]"Microsoft-Windows-RemoteFX-VM-Setup-Package~31bf3856ad364e35~amd64~~10.0.10534.0.RemoteFX clientVM and UMTS files and regkeys"
    2015-09-09 15:11:19, Info                  CSI    000055cf Hashes for file member \??\C:\WINDOWS\SysWOW64\opencl.dll do not match actual file [l:20{10}]"opencl.dll" :
      Found: {l:32 b:AB4N8DQiScfF3OdJKIVfaVDVOuAu0Ch3S1qd4OsLWmw=} Expected: {l:32 b:fHzrSo52aqKOCWJKswo4tfhU7PHsLs6OMsMnvq59gXQ=}
    2015-09-09 15:11:19, Info                  CSI    000055d0 Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10534.0_none_3de21453566a5dbf\opencl.dll do not match actual file [l:20{10}]"opencl.dll" :
      Found: {l:32 b:AB4N8DQiScfF3OdJKIVfaVDVOuAu0Ch3S1qd4OsLWmw=} Expected: {l:32 b:fHzrSo52aqKOCWJKswo4tfhU7PHsLs6OMsMnvq59gXQ=}
    2015-09-09 15:11:19, Info                  CSI    000055d1 [SR] Could not reproject corrupted file [ml:48{24},l:46{23}]"\??\C:\WINDOWS\SysWOW64"\[l:20{10}]"opencl.dll"; source file in store is also corrupted
    2015-09-09 15:11:19, Info                  CSI    000055d2@2015/9/9:22:11:19.691 Primitive installers committed for repair
    2015-09-09 15:11:19, Info                  CSI    000055d3 [SR] Repair complete
    2015-09-09 15:11:19, Info                  CSI    000055d4 [SR] Committing transaction
    2015-09-09 15:11:19, Info                  CSI    000055d5 Creating NT transaction (seq 2), objectname [6]"(null)"
    2015-09-09 15:11:19, Info                  CSI    000055d6 Created NT transaction (seq 2) result 0x00000000, handle @0x814
    2015-09-09 15:11:19, Info                  CSI    000055d7@2015/9/9:22:11:19.736 Beginning NT transaction commit...
    2015-09-09 15:11:19, Info                  CSI    000055d8@2015/9/9:22:11:19.747 CSI perf trace:
    CSIPERF:TXCOMMIT;14462

    Wednesday, September 9, 2015 10:22 PM
  • Try DISM /Online /Cleanup-Image /RetoreHealth, it is recommended over SFC /ScanNow in Windows 8 and newer and appears to have a better success rate at restoring corrupted files and components.

    It appears the issue is indeed caused by system component corruption.

    Brandon
    Windows Outreach Team- IT Pro
    Windows for IT Pros on TechNet

    Wednesday, September 23, 2015 3:24 PM
    Moderator
  • Also note that you posted this Windows 10 question in the Windows 8.1 forums, it will be moved appropriately to the Windows 10 forums.

    Brandon
    Windows Outreach Team- IT Pro
    Windows for IT Pros on TechNet

    Wednesday, September 23, 2015 4:57 PM
    Moderator
  • I should also ask, are you using a Lenovo ThinkPad? ThinkPad Power Manager Gauge is a tool provided for monitoring the battery status on Lenovo devices and you may need to remove or update this utility for compatibility with Windows 10.

    Brandon
    Windows Outreach Team- IT Pro
    Windows for IT Pros on TechNet

    Wednesday, September 23, 2015 5:00 PM
    Moderator
  • Are you using a Lenovo? It seems this is a Lenovo specific thing, as I am researching the same issue because it is annoying.

    I don't think this is a Window's 10 problem....

    Wednesday, November 11, 2015 5:06 PM
  • The solution to this is far easier than suggested. Simply reinstall the power manager from     C:\Program Files\Lenovo\Settingsdependency\Power 
    Wednesday, August 3, 2016 12:08 AM
  • Reinstalling from C:\Program Files\Lenovo\Settingsdependency\Power does not work in my case.  The reinstall stops and indicates it can't be installed on this operating system.  Lenovo Thinkpad T510, updated from Win7 Pro to Win10 Pro.  Unfortunately I did not uninstall this application before updating to Win10.  Therefore, not only will this application not reinstall there is no easy way to uninstall.  The Power Manager resource DLL error only occurs whenever I access the Control Panel, so it's not a big problem, just an annoyance.
    Tuesday, November 29, 2016 6:40 PM
  • The Lenovo Thinkpad T510 Manual- guideusermanual.com/product-name-thinkpad-t510-manual&po=331268&lang=English says that the error comes from the scheduled task by Lenovo Settings Power. By disabling the the task in the Task Scheduler, the error went away.
     
    This does not affect the function of Lenovo Settings, just make the power information a bit slow to load.
    Thursday, April 27, 2017 12:47 PM
  • PWMAL32V.cpl
    PWMAL64V.cpl
    PWMCP32V.cpl
    PWMCP64V.cpl

    find them, delete, a clean world

    Tuesday, May 16, 2017 3:13 PM
  • PWMAL32V.cpl
    PWMAL64V.cpl
    PWMCP32V.cpl
    PWMCP64V.cpl

    find them, delete, a clean world

    This is the solution. Thanks!

    Do a backup of files and registry values first!

    Then:

    1. Find C:\windows\system32\PWMCP64V.cpl   and delete that file.

    2. Wasn't necessary in my case: Then, search your registry for "PWMCP64V.cpl" and delete any references to it.

    3. In particular, there should be several entries under this key that will need to be deleted:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Control Panel\Extended Properties

    • Proposed as answer by MikeSum Thursday, November 9, 2017 11:01 AM
    Thursday, November 9, 2017 11:01 AM
  • nailed it
    Sunday, September 23, 2018 5:40 PM