Topics

1

General Computer Support / WARNING: File c:\program files...does not conatin #PRAGMA AUTORECOVER

« on: May 12, 2016, 10:34:12 pm »

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

2

General Computer Support / Access denied log reports

« on: February 09, 2016, 01:26:43 am »

The last few times Tweaking was run (over the last couple of months) a consistent set of logged 'access denied' errors shows up in the manifest. Checking the logs going back to last April up until ~December 1st of 2015 there were no error logs.

Security Software is Norton Security and Vipre. Malwarebytes is manually run occasionally as are a couple of other AV/AM programs. They have always been on my systems over the years as an additional check on system security.

There are system errors that consistently occur in recent weeks - for example, loss of sound, anchored programs not showing up in the task bar, and programs that will not start. Most of these are fixed when the Tweaking program is run (in safe mode). After a few days the problems start cascading again.

The most likely cause of all of this is...well, no doubt my own fault.  Comes from 40+ years of being around computers.

Suggestions about what needs to be done to correct the problems are most welcome.

-Mike

3

General Computer Support / WMI repository reset failed - Win 7 Ultimate 64

« on: October 21, 2015, 06:35:31 pm »

Shane,

This issue is a recurring one when I run the repair process. The WMI repair log contains about 3400 lines of text with errors similar to the snippet I am posting here - with the exception that there are many different programs with the same #PRAGMA AUTORECOVER error in the entire log. I should add there are about 230 lines of deleted files like this one: C:\Windows\System32\Wbem\AutoRecover\FAAD7D567E76CAB10704AFD7C0488F23.mof

In years past I ran into a somewhat similar error on another computer. What I recall doing is deleting the WBEM folder (backing it up, of course) and rebooting which solved the issue. Perhaps I was just lucky it worked. Your suggestions would be appreciated.

Here is the snippet:
------------------------------------------------------------------------------------------
smi2smir.exe: No command argument specified, or unknown command argument
WMI repository reset failed
Error code:  0x8007007E
Microsoft (R) MOF Compiler Version 6.1.7600.16385
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: c:\as.mof
MOF file has been successfully parsed
Storing data in the repository...
Done!
Microsoft (R) MOF Compiler Version 6.1.7600.16385
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: c:\fw.mof
MOF file has been successfully parsed
Storing data in the repository...
Done!
Microsoft (R) MOF Compiler Version 6.1.7600.16385
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: c:\documents and settings\amadeus\appdata\roaming\kompozer\profiles\nfd6w8b7.default\xul.mfl
c:\documents and settings\amadeus\appdata\roaming\kompozer\profiles\nfd6w8b7.default\xul.mfl (1): error SYNTAX 0X8004400a: Unexpected token at file scope

Compiler returned error 0x8004400aMicrosoft (R) MOF Compiler Version 6.1.7600.16385
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: c:\program files\common files\microsoft shared\officesoftwareprotectionplatform\osppwmi.mof
MOF file has been successfully parsed
Storing data in the repository...
Done!
Microsoft (R) MOF Compiler Version 6.1.7600.16385
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: c:\program files\condusiv technologies\diskeeper\dkdecoupledprovider.mof
MOF file has been successfully parsed
Storing data in the repository...
Done!
Microsoft (R) MOF Compiler Version 6.1.7600.16385
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: c:\program files\intel\wifi\bin\iwmspdel.mof
MOF file has been successfully parsed
Storing data in the repository...
WARNING: File c:\program files\intel\wifi\bin\iwmspdel.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!
-------------------------------------------------------------------------------

Best regards,

-Mike