Boot failures, BSOD, event log forensics, profile corruption, error codes
Intune Win32 supersedence or dependency chain stopped working as it grew? Learn documents graph limits, conflict states and Relate permission. Check these first.
A fake Advanced IP Scanner MSI reached Intune endpoints. Verify the installer source, SHA256 hash and signature with PowerShell before you package a Win32 app.
Hybrid join error 0x801c03f2 (DSREG_E_DIRECTORY_FAILURE): the server message separates a sync delay, an out-of-scope OU, a missing userCertificate or bad SCP.
Intune EnterpriseEnrollment CNAME auto-discovery ends for Windows MDM-only enrollment on January 15, 2027. How to audit DNS and what users will be asked for.
Intune Win32 install script works in testing but writes to WOW6432Node or SysWOW64 when deployed? The IME launched 32-bit PowerShell. Fix it with Sysnative.
ESP fails with Another installation is in progress during Autopilot? Mixing LOB MSI and Win32 apps makes both use TrustedInstaller. Here's the fix from Learn.
Intune MSIX or APPX app fails with 0x80073CFB, package already installed? A rebuilt or re-signed package kept the same version. Fix it with a version bump.
Autopilot VM failing at Preparing your device for mobile management? Microsoft says give the VM at least 2 processors and 4 GB of memory. Check it in Hyper-V.
0xcaa9001f in CoManagementHandler.log means ConfigMgr tried Integrated Windows auth on a non-federated domain. Fix Cloud Management and both user discoveries.
Autopilot device preparation not running and the ESP shows in OOBE? The device is still registered in classic Autopilot. Check it, then deregister or associate.
Autopilot ESP timeout in device setup shows Setup could not be completed. Find the app that blocked ESP in the registry, fix it, then size the time limit.
0x800F081F (CBS_E_SOURCE_MISSING) on .NET Framework 3.5 means Windows found no usable NetFx3 source. Fix the sxs path, OS version match and share access.
Error 80090016 (NTE_BAD_KEYSET) means the device keys Entra ID registered are gone from the TPM. Don't clear the TPM; re-register the device by join type.
0x800706FD DenyLocalLogOn in Autopilot hybrid pre-provisioning means a UserRights conflict needed a domain controller. Find the policy, then fix the tech flow.
Feature update error 0xC1900208 (MOSETUP_E_COMPAT_INSTALLREQ_BLOCK) means Setup found a hard compat block. Read CompatData XML and fix the app or driver.
Hybrid join error 0x801c001d (DSREG_AUTOJOIN_ADCONFIG_READ_FAILED) means Windows could not read the SCP from AD. Check dsregcmd, event 220 and the SCP keywords.
Intune can enforce several valid Windows build ranges while Company Portal displays only the first. Verify compliance in Intune before directing users to update.
Intune now uses push notifications for Win32 app changes, but a Windows device may still wait if it is offline or WNS is blocked. Trace assignment, sync, IME, and app delivery in order.
A Win32 app can be healthy while one Windows device never receives it. Use Intune assignment filter mode, device properties, requirements, and IME evidence to find the exclusion.
A Win32 app can remain unavailable or fail while its dependency is missing. Use Intune assignment, automatic-install, context, and IME evidence to repair the dependency chain.
A Win32 app can be absent from Company Portal without an installer failure. Use Intune requirements, applicability evidence, and IME logs to find the real boundary.
When a Win32 app is present and locally detected but Intune still reports Failed, use policy revision, IME reporting, and AppWorkload evidence to isolate a stale or mismatched result.
An Intune Win32 app works when run by hand but fails when deployed because Intune needs a silent install. Verify the command, context, logs and detection rule.
A superseding Intune Win32 app can remain blocked when the old app is still detected, not targeted, or stuck in uninstall. Use the app graph and client logs to fix the conflict.
An Intune Win32 app can return exit code 0 and still report Failed when detection cannot prove installation. Use logs, context, and exact evidence to fix it.
Troubleshoot Intune Win32 MSI deployments that return error 1618 because Windows Installer is already busy, using IME logs, MSI evidence, and a safe retry workflow.
Intune Win32 app error 0x80070643 means a fatal installation failure, not one specific root cause. Use Intune and MSI logs to isolate the failing action, then fix the package, context, or device condition.
When a Microsoft Intune Win32 app stays Installing, verify assignment deadlines, download state, installer exit, detection, and IME evidence before rebuilding the package.
Fix Intune Win32 detection scripts that miss installed software because the command launches 32-bit PowerShell and reads the redirected registry view.
When an Intune Win32 app never installs because it is Not applicable, use client evidence to separate requirements, assignment, detection, and install-context problems.
Troubleshoot Intune Win32 app error 1603 (ERROR_INSTALL_FAILURE). Learn why the generic MSI fatal code is never the root cause, where to find the real failure in AppWorkload and verbose installer logs, and how to fix it.
Learn how to handle Intune Win32 app return code 3010, map it to a soft reboot, verify detection, and avoid treating a successful install as a failed deployment.
Fix an Intune Win32 app detection script that works in an admin PowerShell window but reports not detected under the Intune Management Extension SYSTEM context.
Read AppWorkload.log, IntuneManagementExtension.log, AppActionProcessor.log and AgentExecutor.log to find where a Win32 app install, detection or report failed.
Learn when an Intune Win32 app detection rule should check HKLM or HKCU, how registry view changes the result, and how to prove the correct fix on Windows.
Choose System or User install behavior for an Intune Win32 app, then align the install command, detection rule, registry hive and logs to fix Failed status.
Intune shows Failed but the Win32 app is installed on Windows? Check the detection rule, install context, IME logs and reporting to find the cause and fix it.
Fix the Windows Autopilot known issue where automatic keyboard setup does not accurately update the keyboard language during provisioning.
Troubleshoot the July 2026 Windows 11 25H2 issue where some Dell devices show poor performance after KB5095093 because of an Intel Innovation Platform Framework driver conflict.
Troubleshoot Windows 11 25H2 devices that stay stuck in Intune when Microsoft blocks the target version with a safeguard hold.
Stop Windows Autopilot devices from silently encrypting with XTS-AES 128-bit when your Intune BitLocker policy requires XTS-AES 256-bit. Cover the known race condition, ESP timing, and decrypt/re-encrypt repair.
Microsoft's July 2026 WSUS service degradation can slow syncs or time out. Here's how to confirm impact, reduce noise, and keep Windows patching moving.
Fix the Windows Autopilot OOBE error that says a username belongs to another organization by checking tenant IDs, registration, and profile state.
Fix Intune Connector error Cannot start service ODJConnectorSvc on computer '.': check MSA replication, Log on as a service and OU rights in hybrid join.
Autopilot device ESP ignoring blocking apps in a user-targeted profile? Move the ESP profile to device groups or the default profile and verify app targeting.
Fix Windows Autopilot user-driven Microsoft Entra hybrid join when the deployment profile is set to Administrator but the enrolling user still lands as a standard user.
Fix Windows Autopilot Reset when required apps are not shown on the Enrollment Status Page and users reach the desktop before those apps finish installing.
Fix Windows Autopilot Reset when the device shows 'Autopilot reset ran into trouble. Could not find the recovery environment' and local reset fails because WinRE is disabled or misconfigured.
Fix Windows Autopilot TPM attestation timed out errors on devices with Infineon SLB9672 TPM firmware 15.22, and verify the right OEM-first remediation path.
Troubleshoot Windows Autopilot TPM attestation error 0x80070490 on AMD ASP fTPM devices during self-deploying mode or pre-provisioning, with firmware-first remediation.
Fix Windows Autopilot device preparation security group membership failures that leave devices non-compliant, and verify Intune Provisioning Client ownership and enrollment time grouping.
Troubleshoot Windows Autopilot TPM attestation failures on ST Micro and Nuvoton TPMs that support RSA 3072bit during pre-provisioning or self-deploying mode.
Fix the Windows Autopilot 50-record limit in Intune and Microsoft Graph by using skipToken pagination or the AutopilotV1DeploymentStatus export API.
Fix Windows Autopilot device preparation when Microsoft Entra local administrator settings cause provisioning to skip and users reach the desktop without expected apps.
Fix Windows Autopilot TPM attestation and ESP failures caused by incorrect device time, and verify the right logs, ports, and clock-sync checks before reimaging.
Fix Windows LAPS not applying during Windows Autopilot pre-provisioning technician flow by validating the Microsoft-known issue, checking LAPS event evidence, and moving verification to the user phase.
Fix Intune Connector `A constraint violation occurred` (0x8007202F) during Autopilot hybrid join by correcting OU delegation, computer-account limits, and ODJ setup evidence.
Troubleshoot Windows Autopilot self-deploying mode on Shared PC devices when the Enrollment Status Page account setup phase does not appear after a user signs in with a FIDO2 security key such as a YubiKey.
Troubleshoot Windows Autopilot TPM attestation error 0x81039023 during pre-provisioning or self-deploying mode and verify when outdated Windows 11 21H2 media is the real cause.
Troubleshoot DFCI enrollment failures on Windows 11 24H2 Pro during Autopilot, including KB5046740, edition step-up, OEM readiness, and Intune checks.
Troubleshoot false Failed status in the Windows Autopilot report when the device actually finished provisioning successfully, and verify the real state with event logs, Graph, and Intune exports.
Troubleshoot Autopilot self-deploying mode error 0x801C03EA when TPM attestation fails, blocking Microsoft Entra join with a device token during kiosk and shared-device deployments.
Troubleshoot Windows Autopilot TPM attestation error 0x81039024 during pre-provisioning or self-deploying mode when Windows 11 blocks attestation because known TPM vulnerabilities were detected.
Fix the Intune Connector for Active Directory error `MSA account <accountName> is not valid` by validating connector build, AD replication, and MSA prerequisites.
Troubleshoot Autopilot self-deploying mode error 0xC1036501 when multiple MDM configurations in Microsoft Entra ID block automatic Intune enrollment.
Troubleshoot Windows Autopilot error 809 when a deleted deployment profile leaves devices stuck without a valid assigned profile during OOBE.
Troubleshoot Windows Autopilot error 815 when a device has no assigned deployment profile and no default profile exists to catch it during OOBE.
Troubleshoot Kerberos and NTLM failures caused by duplicate SIDs after Windows hardening updates, including Event ID 6167, rollback limits, and rebuild guidance.
Troubleshoot Windows Autopilot Microsoft Entra hybrid join deployments where quality updates time out during OOBE when Allow OOBE Updates is enabled in the Enrollment Status Page profile.
Fix SeLogonAsServicePrivilegeMissing in the Intune ODJ connector for Autopilot hybrid join by updating the build and adding Microsoft's bypass key.
Fix local Windows Autopilot Reset when an Intune User Rights policy adds the local admin to Deny access to this computer from the network and CTRL+WIN+R stops working.
Troubleshoot Windows Autopilot pre-provisioning error 0x801C03F3 when Microsoft Entra ID cannot find the device object and bench deployments stop before enrollment completes.
Prepare for Kerberos RC4 hardening and fix authentication failures before the July 2026 Windows update enforces AES-only defaults on domain controllers.
Troubleshoot Autopilot.dll WIL error 0x80070491 by separating harmless Event Viewer noise from real Autopilot enrollment, reuse, and ESP issues.
Fix Samsung Windows 11 C: drive access denied failures caused by Galaxy Connect or Samsung Continuity Service with Microsoft's validated recovery steps.
Troubleshoot Windows 11 25H2 devices that stay in Offering, never download, or never install after targeting them with an Intune Feature Update policy.
Fix Intune device already enrolled errors 8018000A and 0x8007064C by removing stale work accounts, old MDM certificates, cloned enrollment artifacts, and stale records.
Fix Autopilot hybrid join error 0x80070774 by removing Assign user from hybrid profiles, checking ODJ connector rights, and validating DC reachability.
Fix Intune error 80180003 and 0x801c0003 by validating user licensing, enrollment limits, Windows edition support, and Microsoft Entra device join policy.
Troubleshoot Intune enrollment error 0x80180018 by checking user licensing, Entra auto-enrollment scope, MAM precedence, and MDM URL settings.
Troubleshoot Autopilot pre-provisioning error 0x80180005 by checking ZTD profile assignment, device reuse blocks, ESP targeting, and hybrid join prerequisites.
Fix Autopilot import errors 806 and 808 in Intune by removing stale device records, validating tenant ownership, and preparing support evidence.
Troubleshoot Intune error 65000 type 2 by checking per-setting status, DMEP logs, scope conflicts, unsupported Windows settings, and assignment failures.
Troubleshoot Windows 11 24H2 feature update rollbacks from Intune when devices fail with 0xC1900101 or phase-specific driver rollback codes.
Troubleshoot Intune BitLocker recovery key escrow failures by checking Entra join, silent encryption prerequisites, policy conflicts, WinRE, TPM, and RBAC.
Troubleshoot Intune 0x87D1FDE8 remediation failed errors by checking CSP scope, OS support, assignments, sync state, and device-side MDM logs fast now.
Troubleshoot Autopilot Securing your hardware failed 0x800705B4 by checking TPM 2.0, attestation URLs, profile mode, logs, and OOBE timing.
Troubleshoot OneDrive Can't sign in error 0x8004de40 or 0x8004de88 on enterprise Windows devices by checking TLS, proxy inspection, Microsoft 365 endpoints, sync client state, and tenant sign-in evidence.
Troubleshoot macOS Platform SSO error 10001 in Intune by checking the SSO payload, Company Portal version, profile conflicts, and Entra device registration.
Autopilot 0x80180014 means Intune is blocking enrollment: a reused device record is blocked or Windows MDM is restricted. Unblock the device, then retry.
Troubleshoot Intune Win32 app installs that finish but report detection failed or 0x87D1041C because the detection rule cannot prove the app is installed.
Troubleshoot Intune Win32 app deployments that show The unmonitored process is in progress, however it may timeout, error 0x87D300C9, in Company Portal or the Intune admin center.
Recover from a Microsoft 365 admin lockout after MFA enforcement or Conditional Access blocks the admin portal.
Fix Auto MDM Enroll: Failed 0x8018002b (Event 76) on GPO-enrolled hybrid joined devices: set MDM user scope, set MAM user scope to None, fix .local UPNs.
Fix Windows Autopilot hardware hash CSV import error 400 Edm.Binary by validating the hash, headers, encoding, and Intune import workflow.
Fix Intune Settings Catalog policy conflicts by tracing per-setting status, assignment failures, scope, Windows support, and duplicate CSP values.
Fix Intune device sync failures after Conditional Access changes by checking enrollment scope, device compliance, MDM URLs, and error 0x80180028.
Fix the Teams Meeting Add-in missing from classic Outlook after a New Teams update by checking COM add-ins, LoadBehavior, TeamsMeetingAddin files, and policy blocks.
Fix Autopilot device preparation failures in Intune by checking enrollment time grouping, app status, scripts, RBAC, and known OOBE issues.
Diagnose and fix Windows LAPS password rotation failures in Intune-managed environments. Covers policy conflicts, backup directory mismatches, and device state issues.
The May 2026 Windows security update KB5089549 fails on devices with low EFI System Partition space. Here is how to identify affected devices, fix the ESP, and deploy the update with Intune.
Troubleshoot Windows Autopilot TPM attestation error 0x81039001, also shown as E_AUTOPILOT_CLIENT_TPM_MAX_ATTESTATION_RETRY_EXCEEDED, during Securing your hardware in pre-provisioning or self-deploying mode.
A comprehensive guide to fixing the 0x80004005 error during Windows Autopilot Hybrid Azure AD join deployments.
Use AI safely to accelerate CMTrace and ProcMon troubleshooting with a repeatable workflow for desktop engineering teams.
The most common Windows Blue Screen of Death (BSOD) error codes, what they mean, and how to fix them.
Diagnose a temporary or corrupted Windows profile, protect user data, and rebuild access without deleting profile folders or editing registry keys blindly.
Find out why Windows Location Services is unavailable by checking user consent, Group Policy, Intune policy, and service state without overriding managed settings.
Diagnose Windows SMB share discovery, access denied, and connection failures using firewall, share ACL, NTFS, and signing evidence.
Diagnose Windows Remote Desktop connection failures with read-only checks for reachability, policy, firewall, account access, and Network Level Authentication.
The essential Windows Event Logs every IT pro should monitor. Learn to read, filter, and act on Windows logs effectively.
Diagnose Windows OOBE and first sign-in failures after imaging with setup logs, deployment context, and safe recovery steps—without deleting profiles or provisioned apps.
Type to search…
We use Google Analytics cookies to see which pages are useful. No ads. You can change this anytime with "Cookie settings" in the footer. Cookie Policy
