![]() An English post lists a number of event entries that can occur through the Performance Counter service. The /d switch is not even documented in the Microsoft document linked above – but I found descriptions here, here, and here. ![]() The system then omits the performance check of the USB ports.īoth commands did not help in this case. The /d:usbperf option can be used to disable the service specified after the switch (usbperf in this case).The /r option restores the counter registration settings and explanatory text from the current registry settings and cached performance files related to the registry (see also this Microsoft post).The lodctr ommand mentioned above can be run on Windows Server and allows registering or saving performance indicator names and registry settings to a file, as well as setting trusted services. The error occurs very frequently under Windows, as an Internet search revealed ( here is an entry from 2012 on Windows 7), and points to an error in the handling of performance indicators. While the event entries are only a "cosmetic issue", they do flood the log files in question. ![]() Therefore, uninstalling the USB controller did not help either. In the above example, this scenario does not apply either, as VMware was used for virtualization. Provided the VM is hosted under Hyper-V, there is no USB port available by default. A special feature mentioned in the above post is the use of a virtual machine for the Windows Server installation. The administrator had still posted the above screenshot of an entry in the event viewer. reboot WITHOUT successĪnyone have an idea how to get rid of the event "stuffing"? Test installed USB controller, but also no improvement Machines (get-childitem -recurse *.ini | Select-String -pattern "usbperf" -context 0 => also nothing found). On VMware virtual server 2012R2 with error ID 2001 usbperf (The value of "First Counter" under the key "usbperf\Performance" cannot be read. An administrator reported the error for a Windows Server 2012 R2 virtualized with VMware and asked for a workaround. I first came across this Windows error in a German Windows Server Facebook group.
0 Comments
Leave a Reply. |