Share via

User OOBE Broker process running in background

Anonymous
2020-06-30T08:33:51+00:00

Hey Folks,

   I hope this is in the correct location.

   For the past little while I have noticed that the User OOBE Broker process has been running in the background. My understanding is that OOBE is tied the blue box that asks you set up Windows and guide through various configurations. However, I have been using Windows (10) for sometime now question why this process is continuing to run after I have already installed Windows.

   If the OOBE is in fact linked to the installation setup screen(s), then could someone please guide me as to how call up the aforementioned screen(s) so I can do what is necessary in order to finish this process and close it. It may or may not be relevant but I do have the May 2004 Update installed.

Thank you,

D.

Windows for home | Windows 10 | Licensing and activation

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

10 answers

Sort by: Most helpful
  1. Anonymous
    2020-06-30T08:51:49+00:00

    Hi KingFirebeard, My name is Jeremy, a Windows Independent Adviser. I'll be happy to help you out today. Let’s see what I can do.

    To give you information about OOBE, it means Out Of Box Experience. It's a part of the Windows setup process.

    Please refer to the following methods for a possible fix

    Unplug your external devices.

    Sometimes, your PC’s external devices can be the cause of problems. Try unplugging all your devices, and then plugging them in one at a time.

    If it still running on the background, try these

    1. Press on Windows + Q and type CMD, right-click Command prompt and Run as Admin
    2. When Command Prompt opens, enter " sfc /scannow " and press Enter to run it

    *SFC scan should now start.

    *Keep in mind that this scan can take up to 15 minutes, so don’t interrupt it.

    *Sometimes your Windows installation can become corrupted, causing the problem to exist

    If the problem still persists, or if you were unable to run SFC scan, try using DISM scan instead. To do that, follow these steps:

    1. Open Command Prompt as administrator.
    2. Enter " DISM /Online /Cleanup-Image /RestoreHealth " and press Enter to run it.
    3. DISM scan will now start.

    *This scan can take more than 15 minutes to complete, so don’t interrupt it.

    *Once the DISM scan is finished, check if the problem is resolved.

    Let me know if you'll get any error from the commands given

    Kind regards,

    Jeremy

    50+ people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2020-06-30T10:22:36+00:00

    Jeremy,

       Thank you for taking the time to speak with me.

       As requested I ran both the "sfc/ scannow" and the "DISM cleanup." They returned, "Windows found no integrity violations" and "Windows Resource completed the process successfully," respectively. Unfortunately the OOBE process continues to remain, even after a Reboot.

    20+ people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2020-08-12T15:59:40+00:00

    [SOLVED]

       It seems that the OOBE process is also tied to the creation of User accounts. Taking this knowledge into account I created a second account on my PC [Local account (Standard then elevated it to Administrator)], signed-out, restarted, then logged into the newly created account and viola! .. The process is no longer present.

       Be advised though, you will need to make several adjustments to your new account, in form of tasks and removing any unneeded software, etc... this essentially reinstates Windows as a new PC. Also, under this new account you will no longer be able to have a one-login-to rule-them-all so, no more click and auto sign-ins'.

       Hope this helps others as others in this forum have helped me.

    Thank you,

    D.

    10+ people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2020-08-16T12:24:08+00:00

    That worked for me, sfc /scannow found some issues and was resolved and to be safe I also ran DISM command. Thank you Jeremy.

    10+ people found this answer helpful.
    0 comments No comments
  5. Anonymous
    2020-07-10T15:01:19+00:00

    I'm having the same issue with have user oobe broker running in the background and I can see it in the task manager.  Can we end this process in the task manager or does it need to continue to run in the background? I have done all the stuffKingFirebeard has done.    Also another thing I noticed is that when this oobe is running my onedrive folder shows under common logs filecoauth files what are those.? It creates one every 10 mins.  But my onedrive is disable because I don't use it.  So why is it creating those files then?  When I turn on my computer or restart it does not create those files until oobe broker is running.  I tested this to makesure  it was the oobee doing this I have ended the user oobe broker  in task manager and that stopped filecoauth files to not be created.    So could you please tell me if it is alright to end the oobe in the task manager?  Also what does filecoauth.exe do and why are they creating logs if my onedrive is disabled?

    10+ people found this answer helpful.
    0 comments No comments