🆘Error code reference

This document provides instructions on interpreting error codes and locating their descriptions in the Scappman error code table at the bottom of the page.

How to read Error Codes

When troubleshooting issues related to Intune and PSADT (PowerShell Application Deployment Toolkit), it's essential to understand the format of the error codes. These codes are often presented in Hexadecimal (Hex) format, which means they may look like a series of alphanumeric characters prefixed by 0x. For example, an error code might appear as 0x8007EA6C, where 0x8007 is a generic prefix, and EA6C is the actual error code in hexadecimal.

How to Convert Hexadecimal to Decimal

When you encounter an error code in Hexadecimal format, it is often prefixed by a generic value like 0x8007. To properly interpret and troubleshoot the error, you need to focus on the remaining part of the error code after removing the prefix.

Step-by-Step Conversion Process

1. Split the Hexadecimal Code: The error code may begin with a prefix like 0x8007 (a common Microsoft prefix) followed by a specific hexadecimal value that represents the actual error. For example, if the error code is 0x8007EA6C, you need to split the prefix and focus on the remaining part:

   • Prefix: 0x8007

   • Remaining Value: EA6C

   The prefix 0x8007 is generic and can be ignored for troubleshooting purposes.

2. Convert the Remaining Hexadecimal Value to Decimal: After removing the prefix, convert the remaining hexadecimal value (e.g., EA6C) to decimal. You can use a calculator or an online tool to convert EA6C from hexadecimal to decimal. For example:

   • EA6C in hexadecimal is 60012 in decimal.

   In this case, the hexadecimal error code 0x8007EA6C corresponds to the decimal code 60012

3. Compare the Decimal Code to the Table: Once you have the decimal value (60012), compare it to the list of known error codes in our table below to determine the specific issue.

Example Breakdown:

• 0x8007EA6C (system-prepended) → 0xEA6C (hexadecimal) → 60012 (decimal)

---

Common Prefixes Used by Microsoft Intune

Microsoft Intune often uses standard prefixes to represent different types of errors or categories of issues. These prefixes can help you quickly identify the nature of the error. Here are a few common prefixes and their meanings:

Prefix	Meaning
0x8007	Microsoft Intune and System Errors Generic error codes used by Intune and Windows update processes.
0x87D1	Deployment Errors Used in Intune application deployment failures, especially related to app installation or update issues.
0x800F	Feature and Configuration Errors Typically related to the configuration of features, settings, or specific components failing to install or configure.
0x8024	Windows Update Errors Often seen when there are issues with updating the operating system or applications through Intune or Windows Update.
0x800B	Security and Certificate Errors Related to issues with certificates, security policies, or authorization failures.

---

Scappman Error Codes Table

To assist with troubleshooting, we've compiled a table listing common error codes with their Decimal and Hexadecimal equivalents. You can look up the error code in this table

Decimal Code	Hexadecimal Code	Description
60001	0x0000EA61	PSADT failure exit code
60002	0x0000EA62	Missing file
60003	0x0000EA63	The function [${CmdletName}] requires the toolkit to be running with Administrator privileges if the [-RunLevel] parameter is set to 'HighestAvailable'.
60004	0x0000EA64	Failed to load assembly
60005	0x0000EA65	Error in displaying the Installation Prompt
60007	0x0000EA67	Failed to export the scheduled task XML file [$xmlSchTaskFilePath]
60008	0x0000EA68	Module [$moduleAppDeployToolkitMain] failed to load
60009	0x0000EA69	No logged-on user detected
60012	0x0000EA6C	The user selected Defer/Postpone when prompted to close the app and update
70001	0x00011111	The user selected No when prompted to close the app and update (Specific applications only)
9000	0x00002328	Post-Install script failure