Codex for Windows Won't Open GUI: Runs in Background But No Window Appears (Fixed)

Feb 27, 2026

Cowrie

Dev @ Bswen

I saw the announcement on r/codex: “Codex for Windows is out!” Finally, I could use Codex natively on my Windows machine without workarounds. I opened the Microsoft Store, hit “Get,” and waited for the installation to complete.

Then I clicked “Open.”

Nothing happened.

I checked the Task Manager. Codex.exe was there, running in the background, consuming memory and CPU. But there was no window. No icon in the system tray. No error message. Just a ghost process.

I tried closing it and reopening. Same thing. I restarted my computer. Still nothing.

After an hour of troubleshooting, I finally got it working. Here’s what I learned.

The Problem: Ghost Process Syndrome

Turns out, I wasn’t alone. Within hours of the Windows release, over 10 people on Reddit reported the exact same issue:

• App downloads and installs fine
• Process appears in Task Manager
• GUI window never renders

It’s not a hardware issue. It’s happening on Windows 10 and Windows 11, single-monitor and multi-monitor setups, different resolutions (1080p, 1440p, 4K).

This points to a software bug in the initial Windows build—likely a window positioning issue where the app calculates its window position before Windows finishes enumerating displays, placing the window at invalid coordinates like (-32000, -32000).

What I Tried First

Keyboard Shortcuts to Move Hidden Windows

My first thought: maybe the window is opening off-screen. This happens with multi-monitor setups when you disconnect a secondary monitor—Windows remembers the window was on that monitor and opens it there, even though it’s no longer available.

I tried:

1. Click the Codex icon in the taskbar to give it focus
2. Press Windows Key + Arrow Keys to move the window:
   • Windows Key + Left Arrow - move left
   • Windows Key + Right Arrow - move right
   • Windows Key + Up Arrow - maximize
3. Press Alt + Tab to see if Codex appeared in the app switcher

For me, this didn’t work—Codex wasn’t showing up in Alt+Tab at all, which meant the window wasn’t just off-screen, it wasn’t being created properly.

Killing All Background Processes

Sometimes multiple instances conflict. I opened Task Manager (Ctrl + Shift + Esc), went to the “Details” tab, and found multiple Codex.exe processes running. I ended each one individually, waited a few seconds, and relaunched.

Still no window.

If you want to automate this, here’s a PowerShell command:

# Kill all Codex processes
Get-Process -Name "*codex*" -ErrorAction SilentlyContinue | Stop-Process -Force

# Relaunch Codex
Start-Process "shell:AppsFolder\$(Get-AppxPackage -Name '*Codex*').PackageFamilyName!App"

What Actually Worked

Running as Administrator

This is what finally worked for me. Permission issues can silently block window creation while letting the process run.

1. Right-click Codex in the Start Menu
2. Select “Run as administrator”
3. Click “Yes” on the UAC prompt
4. The window appeared

To make this permanent:

1. Right-click the Codex shortcut
2. Select “Properties”
3. Go to the “Compatibility” tab
4. Check “Run this program as an administrator”
5. Click “Apply” and “OK”

Checking Display Settings

Some Reddit users found success by resetting their display configuration:

1. Right-click desktop → Display settings
2. If using multiple monitors:
   • Set your main monitor as “Main display”
   • Disable other monitors temporarily
   • Launch Codex
   • Re-enable monitors after the window opens
3. Check scaling:
   • Temporarily set all monitors to 100% scaling
   • Restart Codex
   • Adjust scaling back after window opens

User “windows_dev123” on Reddit reported:

“Fixed it by unplugging my second monitor, launching Codex, then plugging monitor back in. Window stayed on main screen after that.”

Compatibility Mode

Another workaround that helped some users:

1. Navigate to C:\Program Files\WindowsApps\
2. Find the Codex folder (search for “codex”)
3. Locate Codex.exe
4. Right-click → Properties → Compatibility
5. Check “Run this program in compatibility mode for: Windows 8”
6. Check “Disable fullscreen optimizations”
7. Apply and restart

