Recurring Event ID 65 AppModel-Runtime - Windows 10 2004

Hi!

I've recently been having some BSOD issues so I decided to reinstall Windows. I still don't know whether it has fixed the problem yet, but since installing Windows 10 2004 (19041.329) I've noticed a recurring error in Event Viewer that slightly concerns me:

Event ID 65 - AppModel-Runtime
Failed with 0x57 retrieving AppModel Runtime status for package Windows

I'm not sure if this is a 2004 quirk, as I don't recall getting it on 1909, but I've had about 40 of these errors since reinstalling Windows just over 24 hours ago.

Has anyone else got this error?

Have you fixed this issue ?.
It started happening right after I've fresh installed Windows 10 (2004) I didn't had this issue on 8.1.One of my friends also fresh installed Windows 10 yesterday he said he was also having the same issue.Is this error come packed with the new media creation tool kit i wonder.

It's a new issue in Windows 10 2004.

Mentioned frequently in this current thread -

Known and Resolved issues for Windows 10 May 2020 Update version 2004

OldNavyGuy said:

It's a new issue in Windows 10 2004.

Mentioned frequently in this current thread -

Known and Resolved issues for Windows 10 May 2020 Update version 2004

So it's on the Window's side of error not ours.

It has occurred in earlier releases.

I've never seen it in 1909.

never seen it in 2004, stop using customized windows iso's with things ripped out.

Diceman2037 said:

never seen it in 2004, stop using customized windows iso's with things ripped out.

Unless Microsoft are providing said customised ISOs on their own website, that’s not the issue.

Diceman2037 said:

never seen it in 2004, stop using customized windows iso's with things ripped out.

I got it from microsoft it's their own original media creation tool kit.

I suddenly saw a clump of 21 of these 65 errors in my W10 Pro 1909 system, and eventually traced it to the O&O AppBuster program.

I had this on my system from previous attempts to clear out Windows apps (I think from an earlier W10 release), and ran it up to see what, if anything, was in my system now. I didn't actually use it to remove anything, but evidently the very process of the app populating itself with the Win apps list caused the errors to appear in the EL. The whole process to produce errors was repeatable, and timed.

The O&O app's latest release is from February 2019, and I suspect that there have been changes in the Windows app management since then.

I won't be running O&O AppBuster in the foreseeable future.