What Is Event 65, AppModel-Runtime on Windows?

The “Event 65, AppModel-Runtime” error in the Event Viewer is common and can be frustrating due to its frequent appearance on PCs.

Luckily, you can easily remove it from your device with the right hacks. In this article, we’ll help you get the best solution for “Event 65, AppModel-Runtime” on your Windows 10/11 computer. So, keep reading to find out.

About Event 65, AppModel-Runtime on Windows

“Event 65, AppModel-Runtime” is a Windows 10/11 error that mostly occurs if you haven’t updated your Windows system. It may cause the computer to freeze or even crash. However, some users say that the error just pops up but does not cause any issues on their devices.

You are more likely to experience the “Event 65, AppModel-Runtime” error while gaming on your PC, and it usually displays the following description in the Event Viewer:

“Failed with 0x57 retrieving AppModel Runtime status for package Windows”

What Causes “Event 65, AppModel-Runtime” on Windows Computers?

This issue is mostly caused by factors such as:

• Outdated device drivers
• An outdated Windows system
• Poor configuration of full-screen optimization, focus assist, and variable refresh rate

How to Fix “Event 65, AppModel-Runtime” on Windows PCs

Before you apply any of the hacks we’ll discuss below, you need to create a restore point. Doing this will allow you to easily restore your machine’s health if things go wrong during the process. Although that’s unlikely to happen, it’s better to be safe than sorry.

Follow these steps to create a restore point:

1. Press the Windows + S shortcut keys to open the Windows search box and type in “create” (without quotes).
2. Click the Create a restore point result to open the System Properties page.
3. Select Create at the bottom, and then name your restore point. Tip: You could just use a date or a memorable name like “before making changes”.
4. Click Create.
5. You will see the “The restore point was created successfully” message when the process completes. Now, click the Close button.
6. Choose OK.

Let’s now jump into the best troubleshooting methods to remove “Event 65, AppModel-Runtime” from your PC.

Hack 1: Update Windows

Since an outdated Windows system is among the primary causes of the “Event 65, AppModel-Runtime” error, you should first update it before moving on to other solutions.

Here is how to go about it:

1. Press the Windows + I keyboard combination to launch the Settings application.
2. Open Update & Security, and then click the Check for updates button on the right pane.
3. Wait for Windows to check for the available updates and download them.
4. Restart your computer to install the updates.
5. Now, check if the problem reoccurs.

Hack 2: Update the Graphics Driver

Your video games require an updated graphics driver to provide a fantastic gaming experience and keep up with high graphics settings.

You can easily update the graphics driver by following these instructions:

1. Use the Win + X shortcut to open the Quick Link menu.
2. Choose Device Manager.
3. When a new window opens, double-click Display adaptors to expand it.
4. Right-click on the displayed graphics driver and choose Update driver.
5. Select Search automatically for drivers, and then follow any further instructions to install the updated driver.
6. Restart your Windows PC.

You could also use a professional driver updater to help ensure your device drivers always stay updated. We highly recommend Outbyte Driver Updater. This competent tool scans your PC for outdated drivers and lets you update them in a single click. Additionally, Outbyte Driver Updater only installs manufacturer-recommended driver versions for your computer to help you avoid running into compatibility issues.

Hack 3: Disable Full-Screen Optimization for the Affected App

The Windows 10/11 full-screen optimization feature allows you to play video games on a borderless full screen and boost your PC’s performance. However, this feature might sometimes trigger the “Event 65, AppModel-Runtime” error. So, deactivating it could help eliminate the error.

Here’s how to do so:

1. Right-click on the affected app’s shortcut on your desktop and select Properties.
2. Open the Compatibility tab.
3. Under the Settings section, select the option that says “Disable full-screen optimisations”.
4. Click on the Apply button, and then choose OK.
5. Restart your PC and check if the issue was solved.

If you are still getting “Event 65, AppModel-Runtime”, then proceed to the next hack.

Hack 4: Disable Variable Refresh Rate

The Variable Refresh Rate (VRR) feature enables you to minimize screen tearing when gaming in full screen. However, it can sometimes affect your game’s proper display, hence the error.

Use this simple guide to disable Variable Refresh Rate:

1. Hit the Windows button and click on the Settings icon.
2. Go to System.
3. Scroll down the right pane and select the Graphics settings link at the bottom.
4. Under the Variable refresh rate section, click on the toggle button to disable VRR.
5. Reboot the PC, and then check if the error reoccurs.

Note: You will see the Variable refresh rate toggle-button only if:

• You have Windows 10 version 1903 or later.
• You have a GPU with at least WDDM (Windows Display Driver Model) 2.6 drivers that support FreeSync/G-SYNC/Adaptive-Sync and Variable Refresh Rate.
• Your Windows PC has a FreeSync, Adaptive-Sync, or G-SYNC capable monitor.

Hack 5: Perform an SFC Scan

Running an SFC scan allows you to check for corrupted system files that may be causing “Event 65, AppModel-Runtime” and automatically repair them.

These steps will guide you through performing an SFC scan:

1. Press the Windows key and type in “cmd” (without quotes).
2. Choose Run as administrator on the right menu pane.
3. Select Yes on the UAC (User Account Control) confirmation prompt.
4. When the CMD window appears, type “sfc /scannow” (no quotes).
5. Hit Enter, and then wait for the process to complete.
6. Restart your PC.

Conclusion

We hope the “Event 65, AppModel-Runtime” error is now a thing of the past on your Windows 10/11 machine. If you have additional tips regarding how to effectively resolve this problem, share them with us in the comments section below.