vMedia Release Notes
Version 3.2.66 – July 27, 2026
About vMedia Versions
You are currently running either the production version or the development version of vMedia.
- Development (“Dev”) release: available for ‘early adopters’ to test out new features. Installation is completely optional.
- Production (“Prod”) release: available to the general user base after a Dev release has proven stable. Installation is recommended.
Your current version is displayed in the upper left corner of your vMedia home screen.
Before You Proceed
Attention: Ensure that you have downloaded the correct version of vMedia (Development or Production) and consider the following recommendations to help mitigate the risks of potential downtime for vMedia users.
- If installing a Development release, we highly recommend running the installer in a non-production location. That location may be on the same server as the production location of vMedia but must be in a different folder.
- If installing a Production release, we highly recommend making a backup of the system prior to running the installer.
- Refer to guidance on Vertican system requirements, including vMedia Recommended Environments.
Download
Download the vMedia_Install.exe from the vMedia Product Info page, which is also found by navigating to vPortal > My Vertican > My Products and clicking the [View License Details] button next to vMedia.

From the Product Info page, scroll down the page and download either the Production or Development version of vMedia.
- Production Version
- Scroll to the Software Download section.
- Click “Download vMedia”.

- Development Version
- Scroll to the vMedia Development Version section.
- Click “Download vMedia Development Version”.
.
Installation Instructions
Below is a set of brief instructions for experienced users. You may refer to the Detailed Installation Guide if needed.
- Required: Please make sure all users are logged out of vMedia prior to installation, including all tools and vMedia components (e.g., Print to vMedia, File to vMedia, Send to vMedia, and Spectrum Importer).
- Reminder: Do a backup before you begin!
- Run the installer from any workstation that has access to the server and to the selected installation folder.
- Existing un-upgraded workstations may continue to function properly without re-running the workstation setup. However, certain new features may not work until the user’s workstation has been upgraded. If users receive warning messages concerning outdated components or lose any vMedia functionality, then proceed to Step 5.
- Run ws_run.cmd from the installation folder selected in step 3. This needs to be done at each workstation.
- A user account that has permission to perform administrative installation rights must be used.
- Do not right-click ws_run.cmd and Run as Administrator since this will cause a conflict with the Windows Command Prompt.
- A reboot may be required during the installation.
- Do not bypass this requirement.
- Allow time for Windows to fully reboot between launches of ws_run.cmd, as not doing so can cause complications with the installation.
- To use an existing vMedia named user license, the computer or workstation must have an existing vMedia client already installed.
- If any terminal servers are in use after a successful upgrade, be sure to run ws_run.cmd at each terminal server to complete the upgrade for terminal-server users. Terminal server installation may require more assistance. Please refer to this special case below.
.
Special Case – Windows RDS/RDP Terminal Servers
-
- If you are running vMedia on a Windows 2019 or 2022 Remote Desktop Services (RDS) or Remote Desktop Protocol (RDP) terminal server:
- Microsoft terminal servers have special installation requirements for all applications.
- These special instructions apply if you wish to uninstall/reinstall vMedia or its print drivers in order to resolve print driver compatibility issues.
- Common terminal server procedures are documented in the vMedia Help Manual and Vertican Knowledge Base.
- vMedia Help Manual
- Setup > Install – Upgrade – Migrating > Installing vMedia on a Terminal Server.
- Vertican Knowledge Base
- Open Problem ID 005333 Installing vMedia on a Terminal Server, RDP, RDS or “Remote Desktop.”
- If this link does not open on the correct Problem ID, enter 5333 in the Problem ID field, click the [Search] button, and select 005333 in the results.
- vMedia Help Manual
- While Vertican provides the above help resources, your server setup may have unique requirements based on security or other factors.
- Due to the complexity of Microsoft terminal servers, we recommend using Vertican Professional Services for vMedia installation assistance.
- If you are running vMedia on a Windows 2019 or 2022 Remote Desktop Services (RDS) or Remote Desktop Protocol (RDP) terminal server:
Support
As previously communicated, as of October 1, Direct Support that goes beyond what Ask Goldie can provide is handled through Professional Services.
- If you require assistance with installation or updating user licensing, please submit a query to Ask Goldie.
- If you need vMedia migration assistance, order the vPro Service Package.
- If you are using a Microsoft terminal server, or need other assistance, purchase Web Based Consulting.
Whats New in 3.2.66 Production Release
- Export2CM.exe had a startup error, which was fixed.
- vParser was enhanced to support upcoming features.
- Spectrum Import had an error 107, which was fixed.
- Scanning errors occurred for DBF users, which was fixed.
- Group Compress and Overwrite for vMedia Spectrum Export was fixed.
Known Issues in 3.2.66
All known Issues in this version are also in previous versions but were not found until after version 3.2.24 was released. They will be corrected in an upcoming release.
- Under specific circumstances, an INI error can occur during import in VMPT. Clicking OK should allow you to continue without loss of data.
- vMedia internal viewer (beta) may not work with some QLAW installations.
- A more recent version of the third-party GDPic library has been included to correct memory leaks caused by modern PDFs with redactions.
- If you are having problems, schedule Vertican Professional Services.
- Installing the new GDPic library may cause problems with older CM and QLaw installations for the affected workstation.
- If you deselected columns for viewing in the search results grid, they will all still show up in the next session.
Previously in 3.2.x
- The clipboard was being used for debugging purposes and its use was expanded in vMedia 3 but was depreciated starting with version 3.2.15. That feature has been removed as it is no longer needed as of 3.2.44. It was causing problems for some customers who had recently upgraded directly from Version 2.
- The option to set the order and what fields would show in the search results grid was not working. The order will show correctly now.
- If Spectrum importer is crashing after processing 50 to 75 “Modern PDFs with Redactions,” it’s likely a memory leak with the existing GDPic library caused by the new PDF documents. Schedule Vertican Professional Services to install a new version of GDPIC.
- The debugging system was upgraded because it was overrunning the system’s garbage collection process and causing unexplained or unusual errors or events under certain conditions.
- Spectrum Import had a bug that was causing problems with certain configurations. This was fixed.
- Various minor fixes and improvements have been made in the View and Scanning modules.
- A bug that was in 2.9.1 involving the Add Reference process in the Scanning module was fixed.
- Log files can be saved to a folder – see Sample_SaveDebug.txt for more information.
- Creation/Modify date in VMPTV was fixed.
- DDATE was not showing the correct date for some installations.
- vMPTV had a bug that could change INI files to OLD files in F:\imaster
- vMPTV had a bug that was putting the wrong date into a date field under specific circumstances.
- Date fields can now be part of volume naming.
- New ws_run.cmd (backs up INI files, maps drives for admin user, and calls Workstation_Setup).
- New vMedia_Diagnostsitcs.cmd command script.
- A bug in vParser was fixed that forced the user to click OK to continue.
- VMPTV can be set to watch a folder for printing jobs on a workstation that fails to load VMPTV.
- Fixed remaining C:\programdata\vmedia folder issues.
- Better printer support for Windows 11 support and greatly improved Windows 10 support.
- Forcing Workstation_Setup back to c:\imaster.
- Fixed error when moving metadata viewer form in vMedia.
- Fixed startup version detection in several executables.
- Fixed page 1 duplicating to page 2 for some documents in Spectrum Importer.
- General bug fixes and improvements, and unofficial Windows 11 support.
- New debug logging control (See SaveDebug_Configuration_Guide.pdf).
- New DocList.exe with INI to correct for slower performing computers.
- New printer drivers that fix many Windows 10 & 11 issues.
- VMPTV workaround in case VMPTV refuses to execute after an OS upgrade.
- Legacy Import/Export fixes to make it compatible with Spectrum Importer.
- vMedia now uses vMedia.ini instead of iMaster.ini with auto conversion.
- New internal viewer (demonstration) will allow you to replace FView in a future release.
- Export2CM batch mode.
- vmConv.exe is a utility to quickly stitch vMedia documents back into a PDF.
- GetDocID.exe update to provide more functionality.
- Full Integration with Q-LawE.
- SQL Server Enhancements.
Finding Release Notes
- In addition to the Release Notes on this page, you can always find current release notes on the vMedia Product Info page in vPortal.
- In the Software Download section, click Download Release Notes.
