sandisk cruzer 32G

I had Classic start on windows 10. It disappeared.
On he regular windows start is found the administrator and the cmd prompt.
Got to Clean and it died there.

You might try to clean it in Windows 7 or Windows 8. I have now tested two Verbatim flash drives and they both have the error. The two 32 GB drives, one a SanDisk, seem to be OK.

In Windows 10 I finally got all the way thru Diskpart. The Sandisk drive is now ntfs.
BUT, I am unable to move anything to the drive.

The Sandisk no longer works on Windows 7 pro 64-bit. Unable to do anything there.

Look at the drive in Disk Management and see if it actually shows a healthy partition. When I was using Diskpart in Windows 10 it would, on occasion, show as successful but the drive had not been configured.

It may also be you need to add a drive letter, as was mentioned earlier. If you are not using the assign command after you create the partition, it may not pick up a letter automatically.

My Sandisk Cruzer finally bit the dust on my Windows 7 pro 64-bit computer. But Wait there is
more..... I went online and started reading about Flash Drives. It seems that different flash
drives can only beformatted the way the mfg lets it be formatted. For EX: PHY can only be
formatted "exfat". I don't know the way Verbatim disks can be formatted. The Sandisk seems
to work for "Fat32".

So I trotted over to wiffies computer (running Windows 7 pro 32-bit) and formatted the
Sandisk drive to Fat 32. Copied and Pasted several programs from her computer to the
Sandisk and it WORKED!!!!
Went back to my computer running Windows 7 pro 64-bit and the Sandisk worked there.
Haven't tried it on Windows 10 which I guess will not work. At least I know that I don't
have tojunk the Sandisk.
Nothing is ever easy....

I just tested the Sandisk drive on Windows 10 on the 64-bit computer. Nothing showed
that I created on the Windows 7 pro 32-bit computer. I would gather from that, that the
windows 10 OS doesn't like Fat 32. If I right click on the drive and click in properties,
the disk shows it contains 40,000+ bytes. I'm dead in my tracks.....

I have a sandisk cruzer 32gb formatted ntfs and it works fine. I also have a 16gb pny usb formatted FAT and it is OK too.

I was reading sometime back that cruzers that had some bit setting flipped which made them show as fixed rather than removable media. You could try flipping it back with this lexar "bootit" utility and see if it works http://www.computrogeek.com/2013/06/...load-2013.html - the comments say it works with sandisk but I've not tried it...

In Windows 10 on the 64-bit puter I finally got it to format as NTFS.
But Ready boost is not cooperating. I click on "do not use this device".
Set the space reserved for system speed to as low as I can set it.
Click Apply and Ok.
Makes no difference as the next time I look at it is back to where it
was the 1st time (30364).
So "readyboost" is eating up 71,647,232 bytes of my Sandisk.
When I click on "properties" Windows 10 says that the Sandisk is working properly.

jack said:

My Sandisk Cruzer finally bit the dust on my Windows 7 pro 64-bit computer. But Wait there is
more..... I went online and started reading about Flash Drives. It seems that different flash
drives can only beformatted the way the mfg lets it be formatted. For EX: PHY can only be
formatted "exfat". I don't know the way Verbatim disks can be formatted. The Sandisk seems
to work for "Fat32".

So I trotted over to wiffies computer (running Windows 7 pro 32-bit) and formatted the
Sandisk drive to Fat 32. Copied and Pasted several programs from her computer to the
Sandisk and it WORKED!!!!
Went back to my computer running Windows 7 pro 64-bit and the Sandisk worked there.
Haven't tried it on Windows 10 which I guess will not work. At least I know that I don't
have tojunk the Sandisk.
Nothing is ever easy....

Did you use Diskpart to clean the drive from your wiffie's Windows 7 computer?

Windows 10 does fine with Fat32. But there does appear to be some difference between 8.1 and Windows 10 regarding these types of drives. I wonder if the new build does the same thing....