Turns out that when you remove the GPO from workstations the Applocker service gets disabled before it can update it’s policies so the policies remain intact. It is almost as if once the Applocker rules are applied they are never removed.Īfter a little more digging I found this article: Problem: AppLocker Rules Still Enforced After the Service is Stopped However, after removing the GPO, refreshing the GPO’s (GPUpdate /force) and rebooting several times the error still occurs.
#Applocker gpo .exe
exe based rules, Windows will automatically disable ALL modern apps unless unlocked by specific AppLocker rules. These rules target the new Modern UI style apps. Under Windows 8.x and 10, the new applications require new AppLocker rules called Package App Rules. Looking at the event logs, the AppLocker event log reads: “ No packaged apps can be executed while Exe rules are being enforced and no packaged app rules have been configured”
Now I know I have some AppLocker GPO’s in the environment that prevent users from running applications under their user folder (C:\User\Username) but that does not explain why these apps are not running as they are not run from one of these locations. Before they join the domain all apps are functioning fine, however, as soon as one of them joins the domain ALL the Windows 10 packaged apps stop working even the start menu (Cortana) doesn’t work and the Edge browser does not appear on the taskbar.
In my lab I had newly built Windows 10 Enterprise PC’s that are joined to a domain. I know that this is not a System Center related post but I just spent the good part of 2 hours pulling my hair out over this issue so I thought I better have something to show for it at the end of it all.
0 kommentar(er)
