New
#11
I am only an egg, so please don't shoot me. It seems that this issue is limited to machines that have been upgraded to Win 10. Have you tried doing a clean install of 10 after the upgrade (to secure digital entitlement)?
I am only an egg, so please don't shoot me. It seems that this issue is limited to machines that have been upgraded to Win 10. Have you tried doing a clean install of 10 after the upgrade (to secure digital entitlement)?
I'm having this exact same problem.
I have a Windows 10 x64 Enterprise LTSB image that works fine on the VirtualBox server, but the second I pull it down to a physical machine, search is completely broken. Now I know that Cortana is still in LTSB even though Microsoft claims it's not, so it's probably the same issue as other people are experiencing.
I've narrowed it down to a GPO of some kind, but I haven't gone into a granular search through the various policies here that could be causing it. The VBox image does not have all the group policy items that a production machine does.
Has anyone determined what group policy setting causes search to blow up?
I'm working slowly on applying each individual policy to see what happens and I will let everyone know if I find anything.
I don't know if this is too late now, but looking at your screenshots of the policy being applied, you're applying security ACLs to a registry key HKLM\Software. Having a stab at it, I'd say you're missing the ACL for APPLICATION PACKAGE AUTHORITY\ALL APPLICATION PACKAGES on that key. It only needs read access. I've attached a screenshot of how mine looks. When I was testing this, that registry ACL was the key. I could remove the ALL APPLICATION PACKAGES ACL, force a policy update and the start menu broke, add it back in, force an update again and it would work, it was that clear cut. Not to say that didn't take hours of troubleshooting to get to though.