Win32 App Detection Rule — Troubleshooting MSI Product Code Issues
You deploy a Win32 app via Intune to Windows 10 devices. The app installs successfully, but the detection rule incorrectly reports the app as not installed, causing Intune to attempt reinstallation repeatedly. Which detection rule method is most likely causing this issue?
Quick Answer
The answer is that an MSI product code detection rule using a product code that does not match the installed app is the most likely cause. This happens because Intune compares the specified product code against the Windows Installer database; if the code is incorrect, missing, or from a different version of the application, the detection rule fails even though the app installed successfully. On the MD-102 exam, this scenario tests your understanding of how detection rules validate deployment status, and it often appears as a trap where you might overlook the exact match requirement for MSI GUIDs. Unlike file or registry detection, which rely on straightforward paths or keys, MSI detection is brittle because a single typo or mismatched version string causes false negatives. Remember the mnemonic: “MSI means Match the Specific Identifier” — always verify the product code from the actual installed app’s properties, not the deployment package.
⚠ Common exam trap
Many candidates assume any detection rule method will work as long as the app is installed, but they overlook that MSI product code detection requires an exact GUID match, and a mismatch will cause Intune to perpetually attempt reinstallation.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
MSI product code detection uses a product code that does not match the installed app
When an MSI product code detection rule uses a product code that does not match the GUID of the installed application, Intune will always evaluate the app as 'not installed' regardless of the actual installation state. This mismatch causes Intune to repeatedly attempt reinstallation on every check-in cycle, as the detection logic never finds a matching product code in the Windows Installer database.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
MSI product code detection uses a product code that does not match the installed app
Why this is correct
Mismatched product code causes detection failure.
- ✗
File existence detection checks for a file that is installed by the app
Why it's wrong here
If file exists, detection should succeed.
- ✗
Registry detection checks for a registry key that is created by the app
Why it's wrong here
If key exists, detection should succeed.
- ✗
Custom script detection returns exit code 0 even if app is not present
Why it's wrong here
Exit code 0 typically indicates success, so detection would pass.
Go deeper
Related to this question
Learn chapter
Enrolling Devices with Microsoft Intune
Key term
Win32 app
A Win32 app is a traditional Windows program that runs directly on a Windows PC, using the same system resources and displaying a standard window with menus and buttons.
Key term
Intune
Microsoft Intune is a cloud-based service that helps organizations manage their users' devices and applications, ensuring security and compliance without needing to own or control the physical hardware.
About these practice questions
One of 942 original MD-102 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
Same concept, more angles
2 more ways this is tested on MD-102
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. You need to deploy a custom Win32 app to Windows 10 devices. The app installation is silent and requires a reboot. You set the installation behavior to 'system' and the device restart behavior to 'Allow'. After deployment, users report that the app is installed but not working properly. What is the most likely cause?
medium- A.The app requires user interaction to complete setup
- B.The detection rule is misconfigured
- ✓ C.The device was not restarted after installation
- D.The app was not wrapped correctly with the Intune Win32 Content Prep Tool
Why C: When the device restart behavior is set to 'Allow', Intune will request a reboot but does not force it; the user can postpone or ignore the prompt. If the app requires a reboot to complete its installation or initialize properly, skipping the restart leaves the app in a partially installed state, causing it to appear installed but malfunction. This is the most likely reason the app is not working correctly after deployment.
Variation 2. You deploy a Win32 app via Intune to Windows 10 devices. The app installs successfully on some devices but fails on others with no error in the Intune console. The app logs show 'Access Denied' during installation. What should you check first?
hard- A.The device is not Microsoft Entra ID joined
- B.The device has insufficient disk space
- C.The app is not signed
- ✓ D.The installation context (user vs system) in the app deployment
Why D: The 'Access Denied' error in the app logs indicates a permissions issue during installation. In Intune, Win32 apps can be deployed in either 'user' or 'system' installation context. If the app requires administrative privileges (e.g., writing to Program Files or the registry under HKLM) but is configured to run in the user context, it will fail with an access denied error on devices where the user lacks sufficient rights. Therefore, verifying the installation context is the first troubleshooting step.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This MD-102 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the MD-102 exam.