PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteIntune Win32 app requirement rules decide whether a Windows device is eligible to install an app; detection rules decide whether the app is already installed. Use built-in operating-system and hardware requirements when they express the prerequisite, then add file, registry, or PowerShell checks only when needed. Keeping eligibility separate from installed-state detection prevents a common configuration mistake: treating a post-install artifact as a condition the device must meet before installation.
What requirement rules check—and what they do not
A requirement rule is an eligibility gate. Intune evaluates it to determine whether the device meets the conditions for the app to be installed. Detection runs separately and reports whether the app is present. Microsoft’s Add and assign Win32 apps to Microsoft Intune documentation describes these as distinct configuration decisions.
As an Amazon Associate I earn from qualifying purchases.
For a Win32 app, configure requirements in the app’s Requirements step. Detection must also be configured separately, and at least one detection rule is required. If several detection rules are configured, all must be satisfied for Intune to detect the app as installed.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsChoose the simplest rule that expresses the prerequisite
Start with the installer’s actual prerequisites. A rule that is stricter than the installer’s needs can make an otherwise compatible device ineligible; a rule that checks the wrong state can prevent deployment or misreport installation.
#1 Best Overall
- 1.1 GHz (boost up to 2.4GHz) Intel Celeron N5030 Quad-Core
| Rule type | What it can evaluate | Best fit |
|---|---|---|
| Built-in operating-system and hardware fields | Architecture, minimum OS version, free system-drive space, physical memory, logical processor count, and minimum CPU speed | Requirements directly expressible as a supported OS or hardware threshold |
| File | File or folder presence and properties such as date, version, or size | A stable prerequisite artifact whose state genuinely indicates eligibility |
| Registry | A key or value evaluated as a value, string, integer, or version | A prerequisite reliably recorded in the registry |
| PowerShell script | A script’s typed output compared with a configured value | A condition the other available methods cannot express |
Built-in OS and hardware requirements
Set the operating-system architecture and minimum operating-system version required by the app. Optional hardware thresholds cover free disk space on the system drive in MB, physical memory in MB, minimum logical processor count, and minimum CPU speed in MHz. Use a threshold only when it reflects a real prerequisite.
File requirements
A file rule can inspect a file or folder and compare a supported property, including date, version, or size. Configure its folder path, target file or folder, and property or comparison method. A required runtime executable or configuration file can be a useful check if its presence truly means the device is ready.
Avoid using a file created by the app installer as a requirement: the device needs to pass requirements before installation, so an artifact that appears only after installation can block the very installation meant to create it.
Recommended Free Tools
Registry requirements
Configure the registry key path and, when applicable, the value name. The rule can evaluate a value, string, integer, or version. If the value name is blank, Intune evaluates the key itself; when the chosen method needs a value, a blank value name means the key’s default value is used.
Rank #2
- 256 GB SSD of storage.
- Multitasking is easy with 16GB of RAM
- Equipped with a blazing fast Core i5 2.00 GHz processor.
Confirm that the installer writes the prerequisite to the registry view the rule reads. On 64-bit Windows, the rule can use the 32-bit registry view for a 32-bit app where appropriate; otherwise, the default view on 64-bit clients is 64-bit.
Configure a PowerShell requirement rule
Microsoft recommends selecting Script when the condition cannot be expressed with a file rule, registry rule, or another method in the Intune admin center. The script should check eligibility and return a value compatible with the configured output type and comparison; it should not make unrelated changes.
- Open the app configuration. In the Intune admin center, open the Win32 app and go to its Requirements step.
- Add a script requirement. Select the script-based requirement option and provide the PowerShell script that checks the prerequisite.
- Choose process bitness. On 64-bit clients, select whether the script runs in a 32-bit or 64-bit process. Choose deliberately if the check reads a path, registry location, or component that differs by process context.
- Set execution credentials and signature checking. Use logged-on credentials only if the condition depends on that user’s state. If signature checking is enabled, the script needs a trusted publisher signature.
- Set the output type and comparison. Select the data type, operator, and comparison value that match the script’s result.
- Keep detection separate. Configure the app’s detection rule independently to report installed state.
Understand the typed comparison
Microsoft Graph’s Win32LobAppRequirementRule resource documents output types of string, dateTime, integer, float, version, and boolean. The documented comparison operators are equal, not equal, greater than, greater than or equal to, less than, and less than or equal to.
For example, a script that returns a version should be compared as a version rather than as arbitrary text. A boolean check should produce a boolean-compatible result and use a comparison suitable for that type. The selected type and operator must agree with both the value the script emits and the value entered in the rule.
Rank #3
- 14" diagonal, 1366x768 resolution, HD BrightView LED, Glossy NON-TOUCH Display
The Graph resource also represents a requirement script’s execution account as system or user. Use the Intune admin center’s fields to configure the tenant; Graph’s resource description clarifies the properties involved.
32-bit and 64-bit context can change what a rule sees
On 64-bit Windows clients, file-path expansion and registry access can be associated with a 32-bit app context. PowerShell requirement rules separately let you select 32-bit or 64-bit process execution; the documented default is 64-bit on 64-bit clients. On 32-bit clients, execution is always 32-bit.
When a check works on one architecture but not another, verify the context as well as the path or registry location. A rule can be logically correct yet inspect a different view of the system than the installer or prerequisite uses.
Requirement rules and detection rules answer different questions
| Decision point | Requirement rule | Detection rule |
|---|---|---|
| Question | Is the device eligible for this app? | Is the app installed? |
| Available methods | Architecture, minimum OS, optional hardware thresholds, file, registry, or script requirements | MSI, file, registry, or custom detection script |
| Script result | Typed output compared with a selected type, operator, and value | Exit code 0 and nonempty STDOUT; any STDERR data means not installed |
| Bitness | Script process can be selected on 64-bit clients; file and registry rules also have relevant 32-bit-context choices | Script process can be selected on 64-bit clients |
| Execution context | Requirement configuration offers logged-on credentials; Graph describes system or user account | Graph documents the detection script as running in the same context as the associated app install context |
For a required app, Microsoft says Intune may offer it again within approximately 24 hours if detection reports that it is absent. That behavior concerns detection, not the requirement’s eligibility comparison.
Rank #4
- 【Efficient Performance】 Powered by Intel Core i3 processor (2 cores, 4 threads, up to 3.4GHz) with 12GB RAM and 256GB SSD. Handles multitasking, office software, online classes, and HD video streaming smoothly. Integrated Intel UHD Graphics 620
- Backlit Keyboard & Complete Package】Comes with a cool backlit keyboard. Comes with awebcam, dual stereo speakers (8Ω/1.0W each), DC charger, and user manual – ready for late-night studying, online classes, video conferencing, and daily productivity
- 【Vibrant Display】 15.6-inch Full HD (1920x1080) anti-glare screen with 16:9 aspect ratio delivers crisp images and vivid colors – perfect for studying, watching lectures, or entertainment. Thin-bezel design maximizes viewing area
- 【Fast Connectivity & Expansion】 Equipped with WiFi 6 (802.11ax) and Bluetooth 5.2 for stable, high-speed wireless. Features 3 x USB 3.0, HDMI 2.1, Type-C (supports PD3.0 fast charging), and a TF card slot expandable up to 2TB – easily connect external monitors, mice, drives, or expand storage for all your files
- 【Long Battery Life & Portable】 Built-in 11.55V 5000mAh/57.75Wh high-capacity battery delivers approximately 7 hours of mixed-use battery life – enough for a full day of classes and assignments. Lightweight at just 1.63kg (3.6 lbs) and 19.5mm thin, plus a compact packing size – easily slips into a backpack for campus, library, or coffee shop
Custom detection scripts have a stricter success contract
Do not apply requirement-script output rules to a custom detection script. For custom detection, Microsoft documents success as exit code 0 plus some data written to STDOUT. Intune does not require a particular STDOUT string, but any STDERR data causes the app to be evaluated as not installed—even if the script exits 0 and writes to STDOUT.
- Write a simple, nonempty STDOUT value only when the app is present.
- Keep diagnostic messages off STDERR; an STDERR message can make detection report the app as absent.
- Exit nonzero when the check fails.
- Microsoft recommends UTF-8 BOM encoding for the custom detection script. This recommendation is specific to the documented detection behavior; it should not be generalized to every Intune script feature.
Win32 app management context and limits
Win32 app management uses the Intune Management Extension, which Microsoft says is installed automatically when a Win32 app or PowerShell script is assigned. Microsoft’s Win32 app management documentation lists support for 32-bit Windows, 64-bit Windows, and ARM64, and says apps must install silently. It identifies Windows Enterprise, Pro, and Education editions as supported and sets the Win32 app size limit at 30 GB. These are management constraints, not special behaviors of requirement rules.
The same overview describes PowerShell installer scripts as running in the app installer’s context, requiring silent operation, limited to 50 KB, and using return codes to indicate installation success or failure. Those installer-script limits and semantics do not define how a separate requirement script’s typed output is compared.
Microsoft’s overview also describes a Multi-Admin Approval caveat: with MAA enabled, scripts cannot be uploaded during app creation and must be added or modified afterward. It notes that certain script properties can currently be edited without MAA requests and that this behavior is expected to change. Because this is a changeable workflow detail, verify the current documentation and tenant behavior before relying on it.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
