SearchApp crashes and restarts Explorer

Topic

New Reply

[Simon_Weel]

Since this week, we can no longer search for files. Type something into the search bar in Explorer and it will start searching. As soon as something is found, Explorer closes and restarts. Two errors are logged in the Application log:

Faulting application name: SearchApp.exe, version: 10.0.19041.1023, time stamp: 0x51ea1ff4
Faulting module name: KERNELBASE.dll, version: 10.0.19041.1023, time stamp: 0x924f9cdb
Exception code: 0xc0000409
Fault offset: 0x000000000010b39c
Faulting process id: 0x2af4
Faulting application start time: 0x01d76e7e1430bfe5
Faulting application path: C:\WINDOWS\SystemApps\Microsoft.Windows.Search_cw5n1h2txyewy\SearchApp.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: b4726cef-cb31-49e3-824d-fbf71fd2306b
Faulting package full name: Microsoft.Windows.Search_1.14.2.19041_neutral_neutral_cw5n1h2txyewy
Faulting package-relative application ID: CortanaUI

and

Faulting application name: explorer.exe, version: 10.0.19041.1023, time stamp: 0xc438eef0
Faulting module name: ucrtbase.dll, version: 10.0.19041.789, time stamp: 0x2bd748bf
Exception code: 0xc0000409
Fault offset: 0x0000000000071208
Faulting process id: 0x27cc
Faulting application start time: 0x01d76e7ce0ae3b66
Faulting application path: C:\WINDOWS\explorer.exe
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll
Report Id: 46df87cc-2c7c-4261-92cc-d890d639d26d
Faulting package full name:
Faulting package-relative application ID:

The last line in the first error suggests it has something to do with Cortana. Since Cortana is not available in our country, I disabled it using a GPO. After changing the setting to Enabled, Cortana can be started, greets with ‘not available in your country’ and that’s it. A search still crashes Explorer.

Did some searching and just about all websites recommend deleting the registry key ‘search’: HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Search but that doesn’t resolve the problem. Any ideas?

• This topic was modified 3 years, 11 months ago by Simon_Weel.

Reply | Quote

Replies

https://www.c-amie.co.uk/technical/windows-10-search-not-working-after-in-place-upgrade/

Can you see if that helps?

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

Checked it out and there’s no ‘C:\Users\<username>\AppData\Local\Packages\Microsoft.Windows.Cortana_cw5n1h2txyewy’ folder?  Nothing with Cortana in the name. So I created the folder myself, just in case. But a search still crashes.

Reply | Quote

This won’t fix your current crashing but instead of using Windows search use the best, fastest search, free, portable / install ‘Everything‘ app.

Reply | Quote

Alex5723 wrote:

This won’t fix your current crashing but instead of using Windows search use the best, fastest search, free, portable / install ‘Everything‘ app.

Everything is indeed a very nice util. Unfortunately, using it to search network shares isn’t as easy as searching on a local drive…

Reply | Quote

Simon_Weel wrote:

using it to search network shares isn’t as easy as searching on a local drive…

see: Using Everything for Mapped Network drives (shared folders)

You may replace Windows Search with EverythingToolbar now

Reply | Quote

I started getting exactly the same search crash immediately upon the update to KB5003637 (though I am not seeing the explorer.exe problem). I have tried all and sundry recommendations — even a repair install of Windows 10 — with no luck. I should note that the problem is restricted to my main user profile — I created and logged into a second user account, and no search crash. I’m not willing to migrate my profile over to a new user, however, at this point — I reverted to a saved image and my system is working perfectly again on 14093.985.

Reply | Quote

Well, I finally resolved the issue.

I tried updating Windows 10 again and found that the latest cumulative update KB5004237 was still exhibiting the crash problem. I also found that if I boot into my normal user profile in safe mode, search works fine. So it’s something that gets loaded for my profile in normal mode but not safe mode. I restored my Macrium image and did some further sleuthing.

Searching on the exception code 0x88985004, I found it defined as: “A font file exists but could not be opened due to access denied, sharing violation, or similar error.”

I assumed that searchapp.exe in the newer builds (with News & Interests enabled) is attempting to access a font file that has a problem or that it lacks permissions to access.

I used the Everything app to locate all .ttf files on my system. Finding some installed by my Emby and Calibre content servers (apps that would run in normal but not safe mode), I changed security properties for the fonts and their containing folders to add read/execute permissions for “ALL APPLICATION PACKAGES”. I also added this permission to C:\Users\[username]\AppData\Local\Microsoft\Windows\Fonts folder and its contents. I then un-paused Windows updates on my system and let the latest update install. After it did so, search was working properly (as was the News & Interest feed, before I turned it off).

Hope this helps someone else!

Reply | Quote

Wow, thank you a lot! That did the trick for me!!!
After searching and trying things out for 2 month!

Great work!

Reply | Quote

According to several websites, the problem is caused by Windows update 5003637. So removed the update, disabled Windows Update service, performed a reboot and… still crashes. Created a new (domain) user and tried it. Still crashes. BUT – when logged on as Admin, search works fine.

Reply | Quote

Well, the problem magically solved itself. That is, it’s probably fixed in a recent Windows update.

Reply | Quote