02-22-2016 04:13 PM
I think the problem may be OS dependent. Try running the cruzer blade within XP. I found it to work when I did but when I went over to Win 7 and higher I had problems. I have this theory there may be a virus causing it.
05-31-2016 12:48 AM
Check your sd card if it is a FAT32 format drive, then manage your disk management by going to Start menu, right click My Computer, click Manage and look for Disk Management. You can see there the drive of your SD card showing FAT32, right click the SD card drive and format (make sure you backup your files). Change FAT32 format to NTFS, thick quick format and wait when its done. That’s it, you now have a working SD card. Good luck!
08-21-2016 03:59 PM
Ok, Just Copy All Of the Files And Folders To Some Other Storage Device If you want to keep them. Then If Your USB Flash Drive Is Under Warranty And As You Said Don't Want to Expose It To Others. Then You Should call SanDisk And As Fot an Exception.
On Damage USB Flash Drives. Then Thay May Tell You How To Make It Unreadable Before You Send It Back For Replacement.
I Read Some Where That one Person Did That And SanDisk Made A Exception The There Return Policy About User Adbuse.
Also I Have Taked A Look At This Write Protect Issue. It Not A Windows System Problem Or SanDisk Chip Issue, As The SadDisk USB Flash Drives Are Setup To Automaticly Go Into Wrire Protect Mode If Durring Writing To its Drive An Error Of Unrecovery Type, It Will Go Into Write Protect Mode. And At This Date And Time Your Only Option Is If Under Warranty Is To Return It, For Replacement Or maybe Refund ?
01-17-2017 01:50 PM - edited 01-17-2017 01:52 PM
SanDisk are f*cking cunts.
No seriously. This is what you call built-in obsolescence.
For most of you, your drives have disabled the write access themselves, because - and that's what this sh*tty company tells you - to protect them from data loss. It's hardware based, you can basically not get around it. Or only with some f*ggo tool SanDisk has themselves.
My stick was working perfectly fine and the only thing I probably triggered was a GB written counter which caused the drive to shutdown. A drive just doesn't go defect from nowhere. Also, why can I still read it perfectly and just not write to it anymore.
I call bullsh*t. So are the products of them.
If you're lucky you just set a software partition or file system read-only flag. But for many people who participated in this thread, it's the story I just posted. You lost here.
The only win you can get out of this situation is the experience to dump SanDisk products.
Oh, and stop censoring my badwords. If you want feedback, deal with it.
01-17-2017 03:54 PM
03-13-2017 12:58 AM
Who cares if he will get banned by a company which somehow manages to manufacture fricken DEAD ON ARRIVAL product when its manufacture process became mature TEN YEARS AGO!
First time I connect this drive and it's ALREADY broken! What the fruck?!!
05-08-2017 01:11 PM
Found at Toms Hardware:
Works for Windows 7 Professional SP-1 64-bit
08-15-2017 09:52 AM
I too, learned 'the hard way" as you did about the limitation of FAT32. There is one soulution, albeit a rather extreme one. If your familiar with partitioning a drive, then you could partition your drive in to 4 partions. You'd lose just a bit of memory space due to the partitions, but would be able to use the greatest part of the drive as opposed to just slightly less and 4 Gb. Just a thought. The alternative would be to format the drive in NTFS; which doesn't limit file sizes.