Closed Pre-Release 5.05

  • Release Candidate 6
    We are at a “proposed final” true release candidate with nothing known remaining to be changed or fixed. 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:

    This forum does not automatically send notices of new content. So if, for example, you would like to be notified by mail when Steve posts an update to his blog (or of any other specific activity anywhere else), you need to tell the system what to “Watch” for you. Please checkout the “Tips & Tricks” page for details about that... and other tips!

  • Announcing “BootAble” – GRC's New Boot-Testing Freeware
    Please see the BootAble page at GRC for the whole story.
  • 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.)


(as in GRC)
Staff member
Feb 1, 2019
Southern CA, USA
5.05: Fixed “SMART”, which I broke in 5.04.

Several immediate testers have confirmed that the persistent problem I was hoping to fix with the 5.04 release is fixed — which was SpinRite's previous problems with very troubled drives. Several people who had such drives have confirmed that 5.04 managed to plow through regions where it was previously giving up and/or getting stuck.

We've also had several confirmations that the new "video restoration" hack of pressing backspace four times brings video back online.

BUT! — It was also quickly observed that 5.04 broke SpinRite's SMART subsystem reporting. It was the result of the reworking I did of SpinRite's AHCI to fix the trouble drive problem. And it was quick to fix once I knew I broke it. So this release 5.05 should have everything working again.

Everyone who grabbed 5.04 should replace it with 5.05.

You may obtain this update as before by going to GRC's Pre-Release page, entering your SpinRite license serial number or transaction code and clicking the links to obtain your personal pre-release copies of either the full Windows/DOS SpinRite and/or just the DOS code.

Thanks, all!
Seems to be working as expected.

I ran this (WDC WD20EARS-00MVWB0) drive all the way through Level 3 using Pre-Release 5.03 last night. It had a couple of issues where there were some unrecoverable data near the end, and also a sector near the middle that appeared to have never even been looked at. On the Graphic Status Display screen, after everything was finished, there was a white dot near the center of the grid. Not the slightly larger blue dot associated with analyzing, but the smaller white dot associated with unprocessed. I don't recall ever seeing Spinrite "not process" a portion of a drive before. It ran for 13 hours over night so of course I didn't see what was on the screen at the time.

I ran the same drive again all day today using 5.05, which ran a little over 13 hours. Today it seems to have made it all the way through with no complaints, other than what appears to be an innocuous write error and some SMART activity that is a bit of a mystery to me.

I wouldn't bother posting these two logs other than the unusual situation where it seems like 5.03 actually skipped a spot near the middle of the drive.


  • PR5.03 (WDC WD20EARS-00MVWB0).TXT
    8.5 KB · Views: 53
  • PR5.05 (WDC WD20EARS-00MVWB0).TXT
    6.7 KB · Views: 48
Attached is the log of another drive that I had issues with in the past. It was completed successfully this time.


    3.7 KB · Views: 45
  • Like
Reactions: Steve