Create Intune-ready PowerShell scripts for Windows registry changes—right in your browser.
This tool helps you build, validate, and export scripts for registry keys and values, supporting both Intune Proactive Remediations and Win32 app deployments.
You can now not only export, but also push remediations directly to Intune from your browser—no manual upload required.
All actions happen securely and locally in your browser; no data or credentials are stored or sent to any server.
The only permission required is the delegated Intune permission DeviceManagementScripts.ReadWrite.All for direct deployment.
Features:
✅ Single hive per export: Choose HKLM (System) or HKCU (User) for all entries.
✅ Multiple entries: Add as many registry changes as you need—create, update, or delete keys and values.
✅ Two export paths:
- 🛠️ Remediation scripts: Generate and push Detection.ps1 and Remediation.ps1 directly to Intune Remediations (requires only the delegated permission
DeviceManagementScripts.ReadWrite.All) - 📦 Win32 app bundle: Export Install.ps1, Uninstall.ps1, and a custom Detection script for packaging as a Win32 app.
Privacy:
All processing happens locally in your browser. No scripts, registry data, or credentials are ever stored or transmitted to any external server.
If you like what I share and want to keep this blog alive, you can support me here.
Intune registry package
Registry entries
Define registry keys, values, and actions. Use the hive prefix that appears automatically.
No entries yet. Use “Add entry” to get started.
Exports
Generate Intune remediation scripts or a Win32 package bundle with one click.
Registry remediations export
Detection script Detection.ps1
Remediation script Remediation.ps1
ℹ️ Remediation guidance
- 🧭Where: Intune → Devices → Scripts and remediations → Remediations
- 👤Context: HKLM = System; HKCU = User (Run using logged-on credentials)
- ⚙️64-bit PowerShell: enable “Run script in 64-bit PowerShell”
- 🔁Behavior: Detection exit 0 = compliant, exit 1 = remediate; scripts are safe to re-run
Registry (Win32) export
Custom Detection (Win32)
Install.ps1
Uninstall.ps1
🧰 Win32 guidance
-
🧪
Detection script: must output text and
exit 0when detected (elseexit 1).
Detection script file:(auto-filled) -
🖥️
Program commands:
Install:powershell.exe -ExecutionPolicy Bypass -File .\Install.ps1
Uninstall:powershell.exe -ExecutionPolicy Bypass -File .\Uninstall.ps1 -
📦
Packaging:
IntuneWinAppUtil.exe -c C:\Source\MyBaseline -s Install.ps1 -o C:\Output
