I often have a problem of missing full shutdown in Win 10 on a computer but not in other.
I noticied that it solve if I before manually unmont a ImDisk unit and a ProxyCypt unit.
Do it is a bug?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I just checked in a virtual machine and I saw no issue.
However, since some times, I too have difficulties with the shutdown of Win 10. But even by uninstalling ImDisk (so no ProxyCrypt nor ramdisk), the issue remains.
So, even if it seems to work for you by unmounting the ImDisk volumes, I think we likely have the same bug. Perhaps the Nvidia graphic driver (if you have a Nvidia card)? Or a virus?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I not have a virus.
The problem persist also changing antivirus.
My esperience with Nvidia problem, Intel Graphics problem.
Also you has the same problem with same solution?
Then problem can to be imdisk?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Auto-Dismount when system enters a Suspended state.
Do it is possible to add a option to Auto-Dismount when system enters a shutdown state to try if it solve the problem?
I think that with the latest versions of Windows, ImDisk cannot normally unmount the driver due to the transactional ntfs that leaves open handle.
But it affect crypted driver and not uncrypted driver.
It happens in two different computers with the same last OS.
Last edit: Mario Pilesi 2023-03-28
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
ProxyCrypt always dismounts the volume at shutdown. This is required because if the system kills the process with the volume open, Windows could try to send requests to the volume, and these requests would not be processed, which leads to a system freeze.
The technique used is very common and reliable (processing WM_ENDSESSION in an invisible window). For now, it perfectly works for me on my Windows 11. But of course, there could still be a bug somewhere.
I will check that again.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
ty, please try to mount a ntfs crypted volume, and copy and execute files.
After close, see if have opened transactional ntfs files and shutdown without expliti unmount.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You should avoid to put an ImDisk utility inside an ImDisk volume. This case requires to unmount each volume in the correct order, and it's currently impossible to do that programmatically.
Besides, I don't see the point to keep RamDyn in an encrypted volume. RamDyn is a legitimate software that writes nothing on the hard drive.
If the system still hangs with RamDyn on C:, then there is another issue. As I said, I will check a few things but it does not mean I will be able to do something. Microsoft has made things very limited about the shutdown...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Maybe because you use the flag IMDISK_API_NO_BROADCAST_NOTIFY that does not give time to completely close the handle?
I get a similar behavior when I use API before turning off:
- ImDiskSetAPIFlags(3) hang shutdown
- ImDiskSetAPIFlags(2) fine shutdown
It seems related to the 5 second limit for the shutdown.
It seems related to this and this.
Last edit: Mario Pilesi 2023-04-14
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I often have a problem of missing full shutdown in Win 10 on a computer but not in other.
I noticied that it solve if I before manually unmont a ImDisk unit and a ProxyCypt unit.
Do it is a bug?
I just checked in a virtual machine and I saw no issue.
However, since some times, I too have difficulties with the shutdown of Win 10. But even by uninstalling ImDisk (so no ProxyCrypt nor ramdisk), the issue remains.
So, even if it seems to work for you by unmounting the ImDisk volumes, I think we likely have the same bug. Perhaps the Nvidia graphic driver (if you have a Nvidia card)? Or a virus?
I not have a virus.
The problem persist also changing antivirus.
My esperience with Nvidia problem, Intel Graphics problem.
Also you has the same problem with same solution?
Then problem can to be imdisk?
Auto-Dismount when system enters a Suspended state.
Do it is possible to add a option to Auto-Dismount when system enters a shutdown state to try if it solve the problem?
I think that with the latest versions of Windows, ImDisk cannot normally unmount the driver due to the transactional ntfs that leaves open handle.
But it affect crypted driver and not uncrypted driver.
It happens in two different computers with the same last OS.
Last edit: Mario Pilesi 2023-03-28
ProxyCrypt always dismounts the volume at shutdown. This is required because if the system kills the process with the volume open, Windows could try to send requests to the volume, and these requests would not be processed, which leads to a system freeze.
The technique used is very common and reliable (processing WM_ENDSESSION in an invisible window). For now, it perfectly works for me on my Windows 11. But of course, there could still be a bug somewhere.
I will check that again.
See down.
Last edit: Mario Pilesi 2023-03-30
ty, please try to mount a ntfs crypted volume, and copy and execute files.
After close, see if have opened transactional ntfs files and shutdown without expliti unmount.
I found some ideas.
I have a encrypted volume that open with ProxyCrypt64avx.exe in X:
In X: I have RamDyn.exe
I create a volume Y: with X:RamDyn.exe
Before shutdown I use
imdisk -D -m Y:
imdisk -D -m X:
RamDyn.exe close and shutdown work
If I not force unmount the shutdown hang and
sometimes but not always i get "Task Host Window" warning.
I have tested:
If I move RamDyn.exe from X:encrypted to C:phisical
Shutdown sometimes it works and others are not (timeout?).
Last edit: Mario Pilesi 2023-03-29
You should avoid to put an ImDisk utility inside an ImDisk volume. This case requires to unmount each volume in the correct order, and it's currently impossible to do that programmatically.
Besides, I don't see the point to keep RamDyn in an encrypted volume. RamDyn is a legitimate software that writes nothing on the hard drive.
If the system still hangs with RamDyn on C:, then there is another issue. As I said, I will check a few things but it does not mean I will be able to do something. Microsoft has made things very limited about the shutdown...
Maybe because you use the flag IMDISK_API_NO_BROADCAST_NOTIFY that does not give time to completely close the handle?
I get a similar behavior when I use API before turning off:
- ImDiskSetAPIFlags(3) hang shutdown
- ImDiskSetAPIFlags(2) fine shutdown
It seems related to the 5 second limit for the shutdown.
It seems related to this and this.
Last edit: Mario Pilesi 2023-04-14