Windows 10: WebDAV broken in update 1903

Discus and support WebDAV broken in update 1903 in Windows 10 Network and Sharing to solve the problem; Hi, it appears that after update 1903, something got broken in WebDAV support. Previously, I could run WebDAV server on a Linux host like this:... Discussion in 'Windows 10 Network and Sharing' started by Vladimir Prus, Aug 11, 2019.

  1. VLADIMIR PRUS
    Vladimir Prus Win User

    WebDAV broken in update 1903


    Hi,


    it appears that after update 1903, something got broken in WebDAV support. Previously, I could run WebDAV server on a Linux host like this:


    sudo docker run --restart always -e AUTH_TYPE=Digest -e USERNAME=ghost -e PASSWORD=secret1234 --publish 7777:80 -d bytemark/webdav


    And then I could connect to port 7777 on that server from Windows 10 and put files there with no issues. Now, any attempt to put file there

    results in "Can't read from source file or disk". Logs on the server side report this:


    192.168.173.26 - - [11/Aug/2019:09:00:14 +0000] "OPTIONS / HTTP/1.1" 401 381 "-" "Microsoft-WebDAV-MiniRedir/10.0.18362"

    192.168.173.26 - - [11/Aug/2019:09:00:14 +0000] "OPTIONS / HTTP/1.1" 401 381 "-" "Microsoft-WebDAV-MiniRedir/10.0.18362"

    192.168.173.26 - - [11/Aug/2019:09:00:14 +0000] "OPTIONS / HTTP/1.1" 401 381 "-" "Microsoft-WebDAV-MiniRedir/10.0.18362"

    192.168.173.26 - - [11/Aug/2019:09:00:14 +0000] "OPTIONS /desktop.ini HTTP/1.1" 401 381 "-" "Microsoft-WebDAV-MiniRedir/10.0.18362"

    192.168.173.26 - - [11/Aug/2019:09:00:15 +0000] "OPTIONS /desktop.ini HTTP/1.1" 401 381 "-" "Microsoft-WebDAV-MiniRedir/10.0.18362"

    192.168.173.26 - - [11/Aug/2019:09:00:15 +0000] "OPTIONS / HTTP/1.1" 401 381 "-" "Microsoft-WebDAV-MiniRedir/10.0.18362"

    192.168.173.26 - - [11/Aug/2019:09:00:15 +0000] "OPTIONS / HTTP/1.1" 401 381 "-" "Microsoft-WebDAV-MiniRedir/10.0.18362"

    192.168.173.26 - - [11/Aug/2019:09:00:15 +0000] "OPTIONS / HTTP/1.1" 401 381 "-" "Microsoft-WebDAV-MiniRedir/10.0.18362"

    192.168.173.26 - - [11/Aug/2019:09:00:25 +0000] "OPTIONS / HTTP/1.1" 401 381 "-" "Microsoft-WebDAV-MiniRedir/10.0.18362"

    192.168.173.26 - ghost [11/Aug/2019:09:00:25 +0000] "OPTIONS / HTTP/1.1" 200 - "-" "Microsoft-WebDAV-MiniRedir/10.0.18362"

    192.168.173.26 - - [11/Aug/2019:09:00:25 +0000] "PROPFIND / HTTP/1.1" 401 381 "-" "Microsoft-WebDAV-MiniRedir/10.0.18362"

    192.168.173.26 - ghost [11/Aug/2019:09:00:25 +0000] "PROPFIND / HTTP/1.1" 207 831 "-" "Microsoft-WebDAV-MiniRedir/10.0.18362"

    192.168.173.26 - - [11/Aug/2019:09:00:25 +0000] "PROPFIND / HTTP/1.1" 401 381 "-" "Microsoft-WebDAV-MiniRedir/10.0.18362"

    192.168.173.26 - ghost [11/Aug/2019:09:00:25 +0000] "PROPFIND / HTTP/1.1" 207 831 "-" "Microsoft-WebDAV-MiniRedir/10.0.18362"

    192.168.173.26 - - [11/Aug/2019:09:00:25 +0000] "PROPFIND / HTTP/1.1" 401 381 "-" "Microsoft-WebDAV-MiniRedir/10.0.18362"

    192.168.173.26 - ghost [11/Aug/2019:09:00:25 +0000] "PROPFIND / HTTP/1.1" 207 2021 "-" "Microsoft-WebDAV-MiniRedir/10.0.18362"

    192.168.173.26 - - [11/Aug/2019:09:00:42 +0000] "PROPFIND /desktop.ini HTTP/1.1" 401 381 "-" "Microsoft-WebDAV-MiniRedir/10.0.18362"

    192.168.173.26 - ghost [11/Aug/2019:09:00:42 +0000] "PROPFIND /desktop.ini HTTP/1.1" 404 209 "-" "Microsoft-WebDAV-MiniRedir/10.0.18362"

    192.168.173.26 - - [11/Aug/2019:09:00:42 +0000] "PROPFIND / HTTP/1.1" 401 381 "-" "Microsoft-WebDAV-MiniRedir/10.0.18362"

    192.168.173.26 - ghost [11/Aug/2019:09:00:42 +0000] "PROPFIND / HTTP/1.1" 207 2021 "-" "Microsoft-WebDAV-MiniRedir/10.0.18362"

    192.168.173.26 - - [11/Aug/2019:09:00:44 +0000] "PROPFIND /test.png HTTP/1.1" 401 381 "-" "Microsoft-WebDAV-MiniRedir/10.0.18362"

    192.168.173.26 - ghost [11/Aug/2019:09:00:45 +0000] "PROPFIND /test.png HTTP/1.1" 404 206 "-" "Microsoft-WebDAV-MiniRedir/10.0.18362"

    192.168.173.26 - - [11/Aug/2019:09:00:45 +0000] "PROPFIND / HTTP/1.1" 401 381 "-" "Microsoft-WebDAV-MiniRedir/10.0.18362"

    192.168.173.26 - ghost [11/Aug/2019:09:00:45 +0000] "PROPFIND / HTTP/1.1" 207 831 "-" "Microsoft-WebDAV-MiniRedir/10.0.18362"

    192.168.173.26 - - [11/Aug/2019:09:00:45 +0000] "PUT /test.png HTTP/1.1" 401 381 "-" "Microsoft-WebDAV-MiniRedir/10.0.18362"

    192.168.173.26 - ghost [11/Aug/2019:09:00:46 +0000] "PUT /test.png HTTP/1.1" 201 181 "-" "Microsoft-WebDAV-MiniRedir/10.0.18362"

    192.168.173.26 - - [11/Aug/2019:09:00:46 +0000] "LOCK /test.png HTTP/1.1" 401 381 "-" "Microsoft-WebDAV-MiniRedir/10.0.18362"

    192.168.173.26 - ghost [11/Aug/2019:09:00:46 +0000] "LOCK /test.png HTTP/1.1" 200 447 "-" "Microsoft-WebDAV-MiniRedir/10.0.18362"

    192.168.173.26 - - [11/Aug/2019:09:00:46 +0000] "PROPPATCH /test.png HTTP/1.1" 401 381 "-" "Microsoft-WebDAV-MiniRedir/10.0.18362"

    192.168.173.26 - ghost [11/Aug/2019:09:00:46 +0000] "PROPPATCH /test.png HTTP/1.1" 207 392 "-" "Microsoft-WebDAV-MiniRedir/10.0.18362"

    192.168.173.26 - - [11/Aug/2019:09:00:46 +0000] "HEAD /test.png HTTP/1.1" 401 - "-" "Microsoft-WebDAV-MiniRedir/10.0.18362"

    192.168.173.26 - ghost [11/Aug/2019:09:00:46 +0000] "HEAD /test.png HTTP/1.1" 200 - "-" "Microsoft-WebDAV-MiniRedir/10.0.18362"

    192.168.173.26 - - [11/Aug/2019:09:00:46 +0000] "PUT /test.png HTTP/1.1" 401 381 "-" "Microsoft-WebDAV-MiniRedir/10.0.18362"

    192.168.173.26 - - [11/Aug/2019:09:00:47 +0000] "DELETE /test.png HTTP/1.1" 401 381 "-" "Microsoft-WebDAV-MiniRedir/10.0.18362"

    [Sun Aug 11 09:00:47.973048 2019] [dav:error] [pid 14:tid 140601082137320] [client 192.168.173.26:53610] Could not DELETE /test.png due to a failed precondition (e.g. locks). [424, #0]

    [Sun Aug 11 09:00:47.973075 2019] [dav:error] [pid 14:tid 140601082137320] [client 192.168.173.26:53610] An error occurred on another resource, preventing the requested operation on this resource. [424, #0]

    192.168.173.26 - ghost [11/Aug/2019:09:00:47 +0000] "DELETE /test.png HTTP/1.1" 424 568 "-" "Microsoft-WebDAV-MiniRedir/10.0.18362"


    First, the file is uploaded with no issues, then I see HEAD, followed by another PUT, followed by DELETE (which fails, because the file still locked).


    Does anybody know how to solve this problem?

    :)
     
    Vladimir Prus, Aug 11, 2019
    #1
  2. ANAK
    Anak Win User

    What is "Jackrabbit Webdav Server"? Why is it wanting my password?


    • What is Jackrabbit?
    Sounds scary to me, do you use Java?


    • What's with the unsecure connection?
    As you put it "my destination", is not secure. What I've seen is, this crops up when somehow a microsoft office 07, 10, and 13 application tries to use an unsecure connection.


    • How do I stop this?
    There may be a way but you will need to work in the registry, first go over this KB article: https://Office application opens blank from Sharepoint,WebDAV or site when it is HTTP | support.microsoft.com/en-us/help

    The area you want to concentrate on is: Step 1: Configure WebDAV Redirector on the client. Skip the Windows XP and Windows Server 2003 part and go to the Windows Vista, Windows 7, and Windows 8 To enable Basic authentication on the client computer, and study the steps. You may be adding a key. BasicAuthLevel [some systems already have the key but it's set to 0 ]. Before you start create a restore point: System Restore Point - Create in Windows 10 Then complete the steps from the beginning of the Vista, 7, 8 section.


    • Here's a heads up:
    1.) I've seen that the BasicAuthLevel can exist in your registry but it's set to ( 0 ) which causes the problem you're experiencing. Then all you have to do is change the value by right clicking on it and left click on Modify then enter a 1 or 2 in the value data box.

    2.) It says to use a value of 2 for the BasicAuthLevel value but this is for secure and non secure SSL connections, I haven't found anything as to what is meant by non-secure SSL .

    I did take a look at my registry and found it's set to (1) 1 - Basic authentication enabled for SSL connections only: One (1) is what I'd go with.

    WebDAV broken in update 1903 [​IMG]
     
    Anak, Aug 11, 2019
    #2
  3. HARMANIKSINGH
    HarmanikSingh Win User
    WebDAV error after upgrading to Windows 10

    One of my users have upgraded to windows 10 and since then has not able to copy files to our webdav server.

    Below is the error we get every time we copy/drag from a file from windows folder to webdav folder.

    The following has been tried, has worked in previous windows versions but not working on windows 10:


    • Changing the below registry settings
      • Navigate to the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WebClient\Parameters
      • In this key, change the value of BasicAuthLevel to 2

    • I have tried both of the below
      • Map network drive
      • Add network location

    • Tried using webdav client Cyberduck but it does not work on windows 10
    Is there any other change of setting or an alternate recommended client that I can try?
     
    HarmanikSingh, Aug 11, 2019
    #3
  4. PIPPS
    Pipps Win User

    WebDAV broken in update 1903

    Is my graphics card broken?

    UPDATE: Please see here.

    I have a Sapphire HD 4830.

    When I boot into XP all is initially fine and I am able to see the desktop.

    However, when I click on the start bar and navigate a few steps, I receive an immediate white screen of death and a total irrecoverable lock-up.

    I am confused about what this could mean and I would be grateful for any suggestions on the best course of action to test and repair the problem.

    Does this sort of issue suggest that the graphics card is irretrievably broken?
     
    Pipps, Aug 11, 2019
    #4
