File Picker UI Host High CPU

To troubleshoot File Picker UI Host high CPU usage, confirm the activity in Task Manager, close the stalled file-selection window, and restart the app that opened it. If it returns, compare local and cloud folders, update Windows and the affected app, then investigate background software.

What File Picker UI Host does

File Picker UI Host is a Windows component involved in displaying file-selection windows for some applications. You may encounter it when opening a document, choosing an attachment or selecting a save location. Microsoft's file picker documentation explains how these windows provide access to local folders and participating storage providers.

Activity while a folder loads is different from sustained CPU use after the window closes. The useful clues are which app opened the picker, which location it was browsing and whether the activity stops when you cancel the operation.

Confirm which process is using the CPU

1. Press Ctrl + Shift + Esc to open Task Manager. Expand its view if necessary, then open Processes.
2. Select the CPU column to bring the busiest processes to the top.
3. Look for File Picker UI Host while the slowdown is occurring. Note its CPU reading and whether another process is also busy.
4. Cancel the file-selection window and watch whether the activity falls.
5. Open the same window again from the same app to check whether the behaviour repeats.

There is no single CPU percentage that proves this component is faulty across every computer. Look for sustained activity associated with a repeatable slowdown. If another process accounts for the load, investigate that process before changing file picker settings.

Recover from a stalled file-selection window

Save work in the affected app wherever possible before forcing anything to close. Ending a task can interrupt file selection or an upload, and closing the app may lose unsaved changes.

1. Try cancelling the file-selection window normally.
2. Close and reopen the app that launched it.
3. If the picker remains stuck and Task Manager still shows it consuming CPU, select File Picker UI Host and choose End task.
4. If the problem continues, save other work and restart Windows using Restart from the power menu.

Ending the task is a recovery step. If the same action triggers the problem again, continue with the checks below. Keep the Windows component installed; deleting its executable can break features that depend on it.

Narrow down the app or storage location

Compare a small local folder with the problem location

Create a small test folder on local storage outside any cloud-synchronised directory. Put a known working file in it, then try selecting that file from the affected app. Next, repeat the operation in the folder that caused the slowdown.

If the local folder works, investigate the original location. For cloud storage, check the provider's sync status and whether the selected file is available locally. For a network share or external drive, check that it is connected and accessible in File Explorer. These comparisons help identify a location-specific problem without deleting files.

If the picker offers a view without thumbnails or previews, test that view too. An improvement is a clue to investigate preview handling or particular file types; it does not prove that a file is corrupt.

Compare applications

Try opening the same local file through another app that supports its format. If only one app triggers the problem, update that app and check its support guidance. If the problem started after installing an add-in or extension, temporarily disable that item and repeat the test.

Change one thing at a time and record the result. If several apps show the same behaviour with local files, broader Windows troubleshooting becomes more useful.

Install updates and check for malware

1. Open Settings, find Windows Update and check for available updates. Restart when required.
2. Update the affected app through Microsoft Store or its developer's update mechanism.
3. If the issue involves a cloud location, update the storage provider's desktop app as well.
4. Run a scan using Windows Security or your installed security software, especially if you notice other suspicious behaviour.

High CPU usage alone is not evidence of malware. Equally, a familiar process name is not enough to establish that a file is trustworthy. Let security software assess suspicious files rather than downloading replacement Windows executables from third-party sites.

Investigate persistent Windows or background-software problems

Repair Windows system files

If the issue affects multiple apps after updates and a restart, check Windows system files. Microsoft's System File Checker instructions specify running DISM before SFC.

1. Search for Command Prompt, right-click it and select Run as administrator.
2. Enter DISM.exe /Online /Cleanup-image /Restorehealth and wait for successful completion.
3. Enter sfc /scannow and let verification finish.
4. Record the result, restart Windows and repeat the original file-selection test.

If either command reports an error, retain the exact message for support. A successful repair still needs a practical retest to establish whether it addressed this problem.

Test for a background software conflict

If the problem persists, a clean boot can help isolate interference from startup apps and non-Microsoft services. Follow Microsoft's clean boot procedure, including its instructions for restoring normal startup.

Record what you disable, select Hide all Microsoft services before disabling third-party services, and leave advanced boot options alone. Restart and repeat the same test. If the symptom disappears, re-enable the disabled items in groups to narrow down the cause. Restore your usual startup configuration when testing is complete.

Prepare useful details if the problem continues

Give the app developer or IT support your Windows version, app version, affected folder type, observed CPU behaviour and exact reproduction steps. Include any repair errors and explain whether a small local folder worked. This evidence is more useful than a general report that the computer feels slow.

If support requests graphics hardware details, the guide to checking a graphics card from Command Prompt covers using dxdiag. For wider hardware investigation, browse the computer hardware guides. If that investigation leads to an upgrade for an older machine, consult the Socket rPGA 989 CPU list alongside the computer manufacturer's compatibility information. Sustained picker activity by itself does not establish a need for a processor upgrade.

Start by reproducing the file-selection problem with Task Manager open, then record whether cancelling the window stops the CPU activity.