Are you encountering AppModel Runtime Errors with codes 65, 69, and 79 on your Windows PC? A large number of Windows users have encountered these runtime error codes in the Event Viewer when they face issues with any program or the system itself. You will see a runtime error whenever you try to install, update or run an application on your system. In this article, we have discussed solutions to fix each of the above error codes.

 

Case 1 – Runtime Error Code 65

Error code 65 is generally seen when running applications that use graphics hardware like games.

 

Fix 1 – Use the Windows Troubleshooter

 

1. Use the Windows and R key combination to open the Run dialog.

2. Type ms-settings:troubleshoot to open the System Troubleshoot page.

 

 

3. In the Troubleshoot window, click on Other troubleshooters.

 

 

4. In the Other troubleshooter’s window, scroll down and locate Windows Store Apps.

5. Click on the Run button next to Windows Store Apps.

 

 

6. The Windows Store Apps troubleshooter starts detecting problems.

7. Wait for the troubleshooting to complete. If there are any fixes suggested by the troubleshooter then apply them.

8. Once the troubleshooting process finishes, reboot your PC.

9. On startup, check whether the runtime error occurs repeating the same set of steps that caused the error previously.

 

Fix 2 – Reinstall the Latest Visual C++ Files

 

1. Open Run using the Window and R keys simultaneously.

2. Type appwiz.cpl to open Programs & Features.

 

 

3. In the list of applications, look for Microsoft Visual C++ Redistributable Packages.

4. Right-click on the Visual C++ Package and choose Uninstall. Uninstall all the Visual C++ Redistributable Packages in the list.

 

 

5. Once the uninstallation is complete, restart your system.

6. Visit this link to download the latest version of Visual C++.  Install the packages using the executable downloaded and follow the on-screen instructions.

7. Reboot your PC after you finish the installation. Check if the runtime error is resolved.

 

Fix 3 – Disable Fullscreen Optimization

 

1. Locate the executable of the application/game causing this error for you.

2. Right-click on the exe file and choose Properties.

 

 

3. Go to the Compatibility tab.

4. Check the box associated with Disable fullscreen optimization under the Settings group.

5. Click on Apply and then on OK to save the changes.

 

 

6. Restart your computer and check if the problem is solved.

 

 

Fix 4 – Disable Focus Assist

 

1. Press Windows + I to open Settings.

2. Select System in the left panel.

3. On the right side, click on Focus assist.

 

 

4. Select the Off radio button to turn off the Focus assist setting.

 

 

5. Now check if the runtime error still occurs or not.

 

 

Case 2 – Runtime Error Code 69

 

You will see a runtime error with code 69 in cases when any application setup or update is aborted due to power outages. Generally, it is seen with such applications or the Store itself. Before trying the fixes for this error code try Fix 1 mentioned above for error code 65.

 

Fix 1 – Reset Microsoft Store

 

1. Press Windows + R to open the Run box.

2. Type wsreset to reset Microsoft Store.

 

 

3. Now a command prompt opens.

4. Wait for some time for the reset process to clear the Store’s cache. Once completed, Microsoft Store will open.

5. Try installing or updating new applications and check if the runtime error is resolved.

 

Fix 2 – Remove and Reinstall the Corrupt Applications

 

You need to remove and reinstall the application that has been corrupted while performing an update or installation following the steps below.

Step A: Change the Ownership of the WindowsApps folder

 

1. Go to C:\Program Files.

2. Right-click on WindowsApps folder and choose Properties.

 

 

3. Go to the Security tab and click on the Advanced button at the bottom.

 

 

4. In the Advanced Security Settings for WindowsApp, click on Continue to make changes with administrative rights.

 

5. Now you will see the current owner with a link Change next to Owner. Click on Change.

 

 

6. In the Select User or Group window, click on Advanced.

 

 

7. Click on the Find now button to see the list of all users and groups on the system.

8. Select the Users account in the list to whom the ownership needs to be granted. Click on OK.

 

 

9. Finally click on OK again to change the ownership.

 

 

10. Now you will see that the user has been changed in the Advanced security settings window.

11. Check the option Replace owner on sub containers and objects.

12. Click on Apply and then on OK.

 

 

13. Once the ownership is transferred, you need to give full control of the folder to your account. Repeat Steps 1 – 3 above.

14. Choose the user account under the column Principal and then click on Add button.

 

 

15. In the new window, click on Select a principal.

 

 

16. Now click on Advanced.

 

 

17. In the Select User or group window, click on Find Now.

18. Choose Users in the list that appears. Click on OK.

 

 

19. Again click on OK to add this object.

20. In the Permission Entry for WindowsApps window, check the box associated with Full control under Basic permissions.

 

 

21. Click on OK.

22. In the Advanced security settings window, click on Enable inheritance. Click on Apply and then on OK.

 

 

 

Step B: Remove and Install the Corrupt Application

 

1. Go to the WindowsApps folder. Find the folder name of the application that is giving this runtime error.

 

 

2. Open Run (Windows + R).

3. Type powershell and press Shift + Ctrl + Enter to open PowerShell as administrator.

 

 

4. Enter the command below.

Get-AppxPackage *Microsoft.People* | Remove-AppxPackage

Note: Replace Microsoft.People with the name of the application that is a cause for this error.

 

 

5. Reboot your system. After startup, open Microsoft Store and install the application that was removed. Check if the problem is resolved.

6. Once you complete this, change the ownership of WindowsApps folder to TrustedInstaller.

• Follow Steps 1 – 5 mentioned above in A.
• In Select user or group window, type NT Service\TrustedInstaller in the text box.
• Click on Check Names button to validate the object name entered.
• Click on OK and then Apply to get the changes into effect.

 

 

 

 

Case 3 – Runtime Error Code 79

 

Fix 1 – Perform an SFC and DISM Scan

 

1. Use the Windows and R key combination to open Run.

2. Type cmd and press Ctrl + Shift + Enter.

 

 

3. Type the command below and hit Enter.

 sfc /scannow

 

4. Wait for the scan to finish. Check if the issue is fixed.

5. If the problem still persists, open Command Prompt again as admin using Steps 1 and 2 above.

6. Type the following command and press Enter.

dism /online /cleanup-image /restorehealth

 

 

7. After the command executes, open the application and check if the runtime error still exists.

 

Fix 2 – Run a Command in PowerShell

 

1. Open Run. Type powershell and press Ctrl + Shift + Enter to open PowerShell as admin.

 

 

2. Copy and paste the command given below

ExecutionPolicy Unrestricted -Command "& {$manifest = (Get-AppxPackage Microsoft.Windows.Photos).InstallLocation + '\AppxManifest.xml' ; Add-AppxPackage -DisableDevelopmentMode -Register $manifest}"

Note: Replace Microsoft.Windows.Photos with the application that is causing the runtime error. To know the name of the application, go to the location %localappdata%\Packages in your File Explorer.

3. Now open the application and check if the error is resolved.

Thanks for reading.

We hope this article has been informative enough to clear the runtime errors 65, 69, and 79 respectively. Comment and let us know if these fixes worked for you.