Bandizip in comparison with other archivers
How to use Multi-core Compression
How to use the Finder’s right-click menu for Bandizip
How to set Bandizip as the default app to open archives
How to open ALZ and EGG files on Mac
How to use Extract Here (Smart)
How to split a large file into smaller files with Bandizip
How to view a list of files in an archive
How to modify an archive without decompression
How to set a password for an archive
Versleuteling van bestandsnamen in archieven
How to preview image, document and music files in an archive
Verplaats bestanden naar de Prullenbak tijdens het verwijderen
How to use the Password Manager
How to use Repair Archive
How to use the Password Recovery
Automatische detectie van codepagina werkt niet correct.
How to troubleshoot when Error 22 occurs and Mac Finder on Catalina can’t extract ZIP archive
How to troubleshoot when a split archive can’t be decompressed
How to troubleshoot when an extracted app file can’t be opened
How to troubleshoot when it takes too long to open archives
How to troubleshoot when a badge icon for files doesn’t appear in the Finder
How to troubleshoot when the Finder displays for external volumes incorrectly in the sidebar
How to troubleshoot when I can’t uninstall Bandizip
How to troubleshoot when I can’t install Bandizip on the App Store
How to request a refund for Bandizip that you bought from the App Store

〈 Help

How to troubleshoot when a badge icon for files doesn’t appear in the Finder

A badge icon doesn’t appear if the path added to Bandizip’s accessible folders list overlaps the paths used by other Finder extensions (cloud sync apps, mostly).

This usually occurs when used simultaneously with cloud synchronization apps such as Dropbox, OneDrive, and Google Drive that use Finder Extensions.

It is assumed that according to the order in which the extensions are applied, only the badge icon of the last extension is displayed. As Bandizip doesn’t use any badge icon, the other badge icons aren’t displayed either.

Although there is no general solution for the problem at this moment since it is caused by the limitation of the Finder itself, we are finding out if there is an alternative.