Windows 10: Windows Search cannot find new installed application

Hi all,

recently I observed that, the windows search fails to index my new installed application. This applies for both desktop application as well as application installed from windows store.
The search still works for application which were installed from before. I have tried to rebuild the search index multiple times, disable and start the search services, but none of them fixed this. In the "Start menu" folder, I can find all the shortcut "lnk". The shortcuts for each new installed applications are created, but oddly windows search cannot find these. Does anyone have a suggestion how to resolve this problem. Thanks in advance.

With bests,


:)

 

Search can`t find a new installed applications.

Hi,

Have you tried creating a new user account? If not, try creating a new user account, then check if the issue persists. To create a new user account on your computer, kindly follow the appropriate steps in this article:

Create a local user or administrator account in Windows 10. If the issue doesn't persist on the new user account, it would signify that your current user profile is corrupted.

Kindly get back to us once you've checked if the issue also occurs in a new user account.

 

Search can`t find a new installed applications.

Only the solution described below helps me, but I'm tired of repeating it.

Type this in the command line as administrator:

rd C:\Users\%UserName%\AppData\Local\Packages\Microsoft.Windows.Cortana_cw5n1h2txyewy /s

That's what I mean:









Please let me know if this can be fixed.

Windows specifications:

Edition: Windows 10 Home

Version: 1709

OS Build 16299.192

* A new, clean installation with a flash drive.

The standard Windows fixes do not work for me, as does the disabling/enabling of the search service or the index rebuild.

 

Hi, have you tried the search and indexing troubleshooter?

E.g. Settings, search Troubleshoot, click View all in the CP dialogue, select the troubleshooter.

 

I have already tried it. No issues were found though.
Below is the screenshot of my current folders that are indexed. Is it comparable to the default setting? Am I missing some important locations?

 

Hi, try this (7 & 8): - I can't find one for '10 here.
Search Options - Change or Restore - Windows 7 Help Forums




That's near default. The Graphics.. Photos... and Test... entries are ones I've added.

 

I tried the tutorial you mentioned, but it didn't help either.
As for the locations, on the second thought, I think the most relevant folder for this issue is the "Start Menu" folder containing "lnk" shortcuts, which is indexed. It is strange that the application from windows store is affected too. Do you know how the search work for these store apps, where is the location for these?
Another question: in your "indexing options". If you go to "advanced"/"File Types", how does your "lnk" filetype look like?
Do you have other ideas that I can try out?

 

Start menu shortcuts that appear in Win 10's start menu are here:
C:\ProgramData\Microsoft\Windows\Start Menu\Programs
Try this:
Open Indexing options and that folder and ensure both are visible simultaneously.
Note the number of items indexed.
Add/create a new shortcut in
C:\ProgramData\Microsoft\Windows\Start Menu\Programs
See if the number increments (and check the shortcut appears in your start menu).

 

the number increments, but the new shortcut does not appear in the start menu. It means the indexing is correct. So the problem should be after that. I'm not sure, how the "search" or "start menu" read new entry. I think, we are narrowing down the issue. Do you have any idea how to proceed further from here?

 

Hi, suggest you try creating a new user for test purposes and comparison.
Try installing one of the programs with which you are experiencing difficulty

 

It works with a new user. But, I don't think it is related to the program I was trying to install.
A new problem also arose with the new user, the search field freezes quite often. Not sure what to do next?

 

With your original user try this:
Fix Windows 10 Start menu problems with Microsoft's new troubleshooter tool

then also try this as a mater of routine before the next step
From an admin command prompt
[Windows key + X, click command prompt (admin)]
chkdsk C: /F
Your PC will need to restart.
Make sure the result is clear or fixed- else do not proceed.
Post back the result, which you can get after a restart as follows:
How do I see the results of a CHKDSK that ran on boot? - Ask Leo!

then
from an elevated command prompt
sfc /scannow

That's just to establish a base line and do a basic check for consistency.

My personal view of the start menu: avoid it. Use Classic Shell - something that actually works and works better, and which is actually capable of representing a large categorised start menu properly (which Win 10's can't).

 

I did all the checkdisk and sfc once. Everything is fine, which is why I found it really weird. I have tried a couple of things without success before posting the question here.
I know about classic shell, haven't tried it though. The reason I try to fix start menu search is because I use this while commuting, basically everyday, I just want to get the most out of the battery as possible, which is why I tend to use built-in solution as far as I can. Do you have any experience about power consumption of classic shell? just eager

 

Quite understand wanting to fix it. Good those basic checks passed.

Did you also try the start menu repair tool in my previous post?

The power consumption of a largely passive process such as a start menu is minimal. When not displayed it does nothing. There is a brief scan after logon to update its database (so you can search the start menu), which is probably the most processor intensive activity other than installation. I would suggest things like screen brightness, or active tiles on Win 10's start menu would be more significant. There are larger peaks of CPU use using Win 10's start menu (expect more with more active tiles).

 

I tried the start menu repair tool, it didn't fix the problem. Do you have further ideas?
I think, I would give it a try with classic shell.