Hi,

sorry team boxcryptor but I'm going to be a bit harsh now that I've seen your community and all the problems it has.
First, Let me congratulate you about the wonderful bad work you've done with your forum webapp:

Now I understand a bit better that you don't test thoroughly your products.
A 403 Forbidden is not the fault of the customer by the way.

Second,
Let me lsit some of the problems I've got since I'm using your products:

crash in windows explorer, never fixed
storage being taken over 13G on iOS by your app without any cache on it which is probably done by your logs and noone in your CS have been able to just test it... just test it, not fixed it but just test it.
unavailibility a few times of all my clouds all at once through your ios app

Each time, your team is unable to reproducing bugs, I don't for the others but 3 major bugs in the same not opensource product in the same year, for something I'm paying for premium, ... that's a major disappointment. And actually for customers having major bugs you should at least propose some compensation. That's my idea about customer service, at least when you are unable to actually invest in a real TEST lab with real desktop and not only VMs to actually try to reproduce bugs.

But back to business,
I have reinstalled boxcryptor on one of the host that had problems with it with crashing of explorer and guess what? Still crashing people, YAY.

and still I didn't made the whole list here. And that's only the number of times where the consumer is talking about hanging or crashing with explorer during the use boxcryptor.

And in place of actually working on the problem you redirect to the support which I'm sure gave the same answer a year ago, that they can't reproduce the bug.
And that's with countless version number of boxcryptor but also explorer.
Do you actually realize there is a problem here in terms of internal testing of your product with something else than just a simple fresh windows 10 VM or not?
How is it possible that a free software like cryptomator, which does a lot less true, but sill, written in java is not giving such problems to your paying customers? Again for who you actually don't do a single effort in terms of commercial gesture like giving away a year free for example for the disturbance and the inability of your CS to actually look into the problem...

So I'm going to give your engineers a little heads up in terms of actual capability:
what about after asking for people their logs, you make them download this free software: http://www.nirsoft.net/utils/shexview.html
recommended by many blogs to resolve the explorer crashing like this one
https://askleo.com/what_do_i_do_when_windows_explorer_crashes/

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
  <Provider Name="Windows Error Reporting" /> 
  <EventID Qualifiers="0">1001</EventID> 
  <Version>0</Version> 
  <Level>4</Level> 
  <Task>0</Task> 
  <Opcode>0</Opcode> 
  <Keywords>0x80000000000000</Keywords> 
  <TimeCreated SystemTime="2020-11-04T16:27:45.7796236Z" /> 
  <EventRecordID>255260</EventRecordID> 
  <Correlation /> 
  <Execution ProcessID="0" ThreadID="0" /> 
  <Channel>Application</Channel> 
  <Computer>BATECAVE-PROTEUS</Computer> 
  <Security /> 
  </System>
- <EventData>
  <Data /> 
  <Data>0</Data> 
  <Data>AppHangB1</Data> 
  <Data>Not available</Data> 
  <Data>0</Data> 
  <Data>explorer.exe</Data> 
  <Data>10.0.19041.610</Data> 
  <Data>ab30c679</Data> 
  <Data>9e0a</Data> 
  <Data>134217728</Data> 
  <Data /> 
  <Data /> 
  <Data /> 
  <Data /> 
  <Data /> 
  <Data>\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER936.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER975.tmp.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER993.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA11.tmp.txt \\?\C:\Users\c_cro\AppData\Local\Temp\WER1676.tmp.appcompat.txt \\?\C:\Users\c_cro\AppData\Local\Temp\WER1697.tmp.xml \\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppHang_explorer.exe_20b517f9a12168b4f3f323eee794f6a8934f27_c618b803_cab_a0c033d3-7375-472b-96a2-6e770b2c8013\minidump.mdmp \\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppHang_explorer.exe_20b517f9a12168b4f3f323eee794f6a8934f27_c618b803_cab_a0c033d3-7375-472b-96a2-6e770b2c8013\memory.hdmp</Data> 
  <Data>\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppHang_explorer.exe_20b517f9a12168b4f3f323eee794f6a8934f27_c618b803_cab_a0c033d3-7375-472b-96a2-6e770b2c8013</Data> 
  <Data /> 
  <Data>0</Data> 
  <Data>75422c0b-fae8-4f93-8881-bc6ef2aec58f</Data> 
  <Data>100</Data> 
  <Data /> 
  <Data>0</Data> 
  </EventData>
  </Event>

So in place of redirecting to your CS, maybe we could have this conversation here for once. CS with who I'm already in discussion.
Because you could actual make good work here if you were a bit more open to it.
Like for example discussing about the shellextensions that could interfere with boxcryptor with screenshots as proofs.
Some numbers that the customer should expect as cpu demands when moving a file to an encrypted folder in one of the mainstream cloud like onedrive. etc .
Something actually useful for the customer, for your documentation etc.

Thanks for listening