Screen Startup Looping And File Browser issue

Caleby101

Member
Joined
Jan 22, 2026
Messages
8
SO, I have a ~mild problem and it goes as follows, I start my laptop and I make it to the desktop without issue THEN screen keeps resetting (not sure if that's the best description, took a look at task manager and the startup functions keep skyrocketing CPU usage to 100% :/ ) regardless I can open any of my desktop icons and the issue promptly leaves, cool BUT NO when I open up my file browser I then lose any control I had and cannot do anything else and must restart, ( ill add that it seems to be exclusive to the home tab as I can open folders from desktop but when trying to open the home tab, system kaput)

I have downloaded system updates (nothing for drivers), made some space storage wise, restarted, watched task manager with fear and bumbled around settings with microsoft defender.

Any help?
 

Solution
Got it — SearchHost.exe (“Search Host”) being the biggest consistent CPU user is a strong clue. It’s part of Windows Search (indexing + Start menu/File Explorer search + the “Home/Recent” stuff File Explorer shows). If Search gets stuck or its database is corrupt, it can cause exactly what you’re seeing: File Explorer “Home” tries to load Recents → Search spins → Explorer becomes unresponsive.
Here’s how to confirm and fix it, in the most direct order.

1) Make sure “SearchHost.exe” is the real Windows one (quick safety check)​

  • Open Task Manager → right-click SearchHost.exeOpen file location
  • It should be under something like:
  • C:\Windows\SystemApps...
  • or...
Hi Caleby101 — your description strongly points to Windows Explorer (explorer.exe) getting stuck/restarting, and it’s very likely tied to the File Explorer “Home/Quick access” page (recent files, pinned items, OneDrive “recent”, or a bad shell extension). The “CPU shoots to 100% until you open an icon” also fits an Explorer/startup loop that settles once something breaks the cycle.
Below is the fastest set of fixes that usually resolves “File Explorer Home tab freezes the system”.

1) First: identify what is actually hitting 100% CPU​

When it starts “resetting”:
  1. Press Ctrl + Shift + Esc (Task Manager)
  2. Click Processes → click the CPU column to sort
  3. Tell me the top 1–3 processes pegging CPU (exact names), e.g.:
    • Windows Explorer
    • Antimalware Service Executable
    • Desktop Window Manager
    • Windows Search Indexer
    • OneDrive
    • something else
This matters because the fix changes depending on what is spiking.

2) Unstick your PC when it “locks up” (so you don’t have to hard reboot)​

When File Explorer “Home” freezes:
  1. Press Ctrl + Shift + Esc (Task Manager)
  2. Find Windows Explorer
  3. Right-click → Restart
If Explorer isn’t visible:
  • File → Run new task
  • Type: explorer.exe and press Enter

3) Fix the “Home tab” freeze (Quick Access/Home cache reset)​

A) Change File Explorer to open “This PC” (quick workaround)​

  1. Press Win + R
  2. Run: control folders
  3. In General tab:
    • Open File Explorer to: set to This PC
  4. Under Privacy, uncheck:
    • Show recently used files
    • Show frequently used folders
  5. Click Clear
  6. Apply / OK, then reboot
This alone often stops the Home tab from killing Explorer.

B) Hard reset Quick Access / Home history (more complete fix)​

  1. Press Win + R
  2. Run this folder:
    • %AppData%\Microsoft\Windows\Recent\AutomaticDestinations
  3. Delete everything inside that folder (these are “Recent/Quick Access” databases)
  4. Also go to:
    • %AppData%\Microsoft\Windows\Recent\CustomDestinations
  5. Delete everything inside
  6. Reboot
(If Windows won’t let you delete a file, restart Explorer from Task Manager and try again, or boot Safe Mode.

4) Repair system files (good idea if Explorer is crashing/looping)​

  1. Right-click StartTerminal (Admin) / Command Prompt (Admin)
  2. Run these in order:
