Top critical review
3 people found this helpful
Not quite what I expected
on 16 March 2012
I've used a lot of flash drives over the years and rarely had any problems with any of them and that goes for the cheapest and the most expensive.
However this particular Sandisk Cruzer Blade device is somewhat different.
In the first case it is extreemly small - I would say about 1 inch long.
Secondly it has no led so there is no indication of any activity whatsoever - you have no idea about what is happening with the device - this may not sound much of an issue but believe me it is when there is a problem.
Third it seems to be all plastic including the plug that goes into the USB socket - how long this plastic will last when being shoved in and out of metal sockets I don't know.
Fourth I had the same problem as some other people with one particular PC - in this (Win 7 McAfee) system inserting the drive would cause an Explorer window to pop up and a green bar to start spreading across the top (as if Windows was doing some processing). At this time I could see the directories on the drive. The green bar took about 4 minutes to completely cross the explorer window and then I had a McAfee popup saying my real-time scanning was switched off - this restarted after 30 seconds as it should. Immediately after the McAfee pop-up the explorer window changed so that I could no longer see any directories (worrying, but the data was visible on other systems!) and clicking on the drive produced no results - trying various other actions seemed to indicate that Windows was confused about whether there was a physical piece of media in the socket or not. Anyway it indicated 0 bytes capacity and 0 bytes free (both not true). Another Win 7 and XP Pro system handled it fine. Anyway after talking with Sandisk support I reformatted the drive on the XP system (I could not format it on the Win 7 system where it produced the problems!) and it has worked fine since.
The drive comes with certain software pre-loaded (to provide a secure storage media) - I believe something gets invoked automatically when the drive is inserted - there is an autorun.inf file hidden in the root directory - I believe this probably had something to do with the strange behaviour.
End result is OK, but I was not impressed with this experience froma big-name vendor.