![hqplayer shell replacement no sound hqplayer shell replacement no sound](https://www.lifewire.com/thmb/K5SdZPZFzr7glwo_qe-jvwxq3z8=/1137x853/smart/filters:no_upscale()/SoundSettingsannotated-1d1eae2f17e946ef87867d4f051f7526.jpg)
It will be started together with the entire windows system and all its proccesses, threads and tasks in the background.īut if you entirely replace the windows shell with Roon, only Roon and nothing else will be launched after logon.
![hqplayer shell replacement no sound hqplayer shell replacement no sound](https://img.bidorbuy.co.za/image/fetch/c_limit,h_448,q_auto:eco,w_448/https://imgaz3.staticbg.com/images/oaupload/banggood/images/93/5B/d95711df-a554-44d0-96cb-16aa4c0dc328.jpg)
So what's the difference? If you put in your Autostart Folder, Roon will just get loaded aside from the graphical user interface. Let's say you mainly use Roon as your media player, wouldn't it be convenient having Roon launching automatically right after logon? Of course it would be convenient, but you could also simply put it in the Autostart folder right. So a shell replacement is exactly what the name implies, we're going to replace the shell with something different. It looks almost identical with the MS-DOS command prompt a few of you might still remember from days long gone. On those setups you have no graphical user interface, all you will see after the logon is a command prompt window. In the Windows Server world the shell can also have a different appearance, namely on Windows Server systems which are running in Server Core (core mode).
![hqplayer shell replacement no sound hqplayer shell replacement no sound](https://diyaudioheaven.files.wordpress.com/2019/03/dsdprocessor.jpg)
Of course there is a lot happening, many process and threads are started to present you the windows desktop and load all the features and functions of Windows. So basically this is the entire windows environment which gets loaded after the login. It is your desktop, your start menu, all the basic functions you can see right after you log in to your windows machine. A shell in the windows world is what you already know as your desktop environment or GUI (graphical user interface). The ServiceTool in AO 3.00 now offers more than 35 different variations of the shell replacement, so why do we put so much effort and time into this little feature? And what after all is a shell replacement, and why should you use it in your setup? A few years ago we introduced the "shell replacement" feature in our ServiceTool and since then we put a lot and continous effort into it.