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

Friday, August 03, 2018 

Hi, 

Same Problem! 

I believe I started getting this error after I checked the health of my RAM by running: 

Windows 10 Pro - Windows Memory Diagnostic Tool. 

Regards, 

Saeed Khan

I stumbled upon a possible solution (maybe just a workaround?) on another thread covering the same issue. Here's what I did to resolve the warning (proceed at your own risk):

1. Right click on the Start button and click Run
2. In the Run dialog box type in: netplwiz and click OK or press Enter
3. In the User Accounts wizard look for duplicates of your user account and remove any user account that isn't part of the Administrators group and click OK when done.
4. Sign out of Windows and sign back in again.

A word of caution, consider backing up your user profile. While removing duplicate accounts in this fashion shouldn't affect your user profile in any way, anything is possible. You might also consider creating a local-only administrator account as a backup in case you are the only admin on the account. 

At any rate, this worked for me and I it leave here with the hope that might bring relief to some of you as well. :)

Why would I suddenly have duplicate accounts after a major W10 upgrade? 

I never had any troubles and error messages before the upgrade

I stumbled upon a possible solution (maybe just a workaround?) on another thread covering the same issue. Here's what I did to resolve the warning (proceed at your own risk):

1. Right click on the Start button and click Run
2. In the Run dialog box type in: netplwiz and click OK or press Enter
3. In the User Accounts wizard look for duplicates of your user account and remove any user account that isn't part of the Administrators group and click OK when done.
4. Sign out of Windows and sign back in again.

A word of caution, consider backing up your user profile. While removing duplicate accounts in this fashion shouldn't affect your user profile in any way, anything is possible. You might also consider creating a local-only administrator account as a backup in case you are the only admin on the account. 

At any rate, this worked for me and I it leave here with the hope that might bring relief to some of you as well. :)

I had the same issue, started a few days ago. I contacted MS support via chat (well, that's why they are for, right?) and finally I got into a technician who solved it via remote assistance.

The solution was to switch back to local account from MS account (Settings>Accounts>Sign in with a local account instead). Then logoff-logon again, and then connected back to MS account. (Same steps but "sign in with MS account" this time.)

He said it was something with MS account not synced properly to local computer.

Hope this helps.

followed the exact same steps, as soon as i logged in again with my MS account, the error showed up again.

This is not an issue limited to a few people but widespread and started after the last big upgrade.