![]() This workaround seems to force the Backblaze to use the 32 bit rather than the 64 bit version of bztransmitīackblaze should now start uploading, my install is reporting upload speed of 147GB a day, which is very good.Ĭlick here to get a 30 day free trial of Backblaze rather than the usual 7 days. You can download the new BackBlazeWorkaround.exe copy to the C:\ Program File (x86)\BackBlaze, run as administrator.īackblazeWorkaround.zip (This zip contains the previous batch file, this does not check that the Backblaze files have been updated) It is important to copy to both places, either restart the computer or restart the ‘bzserv’ service, open the Backblaze UI and click backup now. So I renamed the bztransmit64.exe (4492 KB) to in:Ĭreated a copy of bztransmit.exe (2907 KB) and rename the copy to bztransmit64.exe and copied to: I have managed to figure out a workaround for version 5.1.0.141 which might help others with the same issue:Īfter running the bztransmit64.exe -testify I get the crash but not with bztransmit.exe -testify This machine has an Intel chipset whereas the machine the backup worked on was an AMD. I reported to Backblaze and they are currently helping to resolve that issue. On the machine I installed Backblaze it would not backup, just reports that it is producing a file list, it appear that bztransmit64.exe was crashing with an Access Violation Error. Even if I move my OneDrive to my storage drive, the C drive cannot be excluded. ![]() I have tried it before but did not like that I could not select only the folders I wanted to backup, ie OneDrive, instead you have to jump through hoops to exclude everything else. I recently decided to give Backblaze another try, tempted by the unlimited backup for $5 a month. If anyone has Backblaze stuck on ‘ Producing File Lists…‘, please add your computer CPU and Motherboard information to the comments, so Backblaze will do something about it, Thanks IMPORTANT: The workaround in this article is NOT supported by Backblaze, my ticket with them was closed before the problem was resolved on my 2 computers.
0 Comments
Leave a Reply. |