Add configuration to disable checking for updates at startup, including checking for theme updates

[WangJincheng4869]

Code of Conduct

• I agree to follow this project's Code of Conduct

What would you like to see added?

Automatically checking for updates is a great feature, but due to network issues, the startup speed can be slow, usually exceeding 5 seconds. This problem almost always occurs after restarting the computer, so I can quickly access the terminal by turning off the update detection function during startup, just like opening it for the second time.

I tried using the following configuration, but still encountered slow loading issues.

{
  "upgrade": {
    "notice": false,
    "interval": "87600h",
    "auto": false,
    "source": "cdn"
  },
  "$schema": "https://raw.githubusercontent.com/JanDeDobbeleer/oh-my-posh/main/themes/schema.json",
  "blocks": [
    {
      "alignment": "right",
      "segments": [
        {
          "background": "#003543",
          "foreground": "#ffffff",
          "style": "plain",
          "template": " \ue641 {{ .CurrentDate | date .Format }} ",
          "type": "time"
        },
        {
          "background": "#83769c",
          "foreground": "#ffffff",
          "properties": {
            "always_enabled": true
          },
          "style": "plain",
          "template": " \ueba2 {{ .FormattedMs }} ",
          "type": "executiontime"
        }
      ],
      "type": "rprompt"
    },
    {
      "alignment": "left",
      "segments": [
        {
          "background": "#61AFEF",
          "foreground": "#ffffff",
          "properties": {
            "display_host": false
          },
          "style": "diamond",
          "template": "{{if .Root}} \uf0e7 {{end}}",
          "trailing_diamond": "\ue0b0",
          "type": "session"
        },
        {
          "background": "#C678DD",
          "foreground": "#ffffff",
          "powerline_symbol": "\ue0b0",
          "properties": {
            "folder_icon": "\uf115",
            "folder_separator_icon": " \ue0b1 ",
            "max_depth": 2,
            "style": "agnoster_short"
          },
          "style": "powerline",
          "template": " {{ .Path }} ",
          "type": "path"
        },
        {
          "background": "#95ffa4",
          "foreground": "#193549",
          "powerline_symbol": "\ue0b0",
          "style": "powerline",
          "template": " {{ .HEAD }} ",
          "type": "git"
        }
      ],
      "type": "prompt"
    }
  ],
  "final_space": true,
  "version": 3
}

[JanDeDobbeleer]

@WangJincheng4869 that configurations seems correct provided you have an up-to-date version of oh-my-posh. It might also be worthwhile to run oh-my-posh cache clear to avoid any side effects of the previous configuration.

[WangJincheng4869]

@JanDeDobbeleer I executed oh-my-posh cache clear, but the issue still exists.

[JanDeDobbeleer]

@WangJincheng4869 are you sure this isn't cause by something else? You can alternatively set $env.POSH_TRACE = 1 at the top of your $PROFILE to see what oh-my-posh is doing.

[WangJincheng4869]

[PGScully]

Should be $env:POSH_TRACE=1

[WangJincheng4869]

Where will the content be output? I didn't see any information on the terminal

[PGScully]

.oh-my-posh folder in your home directory.

[WangJincheng4869]

Just now, there was another issue of slow loading, but I didn't see any valuable information from the logs. Here are the log files.

20250804T113640.078-init-pwsh.log
20250804T113640.155-get-uuid.log
20250804T113640.279-print-secondary.log
20250804T113640.372-print-primary.log

The following is my configuration file, without configuring too much content

$env:POSH_TRACE=1
Set-PSReadLineKeyHandler -Key Tab -Function Complete

$ProxyUrl = "socks5://localhost:10808"

$env:all_proxy="$ProxyUrl"
oh-my-posh init pwsh --config "D:/Users/jcwang/Documents/PowerShell/capr4n.omp.json" | Invoke-Expression
$env:all_proxy=""

Function proxy {
  $env:all_proxy="$ProxyUrl"
  Write-Host "代理已启用：$ProxyUrl" -ForegroundColor Green
}

Function unproxy {
  $env:all_proxy=""
  Write-Host "代理已禁用" -ForegroundColor Yellow
}

[JanDeDobbeleer]

@WangJincheng4869 if you don't see an -update.log, this means oh-my-posh isn't running update either. Something else is influencing this startup time (can also be Windows defender or another tool blocking the execution of oh-my-posh)

[QianMoXi]

I have the same problem, can't disable update checking.

Disabling oh-my-posh alone reduces my pwsh startup time from 6 seconds to approximately 500ms.

[QianMoXi]

@WangJincheng4869 Do you have Huorong antivirus installed on your computer?

[WangJincheng4869]

@WangJincheng4869 Do you have Huorong antivirus installed on your computer?

yes

[QianMoXi]

Sorry, my previous statement was incorrect. The computer where I encountered this issue does have Huorong antivirus installed.

I just ran a verification in a virtual machine: before installing Huorong, initializing pwsh only took around 300ms; after installing Huorong, the first startup took about 1.9s, while subsequent startups returned to normal.

As for why this issue occurs roughly once every 24 hours, my guess is that Huorong has some internal caching mechanism, and the cache expires after 24 hours.

[WangJincheng4869]

Sorry, my previous statement was incorrect. The computer where I encountered this issue does have Huorong antivirus installed.

I just ran a verification in a virtual machine: before installing Huorong, initializing pwsh only took around 300ms; after installing Huorong, the first startup took about 1.9s, while subsequent startups returned to normal.

As for why this issue occurs roughly once every 24 hours, my guess is that Huorong has some internal caching mechanism, and the cache expires after 24 hours.

Thanks for the reminder, I'll add it to the trusted directory and test it.

[QianMoXi]

I conducted further testing and found that the trusted directory setting is ineffective. As long as any of Huorong’s protection features are enabled, the issue will occur. Reporting this to Huorong for them to address might be a better option.