Verdict: Win32 Disk Imager is not dead in the sense of being broken or unusable, but it is not a maintained tool either. The accurate description in 2026 is a usable legacy tool: it still does its narrow job on Windows, its last release remains version 1.0.0 from 2017-03-08, and no new release has been announced since the maintainer’s return post in November 2024. If you need ongoing updates, security fixes, and new features, you should pick a maintained alternative. If you need simple raw imaging on Windows, Win32 Disk Imager still works.
That nuance matters, because both extreme claims circulate online. One side calls the tool dead forever, pointing to years without a release. The other side calls it actively maintained, pointing to the maintainer’s 2024 post as proof of a revival. Neither claim fits the full timeline. This post lays out what is actually documented, so you can decide with the facts rather than with a slogan.
Timeline: what actually happened
| Date | What happened |
|---|---|
| 2017-03-08 | Version 1.0.0 released, the last release to date |
| 2017 onward | Long quiet period with no new release |
| Later listings | FileHorse describes the tool as discontinued or no longer actively developed |
| November 2024 | Maintainer Tobin posts on the SourceForge blog: returning, rebuilding his build environment on Windows 11, sifting the merge-request backlog |
| 2024 to 2026 | No new release announced since that post |
The 2017 release and the long quiet
Version 1.0.0, released on 2017-03-08, is the last release of Win32 Disk Imager. It is GPLv2 software, Windows-only, with no Mac or Linux version. Its feature set is frozen at that point: Write copies an .img file sector by sector to a drive, Read copies a whole device sector by sector to an .img file, and the Verify Image feature provides the tool’s validation. There is no command-line interface, no scheduled imaging, no compression, and no ISO filesystem parsing. A read-back equals the full device size, and Write overwrites the entire destination drive. Those facts have not changed, because the software has not had a new release to change them.
A long gap without a release does not automatically mean a tool stops working. Raw imaging is a stable job: the sector-copy logic that worked in 2017 still works on the same kind of task today, which is why the tool keeps appearing in Raspberry Pi and retro-gaming guides years later. But a gap does mean no fixes for newly discovered problems, no adaptation to new Windows behaviours, and no new conveniences. Users who treat a legacy tool as if it were maintained will eventually be surprised, usually at the worst moment.
The November 2024 return post
In November 2024, the maintainer Tobin posted on the SourceForge blog that he was returning to the project. He described rebuilding his build environment on Windows 11 and sifting through the backlog of merge requests. That post is real, and it is the reason a flat claim of abandonment is unfair: the maintainer did come back publicly and describe active groundwork. It is also the reason a claim of revival is premature: groundwork is not a release. As of 2026, no new version has been announced following that post, and the downloadable release remains v1.0.0 from 2017.
The honest reading is therefore two-sided. The project has a living maintainer who has shown renewed interest, but it does not have a maintained release cadence. Until a new release actually ships, users should plan as if v1.0.0 is what they have, because it is. Watch the official project page on SourceForge at sourceforge.net/projects/win32diskimager/ for any future announcement, and treat any other site’s claim of a new version with scepticism unless it links to that official source.
What this means for you in practice
- Still fine: writing a known .img file to a card, or reading a card back to a .img backup, on Windows, with the drive double-checked.
- Still fine: keeping a copy of v1.0.0 for a stable, offline imaging workflow you already know.
- Not advisable: relying on Win32 Disk Imager as your only backup strategy, with no restore test and no second copy.
- Not advisable: expecting new features, scheduled imaging, or fixes for new Windows issues.
- Not advisable: using it for jobs it never did, such as making a bootable Windows installer from an ISO; it does not parse ISO filesystems.
When to keep using it, and when to switch
Keep using Win32 Disk Imager if you are on Windows, you understand its limits, and its Read function is the feature you actually need. It remains the simplest route to a full .img backup of a card, and that job has not gone away. Switch to a maintained tool if you want current support: Win32 Disk Imager vs Raspberry Pi Imager for Pi setups, and Win32 Disk Imager vs balenaEtcher for cross-platform flashing with validation. If you stay with Win32 Disk Imager, confirm it still runs well on your system; see Win32 Disk Imager on Windows 11 for platform notes, and get it from the download page.
Frequently asked questions
Is Win32 Disk Imager dead in 2026?
Not quite dead, but not maintained either. The last release, v1.0.0, dates from 2017-03-08, and no new release has been announced since the maintainer’s November 2024 return post. The honest verdict is: usable legacy tool, not a maintained one.
Is it still safe to use Win32 Disk Imager?
For its narrow job on a drive you have selected carefully, it remains usable: it writes and reads raw images as it always has. But because it is unmaintained, you should not expect security fixes or new features, and you must back up anything important before writing.
Did the maintainer abandon the project?
The project went quiet for years, and FileHorse describes it as discontinued or no longer actively developed. In November 2024 the maintainer, Tobin, posted on the SourceForge blog that he was returning, rebuilding his build environment on Windows 11, and sifting through the merge-request backlog. No new release followed that post.
What should I use instead if I want a maintained tool?
For flashing Raspberry Pi cards, Raspberry Pi Imager is the maintained official choice. For general flashing with validation, balenaEtcher is maintained and cross-platform. Keep Win32 Disk Imager for its read-back strength if you are on Windows.