Within 1 minute of rebooting there were 4 off Application Event logg errors :-
Failed to load MOF C:\*\*\*.MOF while recovering repository file
Also BEFORE this problem Autorecover\*.MOF held only 14 off *.MOF files,
but AFTER there were another 40 extra *.MOF files plus 10 of the old 14 were rebuilt and halved in size.
Also there was a new file - C:\WINDOWS\system32\wbem\Logs\MofComp.log
What is that all about ?
Do 50+ off *.MOF files represent 50+ items that have failed to autorecover ?
or are they junk left over after a successful autorecovery ?
Can they now be safely deleted ?
Does MofComp.log hold any information that assists in identifying / correcting problems ?
Windows still seems to work. Is it now actually a bit more broken ?
Is there anything I should do to make it better ?
The clean-up script deleted old Comodo Security files that uninstal had omitted.
Some files/folders were not accessible until I took ownership and deleted them.
I ran the script a dozen times in rapid succession whilst identifying what else I had to own.
I did not realise at the time that the script not only deleted Comodo residues,
but to ensure Windows Security would recognise Comodo was uninstalled,
it also deleted the repository so that Windows would rebuild it.
Windows may have been half way through rebuilding the repository as it was deleted again, and again, and again ...
Is it possible that permanent damage was done by partial rebuilds aborted by deletions ?
I have since found that after deleting all the "brand new" *.MOF files,
They are all exactly recreated when I stop the Winmgmt service and delete the repository.
I am overwhelmed by my ignorance on the above. So many questions.
PLEASE PLEASE give me some clues.
Even one answer to one question will give me more than I have at the moment.
Supplementary information :-
Application Log "event ID 4" type erors "while recovering repository file" - 4 off :-
Failed to load MOF C:\AC30D119A40F2C8C8708A20576\I386\LICWMI.MOF
Failed to load MOF C:\WINDOWS\MICROSOFT.NET\FRAMEWORK\V1.1.4322\ASPNET.MOF
Failed to load MOF C:\WINDOWS\MICROSOFT.NET\FRAMEWORK\V2.0.50727\ASPNET.MOF
Failed to load MOF C:\WINDOWS\MICROSOFT.NET\FRAMEWORK\V3.0\WINDOWS COMMUNICATION FOUNDATION\SERVICEMODEL.MOF
Why did it attempt to load MOF C:\WINDOWS\MICROSOFT.NET\FRAMEWORK\V3.0\...
A long time ago this sneaked onto my system with a security patch that M.$ said was needed for V2.*,
but I instantly recognised garbage I did NOT want and I uninstalled it.
That removed the new C:\WINDOWS\MICROSOFT.NET\FRAMEWORK\V3.0 so why is it being rebuilt ?
New file - In C:\WINDOWS\system32\wbem\Logs\mofcomp.log 27 January 2010, 22:13:20
This shows 5 errors, but no immediately apparent connection with the above 4 off "Failed to load MOF ..." :-
1. Weird error :- same file is parsed TWICE, first time not valid, second time Finished compiling ! ! !
(Wed Jan 27 22:12:48 2010.43232) : Parsing MOF file: C:\WINDOWS\system32\WBEM\AutoRecover\3EC317800FF508210BB945C81C0EACE7.mof
(Wed Jan 27 22:12:48 2010.43252) : (1): error SYNTAX 0X8004401e: This is not a valid MOF file(Wed Jan 27 22:12:48 2010.43322) : Parsing MOF file: C:\WINDOWS\system32\WBEM\AutoRecover\3EC317800FF508210BB945C81C0EACE7.mof
(Wed Jan 27 22:12:48 2010.43322) : Parsing MOF file: C:\WINDOWS\system32\WBEM\AutoRecover\3EC317800FF508210BB945C81C0EACE7.mof
(Wed Jan 27 22:12:54 2010.49431) : Finished compiling file:C:\WINDOWS\system32\WBEM\AutoRecover\3EC317800FF508210BB945C81C0EACE7.mof
// This file DOES exist - and was given a second chamce and it seems to have worked ! ! !
2. Peculiar - Same "(1): error SYNTAX 0X8004401e:" but this time it is NOT given a second chance ! ! !
(Wed Jan 27 22:13:18 2010.73225) : Parsing MOF file: C:\WINDOWS\system32\WBEM\AutoRecover\01F0F06AA3A0296B59BCEAEC356B7524.mof
(Wed Jan 27 22:13:18 2010.73225) : (1): error SYNTAX 0X8004401e: This is not a valid MOF file(Wed Jan 27 22:13:18 2010.73255) : Parsing MOF file: C:\WINDOWS\system32\WBEM\AutoRecover\9AD3182A2F39A3E091E15109132EC6CC.mof
// This file does NOT exist ! ! !
3. 3 off compiler errors, presumably .NET Framework things :-
(Wed Jan 27 22:13:19 2010.73565) : Parsing MOF file: C:\WINDOWS\system32\WBEM\AutoRecover\2B8B1A8B0ACD3EE28B421D3918DC1F29.mof
(Wed Jan 27 22:13:19 2010.73575) : An error occurred while creating object 1 defined on lines 12 - 15:
(Wed Jan 27 22:13:19 2010.73575) : 0X80041002 (Wed Jan 27 22:13:19 2010.73575) : Class, instance, or property 'EventTrace' was not found.
(Wed Jan 27 22:13:19 2010.73655) : Parsing MOF file: C:\WINDOWS\system32\WBEM\AutoRecover\1EBE968EB7AF815A32641E6185350A9E.mof
(Wed Jan 27 22:13:19 2010.73736) : An error occurred while creating object 1 defined on lines 12 - 66:
(Wed Jan 27 22:13:19 2010.73756) : 0X80041002 (Wed Jan 27 22:13:19 2010.73756) : Class, instance, or property 'EventTrace' was not found.
(Wed Jan 27 22:13:19 2010.73776) : Parsing MOF file: C:\WINDOWS\system32\WBEM\AutoRecover\7E27EAAD25AA36FEADFF502991DFC5C1.mof
(Wed Jan 27 22:13:19 2010.74547) : An error occurred while creating object 76 defined on lines 2215 - 2217:
(Wed Jan 27 22:13:19 2010.74547) : 0X80041002 (Wed Jan 27 22:13:19 2010.74547) : Class, instance, or property 'EventTrace' was not found.
I am unable to find any MOF "C:\AC30D119A40F2C8C8708A20576\I386\LICWMI.MOF"
Why is it in Root C:\ instead of ...\AutoRecover ?
Is it a temporary thing created only for use when rebuilding the repository ?
I have attached copies of mofcomp.log and the 3 off *.MOF files with missing 'EventTrace'
and renamed as *.txt to conform to attachment rules.
Regards
Alan
Attached Files
Edited by Alan_B, 08 February 2010 - 04:30 PM.