Excel file corruption when opened in Big Sur, Google FS, and Boxcryptor

arkantrax

I'm running into an error whenever I try to open an encrypted (boxcryptor) excel file (xlsx) from Google FS on Big Sur:

Alert
We found a problem with some content in 'xyz.xlsx'. Do you want us to try to recover as much as we can? ...

When I view the repair result details, I see the following additional details:

Excel completed file level validation and repair. Some parts of this workbook may have to be repaired or discarded.

If I save the repaired file locally, I can open it normally afterwards. If I copy over the repaired file to Google FS, I'll start getting this error again when attempting to reopen.

Here are my version details:

OSX Big Sur: 11.2.3
MS Excel: 16.47.1
Google Drive File Stream: 46.0.3.0 (Intel)
Boxcryptor: 2.38.1090

Some basic troubleshooting with the placement of my excel file:

Unencrypted on local machine: OK
Unencrypted on Google FS My Drive: OK
Google FS parent folder Online Only: OK
Google FS parent folder Offline: OK
Encrypted on Google FS My Drive: OK
Unencrypted on Google FS Shared Drive: OK
Encrypted on Google FS Shared Drive: ERROR
-- Using Catalina 10.15.7 (same version everything else): OK

My total path length for all these scenarios is under 250 char.

I know that there were a lot of fundamental changes in Big Sur that many applications have recommended custom command line arguments to fix for now. Is there anything like that for Boxcryptor?

Robert

Hello arkantrax,

Thank you very much for the information. Please update to the latest Boxcryptor for macOS version 2.40.1234 which improves compatibility with GDFS v45 and later. You can download here:

https://www.boxcryptor.com/download/Boxcryptor_v2.40.1234_Installer.dmg

If the problem still exists, it would be great if you could contact our support via support@boxcryptor.com referencing this thread and ideally including a debug log:

https://www.boxcryptor.com/en/help/faq-and-troubleshooting/macos/#how-to-create-a-debug-log

Best regards,
Robert

arkantrax

Thanks Robert, updating to 2.40.1234 resolved the problem!

Out of curiosity, is this release still in beta? I had Boxcryptor check for updates before manually downloading your link and it said that 2.38.1090 was the most recent available update.

arkantrax

Update: It looks like you just had me download the most recent version available on the official download page, but all of my machines still think that 2.38.1090 is the most recent version

arkantrax

Update 2: And seconds later, one of my machines is saying that 2.40.1233 is now available for download, but this still isn't the version from the Downloads page

Robert

Hi arkantrax,

Thanks for the feedback - great to hear that the issue is resolved using the latest version which is v2.40.1233 for macOS 10.14 - 10.15 and v2.40.1234 for macOS 11 Big Sur.

Please note that we publish auto-updates via staged rollouts, i.e. a new version is not immediately offered as an auto-update to all clients, but first to a smaller subset which is increased over a certain period of time. This process has not yet been completed for version 2.40 and thus it is possible that it is not shown as the latest version via auto-update.

If you want to manually check for the latest version, you can always find them in our changelog and update manually:
https://www.boxcryptor.com/en/help/about/macos/#changelog

Best regards,
Robert

arkantrax

Excellent - that all checks out. Thank you!