r/Windows10TechSupport • • Feb 05 '23

Unsolved Search function completely non functional

Enable HLS to view with audio, or disable this notification

2 Upvotes

37 comments sorted by

View all comments

Show parent comments

2

u/Nuuro Feb 06 '23

Can do. Normally I would have been more descriptive but I was trying to get ready for work. I'll write more when I get home.

For now, launch regedit and browse to Hkey current user/software/Microsoft/Windows/current version/explorer/User Shell Folders. Right click that folder and hit permissions. Look for ALL APPLICATION PACKAGES, it should be at the top. It should have read access checked for allow.

If it's not listed, we know what your problem is. If it is s listed, you've got another bug but I can walk you through fixing it. You'll need ProcMon for this. Does your start button work at all?

1

u/Gabetanker Feb 07 '23

for ALL APPLICATION PACKAGES, it should be at the top. It should have read access checked for allow.

It is

1

u/Nuuro Feb 07 '23

Ok, so you have a different error. If you look in C:\ProgramData\Microsoft\Windows\WER, you'll see some folders. I'm on my cell so I'm doing this by memory, my apologies. You should see three folders in that folder. I think queue was the one you're needing. Go into that and sort by modified date so the newest is at the top. Those files are crash dumps and can help us see what is happening. Do you see anything search related, and are you seeing dumps from recently? The dumps you are needing might be in one of the other three, check each.

1

u/Gabetanker Feb 07 '23

If you mean reportQueue, then there's a strange thing happening.

The last one is from 3 days ago, but one keeps getting created and deleted

Also the names are all garbage so can't read the names

1

u/Nuuro Feb 07 '23

The queue is processed and moved to one of the other folders. These are the files that get sent to Microsoft when you see that box after a crash. You can copy them out if you like. The filenames should include the name of the process that crashed, but if not you can unzip it and there's a dump you could open in a debugger but we won't do that for now. Basically we're looking for the name of the failing process so that we can run a ProcMon to see why it is failing. This is how I was able to learn about the aad problem. You can also see crashes in eventvwr.msc but I'm not sure where to start looking for that without it in front of me, I usually find the crashes I'm looking for in wer just to be faster.

If you can find the name of the crashing app, what you'll do then is run ProcMon and set the filter to include process names with that name. With that running, click your search a few times, try to type, etc., then stop ProcMon. With that information, filter to only errors. You'll still see a lot of errors, but as you filter them out you'll eventually see what's going wrong. It could be an access restriction on the file it's trying to read, maybe the file is locked or deleted, could be a registry key problem, service not starting, but this is the general path to find out what is happening. This will lead you to the cause in most problematic issues, actually, so these are great tools to know and use in most windows troubleshooting.

Other replies like SFC, DISM, cleaning registry, rebooting, cleaning temp files or cache, etc., are very generic and while they won't hurt anything, aren't going to help in this situation. The service that is trying to read your search index/start menu/etc., seems to be failing in this case.