Deploy fio to Microsoft Intune
fioWindowsversion 3.43, 23 September 2026
fio is in the PatchBee catalog as a Windows app from fio, synced from the Windows Package Manager community repository (winget). Pick it in the App Library and PatchBee writes the deployment plan below, builds the package, publishes it to your Intune tenant and assigns it to the Entra groups you choose. New versions then follow through your update rings.
The plan PatchBee writes
fio as an Intune app
The standard form for a MSI (WiX) (x64, per machine). The real plan is generated from the installer when you package, and shown in full before anything is published; every field can be changed.
- Intune app type
- Windows app (Win32), .intunewin
- Install
- msiexec /i "fio.msi" /qn /norestart
- Uninstall
- msiexec /x {07BBA0A0-BCAD-4CF3-9436-58E5A65B2ECC} /qn /norestart
- Detection
- MSI product code. Product code {07BBA0A0-BCAD-4CF3-9436-58E5A65B2ECC}, version 3.43 or newer.
- Requirements
- x86 (32-bit), x64 · per machine
Installers in version 3.43
| Architecture | Type | Scope | Hash |
|---|---|---|---|
| x86 (32-bit) | MSI (WiX) | per machine | SHA-256 published |
| x64 | MSI (WiX) | per machine | SHA-256 published |
PatchBee downloads the installer from the publisher's own URL and verifies its SHA-256 against the catalog before packaging. "None published" means the source carries no hash for this download, so that check has nothing to compare against; packaging still works.
Silent install switches
Recorded for fio in its winget manifest. PatchBee uses them as the installer's unattended switches, so the package installs without a click.
- Install location
- INSTALLDIR="<INSTALLPATH>"
About fio
Fio was originally written to save me the hassle of writing special test case programs when I wanted to test a specific workload, either for performance reasons or to find/reproduce a bug. The process of writing such a test app can be tiresome, especially if you have to do it often. Hence I needed a tool that would be able to simulate a given I/O workload without resorting to writing a tailored test case again and again.
A test work load is difficult to define, though. There can be any number of processes or threads involved, and they can each be using their own way of generating I/O. You could have someone dirtying large amounts of memory in a memory mapped file, or maybe several threads issuing reads using asynchronous I/O. fio needed to be flexible enough to simulate both of these cases, and many more.
Fio spawns a number of threads or processes doing a particular type of I/O action as specified by the user. fio takes a number of global parameters, each inherited by the thread unless otherwise parameters given to them overriding that setting is given. The typical use of fio is to write a job file matching the I/O load one wants to simulate.
- Publisher
- fio
- Homepage
- github.com/axboe/fio
- License
- GPL-2.0
- Source
- winget · fio.fio
- Versions in catalog
- 9
How this becomes an app in your tenant
Sign in with your Microsoft work account and connect your Intune tenant once. Find fio in the App Library, open its plan (the commands, detection rule and requirements above, editable) and publish: PatchBee downloads and verifies the installer, builds the package, creates the Intune app and assigns your groups. When fio ships a new version, PatchBee detects it and rolls it out through your rings, with supersedence and rollback.
Read the step-by-step guideMore Windows apps
Catalog data as of 11 October 2026, from the Windows Package Manager community repository (winget). The product re-reads the source every night and plans against the live catalog, so the version here may already be one behind. Nothing is published to a tenant without an administrator approving the plan.