The ImDisk Toolkit is self-sufficient: it installs the driver if needed. There is not two installations to do. And you're wrong about the setup: the setup GUI is not displayed with IMDISK_SILENT_SETUP: this is a complete silent installation (if you use the value 2). This is one of the innovations of the current version... Of course, you need to define an environment variable, but it's not much less user-friendly than using something like a command line switch. About the driver (the package of Olof), along with the environment variable, you also need to add the -y switch to avoid a dialog box from the extractor (not the installer). But in fact, this is still not enough to have a silent installation in any cases, because if a reboot is needed, you will be prompted for that. This case is avoided with ImDisk Toolkit if you use the value 2 for the environment variable. In fact, it is because of the used value in the command rundll32 setupapi.dll,InstallHinfSection DefaultInstall 132 .\imdisk.inf You have to change 132 by 128 to make a complete silent install, as described here. That said, even as the author of the Toolkit, I cannot provide a silent package that requires no manipulation. So, your project is still interesting, but it would be more simple for you to use the integrated solution of the installer of the Toolkit. For information, if you need to extract the content of the installation package, the installer of setup.exe is started if there is an object named "driver" in the same directory (a file or a directory). But as I said, the GUI is not displayed if you use the environment variable. With that, you keep the possibility to rebuild instantly the previous ramdisks if parameters are found in the registry. This is another newness of this version.