Custom URL scheme (dvagsc://) no longer forwarded to Windows VM via Parallels Desktop

PatrickS11

Bit poster
Hi everyone,

a custom Windows URL scheme "dvagsc://" used to automatically open a Windows application when clicked on macOS (e.g., in Apple Mail). Parallels Desktop forwarded the URL into the running Windows 11 VM. This stopped working recently.

Environment:
  • macOS 15/26 "Tahoe"
  • Parallels Desktop (latest version)
  • Windows 11 Pro VM
  • Parallels Tools installed
  • Integration features enabled (application sharing etc.)
  • macOS apps tested: Apple Mail, Terminal ("open dvagsc://test")
Expected behavior:
Clicking dvagsc:// should launch Parallels (if needed) and forward the URL directly into the VM so the Windows application can process it. This worked flawlessly for a long time.

Current behavior:
  • macOS says "No application specified to open the URL"
  • If I manually choose Parallels Desktop, only the Control Center opens
  • The URL is NOT forwarded to the VM
  • Even when the VM is already running, Windows never receives anything
What I have tried:
  • Reinstalled Parallels Tools
  • Rebooted macOS and VM
  • Verified all integration settings
  • Created a custom macOS URL handler (Info.plist + duti)
    • Still only opens Control Center, no URL forwarding
What I want:
  1. Restore the previous behavior (URL forwarded directly into the VM), or
  2. Allow mapping this custom scheme to a specific Windows application (e.g., Edge inside Windows)
Important: I do NOT want Edge as default macOS browser. Only this one custom scheme should be handled inside Windows.

Questions:
  1. Is forwarding custom URL schemes to the VM still supported?
  2. Was this changed/removed in a recent Parallels Desktop update?
  3. Is there an official method to map a macOS custom scheme into a Windows app?
  4. If the feature is deprecated, is there any recommended workaround?
Happy to provide version numbers or a reproducible test case (e.g. "open dvagsc://test" in Terminal).

Thanks in advance!
 
Hi everyone,

just a quick update: this issue is now resolved.

After installing the latest Windows 11 25H2 update, the custom URL scheme works again as expected. dvagsc:// links are now correctly handled and forwarded to the Windows environment.

It looks like this was caused by a Windows-side issue rather than Parallels itself.

This thread can be closed.

Thanks to everyone who looked into this.
 
Back
Top