v77 - 2016-10-21

I just found an interesting issue. Since the version 20160726, RamDiskUI creates the RamDyn process in the session 0 through a temporary service. The purpose was to avoid that it is killed before the data synchronization was done by the ImDiskTk-svc service.
But as the fast startup feature of Windows writes the whole session 0 onto the hard drive, this means that the dynamic ramdisks are now saved, like the static ramdisks.

Before the version 20160726, this was also the case for ramdisks created after a full restart, because RamDyn is created by the ImDiskRD service.
For the case where RamDyn was running in the user session, the ramdisk was recreated after a full restart, and disappeared with a shutdown/start because the shutdown kills the processes of the user's session, and the fast startup does not restart the services.

Therefore, even if the situation is now more consistent from the user's point of view because RamDiskUI always puts RamDyn in session 0, I will have to change the text and the tests of the related dialog box.

This fast startup feature is really terrible for this kind of tool...