Code:
DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow
chkdsk C: /scan
Reboot when finished.

5) If it still happens: isolate startup / shell extensions​

This is common if something hooks into Explorer (context menu tools, cloud storage, zip tools, etc..

A) Clean boot (safe test)​

  1. Win + Rmsconfig
  2. Services tab → check Hide all Microsoft services → click Disable all
  3. Startup tab → open Task Manager → disable all startup items
  4. Reboot and test File Explorer Home
If it’s fixed, re-enable items in batches to find the culprit.

B) Quick “new user profile” test​

A corrupted profile can cause Home/Recent issues.
  • Create a new local user and test File Explorer there. If the new user is fine, the issue is likely profile/cache related.

Questions (so I can narrow it down quickly)​

  1. What Windows version are you on (Windows 10/11, and if you can: Settings → System → About)?
  2. In Task Manager during the spike, which process name is at the top?
  3. Do you use OneDrive (and is it signed in/syncing)?
  4. Have you installed anything recently that integrates with Explorer (7-Zip, WinRAR, Dropbox, Google Drive, antivirus, mod tools, etc.?
Reply with the top CPU process name(s) and your Windows version, and I’ll tailor the next steps to the most likely cause.
 

the biggest CPU consumer is "search host" at 22% followed by Windows explorer at 25%
outside of that there is a huge list of 1-5% stuff
 

Got it — SearchHost.exe (“Search Host”) being the biggest consistent CPU user is a strong clue. It’s part of Windows Search (indexing + Start menu/File Explorer search + the “Home/Recent” stuff File Explorer shows). If Search gets stuck or its database is corrupt, it can cause exactly what you’re seeing: File Explorer “Home” tries to load Recents → Search spins → Explorer becomes unresponsive.
Here’s how to confirm and fix it, in the most direct order.

1) Make sure “SearchHost.exe” is the real Windows one (quick safety check)​

  • Open Task Manager → right-click SearchHost.exeOpen file location
  • It should be under something like:
  • C:\Windows\SystemApps...
  • or C:\Windows\SystemApps\MicrosoftWindows.Client.CBS...
If it’s anywhere else (Downloads, AppData, weird folder), tell me immediately.

2) Quick test: temporarily stop Windows Search (to prove it’s the culprit)​

This is just a test (search will be worse while it’s off).
  • Press Win + R → type services.msc → Enter
  • Find Windows Search
  • Right-click → Stop
  • Now try opening File Explorer → Home

Result interpretation​

  • If Home no longer locks you up: Windows Search/index is the problem → proceed to step 3/4.
  • If it still locks up even with Windows Search stopped: then it’s more likely Quick Access history, a bad pinned item, OneDrive Recents, or a shell extension (we’ll pivot).

3) Rebuild the search index (most common fix)​

  • Press Win + R → paste:
  • control.exe srchadmin.dll
  • Indexing OptionsAdvanced
  • Click Rebuild
Then reboot and test.
(Rebuilding can make the laptop run “busy” for a while afterward, but it should settle.

4) Clear File Explorer “Home/Quick access” history (often fixes the Home-tab freeze)​

Even if Search is involved, clearing these databases helps a lot:
  • Press Win + R → open:
  • %AppData%\Microsoft\Windows\Recent\AutomaticDestinations
  • Delete everything inside
  • Also open:
  • %AppData%\Microsoft\Windows\Recent\CustomDestinations
  • Delete everything inside
  • Reboot
Then also:
  • File Explorer Options (control folders) → set Open File Explorer to: This PC
  • Uncheck Show recently used files + Show frequently used folders
  • Click Clear

5) I need one key detail from you​

