How to rebuild performance counters on Windows Vista/Server2008/7/Server2008R2
Windows Vista
Windows Server 2008 Service Pack 1
Windows Server 2008 Service Pack 2
Windows 7
Windows Server 2008 R2
When some or all your counters show up as numbers
or
When your counters do not show up
or
Event Type: Error
Event Source: Perflib
Event ID: 1008 and others
In Windows 2000, Windows XP and Windows Server 2003, if you wanted to rebuild the base O.S. performance counters you had to go thru:
300956 How to manually rebuild Performance Counter Library values
https://support.microsoft.com/?id=300956
or use a tool such as exctrlst.exe to try disabling to see what counter had issues.
Windows 2000 Resource Kit Tool : Extensible Performance Counter List (exctrlst.exe)
https://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=7ff99683-b7ec-4da6-92ab-793193604ba4
In Windows Vista/Server 2008 and higher, a very easy command to get your base O.S. performance counters working:
Click on Start, CMD (evelated as an Administrator)
Type "C: " without the quotation marks and Enter.
Type "CD\windows\system32" without the quotation marks and Enter.
Type "LodCtr.exe /S:Backup_Original.INI" without the quotation marks and Enter.
Note: This let's you backup the performance counters before we rebuild.
Type "LodCtr.exe /R:PerfStringBackup.INI" without the quotation marks and Enter.
Open up Perfmon and check to see if your counters are showing up properly.
P.S. Other commands that you can use with LODCTR.exe
========================================================
C:\>lodctr.exe /?
LODCTR
Updates registry values related to performance counters.
Usage:
LODCTR <INI-FileName>
INI-FileName is the name of the initialization file that contains
the counter name definitions and explain text for an extensible
counter DLL.
LODCTR /S:<Backup-FileName>
save the current perf registry strings and info to <Backup-FileName>
LODCTR /R:<Backup-FileName>
restore the perf registry strings and info using <Backup-FileName>
LODCTR /R
rebuild the perf registry strings and info from scratch based on the cur
rent
registry settings and backup INI files.
LODCTR /T:<Service-Name>
set the performance counter service as trusted.
LODCTR /E:<Service-Name>
enable the performance counter service.
LODCTR /D:<Service-Name>
disable the performance counter service.
LODCTR /Q
LODCTR /Q:<Service-Name>
query the performance counter service information, either query all or s
pecified one.
LODCTR /M:<Counter-Manifest>
install Windows Vista performance counter provider definition XML file
to system repository.
Note: any arguments with spaces in the names must be enclosed within
Double Quotation marks.
========================================================
Comments
Anonymous
July 01, 2010
This too is not working. I get the following: " Error: Unable to restore performance counter setting from backup file PerfString Backup.INI, error code is 1006 " What a horrible product. They should really have a hotfix for this one. Too complex and requires too many files, steps and fallback options for different versions of windows to work when fixed manually. This is very bad.Anonymous
July 29, 2010
After following this procedure, permon tells me that my counters are corrupted, so... ...I restored the backup file.Anonymous
March 02, 2011
thanks good formate to describe the commandsAnonymous
March 28, 2011
Same error code1006 here on Win7 64bit german: Fehler: Die Leistungsindikatoreinstellung konnte nicht aus der Sicherungsdatei C:Windowssystem32PerfStringBackup.INI wiederhergestellt werden. Fehlercode: 1006.Anonymous
April 09, 2011
Running this command by itself was the only way for me to get our corrupt counters working. LODCTR /RAnonymous
April 14, 2011
When I run LodCtr.exe /R:PerfStringBackup.INI I receive the following error: Error: Unable to restore performance counter setting from backup file C:Windows system32PerfStringBackup.INI, error code is 5 Anything else I can try?Anonymous
June 27, 2011
As Mike said, running LODCTR /R fixed the error ThanksAnonymous
August 04, 2011
I received the exact same error code 5 msg. Tried the LODCTR /R to no avail. Any other suggestions before a complete rebuild is in order???Anonymous
February 04, 2012
For those people who received error code 5, try to do all again but run cmd as administrator. Worked here :)Anonymous
February 07, 2012
I got the error 5 issue too (wasn't running cmd with elevated priveliges) pathetic that we had the same issues back on server 2003 and now we have them on 2008. MS really need to sort out perfmon/perflibAnonymous
February 09, 2012
I am having issues on a SBS 2008 server with errors below and have gone through above to repair counters (lodctr /R and lodctr /R:PerfStringBackup.INI) but still seeing errors :(
Source: MSExchangeIS Category: Performance Event ID: 8001 User (If Applicable): N/A Computer: SERVER.domain.local Event Description: Unable to read the index for the first counter of the Performance Registry key. Source: NTDS General Category: Performance Event ID: 1228 User (If Applicable): N/A Computer: SERVER.domain.local Event Description: System Monitor was unable to open Active Directory Domain Services performance counters. An attempt to query the following performance counter registry key failed.
- Anonymous
September 27, 2014
Pingback from Fix Perfstringbackup.ini Errors - Windows XP, Vista, 7 & 8 - Anonymous
February 10, 2015
After running CMD as ADMINISTRATOR this isue was fixed but, since the user account has ADMINISTRATOR priviliges, what`s the deal to right click and run as ADMIN??