Use this reference to locate VDM application files, configuration, license files, and saved content. Folder contents vary with the VDM version and features used; a clean installation may not contain every item listed.
Configured locations can differ: settings in the active OPTIONS file can override default content and configuration locations. Check the paths in VDM Settings when looking for your files.
Default folder locations
| Location | Default path or how to open it | Purpose |
|---|---|---|
| AppData | %APPDATA%\BridgeWorks VDM |
User settings and local license files |
| ProgramData | %PROGRAMDATA%\BridgeWorks VDM |
Shared settings, service configuration, and installation logs |
| Program Files | C:\Program Files\BridgeWorks LLC\BridgeWorks VDM |
Installed application and supporting components |
| Documents | Open Documents → BridgeWorks VDM in File Explorer | Views, Jobs, Profiles, and other saved content |
To open AppData or ProgramData, paste the path above into the File Explorer address bar and press Enter. The Windows variables resolve to the appropriate folder on that computer.
AppData: user settings and licensing
This folder may contain:
- OPTIONS — user and application configuration.
- RECENT — recently opened items.
- Knowledge, MCP, and MigrationFiles folders — application data used by the corresponding features.
- <ApplicationID>.licx — local license file in VDM 2026.10.12 and later.
- VDM.licx or VDM.lic — license filenames used by earlier releases.
- VDM.msi — a stored installer package, when present.
Upgrading an already registered installation: after upgrading to VDM 2026.10.12 or later, VDM updates the local license file to the <ApplicationID>.licx format on the next startup. The original VDM.licx is retained, so both files can appear.
To find the Application ID, open Settings in VDM and locate Application ID above License Information. The file is named with that installation's actual ID followed by .licx; it is not literally named ApplicationID.licx. The Application ID identifies the installation and is separate from the License Key used for registration.
The screenshot uses a placeholder Application ID. Folder contents vary by installation.
For a license reset, follow How to Reset Your VDM License and Re-Register.
ProgramData: shared configuration and logs
The default folder is %PROGRAMDATA%\BridgeWorks VDM. Items may include:
- Service — service configuration and supporting data.
- InstallLog_*.txt — installation and upgrade logs.
- OPTIONS — shared configuration settings.
- SERVICEOPTIONS — service-specific settings.
Service executables are installed with the application under Program Files; service configuration and data can be stored in ProgramData.
Program Files: installed application
The default folder is C:\Program Files\BridgeWorks LLC\BridgeWorks VDM. A custom installation location can differ.
This folder contains VDM64.exe, supporting libraries, license agreement documentation, and component folders such as Converter, CrystalConverter, lib, Service, and wwwroot.
Documents: saved VDM content
In File Explorer, open the Windows Documents folder, then BridgeWorks VDM. Documents may be redirected to OneDrive or another managed location, so the full path is not always C:\Users\YourUserName\Documents.
Common content folders include:
| Folder or group | Content |
|---|---|
| Views | Saved VDM Views |
| Jobs | Saved Job definitions |
| Profiles | Saved connection profiles |
| Exports | Exported output |
| Logs | Application logs used for troubleshooting |
| Backups and CalendarBackups | Backup files created by the corresponding features |
| Templates, Formats, Formulas, Parameters, Lists, Linking, and Variable Filters | Reusable definitions and settings |
| BridgitAI, Favorites, and Insights | Content for those features |
Older or file-based Scheduler configurations may also use a Calendar file or folder. A Scheduler configured with a SQL backend may not use a local Calendar file. Use the Scheduler configuration to determine where its data is stored.
Before updates or downgrades: back up the Views and configuration files from the locations your installation actually uses. Keep unchanged View backups because files saved in newer releases may not work in older versions.
Comments
0 comments
Please sign in to leave a comment.