Question

Q: Windows 10 perflib 1008 error

How do I get rid of this perflib 1008 error

Log Name:      Application
Source:        Microsoft-Windows-Perflib
Date:          9/18/2015 3:44:10 PM
Event ID:      1008
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Eduardo-PC
Description:
The Open Procedure for service "WmiApRpl" in DLL "C:\WINDOWS\system32\wbem\wmiaprpl.dll" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section contains the error code.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Perflib" Guid="{13B197BD-7CEE-4B4E-8DD0-59314CE374CE}" EventSourceName="Perflib" />
    <EventID Qualifiers="49152">1008</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2015-09-19T01:44:10.000000000Z" />
    <EventRecordID>19334</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>Eduardo-PC</Computer>
    <Security />
  </System>
  <UserData>
    <EventXML xmlns="Perflib">
      <param1>WmiApRpl</param1>
      <param2>C:\WINDOWS\system32\wbem\wmiaprpl.dll</param2>
      <binaryDataSize>8</binaryDataSize>
      <binaryData>1500000000000000</binaryData>
    </EventXML>
  </UserData>
</Event>



Hi,

Thank you for posting your query in Microsoft Community.

I understand your concern, and we in Community will try to help you in the best possible way we can.

 

Method 1:
I would suggest you to run System File Checker.


System File Checker is a utility in Windows that allows users to scan for corruptions in Windows system files and restore corrupted files. (Also applicable for Windows 10)
https://support.microsoft.com/en-us/kb/929833?wa=wsignin1.0

Method2:
I would also suggest you to Run DISM or System Update Readiness tool


Windows corruption errors may prevent Windows updates from installing. For example, an update might not install if a system file is damaged. The DISM or System Update Readiness tool may help you to fix some Windows corruption errors. (Refer to Windows 8/8.1 also applicable to Windows 10)
https://support.microsoft.com/en-us/kb/947821

Hope the information helps, if you have any further queries, feel free to post. We are here to assist you.

Thank you.

Did this solve your problem?

Sorry this didn't help.

30 people were helped by this reply


Found this: I think is Utilman.exe I am afraid to tinker with this and find myself locked out of the comp.

 Found: {l:32 b:edH/q914QdkEPU3fH5NyG8012CNhRBH9TqtdLBaobzU=} Expected: {l:32 b:JWYUiFDB/hMYEhf3KxRxcP4kK/Y+VRxfzXqStMeV8rg=}
2015-09-19 18:25:09, Info                  CSI    00005162 [SR] Cannot repair member file [l:22{11}]"Utilman.exe" of Microsoft-Windows-UtilMan, Version = 10.0.10240.16384, pA = amd64, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2015-09-19 18:25:09, Info                  CSI    00005163 Hashes for file member \SystemRoot\WinSxS\x86_microsoft-windows-m..nts-mdac-rds-ce-jvs_31bf3856ad364e35_10.0.10240.16384_none_0d9b4ea224376197\adcjavas.inc do not match actual file [l:24{12}]"adcjavas.inc" :
  Found: {l:32 b:6BlfjhjB8GArq4gx7XplKy5YYo32soAk03mrg1eaRRY=} Expected: {l:32 b:4MfTT3V5JEdirlo3HtVRoiged94J/wsbIs0bGYLXdog=}
2015-09-19 18:25:09, Info                  CSI    00005164 [SR] Cannot repair member file [l:24{12}]"adcjavas.inc" of Microsoft-Windows-Microsoft-Data-Access-Components-(MDAC)-RDS-CE-JVS, Version = 10.0.10240.16384, pA = x86, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2015-09-19 18:25:09, Info                  CSI    00005165@2015/9/20:04:25:09.510 Primitive installers committed for repair
2015-09-19 18:25:09, Info                  CSI    00005166 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-utilman_31bf3856ad364e35_10.0.10240.16384_none_0aaa219dcbea9976\Utilman.exe do not match actual file [l:22{11}]"Utilman.exe" :
  Found: {l:32 b:edH/q914QdkEPU3fH5NyG8012CNhRBH9TqtdLBaobzU=} Expected: {l:32 b:JWYUiFDB/hMYEhf3KxRxcP4kK/Y+VRxfzXqStMeV8rg=}
2015-09-19 18:25:09, Info                  CSI    00005167 [SR] Cannot repair member file [l:22{11}]"Utilman.exe" of Microsoft-Windows-UtilMan, Version = 10.0.10240.16384, pA = amd64, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2015-09-19 18:25:09, Info                  CSI    00005168 [SR] This component was referenced by [l:346{173}]"Microsoft-Windows-Client-Features-Package-AutoMerged-enduser~31bf3856ad364e35~amd64~~10.0.10240.16384.Microsoft-Windows-Client-Features-Package-AutoMerged-enduser-Deployment"
2015-09-19 18:25:09, Info                  CSI    00005169 Hashes for file member \??\C:\WINDOWS\System32\Utilman.exe do not match actual file [l:22{11}]"Utilman.exe" :
  Found: {l:32 b:edH/q914QdkEPU3fH5NyG8012CNhRBH9TqtdLBaobzU=} Expected: {l:32 b:JWYUiFDB/hMYEhf3KxRxcP4kK/Y+VRxfzXqStMeV8rg=}
