Automatic1111 Not Launching Fix: Troubleshooting Guide

Updated June 2026

Your Automatic1111 WebUI isn’t launching. This guide offers direct solutions to get your Stable Diffusion environment up and running quickly.

Initial Checks: The Basics

Your Automatic1111 WebUI isn’t launching. This guide offers direct solutions to get your Stable Diffusion environment up and running quickly.

Why this happens: Sometimes the simplest issues prevent launch, often overlooked during frustration.

1. Restart Your Computer: A fresh start can resolve temporary system conflicts or memory issues.
2. Verify Internet Connection: While Automatic1111 runs locally, initial setup and updates require an active connection. Ensure your internet is stable.
3. Check for Disk Space: Stable Diffusion models and dependencies require significant disk space. Ensure you have at least 20-30GB free on your drive.
4. Run webui-user.bat as Administrator: Right-click the batch file and select “Run as administrator” to avoid permission-related blocks.

Understanding Console Error Messages

Why this happens: When Automatic1111 fails to launch, the command prompt window (console) often displays critical error messages detailing the problem. Ignoring these messages prevents proper diagnosis. Common issues include missing dependencies or Python version conflicts.

1. Read the Console Output: When you run webui-user.bat, a black command prompt window appears. If it closes quickly or displays text, read it carefully. The last few lines usually contain the error.
2. Take a Screenshot or Copy Text: If the window closes too fast, run the .bat file again and quickly screenshot or copy the error. You might need to add PAUSE at the end of your webui-user.bat temporarily to keep the window open.
3. Search the Error Message: Copy exact phrases like "ModuleNotFoundError", "CUDA error", or "Python was not found" into a search engine. This often leads directly to solutions.

Python and Git Configuration Issues

Why this happens: Automatic1111 relies heavily on specific versions of Python and a correctly installed Git. Incorrect versions, corrupted installations, or improper system PATH configurations are common culprits.

1. Verify Python Version: Automatic1111 typically requires Python 3.10.6.
   • Open Command Prompt (Windows key + R, type cmd, press Enter).
   • Type python --version and press Enter.
   • If it’s not 3.10.x, or if it says “Python was not found”: Uninstall any incorrect Python versions. Download and install Python 3.10.6 from python.org. Crucially, during installation, check “Add Python to PATH.”
2. Verify Git Installation:
   • In Command Prompt, type git --version.
   • If it says "git is not recognized": Download and install Git from git-scm.com. During installation, ensure “Git from the command line and also from 3rd-party software” is selected.
3. Check webui-user.bat: Ensure python_cmd isn’t incorrectly set or pointing to a wrong path if you’ve manually edited it.

Graphics Card (GPU) and VRAM Problems

Why this happens: Stable Diffusion is resource-intensive, particularly on your graphics card’s VRAM. Outdated GPU drivers, insufficient VRAM, or conflicts with NVIDIA’s CUDA toolkit can prevent launch or cause immediate crashes.

1. Update GPU Drivers: Outdated drivers are a frequent cause of instability.
   • NVIDIA: Download the latest drivers from nvidia.com/drivers. Perform a clean installation.
   • AMD: Download the latest Adrenalin Software from amd.com/en/support.
2. Apply VRAM Optimization Flags: If you have less than 8GB of VRAM, you might need to optimize.
   • Edit your webui-user.bat file. Right-click, select “Edit”.
   • Find the line set COMMANDLINE_ARGS=.
   • Add the following flags inside the quotes:
   • For 6GB VRAM: set COMMANDLINE_ARGS=--medvram
   • For 4GB VRAM: set COMMANDLINE_ARGS=--lowvram
   • You can also combine with --xformers for further optimization if installed (e.g., set COMMANDLINE_ARGS=--lowvram --xformers).
   • Save the file and try launching again.
3. CUDA Toolkit (NVIDIA only): While Automatic1111 typically handles CUDA versions, ensure your NVIDIA drivers are compatible. A clean driver install often resolves this.

Corrupted Installation or Extensions

Why this happens: Files can become corrupted during download or installation. Incompatible or faulty extensions are also a common cause of startup failures after initial setup.

