<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Intune on Zubair | Intune | OS Engineering</title><link>https://zubaircloud.com/categories/intune/</link><description>Recent content in Intune on Zubair | Intune | OS Engineering</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 30 Sep 2026 10:00:00 +0530</lastBuildDate><atom:link href="https://zubaircloud.com/categories/intune/index.xml" rel="self" type="application/rss+xml"/><item><title>Intune: Reliable Win32 app detection with a registry marker</title><link>https://zubaircloud.com/post/intune-win32-registry-detection/</link><pubDate>Wed, 30 Sep 2026 10:00:00 +0530</pubDate><guid>https://zubaircloud.com/post/intune-win32-registry-detection/</guid><description>&lt;p&gt;A Win32 app that installs successfully but then shows &lt;strong&gt;failed&lt;/strong&gt; in Intune is almost always a detection problem, not an install problem. The usual trigger is a detection rule tied to something the app changes on its own — a file version that self-updates, or an uninstall key whose GUID changes between builds.&lt;/p&gt;</description></item></channel></rss>