Hello After updating Windows to build 17063 Boxcryptor Desktop App broke. It does not start anymore. I tried starting it as Admin, reinstalled it, switched off "Check apps and files" in Security Center. No change. The UWP App still works, but it is a bit tedious to work with it "naturally". Happens on both my machines. I created a Feedback Hub entry for it, too. Please feel free to upvote that both sides (MS and Boxcryptor) can work on it. Do you have the same issue? Details from Application Event Log: Application: Boxcryptor.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: CallbackFS.ECBFSError at CallbackFS.CallbackFileSystem.CreateStorage() at Boxcryptor.FileSystem.Volume.() at System.Threading.ThreadHelper.ThreadStart_Context(System.Object) at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object) at System.Threading.ThreadHelper.ThreadStart() Boxcryptor.exe 2.22.706.0 5a300267 KERNELBASE.dll 10.0.17063.1000 b8caedef e0434352 0010d2b2 236c 01d37976a82888b7 C:\Program Files (x86)\Boxcryptor\Boxcryptor.exe C:\Windows\System32\KERNELBASE.dll c72529dc-db82-474e-a279-4ff84e6454dd

Hello mipsen, I have the same issue with Boxcrypter Classic 1.5 and the new normal Boxcryptor. Boxcryptor classic tells in German: The Boxcryptor drive cannot be mounted. Please reinstall. Boxcryptor 2.2: The start box closes after some secounds. LG Culles

Hi Same issue with the build 17053 Regards Cyrille LAPORTE

Windows insider Build 17063 broke the Boxcryptor Desktop App?

tassp9999

Good Day,

Just reporting same issue with build version 17063
I have entered a support ticket & will share if I learn a fix.

Patrick

MaxM

Hello,

same here. No idea how to access my data.

Max

Culles

Good news,

i have found a way to access the files. You can download the portable versions of boxcryptor or boxcrytor classic. With drag 'n drop I have saved the decrypted files in an empty folder (classic version):

no classic: https://www.boxcryptor.com/de/download/?platform=portable
classic: http://www.boxcryptor.com/download/Boxcryptor_Classic_Portable.zip

LG Culles

tdeufel

same problem. (seem to remember that happened once before with a Windows Preview Build)

edirleis

I see same problem as described. Anyone from Boxcryptor looking into this post and can give us a feedback on this issue?

Robert

Hello everybody,

Thank you for reporting this issue. We're aware of it and are also observing it. Please note that we do not support Windows Insider Preview builds due to their unstable nature. We have seen similar issues with new Windows Insider Preview builds in the past which have been fixed in newer builds without any change on our side. I'd like to encourage all Windows Insiders to report this issue also to Microsoft using the Feedback Hub.

Until it has been resolved, you can either use Boxcryptor Portable (as already mentioned here) to access your encrypted files or re-install a stable version of Windows 10.

Best regards,
Robert

AubryJ

Thanks LG Culles it's a great workaround.
BTW Happy new year to all.

salemsen

Any News to this?

vdasdb

this helps:
https://docs.microsoft.com/en-us/windows-hardware/drivers/ifs/blocking-file-system-filter-drivers

salemsen

thanks a lot, this realy helped

salemsen

mmmh, it helped watching the files, but all files aren´t accessible :-( what am i doing wrong?

vdasdb

if you added registry value from my link, checked that legacy filter turned on and files not working - try to check event viewer in parts windows logs\application and system

Robert

Hi everybody,

We have further investigated this issue and can confirm that the reason for it is a change in the default value of the IoBlockLegacyFsFilters registry key value. While the blocking of legacy file system filter drivers was optional, it is now the default since Windows 10 Insider Preview 17063. Because Boxcryptor uses a legacy file system filter driver as part to provide the virtual disk, it cannot be mounted and causes the application to crash.

As described by vdasdb, a quick workaround is to allow loading of legacy file system filter driver. After you change the IoBlockLegacyFsFilters value to 0 and rebooted your computer, Boxcryptor should work again as before. More information how to change this value can be found in the link provided by vdasdb:
https://docs.microsoft.com/en-us/windows-hardware/drivers/ifs/blocking-file-system-filter-drivers

I can ensure you that we are working on a real "fix" for this issue and we will make sure this workaround is not needed anymore until the final release of Windows 10 1803.

Best regards,
Robert

tdeufel

Correction of my last post: Registry editing Does solve the problem. Follow the link given by vdasdb oboave. Just be aware that you might have to ADD the DWORD item "IoBlockLegacyFsFilters° and assign the value "0" (zero). Restart and everything is fine. Relief

salemsen

No, it doesn´t work.

With the registry Hack i am able to connect via boxcryptor to the files, but everything i try to Access the files doesn´t work.

Messages like "file can´t be opened" appear

Robert

Hi,

We have made progress on support for the latest Windows Insider Preview builds, especially making Boxcryptor work even if legacy file system filter drivers are blocked by Windows. If you're interested, you can try this experimental Boxcryptor build which should work on Windows Insider Preview builds "out-of-the-box" without any workaround:

https://www.dropbox.com/s/law463mvy6eyhn3/Boxcryptor_v2.24.737_Setup.msi?dl=0

If you try it, we'd be happy to hear your feedback. Part of the changes are a new filesystem driver version (replacing CBFS 6 with CBFS Connect 2017).

Best regards,
Robert

salemsen

Hi, yes, it works!!! Thanks a lot!!

salemsen

Now, with the latest Insider it doesn´t work anymore, the System says it is ubnable to create a volume mapping

salemsen

17112.rs4_release

salemsen

Setting "IoBlockLegacyFsFilters" = 0 -> Mount Point can be created, but the files are only visible, not accessible

Setting "IoBlockLegacyFsFilters" = 1 -> Mount Point can't be created, the files are not visible and not accessible

Using the latest boxcryptor Version 2.24.747