v77

I can run any .exe file on an ImDisk volume (Windows 11 21H2).

I copied a large file (more than 1 GB) onto the ramdisk (no matter the name, let's say "Z:\test"), and then I used fsutil sparse setFlag Z:\test 1 fsutil sparse setRange Z:\test 0 536870912 The first 512 MB was set to 0, and I retrieved a free space of 512 MB.

Strange... I just did a few tests on a dynamic ramdisk with the "fsutil sparse" commands, and everything works fine. I can convert a file to a sparse file and set a region to 0 (with the region properly unallocated). So I assume an incompatibility from the driver (don't expect a fix). But this has nothing to do with sparse files.

Did you format as NTFS?

By the way, the GUI now allows to start a script just after the ramdisk creation. As it run as a service at system startup, you could have your ramdisk ready sooner. About the options of the command line utility "imdisk.exe", I would recommend to enter "imdisk.exe" in a command prompt, without argument, to see the (very long) syntax help.

The synchronization of all the ramdisks created with the synchronization option can be called from command line, with something like: "C:\Program Files\ImDisk\ImDiskTk-svc.exe" SYNC Of course, it requires administratives privileges. With that, you can either create a shortcut to manually start it from the desktop or the taskbar, or create a scheduled task to start it periodically.

Yes sorry, it seems I missed some parts of your first message. Perhaps a last thing to test if you want: try a dynamic ramdisk with AWE (see in Advanced tab). As the memory allocation method is very different, it might help to locate the issue.

I am now testing exFAT. No crash to report. I will continue the test for a few days. Another thing you could try: use a drive letter other than A or B. It would be surprising, but it is not impossible that there is something with that.