This is what I was thinking. But having this way of grouping the 3 (core, remote, audio device) it is easier from the user point of view.
If drag and drop Roon to App folder and open, first is going to ask for remote connection, if it connects to another core on the network I do not think that is creating any database so @Rugby is right. But the potentially Roon Core is there with the Roon app
Itās still installed, just not configured.
If roon client is running and you go to:
Settings -> General -> XDisconnect
You get a window similar to thisā¦
Itās not an installā¦ itās a configuration. It simply configures the ~/Users/<yourusername>/Library/Roon/ folder to be used as a Core. Just as RoonServer configures a ~/Users/<yourusername>/Library/RoonServer/ folder.
Since the user wants to stop seeing the Core that was set up using the Roon probably by mistakeā¦ He should be able to simply remove, rename to Roon.old, or move to the trash, or put it anywhere but in the Library folder and then restart the Roon app. All the settings and configs should be on his ROCK server as the laptop is merely a remoteā¦ it should just contain cache folders and nothing important to the server.
But please stop saying he installed Roon server and he needs to only install clientā¦ the word install is just confusing the matterā¦ its a config!!! there is an installer for windows, and itās drag and drop for MacOS, but if I recall correctly, windows doesnāt ask if you just want client during the installā¦ it just tells you itās installing Roon.
I think this is the most accurate way to explain
You can see the roon app startup as a install or config. So there is not going to be a database if you select another core 
@RobOK shutting down the core made iPhone running roon app to ask for the core but the iPhone did not see when it got back online. Looks like what you are describing. Iāll retry to replicate this tommorow
I disagreeā¦
Roon Legacy on another computer and Roon (Full) core running on the current local machineā¦
Now I want to get rid of the local coreā¦
It will make a new Roon folder.
Roon should open to this:
No Reinstall requiredā¦ just rename, then delete the Roon folder.
I like to Tinker. 
EDIT: NOTE, windows may be different, but OP is on a macbook.
Just to follow roon terminology, not install or config but āSet upā 
Shots fired. Man down. 
Good Call.
Well, I guess people donāt change cores very often, and the exact process gets forgotten.
Thanks all for the engaging conversations. I have been offline a bit, will reply tomorrow with more details!
Okay problem resolved. The short answer was to connect to the unwanted laptop core and log out (thanks @Rugby !). Then it stops broadcasting as an available Core.
The reason why different posters have different experiences in part is that I have two licenses. So activating my ROCK did not deactivate my laptop core. For many people that happens automatically in the background.
I think I mentioned this was an unusual case to begin with, normally my client stays connected to my desired ROCK core. It was only coming up when ROCK was being restarted or some other connection issue.
Thanks all! Enjoy the music!
Hi!
Since Iāve been referenced, I thought Iād pop by. I went through and spent an hour or so doing tests and screen shots about the installation process, but, I will put that in a new thread linked below (when I get that thread setup) as it really has nothing to do with the OPās request. So, that is where I want to start, the OPās request.
Iāve already sent him a PM on how to resolve, but, I wanted to explain further. Rob also has multiple licenses so that can affect things. As I mention later, Roon displays different things in different environments.
Iām going to give an example as that might clarify things. Lets say there is a house hold with two users and both have laptops (could be any PC) and we call them LaptopA and LaptopB. the Users install Roon as a Core on LaptopA and then install Roon as a remote or client on LaptopB.
Now, during the install, the LaptopA install will get either an option to Find a Roon Core or to be a Roon Core screen. Because there are no other Roon Coreās on the network, at this time, the only option is to āUse this PCā. However, when LaptopB goes to install Roon, they will see a screen like below:
Choosing to Connect to an existing server sets that Roon install up as a Remote Control which means some processes are not setup and it doesnāt broadcast itself as a core. It is common in Roon that screen options will change depending on the specific environment.
All is well and after awhile, they decide to invest in a ROCK NUC. The users setup the ROCK NUC, migrates the library, moves the authorization from LaptopA to the ROCK NUC, and connects both LaptopA and LaptopB to the ROCK NUC so that they are both running as a remote to the ROCK NUCās Core.
Now, we get to the OPs question. The user on LaptopB notices that when the user of LaptopA (former core) is running Roon, they are seeing LaptopA as a valid Core choice to connect to. This is what the OP wanted to stop, LaptopA showing up anymore as a Core option to other Roon Remotes while Roon is running on LaptopA as a Roon Remote.
There are two options (and will go into detail more in the other thread); the right one depends upon what you want.
A. Remove all old aspects of the Roon Core, i.e. databases, so that it is a lean/clean remote.
This is where uninstall/re-install comes from. Depending on how big the library was, it can free up several gigabytes of space. It is fast and gets the job done, with the understanding that during the uninstall the user removes all settings and databases (an option in a Windows uninstall, not sure about Mac).
Now, yes, for those wanting to dive into the base files, there maybe other ways, but, this is the cleanest for most non-technical Roon users.
B. Donāt care about the cleaning unused files out; and just stop the Core from showing up
Connect a remote to LaptopAās Core and on Settings/General āLogOutā. This should stop LaptopAās Core from broadcasting itself as a Core to other remotes.
In the end, LaptopA needs to be logged out from Roon Central, which happens with either option, which is why they both work.
Other Thread:
Installation Discussion with Screenshots (link coming soon ā¢)
