Skip to main content
Vrgear1972
Up and Coming
January 2, 2021
Question

OVRLibraryService not running - set to manual via client install, will not run when attempted

So, after a torturous attempt to get my Oculus client reinstalled recently (see my prior post) I'm now facing another problem. The OVRLibraryService is not running. This means my library is not updating.

The default state of this service is that its been installed with a Startup Type of 'Manual'. So will never run on boot. Attempting to run the service manually throws an error dialog..



Checking event viewer, the following is displayed...

The Oculus VR Library Service service terminated with the following service-specific error: 
There are no more files.

The client was installed via my user, who's a local admin.

Does anyone have any ideas?

 

    45 replies

    Show previous replies
    wilsonbradley
    wilsonbradley
    Up and Coming
    April 5, 2025

    Nope... 

    Disabling [Quality Windows Audio Video Experience] does not allow [Oculus VR Library Service] to start.

    Funny, revisited this after years since trying to clean up Event Viewer bad'ies..

    and found my own post from years ago stating that this by default should NOT START and kept on manual. 

     

    Would be AMAZING if this STELLAR Oculus support would chime in and answer this simple question, so their customers don't waste hours and hours of their time trying to resolve.

    Should it be [Running] or NOT Running?

    START or NOT START???

    i7-9700K, 32GB, RTX 4080 Super, Type-c to Type-c - Quest 3 - 512GB Steam & Oculus/Meta User name: WilsonInVR
    MetaStoreHelp
    MetaStoreHelp
    Community Manager
    April 5, 2025

    Hi there,

     

    Thanks for posting into our forum. We see you're having some problems getting the Library Service to run on your PC, we'd like to look into this a little further! Would you mind sending us a DM to collect some details? To do this, please select our name to get to our profile page. Next, click "Send a Message" to privately message us! Please remember, you must be signed into the community first to send us a private message.

     

    Thanks!

    If you're the author of a thread, remember to mark a reply as the Accepted Solution to help others find answers!
    NomadsAnIsland
    Honored Contributor
    April 13, 2025

    The service only runs when itis needed - to check for or install updates. Then it quits. That's why it is set to manual. It's probably called by the Oculus VR runtime service. The library service won't start manually as you aren't giving it the parameter arguments it needs.

    Edit the OVRLibraryService.log in the Oculus directory on the drive you installed the app which will show when it last ran, successfully or not..

    Mine last ran this morning to apply some updates to various apps.

    boskovic234
    Participant
    April 14, 2025

    hi.. which part that we need to edit on OVRLibraryService.log ?

    i have try all the solution that posted on this thread, but still not good result.. 

    NomadsAnIsland
    Honored Contributor
    April 15, 2025

    The log is for information purposes. Check it to see when the service last ran and if it failed some information is given as to why.

    TurnBasedPlayer
    New Participant
    April 18, 2025

    via Event Viewer when trying to start Oculus Lib service manually: The Oculus VR Library Service service terminated with the following service-specific error:
    "There are no more files."

    via Event Viewer when dreaded "Can't reach Link service" error on startup;

    Log Name:      System
    Source:        Microsoft-Windows-DistributedCOM
    Date:          4/18/2025 6:44:04 PM
    Event ID:      10016
    Task Category: None
    Level:         Warning
    Keywords:      Classic
    User:          SYSTEM
    Computer:      Hiro
    Description:
    The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID 
    Windows.SecurityCenter.WscDataProtection
     and APPID 
    Unavailable
     to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
    Event Xml:
      <System>
        <Provider Name="Microsoft-Windows-DistributedCOM" Guid="{1B562E86-B7AA-4131-BADC-B6F3A001407E}" EventSourceName="DCOM" />
        <EventID Qualifiers="0">10016</EventID>
        <Version>0</Version>
        <Level>3</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x8080000000000000</Keywords>
        <TimeCreated SystemTime="2025-04-19T01:44:04.6881061Z" />
        <EventRecordID>51644</EventRecordID>
        <Correlation ActivityID="{3d00a024-f651-4b0c-b812-64950572c051}" />
        <Execution ProcessID="1068" ThreadID="9104" />
        <Channel>System</Channel>
        <Computer>Hiro</Computer>
        <Security UserID="S-1-5-18" />
      </System>
      <EventData>
        <Data Name="param1">application-specific</Data>
        <Data Name="param2">Local</Data>
        <Data Name="param3">Launch</Data>
        <Data Name="param4">Windows.SecurityCenter.WscDataProtection</Data>
        <Data Name="param5">Unavailable</Data>
        <Data Name="param6">NT AUTHORITY</Data>
        <Data Name="param7">SYSTEM</Data>
        <Data Name="param8">S-1-5-18</Data>
        <Data Name="param9">LocalHost (Using LRPC)</Data>
        <Data Name="param10">Unavailable</Data>
        <Data Name="param11">Unavailable</Data>
      </EventData>
    </Event>
     
    Log Name:      System
    Source:        Microsoft-Windows-DistributedCOM
    Date:          4/18/2025 6:44:04 PM
    Event ID:      10016
    Task Category: None
    Level:         Warning
    Keywords:      Classic
    User:          SYSTEM
    Computer:      Hiro
    Description:
    The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID 
    Windows.SecurityCenter.SecurityAppBroker
     and APPID 
    Unavailable
     to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
    Event Xml:
      <System>
        <Provider Name="Microsoft-Windows-DistributedCOM" Guid="{1B562E86-B7AA-4131-BADC-B6F3A001407E}" EventSourceName="DCOM" />
        <EventID Qualifiers="0">10016</EventID>
        <Version>0</Version>
        <Level>3</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x8080000000000000</Keywords>
        <TimeCreated SystemTime="2025-04-19T01:44:04.6881061Z" />
        <EventRecordID>51643</EventRecordID>
        <Correlation ActivityID="{7b2b0bef-2515-4da6-a7e3-59223e5b6d7d}" />
        <Execution ProcessID="1068" ThreadID="2112" />
        <Channel>System</Channel>
        <Computer>Hiro</Computer>
        <Security UserID="S-1-5-18" />
      </System>
      <EventData>
        <Data Name="param1">application-specific</Data>
        <Data Name="param2">Local</Data>
        <Data Name="param3">Launch</Data>
        <Data Name="param4">Windows.SecurityCenter.SecurityAppBroker</Data>
        <Data Name="param5">Unavailable</Data>
        <Data Name="param6">NT AUTHORITY</Data>
        <Data Name="param7">SYSTEM</Data>
        <Data Name="param8">S-1-5-18</Data>
        <Data Name="param9">LocalHost (Using LRPC)</Data>
        <Data Name="param10">Unavailable</Data>
        <Data Name="param11">Unavailable</Data>
      </EventData>
    </Event>
     
    Log Name:      System
    Source:        Microsoft-Windows-DistributedCOM
    Date:          4/18/2025 6:44:04 PM
    Event ID:      10016
    Task Category: None
    Level:         Warning
    Keywords:      Classic
    User:          SYSTEM
    Computer:      Hiro
    Description:
    The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID 
    Windows.SecurityCenter.WscBrokerManager
     and APPID 
    Unavailable
     to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
    Event Xml:
      <System>
        <Provider Name="Microsoft-Windows-DistributedCOM" Guid="{1B562E86-B7AA-4131-BADC-B6F3A001407E}" EventSourceName="DCOM" />
        <EventID Qualifiers="0">10016</EventID>
        <Version>0</Version>
        <Level>3</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x8080000000000000</Keywords>
        <TimeCreated SystemTime="2025-04-19T01:44:04.6871092Z" />
        <EventRecordID>51642</EventRecordID>
        <Correlation ActivityID="{e726b70e-a57d-4c93-b0bc-600e1cc00703}" />
        <Execution ProcessID="1068" ThreadID="9052" />
        <Channel>System</Channel>
        <Computer>Hiro</Computer>
        <Security UserID="S-1-5-18" />
      </System>
      <EventData>
        <Data Name="param1">application-specific</Data>
        <Data Name="param2">Local</Data>
        <Data Name="param3">Launch</Data>
        <Data Name="param4">Windows.SecurityCenter.WscBrokerManager</Data>
        <Data Name="param5">Unavailable</Data>
        <Data Name="param6">NT AUTHORITY</Data>
        <Data Name="param7">SYSTEM</Data>
        <Data Name="param8">S-1-5-18</Data>
        <Data Name="param9">LocalHost (Using LRPC)</Data>
        <Data Name="param10">Unavailable</Data>
        <Data Name="param11">Unavailable</Data>
      </EventData>
    </Event>
     
    Log Name:      System
    Source:        Service Control Manager
    Date:          4/18/2025 6:44:04 PM
    Event ID:      7023
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      Hiro
    Description:
    The System Guard Runtime Monitor Broker service terminated with the following error: 
    %%3489660935
    Event Xml:
      <System>
        <Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />
        <EventID Qualifiers="49152">7023</EventID>
        <Version>0</Version>
        <Level>2</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x8080000000000000</Keywords>
        <TimeCreated SystemTime="2025-04-19T01:44:04.5305269Z" />
        <EventRecordID>51641</EventRecordID>
        <Correlation />
        <Execution ProcessID="800" ThreadID="7132" />
        <Channel>System</Channel>
        <Computer>Hiro</Computer>
        <Security />
      </System>
      <EventData>
        <Data Name="param1">System Guard Runtime Monitor Broker</Data>
        <Data Name="param2">%%3489660935</Data>
        <Binary>5300670072006D00420072006F006B00650072000000</Binary>
      </EventData>
    </Event>
     
    Log Name:      System
    Source:        Microsoft-Windows-DistributedCOM
    Date:          4/18/2025 6:43:25 PM
    Event ID:      10016
    Task Category: None
    Level:         Warning
    Keywords:      Classic
    User:          Hiro\Gene
    Computer:      Hiro
    Description:
    The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
    {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}
     and APPID 
    {15C20B67-12E7-4BB6-92BB-7AFF07997402}
     to the user Hiro\Gene SID (S-1-5-21-2340526930-274187173-1898877000-1000) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
    Event Xml:
      <System>
        <Provider Name="Microsoft-Windows-DistributedCOM" Guid="{1B562E86-B7AA-4131-BADC-B6F3A001407E}" EventSourceName="DCOM" />
        <EventID Qualifiers="0">10016</EventID>
        <Version>0</Version>
        <Level>3</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x8080000000000000</Keywords>
        <TimeCreated SystemTime="2025-04-19T01:43:25.0780337Z" />
        <EventRecordID>51640</EventRecordID>
        <Correlation ActivityID="{29dfdd4b-54e5-4ba0-a355-cce364ca55e6}" />
        <Execution ProcessID="1068" ThreadID="9052" />
        <Channel>System</Channel>
        <Computer>Hiro</Computer>
        <Security UserID="S-1-5-21-2340526930-274187173-1898877000-1000" />
      </System>
      <EventData>
        <Data Name="param1">application-specific</Data>
        <Data Name="param2">Local</Data>
        <Data Name="param3">Activation</Data>
        <Data Name="param4">{2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}</Data>
        <Data Name="param5">{15C20B67-12E7-4BB6-92BB-7AFF07997402}</Data>
        <Data Name="param6">Hiro</Data>
        <Data Name="param7">Gene</Data>
        <Data Name="param8">S-1-5-21-2340526930-274187173-1898877000-1000</Data>
        <Data Name="param9">LocalHost (Using LRPC)</Data>
        <Data Name="param10">Unavailable</Data>
        <Data Name="param11">Unavailable</Data>
      </EventData>
    </Event>
    NomadsAnIsland
    Honored Contributor
    April 24, 2025

    Manually starting the Library service will always fail. It needs parameters/arguments to run which are not supplied when you start it manually.

    From my OVRLibraryService.log (located in the Oculus directory where the app is installed) when I try to start it manually:

    [Debug] [4/13/2025 12:31:25 PM] Starting up OVRLibraryService v1.16.0.0.
