- Don't autostart UltraMon if only a single monitor is installed or enabled: to enable this option, create a new DWORD value named SingleMonNoAutoStart under HKEY_LOCAL_MACHINE\SOFTWARE\Realtime Soft\UltraMon and set it to 1 to disable autostart if only a s

- New scripting features: you can now get a collection of all open windows via the Window object's GetAllWindows and GetAppWindows methods, this enables a variety of window management tasks, for example moving all windows to a specific monitor, swapping win

- Licensing change: per-computer licensing has been changed to require a license for each computer where the software is used instead of each computer where the software is installed. This mainly affects terminal server environments, if the software is only

- Applying an existing display profile or shortcut with custom display settings may result in the monitor image getting turned upside-down, to fix this, edit the profile or shortcut and set the orientation setting as desired. This is due to legacy display

- No compatibility warning gets shown if only a single monitor is detected when UltraMon runs for the first time. This prevents an unnecessary warning if the software is installed on a terminal server, but the client connecting to the server only has a si

- Moving windows to a different monitor via UltraMon window buttons or the Move Window hotkeys may occasionally not work correctly on 64-bit Windows

- Icon positioning may not work correctly on Vista and later if there are multiple icons whose names begin with the same character(s)

- Hidden UltraMon window gets shown if ATI HydraVision is enabled and the 'allow spanning across displays' option is not enabled

- If Matrox PowerDesk is configured to open all applications on a specific monitor, the Choose Monitor window also gets opened on that monitor

- After changing monitor numbers on Windows 7, monitors may get assigned different numbers after the next reboot

- Smart Taskbar ignores taskbar group policy settings such as 'Lock the Taskbar' and 'Prevent grouping of taskbar items'

- UltraMonTaskbar.exe may crash with an access violation or with a fatal error in TaskBand.cpp at line 1430 when connecting to a system running UltraMon via Remote Desktop

- UltraMon taskbar has gray borders when logging in locally again after having connected to the system remotely. This happened when using the XP default or Vista and later basic theme and visual styles were disabled for the remote desktop session

- Smart Taskbar may no longer work correctly after the main taskbar, explorer.exe, has been restarted

- Setup shows message that you don't have the necessary privileges required to install mirroring. The message has been removed, UltraMon setup requires administrative privileges anyway, independent of the mirroring feature getting installed or not

- When upgrading from 2.7.1, shared wallpapers don't get preserved. Please note that this can still happen if the shared wallpapers aren't stored in the default location Shared Documents\Shared Wallpapers

- Window buttons etc are disabled for a specific application, but occasionally they still get added

- Window buttons may not match the width of the regular window buttons on some systems

- Mirroring starts and keeps running even though the mirror target monitor can't be enabled

- Mirroring: when changing the resolution of the source or target monitor, the mirror image no longer fills the whole screen

- Mirroring fails to start with an invalid configuration message, but settings can't be changed because the monitor selection screen doesn't get shown on systems with only two monitors

- Fatal error in Mirroring.cpp at line 719 when mirror target monitor gets removed/deactivated while mirroring is running. Mirroring now quits without showing an error message when a monitor gets removed/deactivated

- Mirroring a single application: TimerPlus not shown on list of running applications

- Mirroring settings wizard: when clicking on Back to go to the previous page, you'll get an error message if no monitor or application has been selected for mirroring

- Application gets positioned partially offscreen if configured to open on specific monitor but the monitor is disabled

- Offscreen window can't be moved to primary monitor via hotkey or script during single-monitor remote session

- Scripting: Window.Find method with wildcards may fail to find a match even though a window with a matching caption exists

- Scripting: on Windows 7, System.DockedAppBars contains an entry for the start button

- Several memory leaks have been fixed in UltraMon.dll