As I just said here, an issue in Windows 11 24H2 with the UAC prevents executables to run from inside the volume if they require elevation. It is highly unlikely that Microsoft fix it.
After some thoughts, I have a personal interest to find a solution.
It's time to see what can be done with Arsenal Image Mounter. But it's a huge work. In any case, don't expect something before several months at least.
🎉
1
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Olof :)
Why do you keep saying that it's UAC/Windows' fault, if primo ramdisk works without a problem, and even dynamic ram works too?
And from what I understand, there hasn't been any primo update for about a year, so they probably didn't have this problem at all.This is not a complaint, I just have an idea, maybe the situation is not as bad as you say? Maybe installing a trial version of primo will lead you to some solution to the situation?Anyway good luck, i hope you find a solution. until then i'm not installing a new version of windows 24h2.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This issue is likely the same as always: an incompatibility of some Windows functions such as "GetFinalPathNameByHandle" with the ImDisk volumes.
Some softwares, especially a lot of installers (including installers from Windows Update), are affected.
But now, this function is also very likely used by the UAC itself. Therefore, it leads to an error when an executable calls the UAC.
Some incompatibilities were still acceptable. But now, its' all the executables requiring UAC that are affected. It's a major incompatibility, and we can expect nothing from Microsoft about that.
All I know is that we need AIM. But even though Olof worked to make it usable in a similar way to the ImDisk driver, there are still a lot of differences.
So I don't know yet exactly what can be done. But I want a dynamic ramdisk at any cost. :)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
"I'm not Olof. "sorry, I didn't know ;) thanks for the explanation.
And doesn't completely disabling uac solve the problem?
I know it's the atomic option, but if it could be temporary.
Yes, for me dynamic ram is also a necessary option, I keep my fingers crossed for success anyway :)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Disabling the UAC changes nothing, because it just makes the elevation silent.
And even as a workaround, I don't consider that as an acceptable solution.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
As I just said here, an issue in Windows 11 24H2 with the UAC prevents executables to run from inside the volume if they require elevation. It is highly unlikely that Microsoft fix it.
After some thoughts, I have a personal interest to find a solution.
It's time to see what can be done with Arsenal Image Mounter. But it's a huge work. In any case, don't expect something before several months at least.
Hi Olof :)
Why do you keep saying that it's UAC/Windows' fault, if primo ramdisk works without a problem, and even dynamic ram works too?
And from what I understand, there hasn't been any primo update for about a year, so they probably didn't have this problem at all.This is not a complaint, I just have an idea, maybe the situation is not as bad as you say? Maybe installing a trial version of primo will lead you to some solution to the situation?Anyway good luck, i hope you find a solution. until then i'm not installing a new version of windows 24h2.
I'm not Olof. :)
This issue is likely the same as always: an incompatibility of some Windows functions such as "GetFinalPathNameByHandle" with the ImDisk volumes.
Some softwares, especially a lot of installers (including installers from Windows Update), are affected.
But now, this function is also very likely used by the UAC itself. Therefore, it leads to an error when an executable calls the UAC.
Some incompatibilities were still acceptable. But now, its' all the executables requiring UAC that are affected. It's a major incompatibility, and we can expect nothing from Microsoft about that.
All I know is that we need AIM. But even though Olof worked to make it usable in a similar way to the ImDisk driver, there are still a lot of differences.
So I don't know yet exactly what can be done. But I want a dynamic ramdisk at any cost. :)
"I'm not Olof. "sorry, I didn't know ;) thanks for the explanation.
And doesn't completely disabling uac solve the problem?
I know it's the atomic option, but if it could be temporary.
Yes, for me dynamic ram is also a necessary option, I keep my fingers crossed for success anyway :)
Disabling the UAC changes nothing, because it just makes the elevation silent.
And even as a workaround, I don't consider that as an acceptable solution.
I created a small fix for this, but somehow I can't post the github link here. An anti-spam filter deleted it.
Anyway, searching github for " Win11-RAMDisk-Admin-Fix" should take you to my fix.
A similar project is based at Arsenal, maybe you could work on it together?
https://github.com/tmcdos/ramdisk/