This thread got some new life recently, and is a good source for information. My experience should prove helpful or interesting maybe.
I just bought a “Sandisk Cruzer 32 GB”, manufacturer refurbished, shipped from overseas…
My Win XP recognized it as a fixed hard disk, which is the first time I have seen that, and now I realize why after reading the forum entries from last Fall here. I immediately set about looking for a utility to set the removable bit also, but of course did not find one. I decided to live with it and use this for local storage and use my other drives for Windows PE and Rufus ISO bootable images.
However, when I pulled this Sandisk Cruzer from the USB 2.0 port, it always generated a message, “Windows delayed write failed…”, which bothers me more than a little. I tracked this down and found that it was related to hard drives that have write caching enabled. I had already run Si Sandra on this USB stick and saw it had read cache but no write cache . None of the everyday USB’s have write caching, which is why they speak with forked tongues when they crow about 2.5 Gb/s to 5GB/s!!! The worst kind of trickery is being used here. Not lieing because the Standard supports those speeds, but trickery because the hardward is not up to the task. Usually you can get 125MB/s read speeds but the write is 1/3 that or even less.
Anyway, back to the story. Since this Sandisk was generating an error that write cache was not written because I yanked it out of the port, I assumed they turned on the write cache flag when it was refurbished. Open “My Computer” and right click on the Sandisk drive and select “Properties”. Then select the Hardware tab, and then select the Sandisk from the dropdown list (very bad User Interface here, dontcha think!). Then select Properties again and finally select Polices and you will see two radio buttons: “Optimize for Quick Removal” and “Optimze for Performance”. The first option will be selected, so it should be ok. But I wanted to trigger a bit change, so I selected “Optimize for Performance”. Then a checkbox became available, “Enable write-caching”. It was automatically checked by default, so I unchecked it and saved that change. Then I tested the USB by copying some files which went ok, and then I yanked it out of the port without using the “Remove Safely” procedure. Sure enough, I no longer got the “Windows delayed write failed…” message. Good enough.
Now I planned to re-insert the USB in the port and change the flag back to “Optimize for Quick Removal” and expect that to be the best settings.
What a surprise! When I inserted the USB Sandisk 32GB again, I got “Found new hardware.”, “…installing”, “… installed sucessfully and ready for use.”
I opened my computer and in my list of drives I now had a Removable Disk named “Sandisk Firebird USB Device”, and all the data and formatting had been lost!
Well, this could be good news and bad news, take your pick:
The good news: This procedure might work on your good drives for setting the removable bit. Just make sure to back up your data before you do it!
The bad news: This might be a one-of-a-kind glitch on the USB which is malfunctioning still after it was “manufacturer refurbished”.
I decided to try to fip it back to the “fixed disk” state. First I went to format it. Imagine my surprise again, it said “64GB” instead of “32GB”… But the bad news is the format failed, both quick and normal. I used its Polices and set “Optimize for Performance”. Still unable to format it. Pulled it out…no errors… re-inserted…yep, its back as Sandisk Cruzer USB Device. Did not need formatting, but I tried anyway… At first it showed it was 64GB, but then it reverted to 32GB. Gave me an idea: I wrote data to it, pulled it out, no msg, then re-inserted, set Policies to “Optimize for Performance”, “No Write-Enable”. Removed it… haha, got the “Windows - Delayed Write Failed…” msg. But no, I could not duplicate the transformation to “Sandisk Firebird 64GB Removable”.
Quite interesting, but apparently I have a flaky USB here, and those “procedures” which set it to removable do not seem repeatable, sadly.