I am using version 21-May and 05-Jul.
OS: Win 11 Pro, 24H2
Been using RamDiskfeature or 2 months since version 21-may was released.
My img file is 100MB.
When i click unmount in RamDisk Config window, the img file created is around 24GB, the size of this destination drive where the original img is located.
After restarting pc, RAM used was also 24GB.
This happened after i get dialog box, saying files have changed, and i want to write back changes to img file.
Message: J: is in use by another process and cannot be locked. Therefore, it can be modified while copying.
Now i can see saving taking a long time and drive space gradually increasing until it is full.
any more details i can share to help reproduce steps?
Last edit: clark 2025-07-12
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks a lot for the report. Just by checking the source, I have found something. And yes, it should happen in the situation you describe: unmounting, and save in an image file. In this case (and only in this case), the drive number is not initialized, and therefore the disk used is 0, that is, your first physical disk.
I will upload a fix as soon as possible.
👍
1
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
the original img file if present in the C:, ie. OS partition has more serious consequences because there is no space left on it. after a restart, OS may not boot.
Thanks for you reply.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
I am using version 21-May and 05-Jul.
OS: Win 11 Pro, 24H2
Been using RamDiskfeature or 2 months since version 21-may was released.
My img file is 100MB.
When i click unmount in RamDisk Config window, the img file created is around 24GB, the size of this destination drive where the original img is located.
After restarting pc, RAM used was also 24GB.
This happened after i get dialog box, saying files have changed, and i want to write back changes to img file.
Message: J: is in use by another process and cannot be locked. Therefore, it can be modified while copying.
Now i can see saving taking a long time and drive space gradually increasing until it is full.
any more details i can share to help reproduce steps?
Last edit: clark 2025-07-12
Thanks a lot for the report. Just by checking the source, I have found something. And yes, it should happen in the situation you describe: unmounting, and save in an image file. In this case (and only in this case), the drive number is not initialized, and therefore the disk used is 0, that is, your first physical disk.
I will upload a fix as soon as possible.
the original img file if present in the C:, ie. OS partition has more serious consequences because there is no space left on it. after a restart, OS may not boot.
Thanks for you reply.
It should now be fixed. There was also another minor bug.
updated to 20250713, seems to work as expected. Thank you for the quick response.