Downloads of v 2.0.0:


Last Update:

20 Mar 2021

Package Maintainer(s):

Software Author(s):

  • Kied Llaentenn
  • contributors


winfetch neofetch commandline systeminfo screenshot


  • 1
  • 2
  • 3

2.0.0 | Updated: 20 Mar 2021



Downloads of v 2.0.0:



Software Author(s):

  • Kied Llaentenn
  • contributors

  • 1
  • 2
  • 3
winfetch 2.0.0

  • 1
  • 2
  • 3

All Checks are Passing

3 Passing Tests

Validation Testing Passed

Verification Testing Passed


Scan Testing Successful:

No detections found in any package files


To install winfetch, run the following command from the command line or from PowerShell:


To upgrade winfetch, run the following command from the command line or from PowerShell:


To uninstall winfetch, run the following command from the command line or from PowerShell:


NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Enter your internal repository url

(this should look similar to

4. Choose your deployment method:

choco upgrade winfetch -y --source="'STEP 3 URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:

choco upgrade winfetch -y --source="'STEP 3 URL'"

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0

Exit $exitCode

- name: Ensure winfetch installed
    name: winfetch
    state: present
    version: 2.0.0
    source: STEP 3 URL

See docs at

chocolatey_package 'winfetch' do
  action    :install
  version  '2.0.0'
  source   'STEP 3 URL'

See docs at

    Name: winfetch,
    Version: 2.0.0,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller winfetch
   Name     = 'winfetch'
   Ensure   = 'Present'
   Version  = '2.0.0'
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

package { 'winfetch':
  provider => 'chocolatey',
  ensure   => '2.0.0',
  source   => 'STEP 3 URL',

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install winfetch version="2.0.0" source="STEP 3 URL"

See docs at

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

There are versions of this package awaiting moderation . See the Version History section below.

This package was approved by moderator virtualex on 21 Mar 2021.


NOTE: The following text is an excerpt from the official

Winfetch is a command-line system information utility written in PowerShell 5+. Winfetch displays information about your operating system, software and hardware in an aesthetic and visually pleasing way.

The overall purpose of Winfetch is to be used in screenshots of your system. Winfetch shows the information other people want to see. There are other tools available for proper system statistic/diagnostics.

The information by default is displayed alongside your operating system's logo. You can further configure Winfetch to instead use an image, your wallpaper or nothing at all.

According to benchmarks done with Hyperfine, Winfetch on Windows is faster than Neofetch running on Bash emulators like MSYS (Git Bash) or Cygwin.

$ErrorActionPreference = 'Stop';
$toolsDir              = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$version               = '2.0.0'
$executableFullPath    = "$toolsDir\winfetch-$version\winfetch.ps1"
$url                   = "$"
$checksum              = '53EDA3231F7A556076E65B098FF48619739BA0FBEA518E4998B3615A318A218A'

$packageArgs = @{
  packageName   = $env:ChocolateyPackageName
  unzipLocation = $toolsDir
  url           = $url
  softwareName  = 'winfetch*'
  checksum      = $checksum
  checksumType  = 'sha256' 

Install-ChocolateyZipPackage @packageArgs

Install-ChocolateyPowershellCommand `
  -PackageName    "$packageArgs.$packageName.powershell" `
  -PsFileFullPath $executableFullPath
$ErrorActionPreference = 'Stop';
$version               = '2.0.0'

$packageArgs = @{
  packageName   = $env:ChocolateyPackageName
  zipFileName   = "winfetch-$version"
  softwareName  = 'winfetch*'

Remove-Item "$env:ChocolateyInstall\bin\winfetch.bat" -Force
Uninstall-ChocolateyZipPackage @packageArgs

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version Downloads Last Updated Status
winfetch 2.1.0 9 Saturday, June 19, 2021 Ready


  • Fixed errors when using strict-mode
  • Fixed errors when using -noimage
  • Fixed issues with image processing especially for larger images
  • Fixed detailed help not showing

New Features

  • Improved terminal detection
  • Improved scoop pkgs speed
  • Disable unused package managers, use -showpkgs [enabled pkgs]
  • Change the order of info segments
  • Insert blank info lines
  • Hide the colorbar
  • Colorbar now shows 16 colors
  • Add custom info segments in the config
  • Info lines are now written out progressively
  • Info segments can now display multiple lines
  • Show info for multiple disks, use -showdisks *
  • Added legacy windows logo, use -switchlogo to use the alternate logo
  • Added -all parameter to show all built-in info segments (regardless of your config)
  • Added -stripansi parameter to disable colors/fancy formatting similar to --stdout in neofetch
  • Added -configpath parameter and WINFETCH_CONFIG_PATH environment variable to override the default location of the config
  • Command-line parameters will now override those set in the config
  • Long lines will now be truncated instead of wrapping to the next line
  • Added a basic legacy branch for systems older than Windows 7
  • The default config is now embedded within winfetch.ps1 and is generated automatically if your config doesn't exist
  • Added percentage bars to cpu, memory, disk and battery, they are configured similar to neofetch, for example, use winfetch -cpustyle bar -diskstyle textbar

New Info

  • kernel
  • resolution
  • motherboard
  • battery
  • local_ip
  • public_ip
  • cpu_usage
  • locale
  • theme

New Configuration

We have also switched to a much more modular approach for info segments, this simplified the code and made it easier to add new info segments. This change also allows users to add custom info segments in their config. The default config has been updated, see the configuration docs for more information.

If you never used winfetch -genconf before then you should automatically be switched to the new config, otherwise, you can regenerate a new config with winfetch -genconf.
Optionally, you can attempt to migrate your old configuration, this commit may help.


There have been many improvements to speed since v1.2.0. Comparing v1.2.0 to v2.0.0 with the same segments enabled 1500ms -> 350ms which is around a 4x improvement. More details can be seen on the winfetch vs neofetch benchmarks.

This package has no dependencies.

Discussion for the winfetch Package

Ground Rules:

  • This discussion is only about winfetch and the winfetch package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or winfetch, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus