55 off errors on reboot "Failed to Load MOF" + System32\wbem\AutoRecover\*.MOF ??

I removed Comodo 3.5 Firewall and completed removal by rebooting the P.C.
I then checked the event logs to confirm all was well.
I found in the Application Event log that about 1 minute after that latest reboot and login there were 4 errors.

All 4 errors were
Event Type: Error
Event Source: WinMgmt
Event Category: None
Event ID: 4
"Failed to load MOF" {specific file} "while recovering repository file."

The specific files were
C:\AC30D119A40F2C8C8708A20576\I386\LICWMI.MOF
C:\WINDOWS\MICROSOFT.NET\FRAMEWORK\V1.1.4322\ASPNET.MOF
C:\WINDOWS\MICROSOFT.NET\FRAMEWORK\V2.0.50727\ASPNET.MOF
C:\WINDOWS\MICROSOFT.NET\FRAMEWORK\V3.0\WINDOWS COMMUNICATION FOUNDATION\SERVICEMODEL.MOF

Incidentally both the ASPNET.MOF files had a last access date from last year,
so I seems to me that the "Failed to load MOF" was because the was no attempt to read them.
Also .NET v3.0 was purged last year, so the fourth item no longer exists ! ! !

I never knew till then that there had ever been any need to "recover repository files".
There were no further errors when I rebooted 4 times in succession,
so I assumed it was a "one time" failure to recover, and upon the second reboot a full recovery was achieved.
Did I do Good ? ? ?

I then installed Comodo 3.10 Firewall, and the next application event was
Successful auto update retrieval of third-party root list sequence number from:
<http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootseq.txt>

A few days later I did a complete File and Folder comparison between C:\ and an image made before the errors.
I saw that starting a few seconds before, and finishing a few seconds after the "Failed to load MOF" errors,
there were new "Update" time stammps on 51 off C:\WINDOWS\System32\wbem\AutoRecover\*.MOF files.

I am concerned that the 4 events I saw in the event log are only the top of the iceberg off an epic disaster.

Before the disaster C:\WINDOWS\System32\wbem\AutoRecover\ held only 11 off *.MOF files.
After the disaster 4 of those files were unchanged with the original time-stamps and contents,
and 7 were approximately halved in size and updated to the disaster timestamp.
and another 44 of brand new *.MOF files were added, again with the disaster timestamp.

Do all these extra *.MOF files in ...\wbem\AutoRecover indicate a major disaster ?
Does the absence of further WinMgmt event 4 errors show complete recovery without failure on the next reboot ?
Does the continued presence of all these *.MOF files show that after recovery Windows was too lazy to delete redundant files ?
Or has it left it all for me to try and recompile or something ?

From http://nukz.net/reference/wmi/hh/wmisdk/logs_6yb7.htm I learnt that along with all these errors,
there should be a new file Mofcomp.log that will show what went wrong and can be used for recompiling,
but first I would have to download "The WMI Software Developer Kit (SDK)" - I like new experiences but that is too much !

There is in fact no Mofcomp.log anywhere.
Does this indicate Windows cleaned up after a full autorecovery on the second attempt,
Or was it a victim of CCleaner purging *.log files in System32\wbem\ ?

I now envisage restoring the Acronis Partition C:\ image created as a precaution before I removed Comodo.

HELP ! ! ! PLEASE ADVISE ME.

1) How does "System32\wbem\AutoRecover\*.MOF" interact with "Failed to load MOF while recovering repository file" ?
2) How can I determine if "autorecovery" has succeeded or otherwise ?
3) Is there anything I can do to avoid a repetition of these errors ?

I would be interested in any simple way to repair Windows without having to put the system back as it was and repeating the removal and the clean install of a later version - but it has to be much simpler than learning to use the Software Developer Kit.

I am using XP Home with SP3 on a 5 year old Acer laptop, Travelmate 244 LM.

Regards
Alan