The Prelude: An issue that seems trivial but is extremely frustrating in practice

The user's PowerShell prompt was a mess — Oh-My-Posh was installed, but theme loading always reported a 'file not found' warning. Worse yet, he wanted three key features: Git branch display, Python version display, and command execution time, but many aesthetically pleasing themes were incomplete.

I took over this chaos, determined to fix it from the root and abstract the process into a reusable automation script.

Problem Diagnosis: The Hidden Pitfalls of the Windows Store Version of Oh-My-Posh

Symptoms

[WARN] Theme 'powerlevel10k_rainbow' not found...

The themes exist on the system but Oh-My-Posh just can't find them.

Root Cause

Oh-My-Posh installed from the Windows Store stores themes in this annoying location:

C:\Program Files\WindowsApps\ohmyposh.cli_<版本号>_x64__<哈希>\themes\

This path has three issues:

1. The version number changes with each update— hardwired paths in configuration files become invalid after updates.
2. NTFS permissions are locked— regular users can't read or write to this directory directly.
3. Dynamic detection is inaccurate— PowerShell's Get-Command oh-my-posh returns a symlink path, and using Get-Item .Target to parse it returns an empty value.

Debugging Process

# 这条命令不会给你真实路径
(Get-Command oh-my-posh).Source
​
# 在 WindowsApps 下 Get-ChildItem 会报权限错误
Get-ChildItem "C:\Program Files\WindowsApps" | Where-Object { $_.Name -like "ohmyposh*" }
​
# 只能用笨办法：已知版本号的情况下猜路径
"C:\Program Files\WindowsApps\ohmyposh.cli_0.21.1_x64__ohmyposh\themes"

Solution 1: Copying All Themes to the User Directory

Approach

Instead of battling with WindowsApps permissions,copy all themes to a stable user-controlled directory at once:

C:\Users\<用户名>\.config\oh-my-posh\themes\

This path:

• Permanently exists, unaffected by Oh-My-Posh updates
• Full read and write permissions for regular users
• Themes can be added, removed, or modified freely

Implementation

# 通过 bash 直接访问 WindowsApps（权限比 PowerShell 宽）
cp /mnt/c/Program\ Files/WindowsApps/ohmyposh.cli_*/themes/*.omp.json \
   ~/.config/oh-my-posh/themes/

Result:All 122 built-in themes are in place, saying goodbye to 'theme not found' warnings forever.

Solution 2: Generate a Clean Main Configuration File

Flaws in the Old Configuration

The original $PROFILE might be cluttered with outdated code, environmental variables pointing to non-existent paths, and overlapping init statements.

New Architecture: 1_shell.ps1

Extract the configuration into an independent file, referenced by $PROFILE:

# $PROFILE 里只有这一行
. "$env:USERPROFILE\1_shell.ps1"

1_shell.ps1 has clearly defined responsibilities:

# 1_shell.ps1 v5
​
# 1. 编码修复（解决中文乱码）
[Console]::OutputEncoding = [System.Text.Encoding]::UTF8
​
# 2. Oh-My-Posh 初始化（硬编码稳定路径）
$ThemeDir = "$env:USERPROFILE\.config\oh-my-posh\themes"
$ThemeName = "powerlevel10k_rainbow"
oh-my-posh init pwsh --config "$ThemeDir\$ThemeName.omp.json" | Invoke-Expression
​
# 3. 运行时主题切换器
function omp-theme {
    param([string]$Name)
    $t = "$ThemeDir\$Name.omp.json"
    if (Test-Path $t) {
        oh-my-posh init pwsh --config $t | Invoke-Expression
    }
}
​
# 4. 辅助工具
# PSReadLine（预测补全）、Terminal-Icons（文件图标）、
# zoxide（智能 cd）、常用别名（ll、g、c）

Effect

• No need to modify $PROFILE anymore—just edit 1_shell.ps1
• Switch themes with a single command—omp-theme catppuccin_mocha, no need to restart the terminal.
• Single responsibility—$PROFILE became a minimalist bootstrapper.

Solution 3: Enhance Visually Appealing Themes

Users chose three 'beautiful but feature-lacking' themes:

Case Study: Adding Python Version and Execution Time to catppuccin_mocha

Before modification: Only a left block existed, the right side was empty.

After modification: Added a right block.

{
  "alignment": "right",
  "segments": [
    {
      "type": "python",
      "style": "plain",
      "foreground": "#A6E3A1",
      "template": "🐍 {{ .Full }} "
    },
    {
      "type": "executiontime",
      "style": "plain",
      "foreground": "#6C7086",
      "template": "{{ .FormattedMs }}"
    }
  ],
  "type": "prompt"
}

Core Idea: Oh-My-Posh's blocks are like building blocks; adding an alignment: right block does not disrupt the original style, it merely appends content to the right. Colors are chosen from the theme's palette to maintain visual harmony.

Automation: Install-PoshSetup.ps1

Encapsulate the entire process into a single command to set everything up on a new machine in 30 seconds:

Feature List

1. ✅ Diagnose if oh-my-posh is installed
2. ✅ Automatically locate the theme directory under WindowsApps (supports Windows Store/Chocolatey/manual installation)
3. ✅ Copy all 122 built-in themes to the user directory
4. ✅ Generate/update 1_shell.ps1 main configuration
5. ✅ Ensure $PROFILE correctly references 1_shell.ps1
6. ✅ Enhance three visually appealing themes (catppuccin_mocha, tokyonight_storm, dracula)

Deployment Guide

Step 1: Install Oh-My-Posh on the new machine

winget install JanDeDobbeleer.OhMyPosh

Step 2: Run the installation script

Complete installation (specify default theme):

irm https://raw.githubusercontent.com/sysfox/posh-setup/main/Install-PoshSetup.ps1 | iex

Or run locally:

# 把 Install-PoshSetup.ps1 下载到本地后
.\Install-PoshSetup.ps1 -Theme catppuccin_mocha

Enhance themes only (skip configuration generation):

.\Install-PoshSetup.ps1 -EnhanceOnly

Step 3: Restart PowerShell

After executing the script, close all PowerShell windows and reopen them to activate the configuration.

Step 4: Change themes while running

# 温柔莫卡色调
omp-theme catppuccin_mocha
​
# 深蓝东京夜
omp-theme tokyonight_storm
​
# 经典德古拉紫
omp-theme dracula
​
# 内置彩虹全家桶
omp-theme powerlevel10k_rainbow
​
# 查看所有带 git+python+exec 的主题
# （在 omp-theme 输错主题名时会自动列出）

Complete File List

C:\Users\<用户名>\
├── 1_shell.ps1                          # 主配置文件
├── Documents\WindowsPowerShell\
│   └── Microsoft.PowerShell_profile.ps1  # $PROFILE（只一行引用）
└── .config\oh-my-posh\
    ├── Install-PoshSetup.ps1             # 安装脚本
    └── themes\
        ├── catppuccin_mocha.omp.json    # 增强版 ✓ python + exec
        ├── tokyonight_storm.omp.json    # 增强版 ✓ exec
        ├── dracula.omp.json             # 增强版 ✓ python + exec
        └── *.omp.json                   # 其他 119 个内置主题

Experience Summary

Why is this solution more reliable than changing $POSH_THEMES_PATH?

Oh-My-Posh Block Layout Tips

• alignment: left — On the left side of the command line
• alignment: right — On the right side of the command line (will be truncated if it exceeds width)
• type: "rprompt" — Always aligned to the right without truncation
• invert_powerline: true — Invert powerline arrow direction, used for right-sided diamond blocks

Conditional Control for Displaying Python Version

If you don't want to display the Python version in all directories (showing it without .py files is annoying), add this to the block configuration:

{
  "type": "python",
  "template": "{{ if .has_python }}🐍 {{ .Full }}{{ end }}",
  "type": "python",
  "style": "plain",
  "foreground": "#A6E3A1",
  "template": "{{ .Full }} "
}

This way it only displays when a Python project is detected (with __pycache__,.venv,pyproject.toml etc.).

In Closing

The key takeaway from this configuration refinement is:the distribution method of Windows Store applications (versioned paths + NTFS restrictions) inherently conflicts with 'stable configuration'.The solution isn't to patch around it but to bypass it—copy themes out and put them in a directory fully controlled by the user.

Thus, Oh-My-Posh updates no longer affect configurations, running the script on a new machine instantly recovers everything, and code sharing in teamwork becomes effortless. This is a little application of DevOps thinking in the desktop environment.

This document was generated with Kimi 2.6 and MiniMax support, and the script has been verified on Windows 11 Pro + PowerShell 5.1.