Everything below comes from the project's own repository and release notes. None of it is independent testing.
What WINUDF is
WINUDF is a file system driver for UDF volumes. WINUDF.EXE gives DOS and Windows 1.0x through 3.11 drive letters for UDF volumes, and WINUDF.VXD is an IFS Manager file system driver for Windows 95, 98 and ME with long file name support. The project says it reads and writes UDF versions 1.02 through 2.60. That covers the format used on DVDs, Blu-ray discs, packet-written CDs and UDF-formatted USB sticks and disks.
It is one of four related WINDRV packages. The others are WINDISK for disks and optical drives, WINUSB for USB, and WINAUDIO for sound. Each package can be used alone or alongside the others.
The context matters because native support on these systems was thin. A retro-computing write-up on an earlier Windows 95 UDF driver notes that Windows 95 has no native UDF support, so it can't read DVD-Video discs without extra software. That older driver was also read-only. WINUDF adds writing.
Supported systems
The project's list is:
- MS-DOS 3.10 through 8.0, and FreeDOS
- Windows 1.0x and 2.x in real mode
- Windows 3.0, 3.1 and Windows for Workgroups 3.11, with UDF volumes shown as network drives
- Windows 95, 98 and ME
The README lists Windows/386 2.x as "not tried". Don't treat it as supported. Nothing here suggests the driver works on Windows NT-family or modern Windows. Those systems have their own UDF support.
What changed in 1.2
The crash fix for Windows 95, 98 and ME
The headline fix is for crashes. Programs on UDF discs, and WINUDF's own installer, no longer crash with 0xC0000005 on Windows 95/98/ME.
The project explains the cause as a race on the driver's shared buffers:
- A program running from a UDF disc issues a read or write.
- In the middle of that request, a page of the program's own image is paged in from the same disc.
- The page-in reuses the driver's block cache and transfer buffer.
- The original program receives the page-in's data instead of its own.
Version 1.2 locks the read or write buffer before the driver starts the operation. This is the project's account of the bug. The repository does not say how many users or programs were affected. The failure applies to running executables from a UDF disc, not to every use of UDF media.
Storage-boundary fixes
- Extent overflow: Extents for written or filled files are now capped at the largest length an extent can describe, just under 1 GB. Before, filling a hole at once could create an oversized extent, and its length overflowed into the type bits. Merging blocks into the last extent can no longer overflow either.
- DOS 64 KB segment boundary: Buffers are normalized before device transfers. A 32 KB transfer therefore never runs past the end of a 64 KB segment.
The extent fix matters for anyone writing large files to UDF media, because an overflow into type bits could corrupt how a file is described on disc. The project doesn't report real-world corruption cases, so treat that as a reasonable inference rather than a documented outcome.
Long file name and large-file fixes in DOS
- INT 21h function 716Ch now passes the caller's mode, attributes and action to DOS unchanged. The create action had been masked off. On DOS 3.x, which has no function 6Ch, the file is opened with function 3Dh. The project ties this to issues 9 and 12.
- INT 21h function 7142h now accepts negative positions, like DOS's own seek (issue 11).
- Positions beyond 4 GB: The high dword is now stored in the file's system file table entry at offset 07h, a field free for a redirector. It was previously held in a table of eight entries. Any number of open files can now sit beyond 4 GB (issue 10).
- Startup handle cleanup: Before going resident, the program closes handles 0 through 19 without consulting the job file table (issue 8).
- Unloading: Unload now follows interrupt handlers whose IISP header has any kind of jump before the "KB" signature (issue 7).
These are low-level fixes. They mostly matter to people running MS-DOS 7.x tools like DIR and COPY, or developers writing DOS programs against the long-file-name API.
Uninstall and labeling
On Windows 3.x, Program Manager gets an Uninstall WINUDF item, shown as a disk icon with a red cross. Selecting it closes Windows, runs UNINUDF /REBOOT and restarts the computer. The WINUDF.EXE banner and the driver and documentation texts now name the supported range as DOS and Windows 1.x through ME.
How earlier versions fit in
Don't mistake these older items for 1.2 features.
- 1.0 (October 12, 2026): First release, with UDF 1.02 to 2.60 read and write support. An update on October 14 split the package into bin/DOS, bin/WIN3X and bin/WIN9X.
- 1.1 (October 26, 2026): Added the MS-DOS 7 long-file-name API, free-space reporting through 7303h, and 64-bit file positions through 7142h. It also fixed Windows 98 freezing on certain UDF disks, a "disk structure is corrupted" error when copying folders in Windows 98, and hangs when writing INI files or desktop.ini on UDF drives. It added writing to Windows 10 UDF 2.60 disks, and MS-DOS 7.0, 7.1, 8.0 and FreeDOS support.
The release cadence is brisk: three versions in about three weeks. Treat it as young, fast-moving software, not a long-settled driver. That is useful for fixes and a mild caution if you rely on it for irreplaceable data.
Installing it, per the project
Run the installer from DOS, or from an MS-DOS box on Windows 95/98/ME, in the package's bin\DOS folder.
- Run
INSTUDFto install to the default directory. It updates AUTOEXEC.BAT and SYSTEM.INI. - For another location, use
INSTUDF C:\DRV /O /L:R. Options for WINUDF.EXE follow /O, and drive letters start from R. - Keep the whole bin tree together. The installer pulls files for other systems from the folders next to it, so copy all of it to a floppy or a directory.
What the installer does
- DOS and Windows 3.x: WINUDF.EXE goes into AUTOEXEC.BAT after the MSCDEX line. LASTDRIVE=Z goes into CONFIG.SYS when needed.
- Windows 95/98/ME: WINUDF.VXD goes into WINDOWS\SYSTEM, and
device=WINUDF.VXDgoes into the [386Enh] section of SYSTEM.INI. - Backups: The originals are saved as .WNF files.
- Removal: Run
UNINUDF.
Manual setup
- DOS and Windows 1.0x to 3.11: Add LASTDRIVE=Z to CONFIG.SYS. Add
C:\WINDRV\WINUDF.EXEto AUTOEXEC.BAT after the MSCDEX line. - Windows 95/98/ME: Copy bin\WIN9X\WINUDF.VXD to C:\WINDOWS\SYSTEM. Add
device=WINUDF.VXDto the [386Enh] section of SYSTEM.INI.
The project says the installer also adds WINUDF.EXE to DOSSTART.BAT for the MS-DOS mode of Windows 95/98. On MS-DOS 7.x and FreeDOS it uses AUTOEXEC.BAT.
Success should look like UDF discs showing up under their own drive letters, and on Windows 95/98/ME as ordinary drives with long names. I haven't tested that. It follows from how the project describes the driver.
Practical advice
- Back up first. The installer edits CONFIG.SYS, AUTOEXEC.BAT and SYSTEM.INI. It saves .WNF copies, but a separate backup of those files is cheap insurance.
- Update if you run programs from UDF discs on Win9x. That is the case the 0xC0000005 fix targets.
- Be careful with large writes on 1.1 or earlier. The extent overflow fix applies to big hole-filling writes.
- Don't expect more than the documented list. Windows/386 2.x is untested, and the license is GPL-3.0, so the source is open to inspect.
The takeaway
WINUDF 1.2 won't make headlines outside retro computing. For people keeping Windows 95, 98, ME or DOS machines alive, it fixes a nasty crash with a clearly described cause. It also fixes several large-file edge cases and adds a tidy uninstall path on Windows 3.x.
The documentation reads carefully written. All of the evidence is the author's own, though, so independent field reports will tell us how well the fixes hold up.
References
- WINUDF 1.2 Ships Long File Name Fixes and Crash Patches for UDF Discs - news.lavx.hu news.lavx.hu · 2026-11-16T13:09:04.191000+00:00
- GitHub - ages2001/WINUDF: UDF IFS (Installable File System driver) for DOS, Windows 1.0x/2.xx/3.xx/95/98/ME · GitHub github.com
- Operating System Revival: Win 95 UDF Driver 1.02 (DVD Reader) retrosystemsrevival.blogspot.com