[Debug] [4/13/2025 12:31:25 PM] Starting up.
[Debug] [4/13/2025 12:31:25 PM] OVRLibraryService was invoked with no arguments. Exiting.

    Here is an entry that completed with updates:

    [Debug] [4/23/2025 7:28:36 PM] Starting up OVRLibraryService v1.16.0.0.
[Debug] [4/23/2025 7:28:36 PM] Starting up.
[Debug] [4/23/2025 7:28:36 PM] IPC connection opened.
[Debug] [4/23/2025 7:28:36 PM] IPC thread running; waiting for Oaf to connect.
[Debug] [4/23/2025 7:28:36 PM] IPC connection established!
[Debug] [4/23/2025 7:28:36 PM] App libraries for this user: [CORE_DATA]
[Debug] [4/23/2025 7:28:36 PM] OVRLibraryService starting in service mode.  Arguments: [core-upgrade-chunked-finish-ui, oculus-remote-desktop]
[Debug] [4/23/2025 7:28:36 PM] core-upgrade precommand:  stopping Runtime service.
[Debug] [4/23/2025 7:28:36 PM] Waiting for service 'OVRService' to stop.
[Debug] [4/23/2025 7:28:39 PM] Service 'OVRService' is now Stopped.
[Debug] [4/23/2025 7:28:39 PM] Creating NTFS transaction.
[Debug] [4/23/2025 7:28:40 PM] Found existing manifest for 'oculus-remote-desktop' version code 1741060548
[Debug] [4/23/2025 7:28:40 PM] Reusing existing staging directory
[Debug] [4/23/2025 7:28:40 PM] Checking stale files
[Debug] [4/23/2025 7:28:40 PM] Done checking stale files
[Debug] [4/23/2025 7:28:40 PM] Computing hash map
[Debug] [4/23/2025 7:28:40 PM] Number of chunks that need to be downloaded: 0.
[Debug] [4/23/2025 7:28:40 PM] Hot-swapping 'oculus-remote-desktop'. 
[Debug] [4/23/2025 7:28:40 PM] Deleting directory 'D:\Oculus\Staging\oculus-remote-desktop'.
[Debug] [4/23/2025 7:28:40 PM] Deleting directory 'D:\Oculus\tmp'.
[Debug] [4/23/2025 7:28:40 PM] Deleting directory 'D:\Oculus\tmp\7c9e2278-0517-4130-9301-1a7685f92f12'.
[Debug] [4/23/2025 7:28:40 PM] Deleting directory 'D:\Oculus\swap'.
[Debug] [4/23/2025 7:28:40 PM] Deleting directory 'D:\Oculus\swap\oculus-librarian-1eaa146d-f2f4-4f85-bee3-7f74b2bf219b'.
[Debug] [4/23/2025 7:28:40 PM] Deleting directory 'D:\Oculus\swap\oculus-remote-desktop-e2c8a7dc-6a98-4739-aa10-4fb1ede4242a'.
[Debug] [4/23/2025 7:28:40 PM] Committing changes.
[Debug] [4/23/2025 7:28:40 PM] core-upgrade postcommand:  resuming Runtime service.
[Debug] [4/23/2025 7:28:40 PM] Attempting to start service 'OVRService'.
[Debug] [4/23/2025 7:28:40 PM] Service 'OVRService' is now Running.
[Debug] [4/23/2025 7:28:40 PM] IPC connection destroyed.
[Debug] [4/23/2025 7:28:40 PM] Exiting with code 0 (Success).

     Here's the log when there are no updates pending:

    [Debug] [4/24/2025 2:27:00 AM] Starting up OVRLibraryService v1.16.0.0.
