error number 0x80041002

[John Steffensen]

Any explanation to this?

What to do to solve this issue?

Best regards, John

[Nergal]

this is a unclear question, all you've provided us with is a memory address reference. When does this error occur, does speccy quit when it happens? Freeze?

Please run speccy in debug mode

check only one box per debug run but go through all check

Any time, during this debug trail, that the crash occurs post the log created to this thread

 

Edit: Also provide your Windows Version and the version number of speccy (do not say latest version as this provides no information)

Edited July 29, 2013 by Nergal

[Ahuahuachi]

You need to rebuild your repository... Or just write the following on a command line:

 

net stop winmgmt

c:

cd %systemroot%\system32\wbem

rd /S /Q repository

 

regsvr32 /s %systemroot%\system32\scecli.dll

regsvr32 /s %systemroot%\system32\userenv.dll

mofcomp cimwin32.mof

mofcomp cimwin32.mfl

mofcomp rsop.mof

mofcomp rsop.mfl

for /f %%s in ('dir /b /s *.dll') do regsvr32 /s %%s

for /f %%s in ('dir /b *.mof') do mofcomp %%s

for /f %%s in ('dir /b *.mfl') do mofcomp %%s

echo DONE reboot

pause

 

You can also do batch file with this.

[Nergal]

Based on the comments attached to

http://msmvps.com/blogs/lduncan/pages/20217.aspx

I'm not sure I would run that batch, but it did point me in the right direction

Make sure the WMI service is running

 

also can you confirm that

http://support.microsoft.com/kb/2465990/en-us

is indeed what we are talking about

Edited July 31, 2013 by Nergal

[Alan_B]

net stop winmgmt

c:

cd %systemroot%\system32\wbem

rd /S /Q repository

 

THAT IS A CURE THAT MAY BE WORSE THAN THE PROBLEM.

 

It was part of a "standard solution" that was normally recommended for a successful update of my security software package.

It was expected that after a computer reboot the repository would be rebuilt so that Windows would recognise that the old software package had been replaced by a new one.

The repository was never rebuilt properly,

even after many reboots and many attempts at repairing Windows XP.

 

The only way to fix a "Manifest Error" upon every system start-up was to restore a partition image that restored normality - and brought back the obsolete software package.

 

I guess most people are lucky and the repository is correctly rebuilt,

but so many people come unstuck that I lost count of the quantities of solutions that Google found for me (and which failed when I tried).