Ultramon 3.2 update

Ultramon – my favourite multi monitor management tool has gotten an update to V 3.2.0

The developers advise that the details for this release are


Setup will upgrade your existing installation and preserve your settings (version 2.7.0 and later only) and registration information. You don’t need to uninstall your current installation of UltraMon first.

When upgrading from version 2.6 or earlier, settings and display profiles, shortcuts and wallpapers will not be preserved. If you need to preserve settings and files, you’ll need to upgrade to 2.7.1 first, then to version 3.

Please note that 3.2.0 requires a version 3 license, version 2 registration codes won’t work. If you’re unsure what version your license/registration code is, login to your account to review your orders and access your registration information. Version 3 registration codes are backwards-compatible and will work fine with earlier releases of UltraMon.

System administrators: if you’re upgrading UltraMon installations which use version 2 registration codes, you’ll need to specify the new version 3 registration code when deploying 3.2.0, otherwise all upgraded installations will run in trial mode. You can do this by setting the USERNAME and PIDKEY properties, for example on the command line for msiexec:

msiexec /i <setupfile> USERNAME=”<registeredTo>” PIDKEY=<regCode>

New in this release

Support for Windows 8 (release preview):

  • window buttons: the buttons now work on Windows 8, and match the look of the native buttons (Aero and Basic visual styles)
  • wallpaper manager: wallpaper gets laid out correctly if you have a monitor to the left of the primary monitor
  • Smart Taskbar: if UltraMon gets installed for the first time on a Windows 8 system, and the multi-monitor taskbar is enabled, the Smart Taskbar is disabled by default (you can still enable it via UltraMon Options > Smart Taskbar)


• Windows 2000 is no longer supported, 3.2.0 requires Windows XP SP2 or later, or Server 2003 SP1 or later.

• If you have configured compatibility settings for 16-bit applications, you’ll need to recreate those settings. This is due to a change in how 16-bit applications are handled. Please note that your settings will apply to all 16-bit applications, this was the case previously as well, but the user interface allowed setting up different settings for different 16-bit applications.

• All binaries (executables and DLL files) are now digitally signed, previously only the setup file was signed.