[Debug] [4/24/2025 2:27:00 AM] Starting up.
[Warning] [4/24/2025 2:27:00 AM] IPC connection attempt failed!
[Debug] [4/24/2025 2:27:00 AM] IPC thread running; waiting for Oaf to connect.
[Debug] [4/24/2025 2:27:00 AM] App libraries for this user: [CORE_DATA]
[Debug] [4/24/2025 2:27:00 AM] OVRLibraryService starting in service mode.  Arguments: [restart-service]
[Debug] [4/24/2025 2:27:00 AM] Creating NTFS transaction.
[Debug] [4/24/2025 2:27:00 AM] Attempting to start service 'OVRService'.
[Debug] [4/24/2025 2:27:00 AM] Service 'OVRService' is now Running.
[Debug] [4/24/2025 2:27:00 AM] Committing changes.
[Debug] [4/24/2025 2:27:00 AM] Exiting with code 0 (Success).

    ( 

      TurnBasedPlayer
      New Participant
      April 25, 2025

      Confirmed there's need to mess with services.

      And probably not the answer you want to hear, but I had to restore Windows (user settings preserved) in order to get past the dreaded sync error.

      Khngo
      New Participant
      July 19, 2025

      I also can't start the OVR Librori Service (failed to start the OVR Librori Service on the local computer. Details are contained in the system crash log. If this service is not developed by Microsoft, contact the developer of the services and report the error code 18 specific to this service.) I tried a lot of things and reinstalled the Meta Quest driver update, and reinstalled the NVIDIA drivers, it doesn't help.Please fix this error as soon as possible.

      MetaStoreHelp
      MetaStoreHelp
      Community Manager
      July 21, 2025

      Hi there!

       

      Thank you so much for reaching out to us about the issue you're experiencing. We understand how frustrating it is when technology gets in the way of your VR adventures, and we’re here to help.

       

      To troubleshoot this further, please try installing the desktop app using a different user account on the same PC. If that’s not possible, or if the issue persists, feel free to try using a different PC. These steps will help us determine whether the problem is system-wide or account-specific, which will bring us closer to finding a solution. 

       

      If the issue persists, don't hesitate to reach out to us via a private message so that we may continue to look into it for you. 

      To send us a DM, please select our name to get to our profile page, or click here: https://metaque.st/CommunitySupport. Next, click "Send a Message" to privately message us! Please remember, you must be signed into the community first to send us a private message.

       

      From there, we can look into this further. Thank you!

      If you're the author of a thread, remember to mark a reply as the Accepted Solution to help others find answers!
      Terms & ConditionsAccessibility statement