This is an issue I've run into almost every time I run Tweaking.com. Computer is an HP i7 4th, 250GB SSD, 1.5TB HD, 3TB external, 16GB mem, Win 8.1 Pro 64, and the kitchen sink!
The 'Repair WMI' log file begins with:
_____________________________________
The Windows Management Instrumentation service is stopping.
The Windows Management Instrumentation service was stopped successfully.
Could Not Find C:\Windows\System32\LogFiles\WMI\RtBackup\*.*
The directory is not empty.
Deleted file - C:\Windows\System32\Wbem\Repository\INDEX.BTR
Deleted file - C:\Windows\System32\Wbem\Repository\MAPPING1.MAP
Deleted file - C:\Windows\System32\Wbem\Repository\MAPPING2.MAP
Deleted file - C:\Windows\System32\Wbem\Repository\MAPPING3.MAP
Deleted file - C:\Windows\System32\Wbem\Repository\OBJECTS.DATA
___________________________________________
And ends with about 340 '.mof' entries.
The next entry following the above is the one that raises the question of whether or not the WMI needs to be restarted or reset:
The system cannot find the file specified.
WMI repository reset failed
Error code: 0x8007007E
The 'Repair WMI' log always contains a long list of errors similar to the following:
________________________________
Microsoft (R) MOF Compiler Version 6.3.9600.16384
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: c:\program files (x86)\windows kits\8.1\include\um\msft_errors.mof
MOF file has been successfully parsed
Storing data in the repository...
WARNING: File c:\program files (x86)\windows kits\8.1\include\um\msft_errors.mof does not contain #PRAGMA AUTORECOVER.
If the WMI repository is rebuilt in the future, the contents of this MOF file will not be included in the new WMI repository.
To include this MOF file when the WMI Repository is automatically reconstructed, place the #PRAGMA AUTORECOVER statement on the first line of the MOF file.
Done!
_________________________________
This applies to the 'c:\program files\' directory as well.
In each instance (about 568 of them) there is a different file reference after the second '\' .
There is one inquiry somewhat similar to this issue from Sept of 2014 involving a laptop but it had to do with missing data from the WBEM sub-directory. Not the issue on this system.
Look forward to your take on this.
-Mike
