I see a lot of customer servers sporting PerfLib #2003 messages in their event logs:
What happens here seems to be updates (or reloads, or phase-changes of the moon) cause the following message:
The solution to this is to set the library to trusted using the lodctr.exe command. However, you’ll need to do this for the 32- and 64-bit subsystems as applicable:
c:\windows\system32\lodctr.exe /t:MSSQL$SBSMONITORING c:\windows\syswow64\lodctr.exe /t:MSSQL$SBSMONITORING
Unfortunately, I can’t tell you how the 32- and 64-bit performance counter libraries work together, but I have noticed that for certain counter libraries, you need to set it as trusted using both 32/64-but versions of LODCTR.