what is windows shell experience and why do i get a window telling me to ask for permission to use it

So.. we have people recommending pointless integrity checks, and mistaken removal of security created policies...come on guys this is not rocket science... a CORE windows module has a policy out of line ...fixed in c48seconds from below...

1: Anyone getting this error is on a non home, aka PRO version of windows

2: CLICK START

3: TYPE local security policy

4: EXPAND APPLICATION CONTOL POLICIES

5: EXPAND APPLOCKER

6: You will have 4 tabs within, and I no doubt no rules setup in there

7: You need to add the defaults, which YUP you guessed it, ADDS windows shell experience in for you

8: Go ahead and right click on all four, and where you see add default option, click it to add them in, (right click on all four), and you will see windows shell added in, close and issue immediately fixed for ever :)

9: And if you don't see 'add defaults' then do the slightly longer route of going through the motions of ADDING a new EXECUTABLE rule... pick literally any file you want notepad.exe ect, as your not going to actually add it, just get to the point where you then get TOLD/ADVISED your missing the default rules and do you want to add them, you click yes of course, and at that point, close the MMC/policy window, done.

10: And to the people suggesting the SELF DESTRUCT option of from an elevated cmd window deleting xyz AppLocker files, JUST DONT DO IT

I don't see anything when I typed "local security policy" at the start button - nothing! what should i be seeing?

So.. we have people recommending pointless integrity checks, and mistaken removal of security created policies...come on guys this is not rocket science... a CORE windows module has a policy out of line ...fixed in c48seconds from below...

1: Anyone getting this error is on a non home, aka PRO version of windows

2: CLICK START

3: TYPE local security policy

4: EXPAND APPLICATION CONTOL POLICIES

5: EXPAND APPLOCKER

6: You will have 4 tabs within, and I no doubt no rules setup in there

7: You need to add the defaults, which YUP you guessed it, ADDS windows shell experience in for you

8: Go ahead and right click on all four, and where you see add default option, click it to add them in, (right click on all four), and you will see windows shell added in, close and issue immediately fixed for ever :)

9: And if you don't see 'add defaults' then do the slightly longer route of going through the motions of ADDING a new EXECUTABLE rule... pick literally any file you want notepad.exe ect, as your not going to actually add it, just get to the point where you then get TOLD/ADVISED your missing the default rules and do you want to add them, you click yes of course, and at that point, close the MMC/policy window, done.

10: And to the people suggesting the SELF DESTRUCT option of from an elevated cmd window deleting xyz AppLocker files, JUST DONT DO IT

This solved it for me, and is the first response here from someone who actually seems to understand what the cause of the problem is. Thanks!

So.. we have people recommending pointless integrity checks, and mistaken removal of security created policies...come on guys this is not rocket science... a CORE windows module has a policy out of line ...fixed in c48seconds from below...

1: Anyone getting this error is on a non home, aka PRO version of windows

...

Windows 10 Home, still get this error.

As I posted above, MS admitted this bug, promised to fix it in RS5, due end of October

Windows 10 Home, still get this error. 

Me too.

As I posted above, MS admitted this bug, promised to fix it in RS5, due end of October 

Could they not push a patch for this sooner? Leaving folk with this annoyance (albeit a minor one) for two months is a bit shoddy.