Jump to content

ccleaner and wmi errors


Recommended Posts

windows 7 sp1 home 32bit

ccleaner pro v5.76.8269

 

just opening the program on the desktop causes two errors in the wmi event log.

Note - CCleaner debug log removed for users privacy/security - Nukecad.

 

Link to comment
Share on other sites

  • Moderators

Does CCleaner run OK for you?

What Antivirus are you using?
Do you have any special firewall settings?

*** Out of Beer Error ->->-> Recovering Memory ***

Worried about 'Tracking Files'? Worried about why some files come back after cleaning? See this link:
https://community.ccleaner.com/topic/52668-tracking-files/?tab=comments#comment-300043

 

Link to comment
Share on other sites

  • Moderators

Apparently that particular error ResultCode in your event log is associated with the operation WbemServices::ExecQuery, which fails with 0x80041032 (WBEM_E_CALL_CANCELLED).

Most Microsoft articles I can find about it only refer to Windows server 2012, that's probably because Win 7 is now EOL.

After some searching I found the following from Microsoft burried in this blog:
http://www.networksteve.com/forum/topic.php/Event_5858_from_WMI-Activity/?TopicId=82067&Posts=1
Scroll down to the post dated April 16th 2013.

Quote

The core problem for this set of issues is that the WMI error event ID 5858 is being generated generically and is not only representing functional error conditions. Unfortunately, for application/backwards compatibility, we cant just get rid of it, because people have gone to the effort of parsing the event (more below) to look for the instances where there is useful data.

Quote

ResultCode details: ......

0x80041032 Call Cancelled. The client application cancelled the request that was made. That is almost always ignorable as a WMI error. The component or application (SCCM, or Group Policy) for example) that was calling into WMI cancelled the request, and will likely generate its own event if it is important to do.

In other words Microsoft said/say: "That error is being generated when it shouldn't realy be. - We can't change that without causing other problems.  - Just ignore it".

 

Please note that I have removed the CCleaner debug log from your first post.
The log contained your CCleaner licence key, which I'm sure you don't want to share with the rest of the world.

 

*** Out of Beer Error ->->-> Recovering Memory ***

Worried about 'Tracking Files'? Worried about why some files come back after cleaning? See this link:
https://community.ccleaner.com/topic/52668-tracking-files/?tab=comments#comment-300043

 

Link to comment
Share on other sites

Final Notes:

Thanks for the link; You are correct. This system is not a server.

Installed version 5.75.8238 same wmi errors

Installed version 5.70.7909 same wmi errors

Installed version 5.68.7820 same wmi errors

Installed version 5.61.7392 same wmi errors

Installed version 5.46.6652 same wmi errors

Installed version 5.44.6575 same wmi errors

After each uninstall no wmi errors.

Installed similar software. No wmi errors.

Final Solution : BYE-BYE CCLEANER!

Link to comment
Share on other sites

  • Moderators

Your choice of course.

I know you are not using a server, but the MS articles for Win 7 are no longer there.
Because Win 7 is EOL MS have removed any references to it in their 'bug' articles.

But did you not understand that this is a Windows wmi error, not CCleaner?
MS are not going to try and fix it now because Win 7 is EOL.
They are not going to fix it on Server 2012 either - they have told users to ignore it.

Quote

 Microsoft said/say: "That error is being generated when it shouldn't realy be. - We can't change that without causing other problems.  - Just ignore it".

 

*** Out of Beer Error ->->-> Recovering Memory ***

Worried about 'Tracking Files'? Worried about why some files come back after cleaning? See this link:
https://community.ccleaner.com/topic/52668-tracking-files/?tab=comments#comment-300043

 

Link to comment
Share on other sites

  • Admin

Hi @mepowers In continuation with what nukecad has said, you may also want to verify if the same event is recorded when using something else that calls upon the WMI service, such as the System Information utility in Windows:

 

  • Click Start > All Programs > Accessories > Run
  • Type: msinfo32.exe > click OK

Afterwards, check to see if the same WMI associated event is recorded in the Windows Event Viewer.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.