FragglePete Posted November 9, 2015 Posted November 9, 2015 Another Windows 10 issue has got me scratching my head. After getting the Application Identity Service up and running and behaving as it should I'm not having issues with creating a new AppLocker policy.... I create a new GPO, go to the Application Control Policies bit, right click Packaged app Rules and Create New Rule..... After setting up the Permissions on who this will apply too (have also tried it on Everyone), when ever I press the 'Select' button from the 'Use an installed package app as a reference', I get a SrpUXSnapIn.dll MMC Error. MMC has to unload and I get an Exception has been thrown by the target of an invocation. !!! wtf? I running Windows 10 Edu, 64Bit with RSAT for Windows 10 installed. Not sure what is going on. A few Google hits point to others that have had the issue but no resolution as of yet. Thoughts? Pete
ModeratelyGruntled Posted December 16, 2015 Posted December 16, 2015 Just found the very same issue, but with Win10 Pro instead of Edu. Did you manage to resolve it in the end?
FragglePete Posted December 16, 2015 Author Posted December 16, 2015 Just found the very same issue, but with Win10 Pro instead of Edu. Did you manage to resolve it in the end? 'friad not. Win 10 on the back burner at the moment and will start looking again in the new year. Pete
Duke5A Posted June 29, 2016 Posted June 29, 2016 I don't know if you guys ever got this to work, but I ran into the same problem with MMC crashing every time the console would try and display a list of installed packages. I customized my image and removed a lot of the crap bundled packages. I thought this might have something to do with it so I installed vanilla Win10 into a VM with the management tools and it worked.
FragglePete Posted June 29, 2016 Author Posted June 29, 2016 I don't know if you guys ever got this to work, but I ran into the same problem with MMC crashing every time the console would try and display a list of installed packages. I customized my image and removed a lot of the crap bundled packages. I thought this might have something to do with it so I installed vanilla Win10 into a VM with the management tools and it worked. Sorry, never really came up with a solution as when I picked up the Windows 10 project again everything seemed to be working as expected. I have no idea what caused the issue and have no solution to how I fixed it. Pete
MrKJLS Posted June 29, 2016 Posted June 29, 2016 I had this issue when I was doing Windows 10. Crashed on my work PC and the boss's PC. Installed RSAT on the PC I was testing on. Worked fine.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now