Windows has a habit of making life difficult for AMP by ignoring its requests to not cache certain AMP components, meaning that things can often get a little rocky after an update.
The usual indicator that this has happened is “Method not found” exceptions after an update.
If this happens to you - go through the following steps:
Follow these steps in the exact order given, do not skip any steps,
- Stop AMP fully by running
ampinstmgr stopall in a new command prompt.
- Use Task Manager to make sure all AMP.exe and AMPService.exe processes are stopped.
- Download a fresh copy of AMPSetup.msi - and run it in Repair mode.
- Reboot the system
- Run
ampinstmgr upgradeall in a command prompt.
After this, everything should be working fine.
6 Likes
You should probably pin this so other people can see it. otherwise its going to be buried
It’s been flagged as a ‘wiki’ post 
so it’ll have some distinction.
Oh is that why i’m able to edit your message?
Something to add to this post.
AMP isn’t working and just showing a Blank Login Screen.
Sometimes, AMP starts before a service called NETWORK SERVICE is started and will not allow ads01 to not start. There is an easy fix for that.
In the start menu, you can search for services.msc and then you will look for AMP - ADS01 and then right click on it to get to the properties and then you will see a drop down menu called Startup Type.
Now you will need to change that from Automatic to Automatic (Delay Start) and then press Stop and wait a few seconds and press Start and then try again. Image below to show what it should look like
If its still having problems after this, Try and restart your Windows System and see if it will work.
2 Likes