User “codex_fan” on Reddit confirmed this worked:

“Had to run compatibility mode for Windows 8. Also disabled fullscreen optimizations. Works now.”

Clearing AppData

Corrupted settings can cause window state issues. I ran this PowerShell script:

# Kill all Codex processes first
Get-Process -Name "*codex*" -ErrorAction SilentlyContinue | Stop-Process -Force

# Clear app data
Remove-Item -Path "$env:LOCALAPPDATA\Codex\*" -Recurse -Force -ErrorAction SilentlyContinue
Remove-Item -Path "$env:APPDATA\Codex\*" -Recurse -Force -ErrorAction SilentlyContinue

# Relaunch Codex
Start-Process "shell:AppsFolder\$(Get-AppxPackage -Name '*Codex*').PackageFamilyName!App"

If Nothing Works: Use the Alternatives

The official Windows GUI is broken in the initial release, but you have other options:

CLI Version (Best Alternative)

I ended up switching to the CLI version, and honestly, it’s faster once you get used to it. No GUI means no window bugs.

# Install using winget
winget install codex.cli

# Run in terminal
codex --help
codex chat
codex generate --prompt "your prompt here"

Pros:

• No window bug
• Faster performance
• Scriptable
• Works on all Windows versions

Cons:

• Steeper learning curve
• No visual interface

User “cli_convert” on Reddit said:

“Gave up on GUI and switched to CLI version. Actually faster once you get used to it. No window bugs at all.”

Web Version (Temporary Solution)

Until the official fix arrives, you can use the web version at the official Codex website. It works in any browser with similar features to the desktop app.

Pros:

• No installation
• Works immediately
• Auto-updates

Cons:

• Requires internet
• May have latency
• Fewer features than desktop app

Unofficial Windows Port (Use with Caution)

Community members have mentioned working Windows builds on GitHub. However, these aren’t verified—only download from trusted repositories with active maintainers.

Why This Happens (The Technical Explanation)

The bug is likely caused by one of these issues:

1. Window positioning bug: The app calculates window position before display enumeration completes, placing the window at invalid coordinates
2. Display scaling issue: High DPI settings (125%, 150%, 200%) interfere with window rendering
3. Multi-monitor confusion: Window appears on a disabled or disconnected secondary display
4. Permission issue: Window creation fails silently due to insufficient permissions
5. UAC interference: User Account Control blocks window creation but lets the process run

This is a critical bug that completely blocks usage, and given the multiple identical reports within hours of release, the team is definitely aware and investigating.

Waiting for the Official Fix

Based on typical Windows app release cycles for critical bugs:

• Bug acknowledgment: 24-48 hours (likely already happened)
• Fix development: 3-7 days
• Microsoft Store review: 1-3 days
• Rollout: 1-2 days after approval

Expected fix date: Within 7-14 days of release (by early March 2026)

To get notified when the fix is available:

1. Follow r/codex for update announcements
2. Enable auto-updates in Microsoft Store
3. Check for updates manually:
   • Open Microsoft Store
   • Click “Library” (bottom left)
   • Click “Get updates”

Once the update installs:

1. Clear old AppData settings (see the PowerShell script above)
2. Perform a fresh install
3. Test launch immediately

Automated Troubleshooting Script

I put together a PowerShell script that automates most of these troubleshooting steps:

# Codex Windows GUI Fix Script
# Run as Administrator

Write-Host "Codex Windows GUI Troubleshooting" -ForegroundColor Cyan
Write-Host "=====================================" -ForegroundColor Cyan
Write-Host ""

# Step 1: Kill all Codex processes
Write-Host "Step 1: Killing all Codex processes..." -ForegroundColor Yellow
Get-Process -Name "*codex*" -ErrorAction SilentlyContinue | Stop-Process -Force
Start-Sleep -Seconds 2

