Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
Microsoft has deprecated the Windows WebClient service, the client-side component that lets File Explorer and some applications access WebDAV locations as folders or mapped drives. The service may still be present in supported Windows client versions, but the available evidence does not establish a universal final-removal date.
Administrators should treat this as a migration warning: inventory WebDAV dependencies now, test a workload-appropriate replacement, and use service-start commands only as temporary continuity measures. This change is about the Windows WebDAV client—not automatically the WebDAV server module in IIS.
What is actually being deprecated?
WebDAV is an HTTP extension that adds file-oriented operations such as creating, copying, moving, deleting, and locking resources. Windows exposes WebDAV through a client-side redirector and the WebClient Windows service:
File Explorer or application
↓
Windows WebDAV redirector
↓
WebClient service
↓
HTTP or HTTPS WebDAV serverMicrosoft describes the Windows Web Client service as allowing WebDAV-enabled folders to appear to protocol clients as UNC-style file shares. See the Microsoft Open Specifications description.
#1 Best Overall
Do not confuse these similarly named technologies:
- Windows WebClient service: the client-side Windows service involved in WebDAV folder and mapped-drive access.
- WebDAV protocol: the HTTP-based protocol used by compatible servers and clients.
- WebDAV redirector: the Windows component that presents WebDAV URLs through a file-system-like interface.
- IIS WebDAV module: server-side functionality hosted in Internet Information Services. Deprecating Windows WebClient does not, by itself, prove that IIS WebDAV has been removed.
- .NET
WebClientclass: an unrelated .NET networking API.
Microsoft’s IIS documentation separately discusses the WebDAV redirector and server functionality. A Microsoft Q&A response also distinguishes the Windows 10/11 WebClient component from WebDAV hosted on an IIS server.
Is WebClient already removed from Windows?
Not universally, based on the available evidence. WebClient is deprecated, and an HTMD article published on November 6, 2023, reported that the service was not started by default and that removal was coming. That wording should be understood as a warning about future Windows changes, not proof that the service has already disappeared from every supported Windows release.
A Microsoft troubleshooting page updated February 12, 2026, still documents the WebClient service, its registry configuration, and related troubleshooting for supported Windows client systems. This indicates that the functionality remained present in at least some supported releases at that time, but it is not a promise of indefinite support.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsNo universal final-removal date is established by the sources reviewed. Availability can vary by Windows edition, release, servicing state, and future feature updates. Administrators should not plan around a particular Windows 11 version unless Microsoft publishes a release-specific announcement or note.
For context, see the original HTMD WebClient deprecation report and Microsoft’s current WebDAV mapped-drive troubleshooting documentation.
Who could be affected?
Potentially affected systems include those that:
- Map an
http://orhttps://WebDAV URL to a drive letter. - Open a WebDAV folder through File Explorer.
- Use a SharePoint or other web-based repository through a legacy WebDAV mapping.
- Run Office-integrated web-folder workflows.
- Use line-of-business software that expects a WebDAV path to behave like a local or SMB share.
- Run logon scripts, scheduled tasks, or services referencing WebDAV UNC paths or mapped drives.
Not every application that uses HTTPS is dependent on WebClient. A product using a direct HTTPS API, a supported synchronization client, SFTP, or a browser interface may be unaffected.
How to find WebClient dependencies
Check the service
On a Windows device, press Win+R, enter services.msc, and locate WebClient. Record whether it exists, its current status, its startup type, and whether it can be started.
Free tools Windows power users keep installed
One-click scans. No signup required.
From an elevated Command Prompt:
sc query WebClientFrom PowerShell:
Get-Service -Name WebClient -ErrorAction SilentlyContinueReview mapped drives
List file-system drives and their displayed targets:
Rank #3
Get-PSDrive -PSProvider FileSystem |
Select-Object Name, Root, DisplayRootLook for targets beginning with http:// or https://, WebDAV terminology, or unusual UNC paths. Also inspect File Explorer locations that open a web folder rather than an SMB share.
Search the surrounding configuration
Review Group Policy, logon scripts, scheduled tasks, deployment scripts, application configuration, and documentation for:
http://andhttps://file pathsdavorwebdav- mapped drive letters assigned to web locations
- references to
HKLMSYSTEMCurrentControlSetServicesWebClient - jobs that upload, download, rename, or lock files through a WebDAV path
This is an initial discovery aid, not a complete enterprise dependency scan. A business application may use WebClient indirectly without exposing an obvious mapped drive.
Can you still start the service?
If WebClient is still installed and your organization permits its use, starting it may restore access temporarily:
Rank #4
net start WebClientTo stop it again:
net stop WebClientThese commands do not reverse Microsoft’s deprecation decision. They are continuity or troubleshooting steps only. They will not help if a future Windows release removes the component, and they should not be treated as a migration plan.
Common WebDAV failures are not always caused by deprecation
Credential prompts and authentication errors
Microsoft documents cases where WebDAV access fails because the redirector uses WinHTTP and handles credentials differently for fully qualified domain names. Symptoms can include repeated credential prompts, disconnected mapped drives, or messages such as “The operation being requested was not performed because the user has not been authenticated.”
Microsoft’s guidance discusses the AuthForwardServerList registry setting for narrowly specifying trusted servers. If it is required, use the smallest possible list, prefer HTTPS, and avoid broad wildcards. Forwarding credentials to every server matching an overly broad pattern creates a security risk. See Microsoft’s guidance on credential prompts when accessing WebDAV FQDN sites.
Recommended Free Tools
“The network name cannot be found”
This error can result from a stopped or unavailable WebClient service, an incorrect URL, authentication problems, proxy behavior, or a server-side issue. Do not assume that starting the service permanently fixes it.
Best Value
Large folders and file limits
Microsoft documents WebDAV enumeration problems and memory growth when folders contain many files. Older IIS redirector documentation lists historical defaults of 50,000,000 bytes for FileSizeLimitInBytes and 1,000,000 bytes for FileAttributesLimitInBytes. These values should not be treated as universal limits for every current Windows release.
For related troubleshooting, consult Microsoft’s documentation on accessing WebDAV web folders and the WebDAV redirector.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.WebDAV is not the same as SMB
A WebDAV mapping may look like a network drive, but it does not provide the same performance, locking behavior, latency, or application compatibility as an SMB share. Applications requiring database-style locking, high-frequency random access, or strict atomic file semantics are poor candidates for WebDAV. They may also be poor candidates for a consumer synchronization folder.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteA SharePoint library mapped through WebDAV is likewise not equivalent to native SharePoint or OneDrive integration. Authentication policy changes, URL changes, credential prompts, disconnected drives, and the eventual loss of WebClient support can all break that experience.
What should replace WebDAV?
The right replacement depends on the workload rather than on the protocol name.
| Requirement | Better direction | Important qualification |
|---|---|---|
| Office collaboration, versioning, permissions, retention, and controlled sharing | SharePoint Online, OneDrive for Business, or Teams-backed libraries | Not a drop-in replacement for every local-path or application-locking requirement. |
| User-facing file synchronization | OneDrive, Dropbox, Box, or Nextcloud desktop client | Synchronization introduces local copies, conflict handling, and offline behavior that must be tested. |
| Traditional internal shared-drive semantics | SMB, Azure Files, or a private network file service | Evaluate network access, VPN, identity, backup, and permissions. |
| Automated partner or server-to-server transfer | SFTP, HTTPS APIs, object-storage APIs, or managed file transfer | Prioritize retry logic, service identities, logging, encryption, and auditability. |
| Legacy vendor workflow | Vendor-supported connector, API, or migration path | Do not replace a required application path with a generic sync folder without vendor validation. |
Microsoft 365 organizations can begin with SharePoint and OneDrive. Organizations seeking self-hosted collaboration may evaluate Nextcloud. Dropbox and Box are possible synchronization or content-management options, but neither should be assumed to reproduce WebDAV path and locking behavior.
Migration checklist
- Identify every WebDAV URL, mapped drive, script, scheduled task, and application dependency.
- Classify each workload as collaboration, synchronization, internal file sharing, or automated transfer.
- Document identity requirements, including SSO, Entra ID, certificates, service accounts, MFA, and conditional access.
- Test permissions, file locking, concurrent editing, renames, special characters, large files, and directory enumeration.
- Test offline behavior, synchronization conflicts, retries, proxy traversal, and recovery after network interruption.
- Validate retention, audit, DLP, legal hold, data residency, and external-sharing requirements.
- Pilot the replacement with representative users and applications.
- Keep a temporary continuity procedure documented, but do not make it the target state.
- Remove obsolete mappings, scripts, and registry workarounds after cutover.
- Monitor for remaining WebClient usage and confirm that business owners have accepted the new workflow.
Bottom line
Microsoft’s confirmed action is the deprecation of the Windows WebClient/WebDAV client service. The service may still exist on supported Windows systems, and the reviewed evidence does not establish a universal final-removal date. That uncertainty is not a reason to wait: any workflow dependent on a WebDAV mapped drive, File Explorer web folder, or legacy application path should be inventoried and migrated before a future Windows change turns a warning into an outage.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
