You ran the MS store repair in powershell - oops
Please try the same command in a Command Prompt - per the tut it can be standard (as opposed to Admin Command Prompt - but that would work too)
Sim: good eyes on the CreateExplorerShellUnelevatedTask - a Google shows up a lot of Farbar reports and some fixit files,
BUT over on Sysnative, the good folks don't think it's a concern (not in the fixit file they created)
AND as our own good fellow Cliff S points out - that task launches File Explore with no UAC check - not sure why it's there, but it seems harmless. That can be investigated later if needed, but for now, I would leave the task disabled since the trigger and actions are unknown
FYI - CCleanerSkipUAC is legit ... but you knew that already
Clint - how was Win10 instaled on the machines - GWX / Windows update or clean install? You might have answered that somewhere in your thread, but my focus is waning.
Are the events for this issue all related to the same license ID?
Is the machine running ok? You're just wondering about the event log entries - yes?
Win 10 was installed as: Did a clean install of Win 8.1 Pro, Installed Win 10 within Windows with DVD made with MCT.
Yes, the events for this issue all related to the same license ID.
The machine is running OK at my login. There are some things that don't work when I log in as Administrator.
MS Store: I don't recall but he tut doesn't show any other output either.
So, we need to figure out what that license ID belongs to and correct it to stop logging the event
I still think it might have something to do with Universal Apps - the re-register of the apps (not the store) gave no output ... and there should have been.
You upgraded a clean install of Win8 Pro to Windows 10 Pro.
There are a few paths forward
1) manually uninstall all universal apps, then reinstall the ones you want
Tut: Apps - Uninstall in Windows 10
- time consuming and might not fix the issue (I might be chasing the wrong rabbit)
2a) Run the apps troubleshooter in Control panel
2b) find the culprit causing the log entry and correct it - time consuming
3a) DISM repair using Source
Tut: DISM - Repair Windows 10 Image
-> 7. To Use DISM /RestoreHealth /Source:esd Command
3b) Repair install Win10 - might not fix the issue
Tut: Repair Install Windows 10 with an In-place Upgrade
!!! Read the caveats in the tut.
4) clean install Win10
Tut: Windows 10 - Clean Install
- if you do go this route, get a fresh download of the Windows 10 ISO - techbench is bigger (wim + home & pro) - MCT - download tool is smaller (esd - one edition)
Pros: Cleanest way to install Windows 10
Cons: The one disadvantage to this, other than time (backup personal data, download and install Windows 10) is that you have to reinstall and configure programs that don't come with Windows. You will need to retrieve your license keys to re-install them. Belarc advisor gets a lot of them for you
5) live with the event log - I'm too anal retentive for this option
I listed the options in the order I would execute them. I wouldn't spend too much time on finding the culprit using the license ID though (either I typo'd the id or a Google search wasn't relative. That's not to say there isn't information out there, just that in my limited capacity, I couldn't find any - maybe the more info on the event log entry itself might help.
Think about the options and post which one(s) you want to pursue.
I have health issues that prevent me from being too responsive. I should bow out because I can't be of much more help. Good luck.
The other members posting on your thread are excellent resources and can guide you to tuts or give you instructions.
Could you grab the license ID in the event and post it here in text to make it easier for someone to search? Thanks!
3252b20c-d425-4711-8cc5-b2f53c830b76Could you grab the license ID in the event and post it here in text to make it easier for someone to search? Thanks!
OK. Got it fixed. I really don't know what the problem was. In my troubleshooting, I opened Event Viewer and clicked on several things. As soon as I clicked on Live mail, the error came up. I tried a repair on Windows Essentials. That didn't do any thing. I uninstalled Windows Essentials. That didn't do anything either. My last resort was to do a Win 10 repair install. That fixed the error. Then I couldn't reinstall WLM. I fixed that in another thread. Windows Live Mail won't install - Page 2 - Windows 10 Forums
Now I don't have any bug(s). Thanks to all that replied.
Good news! Thanks for posting your solution. Cheers!