Patch My PC Blog
Get expert insights, how-to guides, product updates, and best practices for streamlining patch management, improving endpoint security, and optimizing IT operations.
Microsoft Intune is improving Win32 app delivery with push notifications. Changes made by administrators or the service can now prompt devices to check sooner, reducing delivery and refresh delays without changing how you manage apps. Win32_Pull_vs_Push_Illustrated_… This blog follows the tested IC3 notification into the IME, showing how intent 2 selects Win32AppWorkload and brings the normal app check forward.
Required Win32 apps sometimes waited 60 minutes after Autopilot ESP completed. IME 1.103.101.0 introduces a FirstSync registry watcher that detects ESP completion and immediately triggers another app workload check in.
Intune App Inventory no longer has to wait for the regular four hour collection cycle. A new app install can now trigger detection, validation, a fresh inventory run, and a small delta upload within about five minutes.
Defender was running. Windows said it was off. Intune could then mark the device noncompliant, and Conditional Access could block the user. Here is how the startup race happened, what our PowerShell workaround did, and what we found when testing Defender 4.18.26080.4
At first glance, Device Association looks almost identical to Classic Autopilot. Both can involve collecting device information, uploading a CSV, and linking the device to a tenant. But underneath that familiar admin workflow, Windows uses a different deployment, identity, and OOBE model.
What happens between importing a Device Association CSV and Windows knowing which tenant it belongs to? This walkthrough follows all 12 steps, using code and lab evidence to explain TPM attestation, the signed association stored in UEFI, and how Windows retrieves OOBE settings before anyone signs in.
