Skip to main content
Added guidance for those users who dont see the UI option to enable apps running in the background
Source Link

Disabling the "Let apps run in the background" toggle on the "Background apps" page of the new Windows Privacy settings causes start-menu search to break, at least on Windows 10 with the Creator's Update!

I recently reinstalled Windows 10 with the Creator's Update on three machines. After installing Windows, my first step on all of the machines was to click through all the pages under Settings -> Privacy, disabling every single toggle. Included among these was the "Let apps run in the background" setting on the Background apps page.

Soon, thereafter, I noticed that newly installed applications would not show up in the start-menu search - either through win+S or by simply starting to type when the start-menu had focus. On all machines, some results would show and others would be missing. Newly installed stuff would not show. On one, typing google or chrom would yield nothing but the full word, chrome, would show "execute command". At one point, one machine would only complete notepad and the result could not be clicked or activated.

This thread helped me to learn that creating a new local-administrator user on the machines would temporarily solve the issue - thanks! Unfortunately, the problem would ocurr again and so I started trying to track down when, precisely, it started happening. I did this with a process involving many, many restarts and repeatedly installing and uninstalling 7-zip.

I was pleased to discover that my registry hacks that disable Cortana's web-search and windows-store search were not responsible - they were my first guess. Hacking out other parts of Windows didn't break the search; neither did my power-shell script that uninstalls all the bloatware that ships with Windows 10: Facebook, Twitter, XING, Keeper, the list goes on. (This stuff is also automatically reinstalled, repeatedly, and reinstalled for new user accounts.)

Finally, I tracked the problem to this privacy setting - another thing that is user-account specific!

My tests show that you can still disable all applications from running in the background as long as the primary toggle at the top of the "Background apps" page remains On. Here's a screenshot of my settings with start-menu search working:

Working Privacy Settings

All the rest of the privacy toggles can be switched off, on all the other pages.

And, lastly, it seems that if the "Let apps run in the background" toggle is Off, turning it on again and restarting appears to repair the start-menu search although it seems to take a while before the results are 100% again.

Of the solutions listed on this question, only the suggestion to create a new local user account worked and that only until I once again switched off this problematic toggle.


If you don't see the let "apps run in the background" toggle, you can still enable it via the registry. To do so;

  1. Press windows logo key + R to open the run dialog. Type "regedit" then press enter.
  2. Navigate to the following key: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\BackgroundAccessApplications
  3. Right click on BackgroundAccessApplications, and select New -> DWORD (32-bit) Value. Name it GlobalUserDisabled and set its value to 0.
  4. Restart.

Disabling the "Let apps run in the background" toggle on the "Background apps" page of the new Windows Privacy settings causes start-menu search to break, at least on Windows 10 with the Creator's Update!

I recently reinstalled Windows 10 with the Creator's Update on three machines. After installing Windows, my first step on all of the machines was to click through all the pages under Settings -> Privacy, disabling every single toggle. Included among these was the "Let apps run in the background" setting on the Background apps page.

Soon, thereafter, I noticed that newly installed applications would not show up in the start-menu search - either through win+S or by simply starting to type when the start-menu had focus. On all machines, some results would show and others would be missing. Newly installed stuff would not show. On one, typing google or chrom would yield nothing but the full word, chrome, would show "execute command". At one point, one machine would only complete notepad and the result could not be clicked or activated.

This thread helped me to learn that creating a new local-administrator user on the machines would temporarily solve the issue - thanks! Unfortunately, the problem would ocurr again and so I started trying to track down when, precisely, it started happening. I did this with a process involving many, many restarts and repeatedly installing and uninstalling 7-zip.

I was pleased to discover that my registry hacks that disable Cortana's web-search and windows-store search were not responsible - they were my first guess. Hacking out other parts of Windows didn't break the search; neither did my power-shell script that uninstalls all the bloatware that ships with Windows 10: Facebook, Twitter, XING, Keeper, the list goes on. (This stuff is also automatically reinstalled, repeatedly, and reinstalled for new user accounts.)

Finally, I tracked the problem to this privacy setting - another thing that is user-account specific!

My tests show that you can still disable all applications from running in the background as long as the primary toggle at the top of the "Background apps" page remains On. Here's a screenshot of my settings with start-menu search working:

Working Privacy Settings

All the rest of the privacy toggles can be switched off, on all the other pages.

And, lastly, it seems that if the "Let apps run in the background" toggle is Off, turning it on again and restarting appears to repair the start-menu search although it seems to take a while before the results are 100% again.

Of the solutions listed on this question, only the suggestion to create a new local user account worked and that only until I once again switched off this problematic toggle.

Disabling the "Let apps run in the background" toggle on the "Background apps" page of the new Windows Privacy settings causes start-menu search to break, at least on Windows 10 with the Creator's Update!

I recently reinstalled Windows 10 with the Creator's Update on three machines. After installing Windows, my first step on all of the machines was to click through all the pages under Settings -> Privacy, disabling every single toggle. Included among these was the "Let apps run in the background" setting on the Background apps page.

Soon, thereafter, I noticed that newly installed applications would not show up in the start-menu search - either through win+S or by simply starting to type when the start-menu had focus. On all machines, some results would show and others would be missing. Newly installed stuff would not show. On one, typing google or chrom would yield nothing but the full word, chrome, would show "execute command". At one point, one machine would only complete notepad and the result could not be clicked or activated.

This thread helped me to learn that creating a new local-administrator user on the machines would temporarily solve the issue - thanks! Unfortunately, the problem would ocurr again and so I started trying to track down when, precisely, it started happening. I did this with a process involving many, many restarts and repeatedly installing and uninstalling 7-zip.

I was pleased to discover that my registry hacks that disable Cortana's web-search and windows-store search were not responsible - they were my first guess. Hacking out other parts of Windows didn't break the search; neither did my power-shell script that uninstalls all the bloatware that ships with Windows 10: Facebook, Twitter, XING, Keeper, the list goes on. (This stuff is also automatically reinstalled, repeatedly, and reinstalled for new user accounts.)

Finally, I tracked the problem to this privacy setting - another thing that is user-account specific!

My tests show that you can still disable all applications from running in the background as long as the primary toggle at the top of the "Background apps" page remains On. Here's a screenshot of my settings with start-menu search working:

Working Privacy Settings

All the rest of the privacy toggles can be switched off, on all the other pages.

And, lastly, it seems that if the "Let apps run in the background" toggle is Off, turning it on again and restarting appears to repair the start-menu search although it seems to take a while before the results are 100% again.

Of the solutions listed on this question, only the suggestion to create a new local user account worked and that only until I once again switched off this problematic toggle.


If you don't see the let "apps run in the background" toggle, you can still enable it via the registry. To do so;

  1. Press windows logo key + R to open the run dialog. Type "regedit" then press enter.
  2. Navigate to the following key: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\BackgroundAccessApplications
  3. Right click on BackgroundAccessApplications, and select New -> DWORD (32-bit) Value. Name it GlobalUserDisabled and set its value to 0.
  4. Restart.
Source Link
Xharlie
  • 1.2k
  • 8
  • 11

Disabling the "Let apps run in the background" toggle on the "Background apps" page of the new Windows Privacy settings causes start-menu search to break, at least on Windows 10 with the Creator's Update!

I recently reinstalled Windows 10 with the Creator's Update on three machines. After installing Windows, my first step on all of the machines was to click through all the pages under Settings -> Privacy, disabling every single toggle. Included among these was the "Let apps run in the background" setting on the Background apps page.

Soon, thereafter, I noticed that newly installed applications would not show up in the start-menu search - either through win+S or by simply starting to type when the start-menu had focus. On all machines, some results would show and others would be missing. Newly installed stuff would not show. On one, typing google or chrom would yield nothing but the full word, chrome, would show "execute command". At one point, one machine would only complete notepad and the result could not be clicked or activated.

This thread helped me to learn that creating a new local-administrator user on the machines would temporarily solve the issue - thanks! Unfortunately, the problem would ocurr again and so I started trying to track down when, precisely, it started happening. I did this with a process involving many, many restarts and repeatedly installing and uninstalling 7-zip.

I was pleased to discover that my registry hacks that disable Cortana's web-search and windows-store search were not responsible - they were my first guess. Hacking out other parts of Windows didn't break the search; neither did my power-shell script that uninstalls all the bloatware that ships with Windows 10: Facebook, Twitter, XING, Keeper, the list goes on. (This stuff is also automatically reinstalled, repeatedly, and reinstalled for new user accounts.)

Finally, I tracked the problem to this privacy setting - another thing that is user-account specific!

My tests show that you can still disable all applications from running in the background as long as the primary toggle at the top of the "Background apps" page remains On. Here's a screenshot of my settings with start-menu search working:

Working Privacy Settings

All the rest of the privacy toggles can be switched off, on all the other pages.

And, lastly, it seems that if the "Let apps run in the background" toggle is Off, turning it on again and restarting appears to repair the start-menu search although it seems to take a while before the results are 100% again.

Of the solutions listed on this question, only the suggestion to create a new local user account worked and that only until I once again switched off this problematic toggle.