Release notes for previous releases
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.
Please note that if you're using Windows 10, you'll need version 1607 or later of the operating system. To check which version you have, go to Start menu > Settings > System > About.
Windows Vista users: double-clicking the setup file won't work, to install you'll need to open a command prompt and run the following command:
msiexec /i <setupfile>
for example: msiexec /i "C:\UltraMon_3.4.0_en_x64.msi"
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.4.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.4.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>
Improved support for Windows 10:
New registry setting to disable use of UltraMonUiAcc.exe: UltraMonUiAcc.exe is used to add window buttons etc to applications running with elevated privileges, but on some systems may fail to launch with the error message 'A referral was returned from the server'. As a workaround, run regedit.exe, then go to the key HKEY_CURRENT_USER\Software\Realtime Soft\UltraMon\<version> and set the UseUiAcc value to zero.
• When changing taskbar configuration settings via UltraMon Options > Taskbar Extensions, the dialog may hang after hitting OK
• Move Mouse hotkeys don't work if the active application is an elevated application (runs as administrator), for example RegEdit
• Maximized Office 2016 applications don't have UltraMon window buttons on secondary monitors if secondary taskbars are disabled
• Window buttons cause problems with Sticky Notes on Windows 10, and it's not possible to disable them for the application via UltraMon Options > Compatibility without disabling buttons for File Explorer windows as well
• Display Settings may not show a disabled monitor if it only has a single display mode available
• UltraMon taskbar doesn't get hidden for fullscreen Internet Explorer window
• When switching Firefox or Chrome to fullscreen mode, the UltraMon taskbar doesn't get hidden, you need to click on the taskbar then on the application to hide it
• When reconnecting to a VMware View session, open application windows get resized (height gets reduced) when the Smart Taskbar is enabled
• Mirroring doesn't get stopped if a monitor gets turned off or disabled via Display Properties
• Wallpaper: portrait-oriented image may be shown in landscape orientation
• Scripting: Utility.Run can't launch DDE application which hasn't set the application or topic values in the registry
• Scripting: System.DockedAppBars contains fake appbars and uses Start as name for secondary taskbars on Windows 8 and later
• Windows Vista: when running an application as administrator you'll get an error 'A referral was returned from the server' from UltraMonUiAcc.exe. As a workaround run regedit.exe, then go to the key HKEY_CURRENT_USER\Software\Realtime Soft\UltraMon\<version> and set the UseUiAcc value to zero. This way you won't get an error, but UltraMon still won't be able to add window buttons etc to applications running as administrator. This issue occurs because Windows Vista doesn't support the new SHA256 code signing certificate used by UltraMon 3.4.0.
• Runtime error in Adobe Acrobat when moving maximized window if Acrobat was launched from CCH ProSystem Engagement. As a workaround, go to UltraMon Options > Compatibility, then configure settings for Adobe Acrobat and check the 'use alternative method to move maximized window' option
• Docking hints from Xceed Docking Windows library don't work if UltraMon window buttons are enabled for the application