LTR Data logo

Tools and utilities for Windows

Follow on LinkedIn!

Third-party reviews and ratings for ImDisk and ImDisk Toolkit:
Programosy 5/5 stars MadDownload.com Editor's Choice KubaDownload


This page contains downloadable releases of native Windows tools and .NET utilities, including both older software and more recent projects. Source code repositories for many of them are available at GitHub. Downloaded releases can differ from the latest source. Check the framework, architecture and date shown for each download, together with its included documentation. Redistribution and source-code use are subject to each project's license and third-party notices; retain the notices supplied with the software.

Most of the programs here are compressed into ZIP files. ZIP files can be uncompressed in Windows XP and Windows Server 2003 but earlier versions of Windows require a third-party ZIP tool, like the freeware 7-zip.

Please note!

The applications and tools provided at this web site are intended for system administration, backup and recovery operations, research, forensics investigations and similar tasks and for legitimate lawful purposes only. There is no malware, spyware or any similar things spread through the software and the software will not make hidden modifications to user's operating system or environment without user specifically asking for it using command line options, user interface provided options or similar. There are no hidden features for spying on users such as reporting usage information or any other private information back to any other place.

The applications are not tested in all possible environments. Neither authors nor distributors should be held responsible for what the applications actually do when they are used.

If you have any ideas or modifications of source code you would like to share, please send me an e-mail. Licensing differs between projects and their dependencies. See the license supplied with the particular release and its source repository for commercial redistribution and source-code requirements. ImDisk and Arsenal Image Mounter have specific licensing information below. Contact the maintainer if the terms for a particular download are unclear.

Voluntary payments for use of downloaded software

Programs listed here are free to download and use. To make it possible to continue with this and pay for web site, software signing certificates and other costs you are more than welcome to pay a voluntary usage "fee". For information about possible ways to pay, please follow this link.

Ads from Google. Not about my products, but might be of interest:


On this page

Advice and consultation available

Need advice for programming projects or need a C/C++ or .NET C#/VB programmer? Advice how to optimize and simplify administration of computers and networks? Migrate old source code to modern development systems? Have some kind of hard-to-solve problem with computers, networks, drivers, applications etc? Maybe I can help you. Send me an e-mail: olof@ltr-data.se or call me on Phone/Signal/WhatsApp at +46 70 345 89 52. (I speak Swedish and English.)

Click here for update history for this page (last update 18 September 2026)

All file dates are in ISO date format, YYYY-MM-DD. This makes the list easier to sort.

ImDisk Virtual Disk Driver

Current version 2.1.2 built 09 May 2026 packaged 11 May 2026

ImDisk is a virtual disk driver for Windows with a legacy design that emulates disk volumes rather than complete disks. It can create virtual hard disk partitions, floppy or CD/DVD drives using image files or system memory. The install package installs a console-mode control program called imdisk.exe and a Control Panel applet . After install is finished, type imdisk without parameters for syntax help or double click the ImDisk icon in the Control Panel. It also adds a menu item in Windows Explorer so that you can right-click on a file to mount it as a virtual disk drive. Users of mdconfig in FreeBSD will probably be familiar with the command line syntax of imdisk.exe. The driver, service and control program can be uninstalled using the Add/Remove programs applet in the Control Panel. Installation and removal normally work without rebooting, but a reboot can be required if components are still in use.

Physical-memory RAM disks use the separate AWEAlloc driver. Since the May 2026 release, AWEAlloc and DevIoDrv are no longer included in the ImDisk setup package or source repository. Their source and driver packages are available with Arsenal Image Mounter. Install its driver package if AWEAlloc is not already installed from an older ImDisk or Arsenal Image Mounter package.

The ImDisk driver supports forwarding I/O requests to third-party image file format handlers or to services on other computers on the network. This makes it possible to boot a machine with NTFS partitions with a Live-CD and use the included  devio tool to let ImDisk on another computer running Windows on the network mount the NTFS partition on the machine with a faulty NTFS partition. This way you can recover information and even run chkdsk on drives on machines where Windows does not boot. There are also instructions about how to use devio under Windows on Claus Valca's blog.

About the install package

The install package is created using 7-zip sfx stubs and includes an .inf install script. Use a package matching the target Windows version, architecture and driver-signing requirements. Older releases supported systems back to Windows NT 4.0 through this installer; that does not mean every current signed driver loads on every historical Windows version. Windows NT 3.51 and ARM/ARM64 require manual setup; see the notes below and the ARM64 setup guide, applying the AWEAlloc migration note above.

Compatibility

