write protect error

  • SpinRite v6.1 Release #3
    The 3rd release of SpinRite v6.1 is published and may be obtained by all SpinRite v6.0 owners at the SpinRite v6.1 Pre-Release page. (SpinRite will shortly be officially updated to v6.1 so this page will be renamed.) The primary new feature, and the reason for this release, was the discovery of memory problems in some systems that were affecting SpinRite's operation. So SpinRite now incorporates a built-in test of the system's memory. For the full story, please see this page in the "Pre-Release Announcements & Feedback" forum.
  • Be sure to checkout “Tips & Tricks”
    Dear Guest Visitor → Once you register and log-in please checkout the “Tips & Tricks” page for some very handy tips!

  • BootAble – FreeDOS boot testing freeware

    To obtain direct, low-level access to a system's mass storage drives, SpinRite runs under a GRC-customized version of FreeDOS which has been modified to add compatibility with all file systems. In order to run SpinRite it must first be possible to boot FreeDOS.

    GRC's “BootAble” freeware allows anyone to easily create BIOS-bootable media in order to workout and confirm the details of getting a machine to boot FreeDOS through a BIOS. Once the means of doing that has been determined, the media created by SpinRite can be booted and run in the same way.

    The participants here, who have taken the time to share their knowledge and experience, their successes and some frustrations with booting their computers into FreeDOS, have created a valuable knowledgebase which will benefit everyone who follows.

    You may click on the image to the right to obtain your own copy of BootAble. Then use the knowledge and experience documented here to boot your computer(s) into FreeDOS. And please do not hesitate to ask questions – nowhere else can better answers be found.

    (You may permanently close this reminder with the 'X' in the upper right.)


Oct 7, 2020
Does anyone have any ideas on how I can fix this?
This USB doesn't have a write protect switch or slider.

Physical drive size: 61,912,121,344 (61.9GB)
          Drive shows as: Removable
           Device vendor: specific
        Vendor's product: storage_device
         Device revision: 0009
   Physical drive number: 1

   Information for drive's volume #1
    Volume serial number: 14F4-305B
        File system type: FAT32
             Volume Name: 2_7_1-22-AM
             Total bytes: 61,895,933,952 (61.9GB)
              Bytes free: 61,610,524,672 (61.6GB)
       Volume mounted as: D:\

  A newly inserted drive has been identified and is detailed above. Any drive
  volumes that are shown mounted with a drive letter may be further examined
  if the volume contains a recognized file system, before being reformatted.

  If you wish to reformat this drive, please enter the command NUKE and press
  Enter. Or, just press the ESCape key to terminate this program: NUKE

1. Unmounting & deleting drive mount points.
2. Taking the drive offline.
  ====================[ PROBABLE WRITE PROTECTION ]======================

  InitDisk's attempt to write to the selected device failed with an error
  indicating that the drive is probably write protected. You must disable
  write protection for InitDisk to reformat this device.

     Press ESCape to acknowledge this note and proceed...
There are two possibilities I think. One is that the device has decided it is done being writable. When the number of write cycles is reached, the controller will just stop accepting any more. The other possibility is that there is a weird format on the device that Windows will not allow you to overwrite (but that it can read) which will need to be removed outside of Windows. I have heard of people using Linux to blank the device with dd and then InitDisk will be able to work with it.
Have you tried to work with / write to the media with it connected to a different computer / reader?

A quick hardware swap - does the issue follow the media or might there be some peculiar issue with this media in this reader? I suggest this as it might be a quick test / possible solution.
  • Like
Reactions: DarkMatter
2021-05-04 18_29_37-VirusTotal — Mozilla Firefox.png

Is this the right thing?

I wasn’t trying to ruffle any feathers I was simply verifying that I had the right thing.

And I don’t trust VirusTotal 100% but it is better than nothing.

I also don’t trust any download sites assessment either.

I guess I tend to be more cautious than most.

And I DO genuinely appreciate your help and advice!