![]() Cross-forest read access to Computer and User Configurations Windows.I have been banging my head against the wall for some time now. Did you mean on the machine that will be used for the image? I am curious is I need to create another image or will these changes take affect on already imaged machines once i change gpo and force update? Thanks for any input on this. I am curious, I see you set the gpo and the Local Group Policy as well. ![]() ![]() I am not at work at this time to try this fix but am anxious to. So your workaround in gpo looks interesting. I couldn't possible do this one at a time. I tried the copying of the package as stated above and that works but only when a user has already tried to log in and then i could copy the indexed package over into their user profile, but this will not work when you have a school district where hundreds of different students would be logging in to any given machine. Local admin could use search feature but all domain users could not. JP75, I have been trying to get the image for Win 10 Pro to work all summer. Hope this is the cause for someone else and it fixes it. If it's not, check the registry under " HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Windows Search" and remove or set the value to " 1" for this key ConnectedSearchUseWeb. Make sure it isn't set in Local Group Policy in any way as well. Reverting that to " Not Configured" or " Disabled" brought search back as soon as gpupdate /force was run. Search the web or display web results in Search" was Enabled. It was a GPO setting causing the problems and one that doesn't make sense so I assume it's a bug. For reference, UAC is off, Windows Firewall is on (it must be to get built-in apps to work and for search to work), Cortana is on and it's build 1703 Windows 10 Pro. Edge would also reset its default associations. But, for all other users it would break after a few reboots. Domain Admins and the actual local Administrator account allowed the Search function to work. Normally I don't post on forums.but, I've been stuck with the Windows 10 Search box problems since creating images for Win 10 three months ago. I really would like to know what is causing the problem. This has happened to at least 2 separately created sysprepped thick images on two different reference machines. I noticed that there is a language pack related folder in there (\indexed\settings\en-US), not sure if it's related. Needs the indexed folder with all subfolders. In each of these cases the windows.immersivecontrolpanel folder is empty. The local admin user account works fine, but any new (domain) user has a broken search index upon logging in. This happens on Syspreped Win10 1511 machines. ![]() This the the only consistent fix for the issue I have found. Not an ideal fix, but it did work.Ĭopied the file ‘C:\Users\Administrator\AppData\Local\Packages\windows.immersivecontrolpanel_cw5n1h2txyewy’ to C:\Users\\AppData\Local\Packages\windows.immersivecontrolpanel_cw5n1h2txyewy’.I'd give that a try and see if it fixes the problem for you :) I fixed it by copying over a file from the local administrator account where the start menu worked normally, over to the domain profiles that had issues. The search would work just fine for my initial local user (I was using the built-in local administrator user), however once I logged in as a domain user, only certain terms would bring up results. I've run into similar issues with a few of my Windows 10 installs.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |