User Tools

Site Tools


choco_install

Choco install

Return to Cloud Monk's Package Manager Book, Chocolatey Package Manger, Cloud Monk's Development PC DevOps Automation via Ansible-Chocolatey-PowerShell-Homebrew-DNF-APT, Cloud Monk's Development PC Chocolatey List, Development macOS Homebrew List (Homebrew) - Development Mac, Development PC, Cloud Monk's VS Code Extensions, Git Username, git commit Email Address, Authenticating with GitHub from Git

See also Choco search

Windows PowerShell Copyright (C) Microsoft Corporation. All rights reserved.

                                                                                                                       Install the latest PowerShell for new features and improvements! https://aka.ms/PSWindows                                                                                                                                                       PS C:\WINDOWS\system32> Set-ExecutionPolicy Bypass -Scope Process -Force; [System.Net.ServicePointManager]::SecurityProtocol = [System.Net.ServicePointManager]::SecurityProtocol -bor 3072; iex ((New-Object System.Net.WebClient).DownloadString('https://community.chocolatey.org/install.ps1'))                                                                     Forcing web requests to allow TLS v1.2 (Required for requests to Chocolatey.org)
Getting latest version of the Chocolatey package for download. Not using proxy. Getting Chocolatey from https://community.chocolatey.org/api/v2/package/chocolatey/1.1.0. Downloading https://community.chocolatey.org/api/v2/package/chocolatey/1.1.0 to C:\Users\mcsec\AppData\Local\Temp\chocolatey\chocoInstall\chocolatey.zip Not using proxy. Extracting C:\Users\mcsec\AppData\Local\Temp\chocolatey\chocoInstall\chocolatey.zip to C:\Users\mcsec\AppData\Local\Temp\chocolatey\chocoInstall Installing Chocolatey on the local machine Creating ChocolateyInstall as an environment variable (targeting 'Machine')
 Setting ChocolateyInstall to 'C:\ProgramData\chocolatey'
WARNING: It's very likely you will need to close and reopen your shell
 before you can use choco.
Restricting write permissions to Administrators We are setting up the Chocolatey package repository. The packages themselves go to 'C:\ProgramData\chocolatey\lib'
 (i.e. C:\ProgramData\chocolatey\lib\yourPackageName).
A shim file for the command line goes to 'C:\ProgramData\chocolatey\bin'
 and points to an executable in 'C:\ProgramData\chocolatey\lib\yourPackageName'.

Creating Chocolatey folders if they do not already exist.

WARNING: You can safely ignore errors related to missing log files when

 upgrading from a version of Chocolatey less than 0.9.9.
 'Batch file could not be found' is also safe to ignore.
 'The system cannot find the file specified' - also safe.
chocolatey.nupkg file not installed in lib.
Attempting to locate it from bootstrapper.
PATH environment variable does not have C:\ProgramData\chocolatey\bin in it. Adding… WARNING: Not setting tab completion: Profile file does not exist at 'C:\Users\mcsec\Documents\WindowsPowerShell\Microsoft.PowerShell_profile.ps1'. Chocolatey (choco.exe) is now ready. You can call choco from anywhere, command line or powershell by typing choco. Run choco /? for a list of functions. You may need to shut down and restart powershell and/or consoles
first prior to using choco.
Ensuring Chocolatey commands are on the path Ensuring chocolatey.nupkg is in the lib folder PS C:\WINDOWS\system32> choco search microsoft-windows-terminal Chocolatey v1.1.0 2 validations performed. 1 success(es), 1 warning(s), and 0 error(s).

Validation Warnings:

- A pending system reboot request has been detected, however, this is
  being ignored due to the current command being used 'search'.
  It is recommended that you reboot at your earliest convenience.

microsoft-windows-terminal 1.15.2524.0 [Approved] 1 packages found. PS C:\WINDOWS\system32> choco install microsoft-windows-terminal -y Chocolatey v1.1.0 2 validations performed. 1 success(es), 1 warning(s), and 0 error(s).

Validation Warnings:

- A pending system reboot request has been detected, however, this is
  being ignored due to the current Chocolatey configuration.  If you
  want to halt when this occurs, then either set the global feature
  using:
    choco feature enable -name=exitOnRebootDetected
  or pass the option --exit-when-reboot-detected.

Installing the following packages: microsoft-windows-terminal By installing, you accept licenses for the packages. Progress: Downloading vcredist140 14.32.31332… 100% Progress: Downloading chocolatey-core.extension 1.4.0… 100% Progress: Downloading chocolatey-compatibility.extension 1.0.0… 100% Progress: Downloading KB3033929 1.0.5… 100% Progress: Downloading chocolatey-windowsupdate.extension 1.0.4… 100% Progress: Downloading KB3035131 1.0.3… 100% Progress: Downloading KB2919355 1.0.20160915… 100% Progress: Downloading KB2919442 1.0.20160915… 100% Progress: Downloading KB2999226 1.0.20181019… 100% Progress: Downloading microsoft-windows-terminal 1.15.2524.0… 100%

chocolatey-compatibility.extension v1.0.0 [Approved] chocolatey-compatibility.extension package files install completed. Performing other installation steps.

Installed/updated chocolatey-compatibility extensions.
The install of chocolatey-compatibility.extension was successful.
 Software installed to 'C:\ProgramData\chocolatey\extensions\chocolatey-compatibility'

chocolatey-core.extension v1.4.0 [Approved] chocolatey-core.extension package files install completed. Performing other installation steps.

Installed/updated chocolatey-core extensions.
The install of chocolatey-core.extension was successful.
 Software installed to 'C:\ProgramData\chocolatey\extensions\chocolatey-core'

chocolatey-windowsupdate.extension v1.0.4 [Approved] chocolatey-windowsupdate.extension package files install completed. Performing other installation steps.

Installed/updated chocolatey-windowsupdate extensions.
The install of chocolatey-windowsupdate.extension was successful.
 Software installed to 'C:\ProgramData\chocolatey\extensions\chocolatey-windowsupdate'

KB3035131 v1.0.3 [Approved] kb3035131 package files install completed. Performing other installation steps. Skipping installation because update KB3035131 does not apply to this operating system (Microsoft Windows 11 Pro).

The install of kb3035131 was successful.
 Software install location not explicitly set, it could be in package or
 default install location of installer.

KB3033929 v1.0.5 [Approved] kb3033929 package files install completed. Performing other installation steps. Skipping installation because update KB3033929 does not apply to this operating system (Microsoft Windows 11 Pro).

The install of kb3033929 was successful.
 Software install location not explicitly set, it could be in package or
 default install location of installer.

KB2919442 v1.0.20160915 [Approved] kb2919442 package files install completed. Performing other installation steps. Skipping installation because this hotfix only applies to Windows 8.1 and Windows Server 2012 R2.

The install of kb2919442 was successful.
 Software install location not explicitly set, it could be in package or
 default install location of installer.

KB2919355 v1.0.20160915 [Approved] kb2919355 package files install completed. Performing other installation steps. Skipping installation because this hotfix only applies to Windows 8.1 and Windows Server 2012 R2.

The install of kb2919355 was successful.
 Software install location not explicitly set, it could be in package or
 default install location of installer.

KB2999226 v1.0.20181019 [Approved] - Possibly broken kb2999226 package files install completed. Performing other installation steps. Skipping installation because update KB2999226 does not apply to this operating system (Microsoft Windows 11 Pro).

The install of kb2999226 was successful.
 Software install location not explicitly set, it could be in package or
 default install location of installer.

vcredist140 v14.32.31332 [Approved] vcredist140 package files install completed. Performing other installation steps. Downloading vcredist140-x86

 from 'https://download.visualstudio.microsoft.com/download/pr/ed95ef9e-da02-4735-9064-bd1f7f69b6ed/CF92A10C62FFAB83B4A2168F5F9A05E5588023890B5C0CC7BA89ED71DA527B0F/VC_redist.x86.exe'
