0 Replies Latest reply on Oct 8, 2019 9:11 AM by Parsonm

    Access to performance data was denied

    Parsonm Lurker

      In the Event Viewer/Error section I am seeing on a regular basis the following Perflib error:-

       

      Log Name: Application

      Source: Microsoft-Windows-Perflib

      Date: 08/10/2019 15:18:48

      Event ID:      1000

      Task Category: None

      Level:         Error

      Keywords:     

      User:          SYSTEM

      Computer: Home-PC

      Description:

      Access to performance data was denied to user "SYSTEM" (value from GetUserName() for the running thread) as attempted from module "C:\Program Files (x86)\VMware\VMware Player\vmware-authd.exe" (value from GetModuleFileName() for the binary that issued the query).

      Event Xml:

      <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

        <System>

          <Provider Name="Microsoft-Windows-Perflib" Guid="{13b197bd-7cee-4b4e-8dd0-59314ce374ce}" />

      <EventID>1000</EventID>

      <Version>1</Version>

      <Level>2</Level>

          <Task>0</Task>

      <Opcode>0</Opcode>

      <Keywords>0x8000000000000000</Keywords>

          <TimeCreated SystemTime="2019-10-08T14:18:48.160694000Z" />

      <EventRecordID>4744</EventRecordID>

          <Correlation />

          <Execution ProcessID="2764" ThreadID="3712" />

      <Channel>Application</Channel>

      <Computer>Home-PC</Computer>

          <Security UserID="S-1-5-18" />

        </System>

        <EventData>

          <Data Name="User">SYSTEM</Data>

          <Data Name="Module">C:\Program Files (x86)\VMware\VMware Player\vmware-authd.exe</Data>

        </EventData>

       

      System information.

       

      Windows 10 1903 build 18362.388

      VMWare Workstation 15.5 Player

       

      It started occurring in the first build of 1903 when I was running Workstation 15 and after a number of Windows 10 updates and updating Workstation to 15.5, I am still seeing it.

      As far as I can make out, SYSTEM is not permitted access to the relevant file. Is anybody else seeing it and any clues as to how it can be dealt with?

       

      Thanks