OSManagerCLI Release Notes

v1.12 — 01/Jul/2026

Safe reimaging. OSManagerCLI now re-checks for any networking changes immediately before a Redisguise to ensure the correct machine gets reimaged.
Diagnosing networking issues. OSManagerCLI now diagnoses any API connection issues thoroughly, giving much clearer feedback about how to resolve them.
A stray click can no longer pause the program. The console’s Quick-Edit / “Select” mode is disabled, so accidentally clicking in the window won’t silently freeze the app mid-run.
Smarter network-address selection when a machine has more than one IP address.
New -Help parameter prints usage instructions directly on the command line.
Added a reminder not to disconnect the network for 10 minutes after starting a Redisguise.

More robust hands-free (command-line) reimaging. When driven from the command line, OSManagerCLI now checks your inputs up front (for example, confirming the -IngestOSFilePath file exists before it starts) and exits cleanly with the relevant code at every step. See Command line & exit codes.
Meaningful exit codes. OSManagerCLI now returns a specific exit code for every outcome, so scripts and automation can tell exactly how a run ended. Look any code up with the new -DescribeExitCode <n> flag, or list them all with -ListExitCodes.
New -Version parameter prints just the version number, handy for scripting and support.
Reliability improvements for Windows 10 servers.
Running hands-free (with -MachineToReimageHandle) no longer adds or updates a Start Menu shortcut.

The Start Menu shortcut is now only added or updated for a local install. Running from a removable/USB drive no longer touches your Start Menu.
You can now run multiple instances on one laptop, for example a local install on your C: drive and a portable copy on an External SSD. Your laptop hosts a separate share for each (\\<your-laptop>\d3OsDeploymentShare, \\<your-laptop>\d3OsDeploymentShare2, and so on), and the correct share is always used when requesting a reimage, so there are no conflicts.
On start-up, OSManagerCLI now checks Windows Group Policy to make sure Guest is not blocked under Local Policies → User Rights Assignment → Deny access to this computer from the network, so that the actors being reimaged can reach the deployment share.

Automatically warns about (and corrects) your Windows settings if Password Protected Sharing isn’t already disabled.
Performs a disk-space check before ingesting a new .iso or .os file.
Cleans up properly after a failed ingestion.
Returns to the Main Menu (instead of the OS menu) after a successful ingestion.

Added a title bar and clearer visibility of which version you’re running.
Fixed a bug (introduced in v1.7) that prevented the exe from running when placed in the root directory of a drive.