Progress: 100% - Completed download of C:\Users\mcsec\AppData\Local\Temp\chocolatey\vcredist140\14.32.31332\VC_redist.x86.exe (13.09 MB). Download of VC_redist.x86.exe (13.09 MB) completed. Hashes match. Installing vcredist140-x86… vcredist140-x86 has been installed. Downloading vcredist140-x64 64 bit
 from 'https://download.visualstudio.microsoft.com/download/pr/ed95ef9e-da02-4735-9064-bd1f7f69b6ed/CE6593A1520591E7DEA2B93FD03116E3FC3B3821A0525322B0A430FAA6B3C0B4/VC_redist.x64.exe'
Progress: 100% - Completed download of C:\Users\mcsec\AppData\Local\Temp\chocolatey\vcredist140\14.32.31332\VC_redist.x64.exe (24.07 MB). Download of VC_redist.x64.exe (24.07 MB) completed. Hashes match. Installing vcredist140-x64… vcredist140-x64 has been installed.
 vcredist140 may be able to be automatically uninstalled.
The install of vcredist140 was successful.
 Software installed as 'exe', install location is likely default.

microsoft-windows-terminal v1.15.2524.0 [Approved] microsoft-windows-terminal package files install completed. Performing other installation steps. WARNING: The installed 1.15.2524.0 version is newer than this package version, it may have autoupdated on your current OS… Progress: 0% - Processing ERROR: The running command stopped because the preference variable “ErrorActionPreference” or common parameter is set to Stop: Deployment failed with HRESULT: 0x80073D06, The package could not be installed because a higher version of this package is already installed.

Windows cannot install package Microsoft.WindowsTerminal_1.15.2524.0_x64__8wekyb3d8bbwe because it has version 1.15.2524.0. A higher version 1.15.2713.0 of this package is already installed.

NOTE: For additional information, look for [ActivityId] 68616441-d410-0000-e53c-7c6810d4d801 in the Event Log or use the command line Get-AppPackageLog -ActivityID 68616441-d410-0000-e53c-7c6810d4d801

The install of microsoft-windows-terminal was NOT successful. Error while running 'C:\ProgramData\chocolatey\lib\microsoft-windows-terminal\tools\chocolateyInstall.ps1'.

See log for details.

Chocolatey installed 9/10 packages. 1 packages failed.

See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log).

Installed:

- kb2919355 v1.0.20160915
- kb3033929 v1.0.5
- chocolatey-core.extension v1.4.0
- kb2999226 v1.0.20181019
- kb2919442 v1.0.20160915
- vcredist140 v14.32.31332
- chocolatey-compatibility.extension v1.0.0
- kb3035131 v1.0.3
- chocolatey-windowsupdate.extension v1.0.4

Failures

- microsoft-windows-terminal (exited -1) - Error while running 'C:\ProgramData\chocolatey\lib\microsoft-windows-terminal\tools\chocolateyInstall.ps1'.
See log for details.
PS C:\WINDOWS\system32>

Chocolatey Software Package Manager: Cloud Monk's Package Manager Book, Cloud Monk's Development PC DevOps Automation via Ansible-Chocolatey-PowerShell-Homebrew-DNF-APT, Chocolatey Glossary, Chocolatey Fundamentals, Chocolatey Inventor - Chocolatey Designer: Rob Reynolds, Chocolatey DevOps - Chocolatey WinOps - WinOps, Chocolatey Tools (InstChoco, choco-package-list-backup and choco-cleaner by bcurran3), Boxstarter, Chocolatey Community Package Repository, Idempotent, Chocolatey install (InstChoco), Refreshenv, PowerShell on Windows, Package managers, Windows Package Managers, Windows Configuration Management - Windows Server Configuration Management, Ansible on Windows, Chef on Windows, Puppet on Windows, Debloat, choco-package-list-backup, Choco Cleaner, (navbar_choco - see also navbar_brew, navbar_package_manager)


© 1994 - 2024 Cloud Monk Losang Jinpa or Fair Use. Disclaimers

SYI LU SENG E MU CHYWE YE. NAN. WEI LA YE. WEI LA YE. SA WA HE.


choco_install.txt · Last modified: 2024/04/28 03:46 (external edit)