Share via

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 No comments

120 answers

Sort by: Most helpful
  1. Anonymous
    2020-09-23T22:17:37+00:00

    Did update to 20H2 by insider... Nope... I guess the error has different types of severity, 

    I am sending a lot of feedback to Microsoft... On the internet I am watching a lot of people with the same problem... with brand new PC.

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2020-09-09T15:08:29+00:00

    1 more, I've been dragging these problems since December 2019. I can't find a solution that works. I have tried hundreds of solutions from all over the internet. All games with directx 12 crash.

    If one day I go down to hell, I already know what my torture will be ... my pc, windows 10 and directx 12

    Thx microsoft, thx nvidia for your wonderful products

    : /

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2020-08-27T04:12:27+00:00

    Hello 

    I was playing a game today and it froze and audio stuttering ensured and checking the event view (Event ID 65) inexorably led me here.  For me, the only instances of this error were within the last 24 hours so I was able to isolate the cause which was enabling Focus assist - automatic rules - when I'm playing again (i.e. turning it "on").  I turned it back off and haven't had this error since.  

    I'm running win 10 Home  v 2004 OS build 19041.450 with windows feature experience Pack 120.2212.31.0

    cheers

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2020-07-21T15:15:34+00:00

    Hi Rao - unfortunately, rolling back to 451.48 did not resolve this issue for me.  I have $1400 worth of graphics cards that are essentially good for Folding @ Home at this point, and useless for any other 3D software.  Given that Prakhar and Microsoft seem to have abandoned this thread and this issue weeks ago, I am starting to think that the best long-term solution will be to switch to Linux.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  5. Anonymous
    2020-06-30T15:23:50+00:00

    Hello Prakhar,

    As requested I rebooted the machine in Safe Mode and Clean Boot.  I did not receive BSODs in either mode.  However, the error did occur in Clean Boot.

    I ran the DISM tool, the restore operation completed successfully, and sfc did not find any issues.

    I will let you know if the error occurs after the DISM restore.

    Thanks!

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments