PATH problems

• If PawOS reports a tool "works in PowerShell but not Command Prompt" (or vice versa), your PATH genuinely differs between the two shells — this is a real environment inconsistency, not a PawOS bug.
• A PATH change may need a fresh terminal/app restart outside PawOS to take effect for tools not launched by PawOS itself.
• If elevation was declined, PawOS wrote to your User-scope PATH instead of Machine-scope — ask again and choose to retry elevated if you need it system-wide.

How it works

What you see

• What to check for common situations: sign-in, commands, installs, PATH, connections, usage limits, payments, previews and builds.
• What PawOS already checks for you, and what to gather before trying again.

What PawOS does

• PawOS reports problems in the task view, Work Records, connection status and check results.
• For commands, installs, builds and tests it shows the real output.

Permissions

• Never bypass permission questions or run unsafe commands to get past a problem.
• If a plan, connection permission, local permission or administrator approval is missing, retrying won’t help until that changes.

Records

• Useful details: the task, what it was doing, the command and its result, file paths, check results, and a screenshot if something looks wrong.

Good to know

• Some fixes happen outside PawOS — in a service’s dashboard, your system settings or your account.