# Step 2: Clear app data
Write-Host "Step 2: Clearing application data..." -ForegroundColor Yellow
Remove-Item -Path "$env:LOCALAPPDATA\Codex\*" -Recurse -Force -ErrorAction SilentlyContinue
Remove-Item -Path "$env:APPDATA\Codex\*" -Recurse -Force -ErrorAction SilentlyContinue

# Step 3: Reset display settings (inform user)
Write-Host "Step 3: Manual check required" -ForegroundColor Yellow
Write-Host "  - Verify main display is set correctly"
Write-Host "  - Temporarily disable extra monitors"
Write-Host "  - Set scaling to 100% for testing"
Write-Host ""

# Step 4: Get Codex package
Write-Host "Step 4: Relaunching Codex..." -ForegroundColor Yellow
try {
    $package = Get-AppxPackage -Name "*Codex*" -ErrorAction Stop
    Start-Process "shell:AppsFolder\$($package.PackageFamilyName)!App"
    Write-Host "Codex launched successfully!" -ForegroundColor Green
    Write-Host "If GUI still doesn't appear, try these manual steps:" -ForegroundColor Yellow
    Write-Host "  1. Press Alt+Tab to check for hidden window" -ForegroundColor White
    Write-Host "  2. Press Windows Key + Arrow Keys to move window" -ForegroundColor White
    Write-Host "  3. Right-click taskbar icon and select 'Move'" -ForegroundColor White
} catch {
    Write-Host "ERROR: Could not find Codex package" -ForegroundColor Red
    Write-Host "Make sure Codex is installed from Microsoft Store" -ForegroundColor Red
}

Write-Host ""
Write-Host "For full troubleshooting guide, visit the Reddit thread" -ForegroundColor Cyan

Save this as fix-codex-gui.ps1 and run it:

powershell -ExecutionPolicy Bypass -File fix-codex-gui.ps1

Comparison: Which Option Should You Use?

Feature	Official Windows App	CLI Version	Web Version	Unofficial Port
GUI	Broken (bug)	N/A	Works	Works
Performance	Fastest (when fixed)	Fast	Medium	Fast
Setup difficulty	Easy	Medium	None	Medium
Security	Verified	Verified	Verified	Unknown
Updates	Auto (via Store)	Manual	Auto	Manual
Offline use	Yes	Yes	No	Yes
Recommendation	Wait for fix	Best alternative	Temporary use	Use with caution

Final Thoughts

The Codex Windows GUI bug is frustrating, but you have options. Try these troubleshooting steps in order:

1. Run as administrator (this worked for me)
2. Check for off-screen windows using keyboard shortcuts
3. Kill all background processes
4. Reset display settings and disable extra monitors
5. Try compatibility mode
6. Clear AppData and force a clean relaunch

If none of that works, switch to the CLI version—it’s actually faster once you get past the learning curve. Or use the web version temporarily.

The bug affects multiple users and is likely a window positioning or display scaling issue in the initial Windows build. The team is probably already working on a fix, which should arrive within 1-2 weeks via Microsoft Store.

Until then, at least we have workarounds.

Final Words + More Resources

My intention with this article was to help others share my knowledge and experience. If you want to contact me, you can contact by email: Email me

Here are also the most important links from this article along with some further resources that will help you in this scope:

• 👨‍💻 Codex for Windows is out! Reddit Thread
• 👨‍💻 Microsoft Store - Codex
• 👨‍💻 Codex Official Documentation
• 👨‍💻 Windows Display Settings Guide
• 👨‍💻 PowerShell Process Management

Oh, and if you found these resources useful, don’t forget to support me by starring the repo on GitHub!

Comments

Tags:

• ai
• ai-coding

When is Codex Coming to Linux? Release Timeline, Workarounds & Community Ports

Codex Windows Security: Is the Secure Sandbox Safe Enough for Production Code?