How to Fix File Explorer Crashes on Business PCs
When File Explorer crashes on a business PC, start by saving work and identifying where the problem occurs. A restart may restore access, but the pattern of the failure helps determine whether to investigate a user account, a folder, or the computer itself.
Repeated crashes can interrupt access to shared files and customer documents. Work through the lower-risk checks first, and involve IT before making changes that require administrator access.
Key Takeaways
- Record whether the crash affects one user, one location, multiple PCs, or every account on one PC.
- Restart File Explorer or Windows after saving work, then test the same task again.
- Ask IT to review shell extensions, recent changes, and Windows system files when basic checks don't help.
- Preserve business files and security settings during troubleshooting. Don't delete profiles or make registry changes as a shortcut.
- Give IT the crash time, affected locations, recent changes, and relevant event details.
Identify Where File Explorer Crashes
Before changing settings, write down what happened immediately before the crash. Note whether the File Explorer window closed, the desktop disappeared and returned, or the window stopped responding. A slow folder and a crash may need different investigations.
Compare users and computers
If possible, have an authorized coworker sign in to the affected PC and try the same task. Then test the affected user's account on another company PC, using the same type of file or location.
If the issue follows one person across PCs, IT has a reason to investigate account-specific resources and settings. If multiple users experience it on one PC, the investigation can focus on that device. A comparison test is a clue, not a diagnosis.
Use company-approved accounts for these tests. Don't share passwords or grant an employee administrator access just to make troubleshooting easier.
Compare folders and network locations
Try a local folder and an authorized shared location separately. Record the folder path and the action that triggers the problem, such as opening the folder or selecting a file.
Also note whether the employee is in the office or connected through a VPN. If several coworkers have trouble with the same shared location, report that pattern to IT rather than making changes on every PC.
Restart File Explorer and the PC
Save open work before restarting anything. If a document is stored in a temporary Windows profile, save it to approved storage outside that session and open the saved copy to make sure it's usable.
Ask IT to restart the File Explorer process, then repeat the action that failed. Record whether the window stays open and whether the same folder or file remains accessible.
If the issue returns, save work again and select Start > Power > Restart . Sign in normally and repeat the same test. Restarting Windows gives you a fresh session, while repeating the original action shows whether the interruption has actually stopped.
A restart that works briefly is useful information, but it isn't a lasting repair. If the crashes continue, move on to the scope checks and share the results with IT.
Test the Affected Folder Without Risking Files
When crashes happen around one folder, avoid deleting or moving its contents to force a result. Business folders may contain shared records, unsynchronized work, or files needed by another application.
Check a local folder separately
Open an unrelated local folder that the employee has permission to use. If that works, return to the original folder and note the exact point at which the failure occurs.
For example, distinguish between a crash when the folder opens and one that happens only after selecting a particular file. Give IT the file name and location, but don't send sensitive files through an unapproved channel.
Compare access to a shared location
If the affected location is on a file server or a synchronized workspace, ask whether authorized coworkers can open the same location. Record whether the problem occurs on-site, over VPN, or in both situations.
Trouble accessing a shared location doesn't establish the cause of a File Explorer crash. It does give IT a narrower place to investigate. Our guide to secure file sharing for small businesses covers access controls for shared business files.
Look for User Profile Problems
A problem limited to one account deserves a closer look at that user's session. Ask whether the employee sees their usual desktop, application settings, and files after signing in.
A temporary-profile warning is a separate sign-in issue. Windows can open a temporary profile when it can't load the normal one, and changes made during that session may disappear at sign-out. Save essential work to approved storage before restarting.
Don't delete anything under the user's profile folder or copy the entire profile into a new account. IT should preserve the original data and investigate the sign-in failure first. Our guide to fixing a Windows temporary profile explains the precautions in more detail.
If storage errors appear alongside profile trouble, tell IT before attempting a profile replacement. A new profile won't address an underlying storage problem.
Have IT Review Shell Extensions and Recent Changes
Shell extensions are components that add functionality to Windows, including features connected to file handling. Give IT a list of applications installed or updated before the problem began, especially those that interact with files.
Review extensions in a controlled test
Ask IT to inventory third-party shell extensions and compare them with the actions that trigger the issue. A controlled test should change one item at a time, followed by the same repeatable folder test.
IT can document what changed and restore the original configuration if the test doesn't help. Employees shouldn't remove unfamiliar components or disable security software based on a guessed cause.
Record other software changes
Include changes to business applications, file synchronization tools, and security software in the timeline. A change that occurred before the first crash is worth recording, but timing alone doesn't prove it caused the failure.
If several PCs began having trouble around the same time, tell IT whether they received the same deployment. That information can help the support team decide which devices to compare.
Review Windows Updates Before Rolling Anything Back
A pending restart or an incomplete update is worth noting before more advanced work. In Windows 11, open Settings > Windows Update . In Windows 10, open Settings > Update & Security > Windows Update .
Record any pending restart or installation message, along with the time the trouble began. On a managed PC, follow your organization's patching process and let IT handle approved updates.
Don't uninstall an update or install an unrelated driver solely because the dates appear close. IT can compare update history across affected and unaffected devices before deciding what to test. This approach is especially useful when several employees report the same interruption.
Ask IT to Check Windows System Files
If the problem continues across accounts or other Windows features also behave unexpectedly, ask IT to assess the computer's system files. This is a more advanced step than restarting the PC or comparing folders.
Windows includes Deployment Image Servicing and Management and System File Checker for image and protected-file repair. IT can run the appropriate tools, review their results, and decide whether further repair is needed. These tasks typically require an elevated administrator session.
Before a major repair, make sure important local business files are protected in company-approved storage. Don't grant permanent administrator rights to an employee for a one-time troubleshooting task. Our guidance on managing admin permissions on business PCs covers that decision.
Avoid registry edits or a Windows reinstall as a first response. Both can make recovery more complicated if the original problem and data locations haven't been documented.
Give IT Useful Evidence for Escalation
A concise incident record can save time and prevent the support team from repeating tests. Send the information through your company's approved support channel, especially if paths or screenshots contain customer names.
Capture the pattern and impact
Include the PC name, affected user's account, approximate crash time, and the task being performed. List the affected folder or network path and whether the same action worked for another user or on another PC.
Describe the business impact as well. IT can prioritize differently when a single optional folder is affected than when several employees can't reach files needed for customer work.
Include logs and changes already tested
IT can review Event Viewer for errors around the reported time. If a temporary-profile warning also appears, Windows Logs > Application and the User Profile Service Operational log can provide relevant sign-in details. Record the event ID and full message rather than relying on the warning alone.
List each restart, comparison test, or approved change already made and its result. Don't disable security protection to gather evidence. If the PC shows storage errors or continues to fail, our business computer repair services can help with the next steps.
Restore Access Without Guesswork
File Explorer crashes are easier to investigate when you preserve the details of each test. Start with a restart, then compare the affected user, PC, and location.
Protect business files before making major changes, and keep advanced repairs with IT. A useful resolution means the employee can repeat the original task and access the files needed for work.