Avatar of btm02sf
 asked on

Event ID 69 - AppModel-Runtime errors in Event Viewer - Administrative Events - How to eliminate these errors

On multiple brand new Windows 10 desktops, after joining them to the domain, and after completing all the Windows updates, and after downloading and installing all the updates available in the Microsoft Store, I am getting multiple Event ID: 69 errors in the Event Viewer, in the Administrative Events.

They are logged source is the AppModel-Runtime, and the descriptions are similar, except for the particular package that is generating the error. The text reads similar with the one below:  

Failed with 0x490 modifying AppModel Runtime status for package Microsoft.WindowsStore_12002.1001.1.0_x64__8wekyb3d8bbwe for user [DOMAIN]\[User] (current status = 0x0, desired status = 0x20).

Attached are a couple of screenshots, the first one with all the details for one of these multiple Event ID 69. The second one shows three of the multiple errors that keep appearing in the Event Viewer for all systems.

I've spent a good deal of time trying to figure out what is causing these errors, and how to stop them from appearing in the event log. Unfortunately, I was not able to figure out a solution, so I am hoping that someone in the community will be able to assist. Any feedback or suggestions would be much appreciated.

Thank you.
Windows 10Windows OSDesktops

Avatar of undefined
Last Comment
Hello There

8/22/2022 - Mon
Hello There

I don't think this is a functional error. However, try to run the built-in troubleshooter: Settings -> Update and Security ->  Troubleshoot -> Windows Store apps and try to run wsreset to clear the store cache.

If this will not help, I'd run SFC /scannow and Repair-WindowsImage -Online -RestoreHealth commands.

Also, check out this discussion:

Thank you for responding. I ran the first suggestion with the troubleshooter. I didn't find any problems. I looked up the wsreset details and read the link. It feels to me that these Errors are the result of poor programming on Microsoft's part around the Apps and Microsoft Store. There is no point in running the sfc command when I see these errors on literally all of the Win10 Pro desktops deployed in the last year, as part of transitioning from W7. I would like to be able to make the Eventvwr not record these errors, but I was not able to figure a way to ignore them.

If you know of a solution for getting Eventvwr to ignore the AppModel related errors, it would be great if you could please share it. If not, it's Ok, I will simply let this go, and hope that Microsoft will release one day a fix for these errors.

Thank you
Hello There

View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
Ask your own question & get feedback from real experts
Find out why thousands trust the EE community with their toughest problems.

Thank you for the additional detail, and extra link Hello There. I read it and it clearly confirms that these are stupid little bugs that Microsoft is throwing out in the Event Viewer. The author of the last post on the link you provided says this: "Unnecessary error messages like this are very distracting to the purpose of the Event log in tracking down REAL problems, " He is so right. Which is why I was trying to eliminate these pesky entries.

As for the images that I use on all Dell Optiplexes, I actually use what Dell is sending, and I customize it according to the needs of my clients. It's not worth it for me to create a golden clean image. I think that some of the posts that I read on this said that a few individuals re-installed clean Windows and still got these crappy messages in eventvwr.

As it's very unlinkely that Microsoft will ever fix all the stuff that they are throwing in the Eventvwr to cause us headaches, I will simply ignore them. Thank you again for your assistance.
Your help has saved me hundreds of hours of internet surfing.
Hello There

To your previous question. I am not aware of anything that ignores specific events. Microsoft simply prevents you from doing this. However, you can use Event Viewer filter and create a custom view without Event ID 69.