When the PC is “resetting” and CPU hits 100%, can you tell me:
1) Does SearchHost.exe jump higher than 22% (like 50–90%) when you click File Explorer → Home?
2) What Windows version are you on (Windows 10 or 11)?
If you can, also list the top 5 CPU entries (just the names + %), while it’s actually at/near 100%. That will tell us if another process (like Antimalware Service Executable, OneDrive, DWM, etc. is joining in and making it feel like a total lockup.
 

Solution
I cant actualy check file location as when opening the side menu the option is grayed out and unavailible
 

That’s actually normal in a lot of cases: Task Manager can gray out “Open file location” for some protected / UWP-style system processes, and SearchHost.exe often behaves that way. So we can verify it another way.

Option A (best): get the exact path via an elevated PowerShell command​

  1. Press Win + XWindows Terminal (Admin) (or PowerShell (Admin)
  2. Run:
Code:
Get-CimInstance Win32_Process -Filter "Name='SearchHost.exe'" | Select-Object Name,ExecutablePath,CommandLine | Format-List
  • If it shows an ExecutablePath under C:\Windows\SystemApps\..., that’s the legitimate Windows Search host.
  • If it shows something like C:\Users\...\AppData\... or a random folder, tell me what it is.

Option B: try from Task Manager “Details” tab​

  1. Open Task Manager
  2. Go to Details tab
  3. Find SearchHost.exe
  4. Right-click → Open file location (sometimes it’s enabled here even if it’s grayed out in Processes)

Option C: use Resource Monitor to jump to the file​

  1. Press Win + R → type resmon → Enter
  2. CPU tab → under Processes, locate SearchHost.exe
  3. Check if it lets you right-click/open properties (varies, but sometimes works)

While we’re here: quick “is Search causing the Explorer Home freeze?” test​

Even if we can’t check the file path yet, this test is very telling:
  1. Win + Rservices.msc
  2. Find Windows Search
  3. Right-click → Stop
  4. Immediately try File Explorer → Home
Does Home still hard-freeze the system when Windows Search is stopped?
  • No freeze: we’ll focus on rebuilding the index / resetting Search components.
  • Still freezes: we’ll focus on Quick Access/Home history corruption or a shell extension.

Two quick questions​

  1. Are you on Windows 10 or Windows 11?
  2. When you stop Windows Search (steps above), does File Explorer → Home still lock everything up?
Answer those and I’ll give you the exact next steps based on the result.
 

Ill also add that all of these functions are only present for 1 or 2 task manager ticks before dissaearing even from search
 

That behavior (processes appearing for 1–2 “ticks” then vanishing) usually means something is repeatedly crashing/restarting (very often Explorer and/or Windows Search components) or Task Manager is simply refreshing too slowly to catch it.

1) Make Task Manager “catch” the culprit​

  1. Open Task Manager
  2. Click View → Update speed → High
  3. Then click View → Update speed → Paused right when the spike/freeze starts
  4. Go to Details tab and click the CPU column to sort
This often lets you see the process that’s flashing in and out.

2) Quick confirmation test: disable Windows Search temporarily​

Since you already saw Search Host involved, this is the fastest “yes/no” test:
  1. Win + R → services.msc
  2. Find Windows Search
  3. Right-click → Stop
  4. Try opening File Explorer → Home
  • If the system stops freezing, the problem is almost certainly Windows Search index / Home/Recents related.
  • If it still freezes, it’s more likely Quick Access/Home history corruption, OneDrive integration, or a shell extension.

3) If stopping Windows Search helps: rebuild + clear Home/Recents​

Do both:
A) Rebuild the index
  • Win + R → control.exe srchadmin.dllAdvancedRebuild
B) Clear Quick Access/Home databases
  • Win + R → %AppData%\Microsoft\Windows\Recent\AutomaticDestinations → delete contents
  • Win + R → %AppData%\Microsoft\Windows\Recent\CustomDestinations → delete contents
  • Reboot

4) If you want a more reliable “what keeps restarting” view​

Open Event Viewer:
  1. Win + R → eventvwr.msc
  2. Go to Windows Logs → Application
  3. On the right, click Filter Current Log…
  4. Check Error and Critical
  5. Look for entries mentioning SearchHost.exe, explorer.exe, ShellExperienceHost, or Windows Search
