Well, Olof's comments about it getting harder to keep things working on newer Windows versions are well taken...
1) I was unable to complete my update to 24H2 (the latest "Release Preview") without disabling / bypassing ImDisk (the latest, from the 20240210 ImDisk toolkit) - note that I use ImDisk to provide a RAMDrive behind a "/tmp" mount point.
2) After the update was running and I had re-enabled ImDisk (and my /tmp was using it), I found something new: when trying to execute a new NVidia driver install, I receive an error popup with the message "Incorrect function." - so of course I moved the file out of my ImDisk RAMDrive(a) to my SSD and the same file executed without issue.
a) note that had forced the almost-a-gigabyte expansion to happen in /tmp
I am not expecting any fixes here, just wanted to provide some info for anyone else trying to use the cool ImDisk with the newest Windows 11 - and yes, it is technically still a "pre-release", but I don't really expect the above two issues to vanish when the full release is out.
UPDATE: the problem with 24H2 is actually way worse than this... ANY install package which expands to a "/tmp" tree that is based on an ImDisk RAMDrive and tries to execute from there - will fail. I either need to quit using an ImDisk-based /tmp tree or find another RAMDrive package that acts like a "real" drive - like maybe Arsenal Image Mounter? :(
Last edit: R. Daneel Olivaw 2024-06-08
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
To be clear, this thread is just to document that Windows 11 is tightening up on security issues - perhaps excessively so, but that is where we are now (or will be soon).
24H2 now blocks me from things that used to work fine - like executing out of an ImDisk-based /tmp folder. :(
ImDisk - and v77's Toolkit - have served me well for years... but now changes in Windows 11 have forced me to switch to a different RAMDrive solution (one that does a more complete H/W simulation).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
With 24H2 you can no longer execute .exe at all, even if you only use the RAMdisk as a normal drive and have done nothing but the TEMP folder.
I personally use the RAMdisk as a download folder. No .exe installer can be executed directly from there!
Everything was fine until 23H2.
Here is some reading material and in my opinion also the reason why it no longer works and never again if you do not update the driver. The original DEV has already buried the thing forever.
https://github.com/tmcdos/ramdisk
Here is a ForK with a "new" driver model.
Unfortunately no dynamic size is supported (I don't know if this is just a bug in the GUI or if the driver or the CLI tool can't do it).
With only 64GB RAM, a dynamic size is a must for me on a RAM disk. Especially as a temp or pure download folder.
Think, ImDisk Toolkit is death with Windows 24H2!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Capitalising 'DEV' confuses. I presume that you mean 'dev', i.e., developer.
'ImDisk Toolkit is death with Windows 24H2!' That is overly dramatic, but perhaps only because of poor English; I think that you mean the following. The project 'is dead' with Windows 24H2, i.e., that version of Windows kills the project.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Now, some of the previously non executable files can now run. It is uncertain whether the changes occurred after updating the system to 1150 or due to Microsoft quietly updating databases or components in the background.
Last edit: net 2024-07-22
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
"have forced me to switch to a different RAMDrive solution (one that does a more complete H/W simulation)."
What other working ramdisk do you have? Only primo seems to work well, but it's paid.
I can't confirm these symptoms because I have 23h2. but it sounds scary.
I have been using this ramdisk for a dozen or so years, and I can no longer use Windows without a good dynamic ramdisk.
Bad times await us ehh :(
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yes, that is correct - I did end up using "Primo Ramdisk Standard".
It is indeed a not-free product, but it is what I found that actually looks like a "real" drive to Windows 11 24H2, is dynamic (up to 8GB, which is all I need), and can start up already mounted as my "/tmp" tree.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
its good software,but you're not completely safe ;) I remember that during some windows update, primo didn't work in the new version of windows, and you had to wait a few months or even half a year for the update.That's why it's good to have an alternative.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for the tip, I am indeed having a problem (for over 10 days now) with being unable to apply KB5040529 (the latest 24H2 Cumulative Update Preview) - and of course there is a) NO useful error message, and b) NO hint of any kind of help from "Windows Insiders" support.
But as I did already consider Primo as a possibility for the update failure, I quit using it for my temp and tried again... but it made NO difference - so Primo is back in use again.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Well, Olof's comments about it getting harder to keep things working on newer Windows versions are well taken...
1) I was unable to complete my update to 24H2 (the latest "Release Preview") without disabling / bypassing ImDisk (the latest, from the 20240210 ImDisk toolkit) - note that I use ImDisk to provide a RAMDrive behind a "/tmp" mount point.
2) After the update was running and I had re-enabled ImDisk (and my /tmp was using it), I found something new: when trying to execute a new NVidia driver install, I receive an error popup with the message "Incorrect function." - so of course I moved the file out of my ImDisk RAMDrive(a) to my SSD and the same file executed without issue.
a) note that had forced the almost-a-gigabyte expansion to happen in /tmp
I am not expecting any fixes here, just wanted to provide some info for anyone else trying to use the cool ImDisk with the newest Windows 11 - and yes, it is technically still a "pre-release", but I don't really expect the above two issues to vanish when the full release is out.
UPDATE: the problem with 24H2 is actually way worse than this... ANY install package which expands to a "/tmp" tree that is based on an ImDisk RAMDrive and tries to execute from there - will fail. I either need to quit using an ImDisk-based /tmp tree or find another RAMDrive package that acts like a "real" drive - like maybe Arsenal Image Mounter? :(
Last edit: R. Daneel Olivaw 2024-06-08
In fact, no exe program can run on virtual disk created by ImDisk.However, other memory disk software is working properly.
I can run any .exe file on an ImDisk volume (Windows 11 21H2).
To be clear, this thread is just to document that Windows 11 is tightening up on security issues - perhaps excessively so, but that is where we are now (or will be soon).
24H2 now blocks me from things that used to work fine - like executing out of an ImDisk-based /tmp folder. :(
ImDisk - and v77's Toolkit - have served me well for years... but now changes in Windows 11 have forced me to switch to a different RAMDrive solution (one that does a more complete H/W simulation).
With 24H2 you can no longer execute .exe at all, even if you only use the RAMdisk as a normal drive and have done nothing but the TEMP folder.
I personally use the RAMdisk as a download folder. No .exe installer can be executed directly from there!
Everything was fine until 23H2.
Here is some reading material and in my opinion also the reason why it no longer works and never again if you do not update the driver. The original DEV has already buried the thing forever.
https://github.com/tmcdos/ramdisk
Here is a ForK with a "new" driver model.
Unfortunately no dynamic size is supported (I don't know if this is just a bug in the GUI or if the driver or the CLI tool can't do it).
With only 64GB RAM, a dynamic size is a must for me on a RAM disk. Especially as a temp or pure download folder.
Think, ImDisk Toolkit is death with Windows 24H2!
@buoaggr:
Capitalising 'DEV' confuses. I presume that you mean 'dev', i.e., developer.
'ImDisk Toolkit is death with Windows 24H2!' That is overly dramatic, but perhaps only because of poor English; I think that you mean the following. The project 'is dead' with Windows 24H2, i.e., that version of Windows kills the project.
Now, some of the previously non executable files can now run. It is uncertain whether the changes occurred after updating the system to 1150 or due to Microsoft quietly updating databases or components in the background.
Last edit: net 2024-07-22
"have forced me to switch to a different RAMDrive solution (one that does a more complete H/W simulation)."
What other working ramdisk do you have? Only primo seems to work well, but it's paid.
I can't confirm these symptoms because I have 23h2. but it sounds scary.
I have been using this ramdisk for a dozen or so years, and I can no longer use Windows without a good dynamic ramdisk.
Bad times await us ehh :(
Yes, that is correct - I did end up using "Primo Ramdisk Standard".
It is indeed a not-free product, but it is what I found that actually looks like a "real" drive to Windows 11 24H2, is dynamic (up to 8GB, which is all I need), and can start up already mounted as my "/tmp" tree.
its good software,but you're not completely safe ;) I remember that during some windows update, primo didn't work in the new version of windows, and you had to wait a few months or even half a year for the update.That's why it's good to have an alternative.
Thanks for the tip, I am indeed having a problem (for over 10 days now) with being unable to apply KB5040529 (the latest 24H2 Cumulative Update Preview) - and of course there is a) NO useful error message, and b) NO hint of any kind of help from "Windows Insiders" support.
But as I did already consider Primo as a possibility for the update failure, I quit using it for my temp and tried again... but it made NO difference - so Primo is back in use again.