Can't play video files in Portable Version

Rasoul · June 9, 2021, 11:02am

Hi
I was testing both portable and non-potable apps and realized that I can’t play videos from local vault using portable version installed on my flash drive (Portable app and vault were located on flash drive and I was using WebDav adapter). But after installing EXE installer (full installation enabled) on windows I was able to play those videos.
So I decided to test it on another PC and again I couldn’t play same video files. Then I lunched EXE Installer and checked installing Cryptomator and WebDav System Configuration. After installing non-potable Cryptomator app the problem was fixed (even after uninstalling it).

What is the problem? Am I missing something in Portable app?

As mentioned here WebDAV System configuration writes a key to the registry. Can those registry keys be the solution?
If YES Can you send me those keys because I don’t want to install Cryptomator on every desktop I connect my flash drive; it is the reason why I’m using Portable version.

Michael · June 9, 2021, 3:58pm

Assuming your video files are bigger that 4GB.
But WebDAV cannot handle files that big.

As far as I know, the portable version does not have dokany included as virtual filesystem. That’s the difference.

Rasoul · June 9, 2021, 7:05pm

No Video files are smaller than 4GB

Rasoul · June 16, 2021, 9:45am

Update: There is no issue with video files on Android App. But still having issues with portable App.

infeo · June 16, 2021, 10:10am

Welcome to the Cryptomator Community ,

the keys with their value and necessary data can be found here:

github.com/cryptomator/cryptomator

An unexpected error occured/Windows 10

opened 09:18AM - 26 May 21 UTC

closed 09:42AM - 26 May 21 UTC

kohakunashi

type:bug

### Description I have used Cryptomator for months and it's wonderful program. I used it to encrypt a folder on disk D. Today i unlock vault but it shows "An unexpected error occured" ### System Setup * Operating system and version: Windows 10 Version 1809 * Cryptomator version: 1.5.16 * Volume type: WebDAV ### Steps to Reproduce 1. Open Cryptomator 2. Trying to unlock Vault #### Expected Behavior I expect that the error would be auto fix so I can access my data. #### Actual Behavior The unexpected error promted. #### Reproducibility Always ### Additional Information ``` org.cryptomator.common.vaults.Volume$VolumeException: org.cryptomator.frontend.webdav.mount.Mounter$CommandFailedException: Command failed with exit code 2. Expected 0. Stderr: System error 67 has occurred. The network name cannot be found. at org.cryptomator.common.vaults.WebDavVolume.mountServlet(WebDavVolume.java:86) at org.cryptomator.common.vaults.WebDavVolume.mount(WebDavVolume.java:48) at org.cryptomator.common.vaults.Vault.unlock(Vault.java:151) at org.cryptomator.ui.unlock.UnlockWorkflow.attemptUnlock(UnlockWorkflow.java:100) at org.cryptomator.ui.unlock.UnlockWorkflow.call(UnlockWorkflow.java:81) at org.cryptomator.ui.unlock.UnlockWorkflow.call(UnlockWorkflow.java:44) at javafx.concurrent.Task$TaskCallable.call(Task.java:1425) at java.base/java.util.concurrent.FutureTask.run(Unknown Source) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.base/java.util.concurrent.FutureTask.run(Unknown Source) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.base/java.lang.Thread.run(Unknown Source) Caused by: org.cryptomator.frontend.webdav.mount.Mounter$CommandFailedException: Command failed with exit code 2. Expected 0. Stderr: System error 67 has occurred. The network name cannot be found. at org.cryptomator.frontend.webdav.mount.ProcessUtil.assertExitValue(ProcessUtil.java:28) at org.cryptomator.frontend.webdav.mount.WindowsMounter.mount(WindowsMounter.java:43) at org.cryptomator.frontend.webdav.servlet.WebDavServletController.mount(WebDavServletController.java:102) at org.cryptomator.common.vaults.WebDavVolume.mountServlet(WebDavVolume.java:84) ... 12 more ```

Rasoul · June 27, 2021, 9:03am

I checked Registry Keys and realized these Keys have same value on a fresh Windows 10 and Windows 10 which Cryptomator has been installed on it.

So it wasn’t the solution. I will give the solution in the next post.

Rasoul · June 27, 2021, 9:41am

By installing Cryptomator application value of HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\WebClient\Parameters\FileSizeLimitInBytes entry, would change from 02faf080 to ffffffff (Hexadecimal Format).

Changing value worked for me on Windows 10 installed on Hyper-v VM, I hope it would work in other situations.

Here is the Registry Key example: