Unable to start instances following update to "Callisto" v2.5

[legg1999]

Note - If you do not fill in every section below, your post won’t be answered - you must provide the steps you have followed so far and the actions you’ve already taken. Make sure to remove this notice from your post too.

OS Name/Version: Windows 11 Pro on x86_64

Product Name/Version: AMP ‘Callisto’ v2.5

Problem Description: Following update to ‘Callisto’ v2.5, when I try to start my instances, i am prompted with the message in the attached photo.

If you're sharing console output, logs, or commands you have run, please make sure to use code tags 
(3x backticks for blocks, 1x backtick for a single line) to help make posts readable. This also
provides syntax highlighting.

Steps to reproduce:

• Step 1 Have instances running
• Step 2 Update from AMP ‘Decadeus’ v2.4.8.0 to ‘Callisto’ v2.5
• Step 3 Attempt to open AMP and start instances back up

Actions taken to resolve so far:

[ssfdre38]

put the instance in a docker

[legg1999]

I’ve already tried this, pops up the same response.

[ssfdre38]

can you show the full log of this instance and what game is it?

[Mike]

You’ve switched AMP at some point between running as a service and not running as a service. Shut down ADS and make sure it’s a service in the instance manager GUI app.

[legg1999]

How do I go about doing this? I have only recent begun hosting servers using the AMP service, and I’m not sure how to do this.

[Mike]

Open a command prompt and run:

ampinstmgr stopall

Then open the AMP Instance Manager GUI application, and select “No” when it asks you if you want to start AMP.

Then right click the ADS01 instance and select “Install Service” - once that’s done, right click it again and start it.