You are correct. I’d only allow 1.2 or 1.3, should be possible https://blogs.msdn.microsoft.com/kaushal/2011/10/02/support-for-ssltls-protocols-on-windows/
SSL3 is definitely a huge security risk
Do you say that Windows 10 webdav client is working again, if you force connections to either use TLSv1 or SSLv3? If I understood you correctly, than this would not be a solution to me, due to the security concern you already mentioned. What would be the solution for connections using TLSv1 and up?
Same issue here, can’t get to map anything with Windows 10 but works well with any other webdav client.
Any other recommendations ?
Under Windows 2016 server, you have to install a feature and start services, see here :