Since some time, imdisk.exe and the ImDiskCreateDeviceEx function are able to start the required services if they are not running.
So, is there any reason to keep all the services on auto-start?
Of course, the imdisk driver should be always started, for instance for the case where virtual disks have been registered through imdisk.exe -P, but what about awealloc and imdsksvc?
Auto-start services
Started by
v77
, Oct 04 2016 04:48 PM
1 reply to this topic
#1
Posted 04 October 2016 - 04:48 PM
#2
Posted 04 October 2016 - 06:49 PM
It has evolved the other way around actually. Originally, imdisk.exe etc auto-started driver and service when requested to create a new ImDisk drive. Changing the setup .inf to installing them with auto-start settings is a relatively recent change in that perspective.
It was changed in that way so that users would not need administrative privileges to create ImDisk drives, since loading drivers and services needs administrative privileges.
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users