2015-09-19 18:25:09, Info                  CSI    0000516a Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-utilman_31bf3856ad364e35_10.0.10240.16384_none_0aaa219dcbea9976\Utilman.exe do not match actual file [l:22{11}]"Utilman.exe" :
  Found: {l:32 b:edH/q914QdkEPU3fH5NyG8012CNhRBH9TqtdLBaobzU=} Expected: {l:32 b:JWYUiFDB/hMYEhf3KxRxcP4kK/Y+VRxfzXqStMeV8rg=}
2015-09-19 18:25:09, Info                  CSI    0000516b [SR] Could not reproject corrupted file [ml:48{24},l:46{23}]"\??\C:\WINDOWS\System32"\[l:22{11}]"Utilman.exe"; source file in store is also corrupted
2015-09-19 18:25:09, Info                  CSI    0000516c CSIPERF - FilePI Queue 177ms
2015-09-19 18:25:09, Info                  CSI    0000516d@2015/9/20:04:25:09.710 Primitive installers committed for repair
2015-09-19 18:25:09, Info                  CSI    0000516e@2015/9/20:04:25:09.710 Primitive installers committed for repair
2015-09-19 18:25:09, Info                  CSI    0000516f Hashes for file member \SystemRoot\WinSxS\x86_microsoft-windows-m..nts-mdac-rds-ce-jvs_31bf3856ad364e35_10.0.10240.16384_none_0d9b4ea224376197\adcjavas.inc do not match actual file [l:24{12}]"adcjavas.inc" :
  Found: {l:32 b:6BlfjhjB8GArq4gx7XplKy5YYo32soAk03mrg1eaRRY=} Expected: {l:32 b:4MfTT3V5JEdirlo3HtVRoiged94J/wsbIs0bGYLXdog=}
2015-09-19 18:25:09, Info                  CSI    00005170 [SR] Cannot repair member file [l:24{12}]"adcjavas.inc" of Microsoft-Windows-Microsoft-Data-Access-Components-(MDAC)-RDS-CE-JVS, Version = 10.0.10240.16384, pA = x86, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2015-09-19 18:25:09, Info                  CSI    00005171 [SR] This component was referenced by [l:370{185}]"Microsoft-Windows-Client-Features-WOW64-Package-AutoMerged-enduser~31bf3856ad364e35~amd64~~10.0.10240.16384.Microsoft-Windows-Client-Features-WOW64-Package-AutoMerged-enduser-Deployment"
2015-09-19 18:25:09, Info                  CSI    00005172 Hashes for file member \??\C:\Program Files (x86)\Common Files\System\msadc\adcjavas.inc do not match actual file [l:24{12}]"adcjavas.inc" :
  Found: {l:32 b:6BlfjhjB8GArq4gx7XplKy5YYo32soAk03mrg1eaRRY=} Expected: {l:32 b:4MfTT3V5JEdirlo3HtVRoiged94J/wsbIs0bGYLXdog=}
2015-09-19 18:25:09, Info                  CSI    00005173 Hashes for file member \SystemRoot\WinSxS\x86_microsoft-windows-m..nts-mdac-rds-ce-jvs_31bf3856ad364e35_10.0.10240.16384_none_0d9b4ea224376197\adcjavas.inc do not match actual file [l:24{12}]"adcjavas.inc" :
  Found: {l:32 b:6BlfjhjB8GArq4gx7XplKy5YYo32soAk03mrg1eaRRY=} Expected: {l:32 b:4MfTT3V5JEdirlo3HtVRoiged94J/wsbIs0bGYLXdog=}
2015-09-19 18:25:09, Info                  CSI    00005174 [SR] Could not reproject corrupted file [ml:106{53},l:104{52}]"\??\C:\Program Files (x86)\Common Files\System\msadc"\[l:24{12}]"adcjavas.inc"; source file in store is also corrupted
2015-09-19 18:25:09, Info                  CSI    00005175@2015/9/20:04:25:09.740 Primitive installers committed for repair

Did this solve your problem?

Sorry this didn't help.


Hi Aguabrava,

Thanks for the reply.

I need more information about this issue so that I can assist you better.

1. What is the make and model of your computer?

2. When do you get this error?

3. Did you make any change in your computer?

Let us know the answers of the above questions so that we can assist you better.

Thanks.

 

Did this solve your problem?

Sorry this didn't help.

8 people were helped by this reply


when you provide a link it would help if it worked here is what I found when I clicked on the link    This page doesn’t exist.

Did this solve your problem?

Sorry this didn't help.


I am getting the same wmiaprpl error about once a day.  sfc /scannow doesn't find any relevant issues, and I can't run DISM until Microsoft finally fixes the false opencl.dll errors that you get if you're using the latest NVidia drivers.  Running DISM would replace NVidia's 100k+ opencl.dll with Microsoft's 30k limited functionality one. 

At any rate, I don't think DISM would fix this issue anyway, since no related errors appear in sfc /scannow.

My antivirus is Bitdefender Total Security 2016, by the way, just in case it's somehow relevant.

Did this solve your problem?

Sorry this didn't help.

115 people were helped by this reply


 
Question Info

Views: 22,567 Last updated: June 16, 2018 Applies to: