Event 65, AppModel-Runtime

Anonymous
2020-06-27T16:33:18+00:00

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.

0 comments

120 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2020-07-28T02:46:50+00:00
    1. I didn't even think to reinstall an older version since I figured the issue was typical Windows corruption; my last reinstall was three or so years ago. Then the issue occurred again, this time leading to a BSOD, and I saw multiple instances of Event 65 in Event Viewer. Entered that into Google and found this thread.

    Thanks for the advice. I may reinstall 1909 yet if I can find the patience.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-07-27T22:09:04+00:00

    Hey MisterFlamp - speaking only for me, I did a clean reinstall of 2004.  I have a 1909 USB flash drive ready to go, so guess what my weekend project is, lol

    Fortunately for me, I have multiple drives and a NAS where I can move the important stuff. It's still a pain in the ****, though.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-07-27T21:42:42+00:00

    Which Windows 10 release did you re-install?

    If it was 2004, then that might explain still seeing the issue.

    Suggest doing a clean install from a bootable Windows 10 1909 flash drive and delete the Windows partitions for the install drive.

    Yes, it means re-installing apps and reconfigure. Total PITA if you only have one drive.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-07-27T17:38:10+00:00

    The AppModel runtime errors are gone for me after a clean install of Windows 10. I also installed the latest patches prior to testing.

    I tried the stock NVIDIA drivers, 432.00 with no hitches (due to the bug that is) and no crashes to reboot.

    I tested F.E.A.R. and Doom 2016. Alt-tabbed to the desktop and back to the full screen games.

    No AppModel runtime errors for these.

    I updated to the latest NVIDIA drivers 451.67 for my GTX 1080.

    No frame skipping and crashes again...

    Checked Event Viewer - no AppModel runtime errors due to this issue.

    Conclusion: Stick w/ Windows 10 1909 and do not upgrade to 2004. However, this may not fit others' issues. Certainly does not seem at all related to NVIDIA's drivers.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  5. Anonymous
    2020-07-27T15:52:44+00:00

    Want to add my voice to the list of those experiencing this issue. Did a full Windows reinstall hoping it would resolve the problem but it's still here. That was a fun waste of an afternoon.

    It's absurd that each Windows update introduces yet another new issue. In practice I would opt out of these updates until they're more polished (presuming such a state is even achievable by MS), but I've been downloading them all hoping to see a fix to the problem the last one introduced.

    Then there's radio silence in this thread -- not even a "we acknowledge the issue and are working on it" -- only useless directions like "ignore the errors." Hard to ignore your computer slowing to a crawl until you have no choice but to hard reset, BSOD, etc.

    If I wasn't a gamer I would drop Windows so hard.

    /rant

    Will keep watch on this thread in hopes of an actual resolution.

    Was this answer helpful?

    0 comments