Issue
An Automox command exiting with error code 255, -1073741819, or 0xC0000005 may indicate a configuration issue with the local computer.
This is most often seen in the GetSoftware command from an Automox agent scan, but these errors can also be seen in Worklet or policy results.
If the GetSoftware scan is failing to run, the list of installed Software will not update to show what is installed or missing.
Cause
Error 0xC0000005 is an Access Violation exception that Windows shows when script code tries to access invalid memory: Microsoft - NTSTATUS Values
This is most often seen when an Endpoint Protection Platform (EPP) software (e.g. SentinelOne) attempts to block Automox Agent code from executing.
Resolution
It may be necessary to add EPP exclusions to prevent interference with Automox scripts. This involves excluding paths where Automox code executes.
- Configuring a SentinelOne Exception for Automox
- Prevent Microsoft Defender from Blocking Automox on Windows
- Globally Trust-listing Automox Through EPP Application Control
- Location of Files Required By Automox
If there is already a folder exception in place for Automox, the issue may be a temporary Windows issue:
- Restart Your Computer: A simple restart can sometimes resolve temporary issues.
-
Run System File Checker (SFC):
- Open Command Prompt as Administrator.
- Type sfc /scannow and press Enter to scan and repair corrupted system files.
- Check for Memory Issues: Use the Windows Memory Diagnostic tool or third-party tools, such as Memtest86, to check for memory problems.
- Check for Malware: Run a full system scan with antivirus software to detect and remove malware.