windows install tips

Windows installation tips for the native wrapper

Language: English | Korean

This page collects common Windows friction points for installing Ghost-ALICE OS. Use Team onboarding for the quick copy-and-run install path.

Contents

• 0. Scope
• 1. Recommended Environment
• 2. Open A Windows Terminal
• 3. Run The Windows Wrapper
• 4. When Localized Output Looks Wrong
• 5. FAQ
  • Do I need Git Bash?
  • Do I need to install Python first?
  • Should I use PowerShell directly?
  • Must I always run as administrator?

0. Scope

This page covers only the items below.

• How to use the native Windows wrapper as the public Windows install entrypoint
• How to avoid path and administrator-terminal confusion
• How to keep Windows commands on the same long-flag surface as install.sh
• How to work around localized output issues without changing project files

1. Recommended Environment

The recommended Windows setup is below.

Item	Recommended	Reason
Shell	Command Prompt or PowerShell	Built into normal Windows environments
Terminal app	Windows Terminal, Command Prompt, or PowerShell	No extra Git Bash dependency for installing Ghost-ALICE
Install entrypoint	.\install.cmd	Native wrapper that forwards the same long flags to the installer

Most users do not need to install Python first. If Python 3.11+ is missing, the installer tries the supported preparation path and reports what remains.

2. Open A Windows Terminal

Open Command Prompt, PowerShell, or Windows Terminal, then move to the desired folder.

cd %USERPROFILE%\Desktop

Avoid running install commands from a random administrator terminal. Normal user permissions are enough for most Ghost-ALICE install, update, status, and uninstall tasks.

3. Run The Windows Wrapper

Use the native wrapper on Windows.

git clone https://github.com/AidALL/ghost-alice.git %USERPROFILE%\ghost-alice
cd %USERPROFILE%\ghost-alice
.\install.cmd --addon autopilot

Common follow-up commands use the same long-flag surface.

.\install.cmd --status
.\install.cmd --doctor
.\install.cmd --platform codex
.\install.cmd --visibility dynamic
.\install.cmd --uninstall

For source updates, use the safe updater first.

cd %USERPROFILE%\ghost-alice
.\install.cmd --update-source

If Git reports a conflict, stop and read Install troubleshooting before running the installer again.

4. When Localized Output Looks Wrong

Localized Windows console output can look garbled when the terminal encoding is not aligned. First try Windows Terminal or a fresh Command Prompt before editing files.

cd %USERPROFILE%\ghost-alice
.\install.cmd --status

If a file truly must be resaved in an editor, confirm that it uses a UTF-8 family encoding first. Local encoding edits can become shared project changes, so do not commit them before confirming the cause.

5. FAQ

Do I need Git Bash?

No. Git Bash remains a usable optional shell if it is already part of your workflow, but it is not the Windows default install requirement for Ghost-ALICE.

Do I need to install Python first?

Usually no. If the installer cannot find Python 3.11+, it tries to prepare it automatically when possible. If automatic preparation fails, the installer shows the install command to run manually.

Should I use PowerShell directly?

Use .\install.cmd for public instructions. It chooses the available PowerShell host and forwards arguments with the same long flag spelling shown in the docs.

Must I always run as administrator?

No. Normal permissions are enough for most installation and update work. Open a separate administrator terminal only for system-wide changes or UAC-required cases.