Microsoft Office on Windows with Cryptomator 1.3.0

[tobihagemann]

We've received some reports via email that Microsoft Office on Windows doesn't work as expected with Cryptomator 1.3.0's release candidate. And the reports state that it just worked fine with Cryptomator 1.2.3. Our suspicion is that there is some kind of regression in 1.3.0.

This is a collective thread to investigate the issue. If you're using Windows and Office, please try out our latest release candidate: https://github.com/cryptomator/cryptomator/releases/tag/1.3.0-rc9 (UPDATED TO RC 9)

If you are indeed experiencing issues (e.g., you can't open Word/Excel files that are inside a Cryptomator vault), please let us know what versions of Windows and Office you're using. It would be great if you could turn on debug mode in the settings and send us the log file (located at %appdata%/Cryptomator/cryptomator.log) to support@cryptomator.org afterwards. Please don't post the log file here because they may contain too much information while in debug mode.

Thank you for testing! 👍

Fyi, RC 7 has some known issues (#510, #511) if you're stumbling upon them while testing. (Fixed in RC 8.)

Edit: Updated link to RC 9.

[chrsch]

Hi, experiencing this issue with word and excel files on Windows 10 Pro x64 using MS Office 2016. Happened to me with Word and Excel. The same vault works fine on another machine with Windows 10 Home and MS Office 2013. You'll get log file by mail.

Additional observation: On the Windows 10 Pro machine only office files in subdirectories fail to open. If the file is located in the root of the fault, it can be opened without problem.

[gschlager]

I'm having the same problem on Windows 10 with Office 365. Seems to work when I disable the IPv6 literal.

[cocoon]

I had the same problem with Word from Office 2016 (32 bit) and Word files on Windows 10 x64 1703, word was trying to load the file forever.

I then killed the word process and directly while still vault was unlocked disabled "use IPv6 literal" (like gschlager mentioned) and tried to open the word file again, it showed "Directory name not valid" or something similar (I wasn't able to reproduce the message later again).
I re-enabled "use IPv6 literal" and opened the word file again, word was loading forever again, I had to kill the process.

I then locked the Vault and disabled "use IPv6 literal", unlocked the vault and then the word file opened without a problem.

[An-error-occurred]

Hey there!
I do not have 1.3, I'm still working with 1.2.3 (Onedrive)! Still, Office files won't load.

Here are my observations:

A)
I've installed Cryptomator on my desktop PC (Win10 Pro 1703; Build 15063.413) and own the most recent Office 365.
-> NO ISSUES*

B)
Cryptomator on my Surface (exactly the same Win and Office):
-> OFFICE FILES DO NOT OPEN
Pictures will load and if I copy the office file to another folder outside the vault, I can read and edit the files. The error reads: "[Pfad] konnte leider nicht geöffnet werden"

However, here's the interesting thing: If I go online with my Surface, the problem goes away! *I haven't tested it with my desktop PC.
You've still got my email-address, so if you need further testing or spcific logs from both my PCs, drop me a line.

[overheadhunter]

Please retest with 1.3.0-rc8.

[An-error-occurred]

Same issue. I've sent you the log from my surface.

[overheadhunter]

@An-error-occurred If I undestood you correctly, another way to report your error would be "Office files stored in a vault don't open, when I'm offline". If you agree, I'd like you to open a different issue, even though I'm pretty sure it's an upstream bug caused by Office.

PS we get tons of emails, not sure which one is yours ;) But we didn't receive any log within the last 15min.

[An-error-occurred]

I've used two different email-addresses by accident, sorry.
If you don't find the log, I'll send it again. I've opened a new issue.

[markuskreusch]

Tested on Win7 and 10 using Office 2007 and 2016. Didn't have any problems using RC8 but had the described problems before so seems to be fixed.

[overheadhunter]

Please retest with 1.3.0-rc9.

[cocoon]

Seems to be fixed with 1.3.0 final for me.