Update Failure with Application Deployment - AMP configuration failed with return code 69632

Technical Support
,
1

System Information

Field Value
Operating System Windows - Windows 10 Home on x86_64
Product AMPService ‘Phobos’ v2.6.2.0 (Mainline)
Virtualization None
Application Application Deployment
Module ADSModule
Running in Container No
Current State Indeterminate

Problem Description

Issue

AMP no longer lets me create new instances.
Have updated to most recent version, Same issue, Ran installer, Same issue

Error log

Configuration Failed: AMP configuration failed with return code 69632
Create Instance Failed: AMP configuration failed with return code 69632

Reproduction Steps

  • Press Create instance
  • Click any option for game, Fill out remaining information
  • Press new instance
  • Error above
2

Hey @Eddie_Green,

I saw your post and wanted to help troubleshoot your AMP instance creation failure in Phobos v2.6.2.0. The error “AMP configuration failed with return code 69632” suggests a deeper issue with AMP’s setup. Here are some steps to try:

Steps to Fix:

  1. Check AMP Logs for More Details – Look at AMP/logs to see if there are additional errors beyond the return code.
  2. Run AMP as Administrator – If AMP lacks permissions, try running it with elevated privileges.
  3. Verify AMP Installation Path – Ensure AMP is installed in a valid directory without spaces or special characters.
  4. Check Firewall & Antivirus Interference – Some security software may block AMP’s configuration process. Try temporarily disabling them.
  5. Reinstall AMP Cleanly – Uninstall AMP, delete its configuration files, and reinstall it from scratch.
  6. Check for Known Issues – Some users have reported similar errors. You can find troubleshooting steps here and here.

A Few Questions to Help Troubleshoot:

  • Does the AMP log show any additional details beyond the return code?
  • Have you tried running AMP as Administrator?
  • Is AMP installed in a standard directory (e.g., C:\AMP)?

Let me know if any of these steps help or if you can provide more details—I’d be happy to troubleshoot further! :rocket:

3

I suspect you need to stop “trying to help” - necro-ing 3 year old posts and giving bad advice (AMP should never be run as Administrator) isn’t helping. Just copying and pasting whatever rubbish an AI gave you also isn’t going to achieve much

4

Hey @Greelan,
Appreciate the feedback. My goal is just to help out where I can—like many others, I’ve paid for AMP and want to see it work as smoothly as possible. I understand the frustration when issues go unresolved, and I know everyone wants solid support. I’ll make sure to be mindful of reviving older posts and definitely avoid suggesting running AMP as Administrator moving forward. Thanks for pointing that out!