This version includes a fix for the deletion issue.
As you know, S3 does not have a traditional directory structure. When removing objects within a directory-like structure, we must delete each object individually. This fix will list all objects under the specified “directory” (marker) and then remove each one. This process will take longer compared to other storage systems where deleting a directory automatically removes all files within it.
Hi! Hope you are fine)
Have a problem with 3.18.1108 version - when creating “zero weight” files on the disk mounted by ND - they are not loading to S3 bucket. Can we fix it?
Hi Yaroslav,
Thank you for reaching out to us!
We understand that you are experiencing an issue where zero-byte files are not being uploaded to your S3 bucket when created on a NetDrive-mounted disk.
To help resolve this issue, please try the following steps:
Update to the latest version of NetDrive (3.18.1125)
Check if your S3 bucket has any restrictions on zero-byte files
If the issue persists, please send us your NetDrive log file for further investigation
We appreciate your patience and look forward to assisting you further. If you have any questions, feel free to reach out!
Best regards,
NetDrive Support Team
Hi!
Log files in attach.
So we have two things to fix:
Thank you!
NetDrive3_yaroslav.zip (1.3 MB)
Dear Yaroslav,
Thank you for sharing the logs and your detailed feedback.
We have confirmed the issue where zero-byte files are not uploaded to the S3 bucket. We will investigate this further and work on a solution.
As a temporary workaround, we found that uploading zero-byte files via the File Browser works correctly. Until a fix is released, we recommend using the File Browser for uploading such files.
Regarding the issue with empty folders not being deleted, this has already been resolved in the latest version (3.18.1125) of NetDrive. Please install the latest version from the following link:
If you encounter any further issues, feel free to let us know. We appreciate your patience and cooperation.
Best regards,
Bdrive Support Team
Dear Yaroslav,
Thank you for your patience.
We’ve identified and resolved the issue where zero-byte files were not being uploaded to the S3 bucket. Please try using the following version, which includes the fix:
We kindly ask you to install this version and test if it works as expected. Please feel free to let us know the results or if you encounter any further issues.
Best regards,
Bdrive Support Team
Hi!
Can confirm that problem with uploading zero-byte files has gone in version 3.18.1127.
Problem with deleting folders with files is still in place in version 3.18.1127. Once more - while deleting folder, files in the folder delets but folder is not.
Logs in attach.
090425.zip (1.3 MB)
Dear Yaroslav,
Thank you again for your detailed feedback and for providing the log files.
We are pleased to inform you that the issue where folders containing files could not be deleted (only the files were removed) has been resolved. You can download and test the fixed version using the link below:
Download URL:
https://downloads.bdrive.com/netdrive/builds/0e202a553d2e4dc7b1896067f893b052/NetDrive3_Setup-3.18.1129.exe
Please try using this version and let us know if the problem is fully resolved on your side.
Thank you for your continued support and cooperation.
Best regards,
Bdrive Support Team
Hi Team! While testing version 3.19.7, we discovered an issue: when a file with the .tmp extension is created automatically (via a PowerShell command or from cmd), the file does not appear in the S3 storage. However, when creating the same file (with the .tmp extension) manually (via Windows Explorer), the file does appear in the S3 storage. Logs are attached.
nd3log_3197_042026.zip (1.1 MB)
Hi!
Could you please review this and share your feedback?
Hello Yaroslav,
We reviewed the attached logs, and the issue appears to be related to NetDrive’s file-handling logic rather than S3 itself.
According to the logs, .tmp files created automatically via PowerShell/cmd are being treated as offline only by NetDrive. In that flow, the actual S3 upload steps (UploadNow, S3::Upload, PUT 200) do not occur.
On the other hand, files created through Windows Explorer follow a different path and are reflected in S3 normally.
So at the moment, it looks like automatically created .tmp files are being treated as temporary files and are not uploaded properly.
As a temporary workaround, please try:
.txt, and then.tmp.We believe this should be escalated internally for further review.
Thank you for reporting this issue.
Best regards,
Bdrive Support Team
Hi,
The temporary workaround works, but our software generates .tmp files automatically during normal operation, so this issue is quite critical for us.
Could you please let us know if this behavior is already being addressed internally? If so, when do you expect to release a fixed version?
We’d appreciate any timeline you can share.
Hello Yaroslav,
Thank you for the additional details.
As you mentioned, while the temporary workaround is usable, we fully understand that this is a critical issue in your environment because your software generates .tmp files automatically during normal operation. From our perspective as well, this is not just a minor inconvenience but an important issue that can affect real-world workflow.
This issue is currently being addressed internally.
We are treating it as a high-priority matter and are working to provide a fix as quickly as possible.
At the moment, we are not yet able to confirm an exact release date, but we will share an update with you as soon as we have more concrete progress.
If a fixed build or test version becomes available first, we will make sure to let you know as a priority.
We apologize for the inconvenience, and we appreciate the detailed report and logs you provided.
We are actively working on resolving this issue.
Thank you.
Hello Yaroslav,
Thank you for your patience. The fix for the .tmp file upload
issue is now ready for verification.
Download URL:
https://downloads.bdrive.com/netdrive/builds/13b195e8ab1747c0875d7ef905d98ba5/NetDrive3_Setup-3.19.8.exe
What was the cause
NetDrive’s default filter was classifying every *.tmp file as
“offline only” at file-creation time. This was originally designed
to ignore Microsoft Office’s transient save files, but it was
applied globally across all processes — which is why .tmp files
created by PowerShell, cmd, or your application were silently
prevented from uploading.
What’s new in this build
We have added a new option to opt in to *.tmp file uploads. The
default behavior is preserved (Office transient files are still
filtered), and the new option can be enabled on a per-drive basis
when you need your .tmp files to sync.
How to enable the option
Once this option is enabled, any .tmp file created on the mounted
drive — whether via PowerShell, cmd, or your application’s normal
operation — will be uploaded to S3 like any other file. Delete and
rename operations on .tmp files will also be propagated to S3
correctly.
One note worth mentioning
When this option is enabled, .tmp files created transiently by
MS Office during save operations (e.g., ~WRD0000.tmp) will also
be uploaded briefly before being renamed to their final names.
This does not affect data integrity, but you may see short-lived
.tmp objects appear in S3 if you use Office on the mounted drive.
Please let us know once you have verified the fix on your side.
If you run into any issue, please enable debug logging and share
the nd3svc log — we have added specific trace entries for this
feature that will help us diagnose any edge case quickly.
Thank you again for the detailed reproduction steps and for your
continued cooperation.
Best regards,
Bdrive Support Team