ttcjohnson

so you are saying the img mount process affects the ramdisk creation on boot if incorrect image files are used?

hi ramdisk not created or created but not formatted as well as image(s) not mounted on boot. sometimes ramdisk was created but img not mounted or vice versa, while sometimes both failed at boot with both successful done rarely. as a result i created a bat file to perform the tasks if the drives are not properly created. no related issues found in event log imdisk was running without any problems before on server 2008r2 and 2016, and the only changes were, i added the mount image process in imdisk...

but before i switched to ImDisk, there's no problem. yeah i think it's looking for a temp folder located on a 'physical' disk, which the previous ramdisk software allows to treat the ramdisk as a physical one. is it possible to add this option also to ImDisk?

unfortunately this is not my case. i use R as the ramdisk drive letter and not able to get certain windows update installed. i have tried to change those temp/tmp path but still no luck. the only way is to set all temp/tmp path to a physical disk and reboot to install the updates btw i have set all temp/tmp path to R:\Temp with junctions pointing to it as well like c:\temp etc wanted to report this months early but due to some problems i couldnt get my account verified. sorry about that