Rekordbox 7.2.19 export possibly destroying USBs?

Rekordbox 7.2.19 export possibly destroying USBs?

Y2KJ

Rekordbox 7.2.19 export possibly destroying USBs?

Hi All!

I have had two separately purchased SanDisk Ultra USB 3.0 64GB drives become severely corrupted(?) or completely bricked while exporting after updating to Rekordbox 7.2.19.

Both USB drives ejected themselves during the export process and showed errors about "missing" files that were not actually missing. This did not happen when I tried exporting with an older version, such as 7.2.16.

The USB power-saving settinga were not enabled on either of the devices I have tried connecting these drives to. I have tested them on multiple computers and USB ports, with the same result.

I'm not sure if this issue only affects SanDisk USBs or other brands as well, but my Kingston USB exported successfully without any problems.

I have now had to submit RMA requests to SanDisk for both sticks because, after these incidents, neither USB will stay connected. They seem to be completely bricked? Only staying connected for 5–10 seconds at a time before automatically ejecting/disconnecting. The USB drives are not hot to the touch and do not appear to be physically damaged, burned, or otherwise broken.

Hopefully, SanDisk will approve the RMA for my previously working USB drives that are now essentially paperweights...

Please let me know if anyone else has experienced this issue. And, for everyone else, please be careful until it has been confirmed whether the new version of Rekordbox is causing this or not.

 

TL;DR:

I was exporting from Rekordbox v7.2.19 to two separate SanDisk Ultra USB 3.0 64GB drives when both of them ejected by themselves on separate computers and on separate occasions. Now, neither of them stay connected to any PC, laptop, or other USB port for more than 5–10 seconds before disconnecting/ejecting automatically.

Gabriel

Can you please file an inquiry ticket here and our support team will gather some additional information to assist you in resolving this issue.

1 comment

Sort by: Date Votes
Please sign in to leave a comment.

Sign in

Can't find help? Search our Support Site or alternatively, reach out to our Support agents