If you tell me the exact error names you see there, I can point to the precise fix.

Two questions (so I can stop guessing)​

1) Are you on Windows 10 or Windows 11?
2) After you Stop the Windows Search service, does File Explorer → Home still lock up, or does it behave?
 

Alright, I am using windows 11, stopping windows search does nothing, Ive rebuilt the index and nothing and cleared the Destination folders and nothing
 

Thanks — since stopping Windows Search, rebuilding the index, and clearing Automatic/CustomDestinations didn’t change anything, the next most likely causes are:
  • a third‑party Explorer shell extension (context menu / preview / cloud sync / archive tool) crashing Explorer, or
  • Explorer “Home” trying to enumerate something that’s broken/unreachable (OneDrive “Recent”, a disconnected network/mapped drive, etc., or
  • broader Explorer/system corruption (less common, but we’ll check).
Here’s the clean next path.

1) Turn off the “Home/Recents” features that commonly trigger the hang​

  1. Press Win + R → type: control folders → Enter
  2. General tab:
    • Open File Explorer to: set This PC
  3. In the Privacy section:
    • Uncheck Show recently used files
    • Uncheck Show frequently used folders
    • Click Clear
If you see an option like “Show files from Office.com” (some Win11 builds have it), turn it off as well—Home heavily depends on cloud/recents.
This is mainly to keep you functional while we isolate the root cause.

2) Rule out “unreachable locations” (OneDrive / mapped drives / external drives)​

Explorer Home can hang while it tries to query “recent” items stored in cloud paths or disconnected locations.
Please do this test:
  1. Pause/quit OneDrive (system tray cloud icon → Pause syncing / Quit)
  2. Disconnect any external USB drives
  3. If you have mapped network drives: open Command Prompt and run:
    net use
    If you see mapped drives you don’t need, temporarily disconnect them (you can reconnect later).
Then try opening File Explorer → Home again. (This “disconnect drives” test is a standard way to diagnose Explorer hangs.

3) The big one: test for a bad shell extension (most common persistent cause)​

When a shell extension misbehaves, it runs inside Explorer and can freeze/crash the whole shell.

What to do​

  • Use ShellExView (NirSoft):
    1. Run it as Administrator
    2. Options → Hide all Microsoft extensions
    3. Disable non‑Microsoft extensions in batches (start with Context Menu, Preview, Thumbnail handlers)
    4. Restart Explorer and test Home
This method is specifically recommended for repeatable Explorer crashes/hangs because it’s reversible and isolates the offending add-on quickly.
Fast way to restart Explorer without rebooting:
  1. Ctrl+Shift+Esc → Task Manager → right‑click Windows ExplorerRestart
    (or if needed)
  2. Task Manager → Run new taskexplorer.exe

4) Safe Mode / new user test (tells us instantly if it’s “system” vs “your profile/add-ons”)​

  • Safe Mode test: If Home works in Safe Mode, it’s almost certainly a third‑party extension/startup item.
  • New local user test: If a new account works, your user profile’s Explorer/Home data is likely corrupted.

5) If it still freezes even in Safe Mode: check system integrity + disk​

Run these (Terminal / Command Prompt Admin):
Code:
DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow
If Event Viewer shows disk/I/O errors, run a full disk check next (this matters because disk errors can corrupt Explorer-related caches/components).

Two quick questions (so I can direct you precisely)​

1) Do you use OneDrive (signed in and syncing), and does pausing it change anything?
2) When Home “kills it”, is it a freeze (Explorer “Not Responding”) or do you actually see Explorer restart/flicker like it crashed?
If you can answer those + tell me 2–3 apps you’ve installed that integrate with Explorer (zip tools, cloud drives, antivirus, media/codec packs), I can tell you which shell extensions to disable first.
 

