Cloud Drive Mapper (CDM) 3.20 General Availability Release

Release date: August 18, 2025

End of Support for pre-release versions

Support for CDM’s pre-release versions (v3.19 and earlier) ended on April 16, 2026. Consequently, break-fix support, and contractual SLAs are no longer in effect. If you are still using a pre-release version of CDM, we recommend updating to the latest version.

 

CDM client

Enhancements

  • CDM will now dynamically detect whether a drive is active, enabling us to use the Microsoft Graph notification subscription relay service efficiently for drive changes.

    Reference No: 28775

  • We’ve renamed the CDM core application from CDM.NativeClient to CDM.Core. If your organization uses proxies or security software, you’ll need to update the name of the CDM core application.

    Reference No: 32141

  • You can now deploy a custom bandwidth policy to users and computers using an override key in the registry. The override key can be distributed through Group Policy, Microsoft Intune, or any other orchestration mechanism, allowing for a more customized user experience.

    Reference No: 32379

  • We’ve optimized CDM’s overall ability to support Unicode characters within its file system and Co-Authoring with Microsoft Office.

    Reference No: 34222

  • We’ve optimized the CDM startup flow to ensure internal components are only loaded when necessary. This helps optimize CDM’s background performance before users are logged in or drives are mapped.

    Reference No: 34240

  • We’ve optimized CDM’s loading and mapping time by introducing an event-based system for scenarios where a default mapping group has no drive mappings and you have a delayed registry update for the custom mapping group overrideId.

    Reference No: 34242

  • We’ve changed how the AppData folder structure works to support the ability for multiple users with the same Windows username to use CDM in the future.

    Reference No: 34278

  • We’ve optimized CDM’s drive mapping process to ensure it maps drives faster by running the first delta after the drive has been mapped instead of before, when it may already have retained data from a previous session.

    Reference No: 35025

  • We’ve optimized our caching solution for Microsoft 365 to reduce the number of requests made when mapping multiple drives.

    Reference No: 35031

  • You may notice that we now log the processId and processName in our log files for improved troubleshooting, especially during periods of excessive drive activity.

    Reference No: 35354

Bug fixes

  • Customer Request icon
    Customer-reported

    We’ve fixed the issue related to Office documents with Unicode characters. You can save such documents without any trouble, and their names will also appear correctly in the title bar.

    Reference No: 31151

  • Customer Request icon
    Customer-reported

    We’ve fixed the issue preventing CDM from mapping a Direct: OneDrive with a custom folder redirection policy.

    Reference No: 31375

  • Customer Request icon
    Customer-reported

    We’ve fixed the issue related to parent folders with non-Unicode characters such as ø. You can now open Office documents stored in such folders from the Recent documents list in Microsoft Office apps.

    Reference No: 31677

  • Customer Request icon
    Customer-reported

    We’ve fixed the issue where special characters in Office document names prevented users from saving such files.

    Reference No: 31782

  • We’ve fixed the issue causing File Explorer to hang when you create a file and immediately rename it.

    Reference No: 34813

  • Customer Request icon
    Customer-reported

    We’ve fixed an issue causing File Explorer and CDM to crash when accessing a folder where a sub-site and a folder shared the same name, resulting in an unhandled duplicate.

    Reference No: 35253

  • We’ve fixed the issue preventing users from resolving conflicts that occurred in a previous CDM session.

    Reference No: 35261

  • Customer Request icon
    Customer-reported

    A recent change to Microsoft’s Identity platform malformed our tokens, resulting in access issues. To comply with this change, we’ve implemented a new, improved method for obtaining access tokens for Microsoft Graph and SharePoint resources.

    Reference No: 35538

  • We’ve fixed the issue preventing users from exiting CDM when in an unauthenticated state or following an error at startup.

    Reference No: 35863

  • We’ve fixed the issue that stopped CDM from loading properly on a new Hyper-V virtual machine because the AppData folder was unavailable.

    Reference No: 35889

  • We’ve fixed an issue preventing session migration from completing successfully and causing CDM to crash on VDI servers when using fragmented sync trees.

    Reference No: 36134

CDM installer

Enhancements

  • The upgrade process has been improved significantly to run multiple network providers side by side when changing driver versions. This enhancement eliminates the need to reboot the machine in cases where the upgrade would previously fail without one.

    Reference No: 32442

  • CDM can now gracefully shut down all user sessions in VDI environments and on computers with multiple user sessions running CDM to ensure the upgrade process can successfully complete.

    Reference No: 34199

  • You can now optionally install the Microsoft Office Add-in for CDM via the EXE installer. Although this feature is not currently functional, it can come in handy when troubleshooting issues related to the interaction between Microsoft Office apps such as Word, Excel, PowerPoint, Outlook (classic), and CDM.

    Reference No: 34652

Bug fixes

  • We’ve fixed the issue in the CDM EXE installer that allowed users to quit the installation even though their ability to do so was disabled.

    Reference No: 22551

  • We’ve fixed an issue that would reset the log level after an upgrade.

    Reference No: 34667

Related topics:

Cloud Drive Mapper (CDM) 3.20.1 (GA) Hotfix

Cloud Drive Mapper (CDM) 3.20.2 (GA) Hotfix