Skip to main content

Troubleshooting Slow VDM Startup

Garrick Guillory
Updated

Legacy Application Notice: This article applies to the 2025 legacy VDM application. VDM versions released in 2026 and later use .NET 10 and are not reflected in this article. Behavior, settings, and troubleshooting steps may differ in current versions.

If VDM takes longer than expected to open, review the configured folder locations in Settings. An unavailable or inaccessible path can cause the legacy application to pause while it attempts to access that location.

Check Folder Locations

  1. Open Settings in VDM.
  2. Select User Options.
  3. Locate the Folder Locations section.
  4. Review the configured paths.
  5. Confirm that each location is available and accessible.

Pay particular attention to paths that point to:

  • Network shares
  • Mapped drives
  • OneDrive or other redirected folders
  • Locations that may no longer exist

If a configured location is unavailable, update it to a valid path.

Folder Locations configured under VDM User Options.

Check the Application Logs

If VDM continues to start slowly, review the Application Logs for errors related to folder access.

  1. Open Logs.
  2. Select Application Logs.
  3. Select the appropriate date and time range.
  4. Click Refresh.
  5. Review the log entries for directory or folder-related errors.

Application Logs in VDM.

In the legacy application, an unavailable folder location may generate Error Code 6020 or another message indicating that VDM could not create or access the configured directory.

Correct the Invalid Path

If the logs identify an unavailable folder:

  1. Return to Settings > User Options.
  2. Locate the affected entry under Folder Locations.
  3. Update the path to a valid, accessible location.
  4. Close and reopen VDM.
  5. Confirm whether startup time has improved.

If VDM Is Still Slow to Start

If all configured folder locations are valid and VDM is still slow to open:

  • Confirm that network locations are responding normally.
  • Check whether OneDrive or another synchronization service is delaying access to configured folders.
  • Review the Application Logs for other errors occurring during startup.
  • Contact BridgeWorks Support if the delay continues.

Note: These troubleshooting steps are specific to the 2025 legacy application and may not apply to VDM 2026 and later.

Related articles

Related articles

Comments

0 comments

Please sign in to leave a comment.