This issue presents itself once a user has configured their account as an MS account on a clean install of 19041/19042.
It does not occur for upgrade installs where the account was linked at the time of original win10 installation.
Event 65, AppModel-Runtime
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Anonymous
I am getting these errors with "Failed with 0x57 retrieving AppModelRuntime status for package Windows." Anyone know what's causing this? Computer is up to date with windows updates...
Log Name: Microsoft-Windows-AppModel-Runtime/Admin
Source: Microsoft-Windows-AppModel-Runtime
Date: 6/27/2020 12:18:47 PM
Event ID: 65
Task Category: None
Level: Error
Keywords: Process
User: DESKTOP-E6NN4IN\****
Computer: DESKTOP-E6NN4IN
Description:
Failed with 0x57 retrieving AppModel Runtime status for package Windows.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-AppModel-Runtime" Guid="{f1ef270a-0d32-4352-ba52-dbab41e1d859}" />
<EventID>65</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x2000000000000001</Keywords>
<TimeCreated SystemTime="2020-06-27T16:18:47.3669303Z" />
<EventRecordID>291</EventRecordID>
<Correlation />
<Execution ProcessID="5688" ThreadID="860" />
<Channel>Microsoft-Windows-AppModel-Runtime/Admin</Channel>
<Computer>DESKTOP-E6NN4IN</Computer>
<Security UserID="S-1-5-21-3346474396-2195920789-1777076811-1001" />
</System>
<EventData>
<Data Name="ErrorCode">87</Data>
<Data Name="PackageFullName">Windows</Data>
</EventData>
</Event>
Windows for home | Windows 10 | Performance and system failures
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
120 answers
Sort by: Oldest
-
Anonymous
2020-08-08T17:26:37+00:00 -
Anonymous
2020-08-09T10:34:01+00:00 Hi Prakhar,
I am having the same error. I was playing a game and suddenly my screen froze and then it just went to sleep. While system seems to be working fine. I had to restart the system. First I thought it had something to do with the game but now it is happening even when I am just at my home screen and not doing anything. it is now happening more often and I could not find any solution for this. Please help me with this issue.
-
Anonymous
2020-08-09T22:25:21+00:00 You may want to read this entire thread if you are running Windows 10 2004. You also may want to read the thread about using Rufus to create your 1909 bootable flash drive since the only "fix" is a clean install of Windows 10 1909.
Most likely anyone seeing this issue will say that a clean install of Windows 10 1909 is a total inconvenience.
-
Anonymous
2020-08-09T22:37:36+00:00 To clarify, if 2004 clean install of build 19041/19042 works with creating a local account?
Meaning, bypass the nag to log into your Microsoft account during installation?
If you do an upgrade from 1909 to 2004, no problem either?
This comes to mind: poor testing prior to the 2004 release since clean installs are prevalent, especially if you acquired a new computer that comes with 2004 pre-installed.
-
Anonymous
2020-08-10T02:29:52+00:00 I no longer get these errors after upgrading to 20H2 from 20H1 via the Windows Insider Beta Channel. Might not suit everyone, but it has worked for me. 20H2 has been, to date, as reliable as any ***official*** release of Windows 10.
Another observation (again, only in my case); on 20H1 I seemed to get more Event 65, AppModel-Runtime errors when another account was left logged in in the background. If only one person was logged in, no such errors occurred, nor was there any slowing down of my system.