1 I dont use OneDrive, I never set it up and 2 I can see explorer restarting repeatedly along with resetting my whole screen
 

Thanks — Explorer restarting repeatedly + the whole screen/taskbar resetting means explorer.exe is crashing and relaunching (the desktop is Explorer). Since it’s reliably triggered by File Explorer → Home, and you’ve already ruled out Search and cleared the Destinations caches, the next most common root cause is a buggy third‑party shell extension / preview / thumbnail handler that gets invoked when Home tries to render “Recent/Recommended” items. This is a classic pattern because shell extensions run inside Explorer, so when they misbehave they take the whole shell down.
Below is the quickest path to prove/fix it.

1) Stabilize Explorer (so you can work)​

Even before we find the culprit, make Explorer stop opening Home by default:
  1. Press Win + R → type control folders → Enter
  2. Set Open File Explorer to: This PC
  3. Uncheck:
    • Show recently used files
    • Show frequently used folders
  4. Click Apply / OK
(You’ve already cleared Destinations, but this prevents Home from being hit automatically.

2) Disable Preview + Thumbnails (common crash triggers)​

Preview/thumbnail handlers are frequent offenders (especially with media/PDF/codecs) and can crash Explorer just by showing a list.
  1. Open any folder (one that doesn’t crash)
  2. In File Explorer: View → Show
    • turn Preview pane OFF
    • turn Details pane OFF
  3. Press Win + Rcontrol foldersView tab:
    • check Always show icons, never thumbnails
    • Apply / OK
Now try clicking Home again and see if the restart loop stops.

3) Safe Mode test (fastest “is it Windows or something you installed?” test)​

If Explorer behaves in Safe Mode, it’s almost certainly a third‑party add-on/extension/startup item.
How:
Settings → SystemRecoveryAdvanced startup → Restart now →
Troubleshoot → Advanced options → Startup Settings → Restart → choose Safe Mode
Then test: open File Explorer and click Home.
  • If Safe Mode fixes it: go to step 4 (shell extensions) — that’s the most likely win.
  • If Safe Mode still crashes: we’ll look harder at system file corruption/GPU driver.

4) Find the crashing shell extension (most likely fix)​

Use ShellExView and temporarily disable non‑Microsoft extensions in batches (especially Context Menu, Preview, Thumbnail handlers). This is the standard method to stop repeat Explorer crashes caused by add-ons.
Process (safe + reversible):
  1. Run ShellExView as admin
  2. Options → Hide all Microsoft extensions
  3. Disable a batch of non‑Microsoft items (start with Preview/Thumbnail/Context Menu types)
  4. Restart Explorer (Task Manager → Windows Explorer → Restart)
  5. Test Home
  6. When it stops crashing, re-enable half to narrow down the exact offender (“binary search” method).
Once you identify the extension, the real fix is usually: update or uninstall the associated application.

5) Get the exact crash module (so we can pinpoint it)​

If you can, grab the error:
  1. Win + Reventvwr.msc
  2. Windows Logs → Application
  3. Look for Error entries around the time of the crash (often “Application Error” for explorer.exe)
  4. Copy/paste the details (especially “Faulting module name”)
That DLL name usually tells us immediately which app is doing it.

Quick questions​

1) Does Safe Mode stop the Home-tab crash loop? (Yes/No)
2) Have you installed any of these recently: 7‑Zip/WinRAR, codec packs, PDF tools, RGB/peripheral software, GPU utilities, etc.?
Answer those and I’ll tell you exactly what to disable first (and what the likely culprit is).
 

so, safe mode fixes the problem, I dont think so, I checked the crash logs but there is no DLL or module
 

Perfect — Safe Mode fixing it is the key result. That means Windows itself is basically OK, and in normal mode something “extra” is crashing Explorer (most commonly a 3rd‑party shell extension that loads inside explorer.exe, or a non‑Microsoft startup/service).
Here’s the fastest way to nail down which one.

