With the fast startup, the state of all the running services is written to the disk, like any part of the kernel.
This means that they are not restarted at the next boot. Therefore, if they use a file located on the ramdisk, you remove the content of this file and any link to it, and the service can become unstable.
That's why in a general way, I don't recommend to dismount the ramdisk at shutdown when the fast startup is enabled.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have been testing a workaround to prevent writing the ramdisk to disk on shutdown, when fast startup is enabled in Windows.
Basically, I get the Task Scheduler to run
C:\Windows\System32\imdisk.exe -D -m R:\
, triggered by the shutdown event.http://i.imgur.com/xuFCxBO.png (screenshot of trigger event configuration)
https://i.imgur.com/Hz9b5zQ.png (screenshot of action configuration)
Seems to be working for me - the R:\ is empty on next boot.
Wondering if anyone can confirm that this actually works?
Last edit: Jeremy Wong 2017-04-01
With the fast startup, the state of all the running services is written to the disk, like any part of the kernel.
This means that they are not restarted at the next boot. Therefore, if they use a file located on the ramdisk, you remove the content of this file and any link to it, and the service can become unstable.
That's why in a general way, I don't recommend to dismount the ramdisk at shutdown when the fast startup is enabled.