Thema:

WebDAV broken in update 1903

Loading...

  1. WebDAV broken in update 1903 - Similar Threads - WebDAV broken update

  2. WebDav client logs / debug

    in Windows 10 Network and Sharing
    WebDav client logs / debug: Hi folks, does someone know how to turn on the webdav client logging, to troubleshoot? and where logs are thereafter? Where one can find the possible values for the registry keys hklm/sys/ccs/svcs/webclient/parameters DebugClient and ServiceClient ? yup I already googled much...

  3. High CPU usage on winword.exe windows 10 1903 while editing documents with WebDAV

    in Windows 10 BSOD Crashes and Debugging
    High CPU usage on winword.exe windows 10 1903 while editing documents with WebDAV: Hi, We are using Windows10 1903 with Office Pack 2016, everything works smoothly and fast enough locally, but when the user opens a document with WebDAV on a IIS or apache server winword.exe use a complete CPU core for about 40 seconds, which if so slow I have to say -...

  4. Hich CPU usage on winword.exe windows 10 1903 while editing documents with WebDAV

    in Windows 10 BSOD Crashes and Debugging
    Hich CPU usage on winword.exe windows 10 1903 while editing documents with WebDAV: Hi, We are using Windows10 1903 with Office Pack 2016, everything works smoothly and fast enough locally, but when the user opens a document with WebDAV on a IIS or apache server winword.exe use a complete CPU core for about 40 seconds, which if so slow I have to say -...

  5. 1903 is trash, incesant updates, sfc broken, major slowdown

    in Windows 10 BSOD Crashes and Debugging
    1903 is trash, incesant updates, sfc broken, major slowdown: im an it admin and alot of my clients are having various issues with 1903, from sfc broken and corruption to the machine just slowing down. said machines would run fine on 1809. but then run like trash on 1903. boot times tripled, the spinning circle on boot would start to...

  6. 1903 update has broken iCloud access

    in Windows 10 Installation and Upgrade
    1903 update has broken iCloud access: 1903 update has broken iCloud access. I cannot access iCloud now https://answers.microsoft.com/en-us/windows/forum/all/1903-update-has-broken-icloud-access/e92b7fcc-6c4c-46b1-a10f-050784639943

  7. Windows 10 1903 RemoteFX broken.

    in Windows 10 BSOD Crashes and Debugging
    Windows 10 1903 RemoteFX broken.: I thought I would open up the discussion on this since I can see no sign of it mentioned anywhere yet. Basically RemoteFX is currently broken in Windows 10 1903 at least with generation 2 machines. Basically neither the HtyperV client or Remote Desktop will connect. It...

  8. Microsoft Store broken after 1903 update

    in Microsoft Windows 10 Store
    Microsoft Store broken after 1903 update: I upgraded to the 1903 build a couple of days ago and all seems fine apart from a few Microsoft Store apps and the Store application itself. Usually, when faced with a failed MS Store app I can uninstall the app (either using the GUI or Powershell) and reinstall but since...

  9. Windows settings broken in windows 10 update 1903

    in Windows 10 Customization
    Windows settings broken in windows 10 update 1903: I just updated my gaming pc to windows 10 update 1903, settings was unstable and in the search options (not cortana) The 2 box on the side saying "searching windows" when i click on it, settings freezes and then closes. Is this my fault or a bug?...

  10. WebDAV keeps asking for credentials

    in Windows 10 Network and Sharing
    WebDAV keeps asking for credentials: Hi, Some of my clients have slightly different issues about WebDAV connections. Some of them are prompted on each file (essentially PDFs and MS Office files), some of them on first connection, some of them only with PDFs. The connection is of course saved in the Windows...

Users found this page by searching for:

  1. windows 1903 webdav

    ,

  2. Webdav windows 10 1903

    ,

  3. Windows 10 WebDAV 1903

    ,
  4. webdav windows 10 1903 エラー