Skip to main content

Issues on Windows Based Systems

These checks apply to a drive mapped with Windows' built-in WebDAV client. For an existing connection that fails, identify the failed operation and exact error before changing settings. The Windows setup requirements explain the client service and transfer limits.

We recommend the Files.com Desktop App for desktop access. It connects to Files.com without depending on Windows' deprecated WebClient service.

"Windows Cannot Access..." Error

A stopped or unavailable WebClient service is one possible cause of a mapping failure. Open Services (services.msc) and check whether WebClient is present and running. If it is stopped, ask your IT administrator to start it if your organization permits native WebDAV access. If it is missing, review the client requirements, including the separate Windows Server feature.

If the service is running, verify the site's HTTPS address, then check network access and login requirements. The error message alone does not identify which of these checks failed.

File Size Errors

When a WebDAV download fails with 0x800700DF and a message that the file exceeds the allowed size, compare the file's size with the Windows client's configured limit. A file can fit within your Files.com storage allowance and still exceed that client limit.

If the workflow must use native WebDAV, your IT administrator can review FileSizeLimitInBytes in Microsoft's WebDAV client settingsExternal LinkThis link leads to an external website and will open in a new tab. Changing that value does not remove the client's other transfer constraints.

Interrupted or Slow Transfers

Windows WebClient has connection and request timeouts. If a transfer stops, record the file size, elapsed time, and exact error so your IT administrator can compare the failure with the configured timeout valuesExternal LinkThis link leads to an external website and will open in a new tab and any network interruption.

Check the destination after an interrupted upload. A partial file can be visible before the client has finished writing it, so do not send that file into downstream processing until the upload completes.

Some Files or Folders Are Not Visible on the WebDAV Mapped Drive

Sign in to the Files.com web app with the same account and check the affected path. If the files are visible there, compare the Windows client's error and the path being opened. Long paths can exceed what the client or local application handles.

Long-path support depends on both Windows configuration and application supportExternal LinkThis link leads to an external website and will open in a new tab, so enabling a system setting alone does not make every application accept longer paths. Use the web app to access the file while investigating the affected client's path handling.

WebDAV Drive Is Not Automatically Reconnected After Reboot

Check that WebClient is running after sign-in, then open the mapped drive and complete any credential prompt. If sign-in fails, follow WebDAV Login Issues to check the account before creating the mapping again.