Cannot copy files anymore without a warning message

[An-error-occurred]

Basic Info

This is a bug report.

I'm using Windows in version: Win10 Pro 1703; Build 15063.413

I'm running Cryptomator in version: 1.3.0-RC8

Description

I've realised that the Vaults don't open as "localhost" anymore but as "127.0.0.1".
Since then (but I'm not entirely sure) I cannot copy files without having a windows message pop up that tells me "Durch diese Dateien entstehen möglicherweise Risiken für den Computer." (see attached image).

This is probably a Win-issue and not a Cryptomator problem, but it concerns me now and it didn't before, so I think you should know about it.

Btw. I've tried this: http://www.techn1k-blog.de/netzlaufwerk-nervige-sicherheitswarnungen-abschalten/
No success. The IP I added was 127.0.0.1, just as the drive is called.

[An-error-occurred]

New info: Interestingly, only Drag&Drop gives me the error. Copying / moving by keyboard works. But as I prefer mouse-based copying, it still sucks. Any ideas here?

[tobihagemann]

I'm totally with you. We're able to reproduce this behavior and are currently looking into it. Thank you for your bug report! 👍

[overheadhunter]

We need further testing on this issue. I have tried to play around with the internet security options as advised here, however without success so far. Tried to add 127.0.0.1 and file://127.0.0.1 to the whitelist. Maybe this isn't sufficient or one has to restart the machine in between?

[An-error-occurred]

As I said, I tried the same thing. My link above suggests this solution, too. Apparently, a restart is not needed. I've tried a whole list of things:
\127.0.0.1
\127.0.0.1@42427
the drive letter
...

Nothing seems to work. I disabled Windows Firewall and manually changed every "Internet Security" setting manually to the lowest protection level - it didn't affect the error in any way. If there's st. else I can do / try out, give me a whistle.

EDIT: I've just completed the more sophisticated way described here:

You can control this with Group Policy, as well. Use gpedit.msc and drill down to

User Configuration → Policies → Administrative Templates → Windows Components → Internet Explorer → Internet Control Panel → Security Page

Enable "Intranet Zone Template" with the Low option.

Then enable "Site to Zone Assignment List" and use the Show button to add your "sites" (servername, servername.domain, ipaddress - the values you enter depend on what name or IP you use to access the share) with a value of 1.

Lastly - and this is the most important step - drill down one folder in gpedit to "Intranet Zone" and enable for "Show security warning for potentially unsafe files", choosing Enable from the drop-down.

Close gpedit, reboot or run gpupdate /force and enjoy no more annoying Windows Security dialogues!

But, sadly, still nothing.

[overheadhunter]

Update: We've mitigated this problem by adding an alias for 127.0.0.1 to the hosts file and mounting the drive via net use * \\alias@42427\DavWWWRoot\asdqwe123\vaultname.

Will now need to update the installer to add this alias and the mounter to use it.

Edit: We will provide an RC9 download link shortly.

[overheadhunter]

Fixed with 1.3.0-rc9.

[ghost]

Hi!
With fresh Installation of 1.6.1 on Windows 10 the problem reoccurs, cause the installation does not seem to set the entry in the hosts file

[infeo]

Workaround:
Add to the file C:\Windows\System32\drivers\etc the following line:

127.0.0.1 cryptomator-vault

Admin priviliges are needed for this.

[ghost]

Version 1.6.5 (at least) sets all necessary entry for WebDAV (filesize limit in registry), host file)
via patchWebDAV.*, everything seems fine now when I do first time installations.