none
The reason why error message AppModel-Runtime 69 keep showing on Event Viewer RRS feed

  • Question

  • Hi all.

    Not sure if I'm posting this in the right forum. Microsoft has so many forums (Answers, Docs, Technet, MSDN, and so on) that I may be posting in the wrong place. To the moderator, feel free to move this topic to the right site.

    First of all, I have to say that I'm having no problems with my PC at all, the system is running just fine. I just reached this point because I'm aiming to erase all the 'error' messages in the Event Viewer log (Windows 10).

    So, for anyone who entered in this crusade knows about the AppModel-Runtime error message that keeps showing in the log without a seamless proper reason. There are several topics on the net with people asking for this. The log message goes more or less like this: "Failed with 0x490 modifying AppModel Runtime status for package Microsoft.<package name> for user DESKTOP-ERQCEBP\<my username> (current status = 0x0, desired status = 0x20)."

    Well, I found a possible reason why this is happening (although I still don't know how to solve it), and I though I could share it with the Microsoft users in the forum to discuss this and maybe find a solution.

    I realised that this error occurs every time a Windows 10 app is installed, reinstalled or updated from the Windows Store. By analysing the logs in the Event Viewer and comparing it with the days the apps were installed or received updates in the Windows Store, you can see that the days and the number of occurrences this occurs match.

    It seems not all apps update results in a log event. However, every update that Windows registers in the Windows Store generate an AppModel-Runtime error log. You can check this by opening Windows Store, then in the upper-right corner of the screen, clicking on the three dots, then 'Downloads and Updates'. Then, in the left of the screen select the menu 'Downloads'.

    In that screen, every item listed there generates a AppModel-Runtime log event.

    More, it's even possible for you to generate yourself the log. All you need to do is go to the Windows 10 'Add/Remove Program' screen, select any Windows 10 app you have already installed (Calculator for instance), then click on it, click on 'Advanced Options' just bellow the app name, then click on the 'Restore' option. This will reinstall/redefine/restart the app. At the moment you do this, you will generate the log file.

    So, I think this is all I have to share about this problem. Does anyone have a solution to make ths log stop showing in the event viewer?



    • Edited by RSene Monday, January 20, 2020 10:27 AM
    Saturday, December 14, 2019 6:36 PM

All replies

  • Hi,

    >> "Failed with 0x490 modifying AppModel Runtime status for package Microsoft.<package name> for user DESKTOP-ERQCEBP\<my username> (current status = 0x0, desired status = 0x20)."

    In addition, here is a similar issue with yours, just for your reference, you can try the method mentioned in them:

    https://www.tenforums.com/software-apps/31600-event-id-69-a.html

    Note: This is a third-party link and we do not have any guarantees on this website. This is just for your convenience. And Microsoft does not make any guarantees about the content.

    Besides, kindly refer to the following steps:

    • Right click start buttonàchoose powershell (admin);
    • type SFC /scannow and press enter;
    • Once its completed, copy/paste this command into same window:
      Repair-WindowsImage -Online -RestoreHealth and press enter;
    • SFC fixes system files, second command cleans image files, re run SFC if it failed to fix all files and restart PC.

    Please check if it helps. We are looking forward to your reply~

    Have a nice day!

    Kiki


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, December 16, 2019 7:16 AM
  • Thanks for your reply.

    I run these two commands you mentioned, it seems to me they didn't find errors. I have here the results in images:

    SFC /scannow:

    PS C:\WINDOWS\system32> SFC /scannow

    Iniciando verificação de arquivos. O processo levará alguns minutos para ser concluído.

    Iniciando fase de verificação de verificação do sistema.
    Verificação 100% concluída.

    A Proteção de Recursos do Windows não encontrou nenhuma violação de integridade.
    PS C:\WINDOWS\system32>

    Repair-WindowsImage -Online -RestoreHealth: 


                                                                                                                             

    Windows PowerShell
    Copyright (C) Microsoft Corporation. Todos os direitos reservados.

    Experimente a nova plataforma cruzada PowerShell https://aka.ms/pscore6                                                  

    PS C:\WINDOWS\system32> Repair-WindowsImage -Online -RestoreHealth

    Path             :
    Online           : True
    ImageHealthState : Healthy
    RestartNeeded    : False

    PS C:\WINDOWS\system32>


    • Edited by RSene Saturday, January 18, 2020 12:55 PM
    Monday, December 16, 2019 8:34 PM
  • Hi.

    Today I checked Windows Store to see if it had new app updates, and the system updated four apps. As always, the event viewer generated new 'error' logs related to these app that were updated.

    Please, see the images below:

    Guess I'm out of luck here, right?

    • Edited by RSene Saturday, January 18, 2020 12:51 PM
    Wednesday, December 18, 2019 8:16 PM
  • Hi,

    Sorry for the reply delays.

    You can expedite verification by replying to this thread with your request.  https://social.msdn.microsoft.com/Forums/en-US/dc4002e4-e3de-4b1e-9a97-3702387886cc/verify-account-42?forum=reportabug

    Hope can help you. Have a nice day~

    Best regards,

    Kiki


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.


    Monday, December 23, 2019 8:50 AM
  • Hi. I did the request as instructed, and just recently I was verified. So this week I've edited my previous posts to include the images related to the problem.

    Wednesday, January 22, 2020 6:57 PM