This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Remove From My Forums

Start menu and Edge break when entering domain

Question
0

Sign in to vote

Good day!

We're in the process of testing if Windows 10 works for us in a business environment, but we are having an issue regarding the start menu and modern apps.

When we install a pc and we log in as a local user, everything works fine. But when we enter the computer in our domain, the startmenu stops working 100%. About 90% of the time, the start menu will open, but when typing, the search function won't work. Opening and closing start seems to work, but it just happens again after some time.

Also, apps like edge close down immediately after starting, and repairing them with commands like dism /online /restorehealth only temporarily resolves the issue.

I hope someone can help us with this issue!

Thursday, February 4, 2016 1:24 PM

Answers

0

Sign in to vote
If you're using roaming profiles, this is a much-discussed but as yet unfixed issue.

This is the main thread discussing it:

https://social.technet.microsoft.com/Forums/en-US/fd436515-6423-4015-9afe-d7e6034909ab/windows-10-threshold-2-edgesearch-issues-for-domain-joined-pcs?forum=win10itprogeneral

There are some workarounds discussed there to do with changing permissions in the current user registry, but it's all a bit of a hack at the moment.

I'm not aware of any official response from MS, or even an acknowledgement that it's a problem.
- Marked as answer by WalterEsch Thursday, February 4, 2016 1:53 PM
Thursday, February 4, 2016 1:31 PM

All replies

0

Sign in to vote
If you're using roaming profiles, this is a much-discussed but as yet unfixed issue.

This is the main thread discussing it:

https://social.technet.microsoft.com/Forums/en-US/fd436515-6423-4015-9afe-d7e6034909ab/windows-10-threshold-2-edgesearch-issues-for-domain-joined-pcs?forum=win10itprogeneral

There are some workarounds discussed there to do with changing permissions in the current user registry, but it's all a bit of a hack at the moment.

I'm not aware of any official response from MS, or even an acknowledgement that it's a problem.
- Marked as answer by WalterEsch Thursday, February 4, 2016 1:53 PM
Thursday, February 4, 2016 1:31 PM
0

Sign in to vote

Thanks for the quick reply, we are indeed using roaming profiles.

In that case, we'll just wait upgrading to w10.

Thursday, February 4, 2016 1:45 PM
0

Sign in to vote
This issue has been fixed in Build 14279. In case (some of) your roaming profiles were already affected by this issue, a PowerShell script has to be executed in order to solve the issue for that profile.

NOTE: Build 14279 is really needed to get rid of the issue. Simply running the PowerShell script is not enough if you're on a previous build.
- Proposed as answer by Dennis Ameling Sunday, March 6, 2016 4:13 AM
Sunday, March 6, 2016 4:12 AM