Our knowledge base is a comprehensive resource designed to help you get the most out of our products. It includes getting started articles that guide you through initial setup, detailed information on specific features, and troubleshooting resources to assist you with any issues you may encounter. Explore our knowledge base to find helpful information about our products and answers to common questions.
CBFS™ Connect
Version 2024 Updates
06/10/2024 - Information and upgrade information for version 2024.
Version 2024 Upgrade Guide
06/10/2024 - Technical details about upgrading from version 2022 to version 2024.
Why is not my mounting point visible in File Explorer?
11/04/2017 - Discusses reasons why a mounting point may not show up in File Explorer.
If I grant a specific process access to the drive, will any child processes it creates be able to access the drive as well?
11/04/2017 - Discusses whether child processes can access your application's virtual drive.
Why doesn't CBFS Connect provide asynchronous versions of events?
07/04/2017 - Discusses the reason CBFS Connect doesn't have asynchronous events.
Why doesn't returning error in the DeleteFile event handler prevent file deletion?
07/04/2017 - Why doesn't returning error in the DeleteFile event handler prevent file deletion?
Why Choose CBFS Connect over Dokan?
12/05/2017 - Professionally maintained products are more reliable and can cost less in the long run.
Compare CBFS and FUSE Components
07/08/2021 - Compare the CBFS and FUSE components.
What happens if a certificate used to sign the driver and the DLL expires?
10/25/2024 - An explanation of how certificate validation is performed.
How do I collect a log of file operations on the drive for debugging purposes?
07/04/2017 - How to collect a log of file operations on the drive.
Why can't I create a directory or file whose name ends with a dot (".")?
10/04/2017 - Why can't I create a directory or file whose name ends with a dot (".")?
How do I create a drive for only one user (session)?
07/04/2017 - How to create a drive for only one user (session)