ImDisk receives maintenance fixes, but no new features are planned. Its legacy design is not recommended for recent Windows versions. For full disk integration on modern Windows, consider Arsenal Image Mounter below.

ImDisk Virtual Disk Driver is designed to be a small, simple and yet powerful virtual disk driver. It runs on very old versions of Windows NT as well as modern Windows versions. However, because of this compatibility design and because it emulates disk volumes rather than complete disks, it is not always compatible with all applications and drivers. For instance, you cannot manage things like mount points, drive letters and similar for ImDisk drives using mountvol command line tool or in Disk Management in Windows. As another example, you cannot create or access shadow copies on ImDisk drives. So, applications that use similar Windows features as Disk Management dialog to enumerate disks and disk volumes to find disk properties like sector sizes and similar, might possibly not work as expected with ImDisk drives.

Arsenal Image Mounter - If you need full disk emulation support

If you need full disk emulation, including integration with Disk Management, Volume Shadow Copy Services, mountvol and diskpart command line tools as well as better compatibility with applications, we provide another open source virtual disk project, called Arsenal Image Mounter. It is published together with Arsenal Recon and is available for download here. Its source code and APIs are available under AGPL v3 for projects with compatible licensing. The end-user application has Free and Professional modes; see the product page for their features and licensing. For alternative licensing, contact Arsenal Recon for more information. Source code, command line tools, driver setup packages and similar for Arsenal Image Mounter are available on GitHub. The directory structure is described in this document.

Questions?

Discussions about ImDisk Virtual Disk Driver and other tools published here were previously hosted on the Reboot.pro forum.
Answers to frequently asked questions were collected in Reboot.pro forum topic 15593 (original link no longer available).

ImDisk Toolkit

The ImDisk Toolkit is a complete package that adds a more modern and intuitive user interface to ImDisk. ImDisk Toolkit offers features like automated creation of memory disks at system startup and mounting many different image file formats. It is developed and maintained by "v77". It is available for download here.

Reviewed by Tekzilla

There is a Tekzilla review of ImDisk Toolkit on Youtube:


Third-party reviews and ratings

Programosy 5/5 stars MadDownload.com Editor's Choice KubaDownload

CPU architecture compatibility

Almost all of the source code is identical for all supported CPU architectures. Currently supported architectures are x86, ia64, x64, arm32 and arm64. All features and most limitations are the same in the 64-bit and 32-bit versions. The 64-bit builds avoid the 32-bit address-space limits, but RAM-disk sizes are still constrained by available memory, backing mode and system limits.

Driver files are digitally signed with a certificate trusted by Microsoft.

Driver signing does not guarantee compatibility with every Windows version or security configuration. In particular, the signing-certificate change documented on 5 November 2021 means those newer drivers do not load on x64 Windows Vista or Windows Server 2008 under normal signature enforcement.

Special note for Windows NT 3.51

The .inf file used in the install process is not compatible with Windows NT 3.51. To install on NT 3.51 you can extract the files in the packages using 7-zip and then manually create the driver keys in the registry or using a SCM control tool like sc.exe in the Windows NT Resource Kit. Other Windows versions and architectures must also meet the package and signing requirements described above.

Source code

Source code for all of ImDisk Virtual Disk Driver, including the devio server-side tool, API libraries etc is available as a Github repository. Different parts of the source tree are built in different environments:

API

API functions are available for C/C++, COM and .NET clients. If you want to call functions for creating/removing/querying virtual disks from your own program you can #include the file inc\imdisk.h in your C/C++ source files and link the imdisk.lib library built for the application's architecture (for example, cpl\i386\imdisk.lib for x86). Read inc\imdisk.h in source archive for documentation about C/C++ usage. If you would like information about how to write compatible server-end software in C/C++ you can take a look at the I/O packet structures in inc\imdproxy.h.

A class library DLL for COM and .NET developers is available as separate wrapper DLLs, published at NuGet. LTRData.ImDiskNet and LTRData.DevioNet. Supported frameworks depend on the package and version: the current ImDiskNet project retains a .NET Framework 2.0 target, while DevioNet starts at .NET Framework 4.0; both also have modern .NET and .NET Standard targets.
Look here for on-line documentation about .NET API. There are also, as usual, xml files with method/parameter descriptions available to each assembly file.

There is also a .NET application, DiscUtilsDevio, that combines image file format support in DiscUtils libraries with ImDisk.
DiscUtilsDevio.zip - 559.6 KB (.NET Framework 4.6, compiled 2025-11-02)
DiscUtilsDevio.zip - 550.9 KB (.NET Framework 4.8, compiled 2025-11-02)
DiscUtilsDevio.zip - 1.5 MB (.NET 8.0-windows, compiled 2025-11-02)