Step 1 (fast isolation): do a Clean Boot​

This disables non‑Microsoft services + startup items (but keeps you in normal Windows).
  1. Win + Rmsconfig
  2. Services tab → check Hide all Microsoft services
  3. Click Disable all
  4. Go to Startup tab → Open Task Manager → disable everything listed there
  5. Reboot normally and test File Explorer → Home

If it’s fixed in clean boot:​

Re-enable items in batches until the crash returns (this quickly finds the offender).

Step 2 (most likely fix): disable non‑Microsoft Explorer extensions (ShellExView)​

Because your trigger is specifically “Explorer/Home”, I’d prioritize shell extensions. A bad one can crash/restart the whole desktop exactly like you’re seeing.
  1. Download ShellExView (NirSoft) and Run as administrator
  2. Options → Hide all Microsoft extensions
  3. Sort by Type and focus first on:
    • Context Menu
    • Preview Handler
    • Thumbnail
    • Property Sheet
  4. Disable all non‑Microsoft items of those types (or do half at a time)
  5. Restart Explorer (Task Manager → Windows Explorer → Restart)
  6. Test Home
If it stops crashing, re-enable half to narrow down the single extension (“binary search” method).
Common culprits even if you “didn’t install anything”:
  • OEM utilities (audio enhancements, “control center”, touchpad tools)
  • ZIP tools (7‑Zip/WinRAR)
  • PDF tools
  • GPU tools (NVIDIA/AMD overlay/shell components)
  • Antivirus “scan with …” right-click menu items

Step 3: pull the exact crash “faulting module” (so we can point at the app)​

  1. Win + Reventvwr.msc
  2. Windows Logs → Application
  3. Find the latest Error at the exact time Explorer restarted
  4. Open it and copy/paste:
    • Faulting application name
    • Faulting module name (this DLL name is the money line)
(Alternatively, type Reliability in Start → open Reliability Monitor and click the Explorer crash entry.

Quick questions​

1) Do you have any third‑party antivirus installed (Avast, McAfee, etc., or only Windows Security?
2) In Device Manager → Display adapters, what GPU do you have (Intel / NVIDIA / AMD)?
(Safe Mode uses a basic display driver, so if clean boot + shell extensions don’t reveal it, the GPU driver is the next suspect.
If you paste the faulting module name from Event Viewer, I can usually tell you exactly what to uninstall/update.
 

SO for anyone comming here in the future, I resolved the issue but deleting some older files but most importantly Jupyter software, I dont know what exaly fixed it but I have my file home back
 

Good to hear you got it sorted, Caleby101 — and thanks for coming back with what fixed it.
Even though it’s not obvious at first glance, uninstalling Jupyter (often via Anaconda/Miniconda or a bundled Python stack) can absolutely stop Explorer crash loops because those packages can install Explorer-integrated components (context-menu entries like “Open with…”, file associations for .ipynb, sometimes preview/thumbnail handlers, and background services). If one of those components is buggy/corrupt, Explorer can crash/restart repeatedly when File Explorer “Home” tries to enumerate Recents/Recommended and hits that handler.

For anyone reading this later (and for you, if you want to narrow it down)​

If you ever want to know exactly what was crashing Explorer, check:
  • Reliability Monitor: Start → type reliability → View reliability history → click the Explorer crash → it often shows the faulting module (DLL).
  • Event Viewer: eventvwr.msc → Windows Logs → Application → look for “Application Error” with explorer.exe and note Faulting module name.

If you need Jupyter again (without risking Explorer)​

Consider reinstalling it in a more minimal way:
  • Install Python normally, then use a virtual environment and pip install jupyter, rather than a big distribution that adds lots of shell integration.
If you want, tell me whether it was Anaconda/Miniconda or “plain Jupyter”, and your Windows 11 version (23H2/24H2), and I’ll note the most likely component responsible so future readers have a clearer “root cause.”
 

Back
Top