Recommended or required restart states
Use a local WPF restart workflow that clearly separates recommended restart prompts from required restart enforcement, with configurable postpone choices, user-visible state, and operator-controlled wording.
Tool Detail
Windows restart governance with recommended or required states, a local WPF interface, PreviewOnly test paths, exact Intune Win32 version detection, and a stable PowerShell Gallery module.
Use a local WPF restart workflow that clearly separates recommended restart prompts from required restart enforcement, with configurable postpone choices, user-visible state, and operator-controlled wording.
Validate the restart experience before rollout with PreviewOnly test paths, dedicated launchers, cleaner logging, and support-friendly checks that do not force a reboot during validation.
The Intune detection script records the exact installed version and source, validates the expected GUI files and scheduled task, and confirms that the optional Gallery updater is absent from the clean Intune package.
The stable PowerShell Gallery package supports local install, update, and uninstall workflows, while automatic update remains opt-in instead of enabled by default.
Release 1.1.2
Version 1.1.2 fixes the console launcher selected by a 32-bit Intune installer, reads back the registered task before recording the installation, and requires the headless launcher in Intune detection. The simplified user window and Program Files installation of 1.1.0 are unchanged. The PowerShell Gallery module is also published at 1.1.2.
Full release details, checks, and checksums are published on GitHub.
The local interface requires Windows PowerShell 5.1 and WPF. The included Intune publication workflow targets x64 devices and declares Windows 10 version 1607 as its minimum supported operating system.
Direct preview and GUI launches run in the signed-in user session. Installation, update, and removal require elevation because they write to Program Files and manage scheduled tasks; the Intune package runs those deployment actions as SYSTEM.