The original installation guide was woefully underdeveloped and a bit confusing. This new guide more thoroughly looks at how to install a second instance of Radarr and provides clear examples for what commands to run, what paths to use, and what software to download.

Installing-Multiple-Instances-of-Radarr-on-Windows.md

@@ -0,0 +1,45 @@
+## Introduction ##
+This guide will show you how to run multiple instances of Radarr on Windows using only one base installation. This guide was put together using Windows 10; if you are using a previous version of Windows (7, 8, etc.) you may need to adjust some things. This guide also assumes that you have installed Radarr to the default directory, and your second instance of Radarr will be called Radarr-4K. Feel free to change things to fit your own installations, though.
+
+### Prerequisites ###
+* You must have Radarr already installed. It is _highly_ recommended that you use [the latest installer.exe file](https://github.com/Radarr/Radarr/releases).
+* You must have [NSSM (Non-Sucking Service Manager)](http://nssm.cc) installed. To install, download the latest release (2.24 at the time of writing) and copy either the 32-bit or 64-bit nssm.exe file to C:/windows/system32. (If you aren't sure if you have a 32-bit or 64-bit system, check Settings > System > About > System type.)
+
+## Configuring Radarr ##
+1) Open a Command Prompt administrator window. (To run as an admin, right click on the Command Prompt icon and choose "Run as administrator.")
+2) If Radarr is running, stop the service by running `nssm stop Radarr` in Command Prompt.
+3) Now we have to edit the existing Radarr instance to explicitly point to its data directory. The default command is as follows:
+
+    `sc config Radarr binpath= "C:\ProgramData\Radarr\bin\Radarr.exe -data=C:\ProgramData\Radarr"`
+
+This command tells the original instance of Radarr to explicitly use C:\ProgramData\Radarr for its data directory. If you didn't use the default Radarr install, or if your data folder is somewhere else, you may have to change your paths here.
+
+## Creating Radarr-4K ##
+4) Create a new folder where you'd like Radarr-4K to live. I prefer all my instances in the same place, so my new folder is C:\ProgramData\Radarr-4K.
+5) Back in Command Prompt, create the new Radarr-4K service using `nssm install Radarr-4K`. A popup window will open where you can type your parameters for the new instance. For this example, we will use the following:
+    * **Path:** C:\ProgramData\Radarr\bin\Radarr.exe
+    * **Startup directory:** C:\ProgramData\Radarr\bin
+    * **Arguments:** -data=C:\ProgramData\Radarr-4K
+
+Note that **Arguments** points to the _new_ folder created in step 4. This is crucial, as it keeps all the data files from both instances in separate locations.
+
+6) Click _Install service_. The window should close and the service will now be available to run.
+
+## Configuring Radarr-4K ##
+7) Next we'll need to configure the new service to use its own port, the entry for which is in a config.xml file. This file is created when you first run the service, so start up Radarr-4K with `nssm start Radarr-4K` in Command Prompt. 
+
+8) Navigate to your new data directory (C:\ProgramData\Radarr-4K in this case) to see if the config.xml file is there. If it is, go ahead and stop Radarr-4K with `nssm stop Radarr-4K`. (Don't worry, we'll be starting it back up in a second.)
+
+9) Open the config.xml file using your preferred text editor. There should only be a handful of lines, but the important one is `<Port>7878</Port>`.
+
+Since the first Radarr instance will occupy port 7878, the second instance must use another available port, like 7879 or 17878. I prefer the latter, so I changed the line to `<Port>17878</Port>`. Don't change anything else.
+
+9) After you've set a new port, save the file and close your text editor.
+7) With both services fully installed and properly configured, you can now start them:
+    * `nssm start Radarr` (accessible via http://ip_address:7878)
+    * `nssm start Radarr-4K` (accessible via http://ip_address:17878)
+
+## Notes ##
+* Though this tutorial was tested using Command Prompt, it should work with Windows Terminal as well. But, if you're feeling cautious, just go with Command Prompt.
+* A previous version of this installation guide encouraged users to copy Radarr's config.xml file to Radarr-4K's data directory. However, you'll run into trouble with this method, especially if you have authentication enabled. I'd recommend starting with a clean config.xml file, created when you start the service for the first time (Step 7).
+* If one Radarr instance is updated, both instances will shutdown and only the updated one will start again. To fix this, you will have to manually start the other instance, or you may want to look into using [this script by reloxx](https://www.reddit.com/r/radarr/comments/hou8ro/winps_multiple_instances_restarter/) to address the problem until an official solution is found.

Multiple-Instances-on-Windows.md

@@ -1,24 +0,0 @@
-**NOTE:** This way, if one instance installs an update, both instances will shutdown and only the one with the update will start up again. The update closes all radarr.exe and radarr.console.exe. You have to write a script which checks both instances in an interval and start the one which is down.
-
-# Install Multiple Instances of Radarr on Windows #
-This guide will show you how to have multiple instances running on Windows utilizing only one installation of Radarr.
-
-## Prerequisites ##
-
-* Current installation of Radarr on windows
-* NSSM
-
-## Steps ##
-
-1) Open Services and stop Radarr service if running.
-2) Run CMD as administrator.
-3) Add an argument to the existing Radarr service to explicitly point to the current AppData directory
-
-    `sc config [Radarr Service] binpath=currentBinPath -data=currentRadarrAppData`
-
-4) Copy your current config.xml and paste it into the new AppData folder.
-5) Edit your new config.xml to change the port. Note the service will not run if you use the same port as the previous install.
-6) Start both services.
-
-### Author Note ###
-When testing this out I did not copy the config.xml. It was automatically created during a failed attempt at getting this running. A clean config.xml would be preferable which you can most likely achieve by running the service at step 4 to auto-generate the config files and then stopping the service. I cannot however confirm this to work as its not how I accomplished this.