1. Update Automatic1111: Open Command Prompt in your Automatic1111 directory and run git pull. This updates your local repository to the latest version.
2. Disable Extensions: If Automatic1111 stopped working after installing a new extension, this is a likely culprit.
   • Navigate to your stable-diffusion-webui/extensions folder.
   • Move the problematic extension’s folder out of extensions (e.g., to a temporary folder) or rename it (e.g., _extension_name).
   • Try launching again. If it works, the extension was the issue. Reintroduce extensions one by one to find the specific problem.
3. Clean Reinstallation (Last Resort):
   • Backup any custom models, VAEs, LoRAs, or embeddings from your models folder.
   • Delete the entire stable-diffusion-webui folder.
   • Follow the official installation guide from the Automatic1111 GitHub page to reinstall from scratch.

Diagnostic checklist before you escalate

Most web-app failures can be narrowed to service status, one account session, browser data, an extension, or the network. Test those boundaries in order rather than clearing everything at once. A private window and a second network are especially useful because they change one layer without altering your account data.

1. Check the provider’s official status page before changing local settings.
2. Hard-refresh, start a new session, and test a private browser window.
3. Disable content blockers, privacy extensions, VPN, proxy, and secure DNS temporarily.
4. Compare another browser, device, and network to locate the failing boundary.
5. Record timestamps, error text, and the smallest reproducible sequence for support.

Verify the recovery across session and network boundaries

When Automatic1111 Not Launching starts working, repeat the original action in a fresh tab and then in the normal browser profile. Confirm that buttons, uploads, saved history, and live updates behave normally instead of only rendering the first screen. If private mode works but the regular profile fails, continue isolating cookies and extensions rather than declaring the service fixed.

Restore extensions, VPN, proxy, secure DNS, and content filtering one at a time. Reload after each change. This controlled restoration identifies the incompatible layer and prevents the common outcome where everything is disabled permanently. Finish by testing one other device or network so you know whether the recovery belongs to the account, the device, or the connection.

• The original action succeeds twice in a fresh session.
• The normal browser profile works after cleanup.
• Extensions and network controls are restored individually.
• Saved data and account history remain available.
• A second device or network confirms the result.

Keep a short note of the working configuration and the date of the test. Products, models, browser versions, limits, and safety policies change over time, so a previously successful workaround may later become obsolete. Prefer current official documentation over old forum instructions, and reverse temporary diagnostic changes once testing is complete. This gives you a reliable baseline without leaving extensions disabled, security controls weakened, or experimental settings enabled indefinitely. Recheck the baseline after major updates before assuming an older failure has returned for the same reason.

When none of the fixes work

Repeat the smallest failing action once and record the exact local time and time zone. Note the product, model or feature, account plan, browser or app version, operating system, and whether the same action works in a private window, on another device, or on another network. This evidence is much more useful than saying the tool is “still broken.”

Use the provider’s official support channel. Include a screenshot with sensitive information removed and list the steps already tested. For developer tools, add sanitized request and response details, correlation IDs, and SDK versions. Never send passwords, one-time codes, API keys, session cookies, private repository contents, or complete payment information.

FAQ

Q: My console window closes immediately. How do I see the error?

A: Edit webui-user.bat. Add PAUSE on a new line at the very end of the file, then save and run it. The window will stay open until you press a key.

Q: Do I need an internet connection to run Automatic1111 after installation?

A: No, Automatic1111 runs locally on your computer. An internet connection is only needed for initial setup, updates, and downloading new models or extensions.

Q: Can I use Python 3.11 or newer?

A: While Automatic1111 sometimes catches up, it’s generally recommended to stick with the officially supported Python 3.10.x version (specifically 3.10.6) to avoid compatibility issues. Newer versions can introduce breaking changes.

By systematically checking common issues like Python/Git setup, GPU drivers, VRAM, and isolating problematic extensions, you can effectively fix Automatic1111 not launching and get back to generating images.

Bottom line: Work from the least disruptive test to the most specific one. Confirm service health, isolate session and network variables, then escalate with clean evidence instead of repeating the same failing action.