License

ImDisk includes GPL-licensed floppy-emulation code and other copyright notices. See the separate ImDisk license document and the notices accompanying the release for the applicable terms. Alternative commercial licensing for a version without the GPL-licensed code is available on request. Contact the maintainer at olof@ltr-data.se to discuss availability and terms.

Zero and Random device driver - updated 16 November 2022

The Zero and Random device driver creates two device objects, \Device\Zero and \Device\Random and a symbolic link to each of these under \DosDevices so that they are reachable from Win32 applications using the syntax \\.\zero and \\.\random. The devices work like /dev/zero and /dev/random in *nix like environments. Zero produces zero characters and Random produces random characters in the read buffers. When written to both of the device objects act like a Null device, that is just accepting and ignoring the data in the write buffer. The drivers can e.g. be used with the classic dd tool or with my rawcopy tool to fill files, devices etc with zero or random characters, e.g. to wipe out the contents of a hard drive.

Beginning with version 1.1.0.3 different versions are installed on different versions of Windows. On Vista and later, random numbers are generated by system cryptographic random number generator. On earlier versions random numbers are generated by RtlRandom or RtlRandomEx API functions with a time based seed.

The install package installs the driver and loads it into the kernel and setup for automatic load when Windows starts up. The driver can be uninstalled using Add/Remove programs applet in the Control Panel.

About the install package

The install package is created using 7-zip sfx stubs and includes an .inf install script. Legacy packages target Windows NT 4.0/2000/XP/Server 2003/Vista/Server 2008, with separate 32-bit and 64-bit binaries where applicable. Use a driver package matching the target OS and architecture. Windows NT 3.51 requires the manual installation described below.

Drivers are now digitally signed with a certificate trusted by Microsoft.

Loading a signed driver also depends on the target Windows version and its driver-signing policy; use a compatible signed package.

Special note for Windows NT 3.51

The .inf file used in the install process is not compatible with Windows NT 3.51. To install on NT 3.51 you can extract the files in the packages using 7-zip and then manually create the driver keys in the registry or using a SCM control tool like sc.exe in the Windows NT Resource Kit. On later versions of Windows you just run the package and it will install everything automatically.

Source code

Source code for  this driver is available on GitHub. The source code can be built both with legacy Makefile-based WDK build environments and with modern Visual Studio integrated WDK.

Small native Windows command line utilities

Windows requirements vary by tool and release. Some historical x86 builds run on Windows 95/98/ME or Win32s, while others require Windows NT or later APIs. For example, fdf releases since March 2024 no longer support Windows 95/98/ME. Check each tool's description and release notes for its requirements.

Native build and runtime notes

Many small legacy x86 builds use minimal CRT support code linking to Windows system libraries such as crtdll.dll or msvcrt.dll. Other builds require a separate runtime. Runtime and minimum Windows requirements vary between builds.

Downloads labelled 64 bit in this section are x64 builds. ARM32 and ARM64 downloads are separate architectures. Some builds require a matching Visual C++ runtime; use the version and architecture required by that executable.

Big ZIP files with compiled stand-alone exe-files for most of the utilities listed here and some more:
Zip archive with 32 bit exe files (2.0 MB)
7-zip archive with 32 bit exe files (548.1 KB)
Zip archive with 64 bit exe files (2.1 MB)
7-zip archive with 64 bit exe files (555.4 KB)
Zip archive with ARM exe files (2.3 MB)
7-zip archive with ARM exe files (555.6 KB)
Zip archive with ARM64 exe files (2.4 MB)
7-zip archive with ARM64 exe files (575.7 KB)

Small native Windows utilities with graphical user interface (or with no user interface at all)

Windows requirements vary by tool and release. Some historical x86 utilities support Windows 95/98/ME or Win32s; others use NT-specific APIs or require additional runtimes. See each description and the native build and runtime notes above.

Small .NET command line utilities

Platform requirements vary by tool; Windows-only tools are marked below. Select a download for the runtime installed on the target machine. .NET Framework builds require Windows, while modern .NET runtimes are available for several platforms. A .NET Standard label describes API compatibility, not an installable runtime; select a runnable .NET build for command-line use.

Small .NET tools with graphical user interface (Windows only)

These applications are built with Visual Studio. They require .NET Framework, .NET Core or .NET as specified. Most Windows versions come with .NET Framework preinstalled, you can check which versions and download other frameworks here.
Back to LTR Data homepage