运行时错误(Runtime errors)发生在运行应用程序或软件时。根据原因,有许多类型的运行时错误。这些错误会冻结或使程序崩溃。有时,运行时错误会使系统崩溃。收到运行时错误后,您可以在Windows 事件查看器(Windows Event Viewer)中查看其详细信息。我们已经了解了如何修复AppModel 运行时错误 57、87、490、21(AppModel Runtime Errors 57, 87, 490, 21)等。现在在本文中,我们将描述AppModel 运行时错误 65、69 和 79(AppModel Runtime errors 65, 69, and 79)的可能解决方案。
修复 AppModel 运行时错误 65
许多用户报告说他们在运行 3D 加速程序(如游戏)时收到事件 ID 65(Event ID 65) 运行时错误。(Runtime)如果您在系统上遇到同样的问题,以下解决方案可能会对您有所帮助:
- 运行 Windows 应用疑难解答。
- 重新安装运行时文件。
- 禁用游戏的全屏优化。
- 禁用对焦辅助。
1]运行Windows应用疑难解答
Windows App Troubleshooter是一个 Windows 内置工具。运行此工具可以帮助您解决错误。要运行它,请转到Settings > Update & Security > Troubleshoot。现在,单击右侧的其他疑难解答。(Additional troubleshooters)向下滚动(Scroll)并单击Windows 应用商店应用程序(Windows Store Apps),然后单击运行疑难解答(Run the troubleshooter)。
2]重新安装运行时文件
有时,由于缺少Visual C++库,您可能会收到此错误。在这种情况下,重新安装运行时文件可能会有所帮助。执行以下步骤:
- 启动控制面板并转到Programs and Features > Uninstall a program。
- 向下滚动(Scroll)列表并卸载Microsoft Visual C++ Redistributable包。
- 访问microsoft.com并下载最新的 Visual C++ 包并安装它们。
- 安装库后,重新启动系统。
有帮助吗?
3]禁用(Disable)游戏的全屏优化
一些用户报告说,禁用游戏中的全屏优化功能有助于他们修复错误。
要禁用此功能,请按照以下说明进行操作:
- 右键单击(Right-click)游戏的可执行文件 ( .exe ) 并选择属性(Properties)。
- 在兼容性(Compatibility)选项卡下,您将找到禁用全屏优化(Disable fullscreen optimizations)选项。
- 取消选中该框,单击应用(Apply),然后单击确定以保存设置。
阅读(Read):在 Windows 中禁用脚本错误和运行时错误消息。
4]禁用对焦辅助
根据一些用户的说法,当他们在Windows 10上禁用(Windows 10)Focus辅助时,该问题已得到解决。如果您已启用此功能,请考虑禁用它并查看它是否有帮助。
您可以直接从通知(Notifications)面板禁用它。单击(Click)任务栏右上角的通知图标,然后单击(Notifications)焦点(Focus)辅助图标将其禁用。或者,您也可以从“设置”(Settings)应用中禁用它。转到Settings > System > Focus assist,然后单击关闭单选按钮。
修复 AppModel 运行时错误 69
有时损坏的应用程序包会触发AppModel 运行时(AppModel Runtime)错误 69。这通常发生在应用程序的安装或更新过程可能由于突然断电而终止时。此错误与某些特定应用程序或Microsoft Store相关联。如果您在计算机上收到此错误,以下解决方案可能会对您有所帮助:
- 运行Windows 应用商店应用程序疑难解答(Windows Store Apps Troubleshooter)。
- 重置 Windows 应用商店。
- 删除半更新或半安装的应用程序并重新安装它们。
1]运行(Run)Windows应用商店应用程序疑难解答(Windows Store Apps Troubleshooter)
本文前面介绍了运行Windows 应用商店应用程序疑难解答的步骤。(Windows Store Apps Troubleshooter)请按照以下步骤操作,看看是否有帮助。
2]重置Windows应用商店
有时,由于Windows 应用商店(Windows Store)组件损坏,会发生事件 ID 69 (Event ID 69) AppModel 运行时错误。(AppModel Runtime)在这种情况下,重置 Store 会有所帮助。为此,请按键盘上的Windows + R键以启动“运行”(Run)对话框。在此处键入wsreset.exe并按Enter。不要(Don)害怕重置Windows 应用商店(Windows Store),因为它不会删除您的任何应用数据。
阅读(Read):如何修复 Windows 10 上的运行时错误 217(How to fix Runtime Error 217 on Windows 10)。
3]删除(Remove)半更新或半安装的应用程序并重新安装它们
应用程序安装或更新过程的终止可能会损坏它。在这种情况下,用户在启动该特定应用程序时可能会收到AppModel 运行时错误 69。(AppModel Runtime)请按照下面列出的过程来消除此错误:
- 取得 WindowsApps 文件夹的所有权(Take ownership of the WindowsApps folder)。您将在
C:\Program Files\WindowsApps
位置找到此文件夹。 - 现在,打开WindowsApps文件夹并查找导致问题的应用程序的文件夹名称。例如,人员(People)应用程序的文件夹是在名称Microsoft.People下创建的。
- 以管理员身份运行 PowerShell(Run PowerShell),键入以下命令,然后按Enter。
get-appxpackage *Microsoft.People* | remove-appxpackage
在上述命令中,将“ Microsoft.People ”字符串替换为导致问题的应用名称或字符串。重启你的电脑。重新启动后,访问Microsoft Store并再次安装特定应用程序。
完成后,将 MicrosoftApps 文件夹的所有权还给 TrustedInstaller。
修复 AppModel 运行时错误 79
AppModel 运行时(AppModel Runtime)错误 79的原因是系统文件损坏或应用程序组件丢失/损坏。以下解决方案可能会帮助您修复此错误:
- 运行 SFC 和 DISM 扫描。
- 在Windows PowerShell(Windows PowerShell)中执行命令。
1]运行SFC和DISM扫描
SFC(系统文件检查器(System File Checker))是一个实用程序,可以扫描和修复系统中损坏的文件。以管理员身份打开命令提示符(Command Prompt)sfc /scannow
,键入,然后按Enter。您应该等到扫描完成。如果SFC扫描无法解决问题,请以管理员身份再次打开命令提示符,粘贴以下命令,然后按(Command Prompt)Enter:
dism /online /cleanup-image /restorehealth
2 ]在(] Execute)Windows PowerShell中执行命令
以管理员身份启动Windows PowerShell ,粘贴以下命令,然后按 Enter:(Windows PowerShell)
ExecutionPolicy Unrestricted -Command "& {$manifest = (Get-AppxPackage Microsoft.Windows.Photos).InstallLocation + '\AppxManifest.xml' ; Add-AppxPackage -DisableDevelopmentMode -Register $manifest}"
在上述命令中,您必须将字符串“ Microsoft.Windows.Photos ”替换为您的Broken应用程序。我们在这里写了这个字符串只是为了举例。假设,如果损坏的应用程序是People,您必须输入“ Microsoft.People。”您怎么会知道?在您的计算机上访问以下路径并搜索损坏的应用程序的名称:
C:\Users\username\AppData\Local\Packages
就是这样。我们希望本文能帮助您解决问题。
相关帖子(Related post):修复 .NET 运行时错误 1026,异常代码 c00000fd(Fix .NET Runtime Error 1026, Exception code c00000fd)。
Fix AppModel Runtime Errors 65, 69, and 79
Runtime errors occur at the time of running an app or software. Depending on the cause, there are many types of runtime errors. These errors freeze or crash a program. Sometimes, a runtime error crashes the system. After getting a runtime error, you can view its details in Windows Event Viewer. We have seen how to fix AppModel Runtime Errors 57, 87, 490, 21, etc. – Now in this article, we will describe the possible solutions for AppModel Runtime errors 65, 69, and 79.
Fix AppModel Runtime error 65
Many users have reported that they received Event ID 65 Runtime error on running 3D accelerated programs like games. If you are experiencing the same issue on your system, the following solutions may help you:
- Run Windows App Troubleshooter.
- Re-install the runtime files.
- Disable fullscreen optimization for games.
- Disable the Focus assist.
1] Run Windows App Troubleshooter
Windows App Troubleshooter is a Windows built-in tool. Running this tool may help you solve the error. To run it, go to Settings > Update & Security > Troubleshoot. Now, click on the Additional troubleshooters on the right side. Scroll down and click Windows Store Apps, then click Run the troubleshooter.
2] Re-install the runtime files
Sometimes you may get this error due to missing Visual C++ libraries. In this case, re-installing the runtime files may help. Go through the following steps:
- Launch Control Panel and go to Programs and Features > Uninstall a program.
- Scroll down the list and uninstall Microsoft Visual C++ Redistributable packages.
- Visit microsoft.com and download the latest Visual C++ packages and install them.
- After installing the libraries, restart your system.
Did it help?
3] Disable fullscreen optimization for games
Some users have reported that disabling the fullscreen optimization feature in games helped them fix the error.
To disable this feature, follow the instructions given below:
- Right-click on the executable file (.exe) of the game and select Properties.
- Under the Compatibility tab, you will find the Disable fullscreen optimizations option.
- Uncheck the box, click Apply, and then OK to save the settings.
Read: Disable Script Errors & Runtime Error Messages in Windows.
4] Disable the Focus assist
According to some users, the issue was fixed when they had disabled the Focus assist on Windows 10. If you have enabled this feature, consider disabling it and see if it helps.
You can disable it directly from the Notifications panel. Click on the Notifications icon on the right corner of the taskbar and click the Focus assist icon to disable it. Alternatively, you can also disable it from the Settings app. Go to Settings > System > Focus assist and click the Off radio button.
Fix AppModel Runtime error 69
Sometimes corrupt app packages trigger AppModel Runtime error 69. This generally happens when the installation or update process of an app terminates probably due to a sudden power failure. This error is associated with some specific apps or with Microsoft Store. If you are getting this error on your computer, the following solutions may help you:
- Run the Windows Store Apps Troubleshooter.
- Reset the Windows Store.
- Remove the semi-updated or semi-installed apps and re-install them.
1] Run the Windows Store Apps Troubleshooter
The steps to run Windows Store Apps Troubleshooter are described earlier in this article. Follow these steps and see if it helps.
2] Reset the Windows Store
Sometimes, Event ID 69 AppModel Runtime error occurs due to the corrupt Windows Store component. In this case, resetting the Store can help. To do this, press Windows + R keys on your keyboard to launch the Run dialog box. Type wsreset.exe there and hit Enter. Don’t be afraid of resetting the Windows Store, as it will not delete any of your app data.
Read: How to fix Runtime Error 217 on Windows 10.
3] Remove the semi-updated or semi-installed apps and re-install them
The termination of the installation or update process of an app may corrupt it. In this case, the user may get an AppModel Runtime error 69 on launching that specific app. Follow the procedure listed below to get rid of this error:
- Take ownership of the WindowsApps folder. You will find this folder at
C:\Program Files\WindowsApps
location. - Now, open the WindowsApps folder and look for the folder name of the app that is causing the problem. For example, the folder for the People app is created under the name Microsoft.People.
- Run PowerShell as administrator, type the following command, and press Enter.
get-appxpackage *Microsoft.People* | remove-appxpackage
In the above command, replace “Microsoft.People” string with the app name or string that is causing the problem. Restart your computer. After restart, visit the Microsoft Store and install the particular app again.
When you are done, give the MicrosoftApps folder’s ownership back to the TrustedInstaller.
Fix AppModel Runtime error 79
The cause of AppModel Runtime error 79 is corrupted system files or missing/broken application components. The following solutions may help you fix this error:
- Run SFC and DISM scan.
- Execute a command in Windows PowerShell.
1] Run SFC and DISM scan
SFC (System File Checker) is a utility that scans and repairs the corrupted files in the system. Open the Command Prompt as an administrator, type sfc /scannow
, and press Enter. You should wait till the scanning gets completed. If the SFC scan doesn’t fix the issue, open the Command Prompt again as an administrator, paste the following command, and press Enter:
dism /online /cleanup-image /restorehealth
2] Execute a command in Windows PowerShell
Launch Windows PowerShell as an administrator, paste the following command, and press Enter:
ExecutionPolicy Unrestricted -Command "& {$manifest = (Get-AppxPackage Microsoft.Windows.Photos).InstallLocation + '\AppxManifest.xml' ; Add-AppxPackage -DisableDevelopmentMode -Register $manifest}"
In the above command, you have to replace the string “Microsoft.Windows.Photos” with your Broken app. We have written this string here just for an example. Let’s say, if the broken app is People, you have to type “Microsoft.People.” How could you know that? Visit the following path on your computer and search the name of your broken app:
C:\Users\username\AppData\Local\Packages
That’s it. We hope this article helped you solve the problem.
Related post: Fix .NET Runtime Error 1026, Exception code c00000fd.