Let’s discuss how to fix Intune Agent Crash Access Violation Error 0xc0000005. The Intune Management Agent may sometimes crash due to an Access Violation error (0xc0000005). This error happens when the agent tries to access memory it shouldn’t, often after a recent update.
After updating to version 1.95.103.0 the Intune Management Agent Microsoft.Management.Services.IntuneWindowsAgent.exe started crashing repeatedly. This problem did not occur in earlier versions such as 1.94.153.0 showing that the crashes are specific to the new release.
The crashes often point to WindowsPackageManager.dll_unloaded version 1.26.430.0 as the cause. The “_unloaded” part means the crash might happen after the DLL is removed from memory, possibly because of timing problems or cleanup issues while the agent is handling packages.
Besides WindowsPackageManager.dll, the crashes also involve wintypes.dll, icu.dll, ucrtbase.dll, and ntdll.dll. These are common Windows system files. Their presence in the crash logs shows that the problem is not limited to one file and may happen because of how the Intune Agent interacts with Windows components.
Table of Contents
How to Fix Intune Agent Crash Access Violation Error 0xc0000005
The Intune Management Agent often crashes with an error code 0xc0000005, which is an Access Violation. When the agent tried to use a part of the memory, it was not allowed to access. The issue usually comes from how the agent or one of its related components handles memory. The issue was reported by suettaM in the Tech Community channel.
| Version | Devices | Crashes | Devices with crashes | Time between crashes |
|---|---|---|---|---|
| 1.95.103.0 | 1016 | 3459 | 582 (57%) | 14h 30m |
| 1.95.104.0 | 612 | 0 | 0 (0%) | 365d |
| 1.94.153.0 | 760 | 0 | 0 (0%) | 365d |
| 1.94.106.0 | 27 | 0 | 0 (0%) | N/A |
- How to Fix Intune Error 65000 when Deploying Intune Policy using Settings Catalog
- Fix Intune Enrollment Errors 0x80180014 80180003 Unknown Win32
- Troubleshoot MDM Enrollment Error Code 80180004
- FIX Intune Error 0x80180013
- How to Start Troubleshooting Intune Issues | Fix Intune Issues with Easy Steps MEM
Other Error Codes Besides 0xc0000005
The Intune Management Agent has also shown other error codes besides 0xc0000005. These errors suggest problems with memory handling and possible corruption introduced in version 1.95.103.0. The below list helps you to show more details.
- 0xc0000409 (Stack buffer overrun) – Memory corruption from exceeding buffer limits.
- 0xc0000374 (Heap corruption) – Improper memory allocation or freeing within the process.
Crashes Do Not Happen in a Consistent Way
The crashes can occur at different times. They are most commonly seen during application management tasks such as installing, updating, or evaluating apps deployed through Intune. This indicates that the crashes are likely related to package processing and app deployment operations.
New Connections in Version 1.95.103.0
The updated Intune Agent in version 1.95.103.0 makes additional network connections that were not seen in the previous version. These include Teams endpoints, OCSP/CRL checks, and agents.msub01.manage.microsoft.com.
Possible Root Cause of the Issue
The crashes in version 1.95.103.0 may be caused by problems in how the agent handles memory or cleans up dependencies. Issues like DLL unloading, access violations, and heap corruption point to a regression in the new version. This could be related to how the agent works with Windows Package Manager APIs or other system libraries during app management tasks.
The crashes occur repeatedly and during app-related tasks, administrators may face inconsistent app deployments, failed compliance checks, and increased troubleshooting overhead. Frequent agent restarts can also degrade performance and reliability across managed devices.
Workaround for the Issue
To fix the Intune Management Agent crashes in version 1.95.103.0, you should act carefully and quickly. Going back to a stable version, gathering crash logs, and watching for updates can help keep the system stable. The below list helps you to show more details.
- Rollback to version 1.94.153.0 if possible, since it does not have the crashing issue.
- Open a support ticket with Microsoft and provide crash dumps and event logs for further investigation.
- Monitor for hotfixes or newer releases of the Intune Management Agent, as Microsoft may release a fix quickly.
- Limit large-scale app deployments temporarily to reduce the frequency of crashes until a stable build is available.
Need Further Assistance or Have Technical Questions?
Join the LinkedIn Page and Telegram group to get the latest step-by-step guides and news updates. Join our Meetup Page to participate in User group meetings. Also, join the WhatsApp Community to get the latest news on Microsoft Technologies. We are there on Reddit as well. You can see these details have been discussed in Reddit and other social media forums.
Author
Anoop C Nair has been Microsoft MVP for 10 consecutive years from 2015 onwards. He is a Workplace Solution Architect with more than 22+ years of experience in Workplace technologies. He is a Blogger, Speaker, and Local User Group Community leader. His primary focus is on Device Management technologies like SCCM and Intune. He writes about technologies like Intune, SCCM, Windows, Cloud PC, Windows, Entra, Microsoft Security, Career, etc.