October 2021
M	T	W	T	F	S	S
	1	2	3
4	5	6	7	8	9	10
11	12	13	14	15	16	17
18	19	20	21	22	23	24
25	26	27	28	29	30	31

Archive for the ‘Chocolatey’ Category

Chocolatey: force install sysinternals after hash mismatch

Posted by jpluimers on 2021/09/28

Shortly after UltraVNC mismatching sha256 hash the chocolatey checksum check (Chocolatey: when upgrades or installs keep insisting the hash has changed, and over time the mismatch changes as well), I bumped into another occasion: now (because of a zero sized .nupkg file), I had to force reinstall sysinternals.

The problem however is that sysinternals chocolatey will always install the latest version as per [WayBack] Chocolatey Software | Sysinternals 2019.12.19

Notes

This package supports only latest version.

This package by default installs to tools directory which will create shims for all applications. When you install to different directory, shims are not created but directory is added to the PATH.

This package downloads the nano edition of sysinternals suite when installing it on a nano server.

To have GUI for the tools, install nirlauncher package and use /Sysinternals package parameter.

It means that when reinstalling an older version (in the process of fixing a broken chocolatey install), it is OK to ignore the error caused during forced reinstall:

C:\bin\bin>choco install --force --yes sysinternals
Chocolatey v0.10.15
Installing the following packages:
sysinternals
By installing you accept licenses for the packages.
sysinternals v2019.6.29 already installed. Forcing reinstall of version '2019.6.29'.
 Please use upgrade if you meant to upgrade to a new version.
Progress: Downloading sysinternals 2019.6.29... 100%

sysinternals v2019.6.29 (forced) [Approved]
sysinternals package files install completed. Performing other installation steps.
Sysinternals Suite is going to be installed in 'C:\ProgramData\chocolatey\lib\sysinternals\tools'
Downloading sysinternals
  from 'https://download.sysinternals.com/files/SysinternalsSuite.zip'
Progress: 100% - Completed download of C:\Users\jeroenp\AppData\Local\Temp\chocolatey\sysinternals\2019.6.29\SysinternalsSuite.zip (29 MB).
Download of SysinternalsSuite.zip (29 MB) completed.
Error - hashes do not match. Actual value was 'AE0AB906A61234D1ECCB027D04F5A920D78A31494372193EE944DD419842625C'.
ERROR: Checksum for 'C:\Users\jeroenp\AppData\Local\Temp\chocolatey\sysinternals\2019.6.29\SysinternalsSuite.zip' did not meet 'db59efe1739a2262104874347277f9faa0805a1a7a0acd9cc29e9544fb8040c5' for checksum type 'sha256'. Consider passing the actual checksums through with --checksum --checksum64 once you validate the checksums are appropriate. A less secure option is to pass --ignore-checksums if necessary.
The install of sysinternals was NOT successful.
Error while running 'C:\ProgramData\chocolatey\lib\sysinternals\tools\chocolateyInstall.ps1'.
 See log for details.

Chocolatey installed 0/1 packages. 1 packages failed.
 See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log).

Failures
 - sysinternals (exited -1) - Error while running 'C:\ProgramData\chocolatey\lib\sysinternals\tools\chocolateyInstall.ps1'.
 See log for details.

So in this case, as always the most recent Sysinternals file is used, it is OK to follow the bold guideline above (and quoted below) use the checksum for that file. You might even want to ignore it, as the file is downloaded over https so tampering is virtually impossible:

Consider passing the actual checksums through with --checksum --checksum64 once you validate the checksums are appropriate. A less secure option is to pass --ignore-checksums if necessary.

For this checksum, the forced reinstall becomes choco install --force --yes sysinternals --checksum AE0AB906A61234D1ECCB027D04F5A920D78A31494372193EE944DD419842625C

Alternatively (with a slight chance of yet another checksum) would be choco install --force --yes sysinternals --ignore-checksums

Read the rest of this entry »

Posted in .NET, Chocolatey, CommandLine, Development, Power User, PowerShell, PowerShell, Scripting, Software Development, SysInternals, Windows | Leave a Comment »

Chocolatey: forcing a certain package version and pinning it at that version

Posted by jpluimers on 2021/09/23

For my future self.

Due to an issue with choco-cleaner versions [WayBack] 0.0.6 and [WayBack] 0.0.7, I needed to ensure it was installed as version [WayBack] 0.0.5.2 and keep it that version.

Not sure if this is the canonical way, but this worked:

choco uninstall --yes choco-cleaner
choco install --yes choco-cleaner --version 0.0.5.2
choco pin add --name=choco-cleaner --version 0.0.5.2
choco pin list

This worked to revert:

choco pin remove --name=choco-cleaner
choco pin list
choco upgrade --yes choco-cleaner

Aftere this upgrade, choco-cleaner version 0.0.7.1 shows a nice error message when the environment variable %ChocolateyToolsLocation% fails to exist.

In that case calling RefreshEnv.cmd will create that environment variable.

[WayBack] Chocolatey Software | Commandsinstall: Examples
[WayBack] Chocolatey Software | Commandspin: examples
[WayBack] Chocolatey Software | (unofficial) Choco Cleaner (Script + Task) 0.0.7: releasenotes
[WayBack] Lack of `ChocolateyToolsLocation` environment variable causes `choco-cleaner` to fail in an UAC console · Issue #143 · bcurran3/ChocolateyPackages · GitHub

Default %ChocolateyToolsLocation% location is %systemdrive%\tools according to [WayBack] https://github.com/chocolatey/choco/blob/master/src/chocolatey.resources/helpers/functions/Get-ToolsLocation.ps1#L61
[WayBack] Installed to c:\tools\bcurran3 · Issue #112 · bcurran3/ChocolateyPackages · GitHub

The readme.md on GitHub is out of sync… a bunch of stuff is that I need to get to eventually.

The new package page on chocolatey.org should be current and has this:

Release Notes
INSTRUCTIONS:
Edit C:\tools\BCURRAN3\choco-package-list-backup.config to customize your backup(s). It’s easy, there are comments.
From PowerShell or the Command Prompt, type CHOCO-PACKAGE-LIST-BACKUP to backup your Chocolatey packages list.
From Windows, click Chocolatey Package List Backup in the Windows Start Menu or Package List Backup inside the Chocolatey folder if Chocolatey Shortcuts is installed.
CHANGELOG:
2019.08.27 – can now put title and summary info into the packages.config file, new -EditConfig parameter to edit the config file, Now works from Command Prompt as well as PowerShell, script installation endpoint changed, config file renamed from .xml to .config

–jeroen

Read the rest of this entry »

Posted in .NET, Chocolatey, CommandLine, Development, Power User, PowerShell, PowerShell, Scripting, Software Development, Windows | Leave a Comment »

Chocolatey: when upgrades or installs keep insisting the hash has changed, and over time the mismatch changes as well

Posted by jpluimers on 2021/09/14

A while ago, I bumped into problems updating UltraVNC through Chocolatey.

It is similar to issues with other packages I have seen in the past: sha256 hash mismatches of which the reported mismatch changes over time, though the version stays the same.

This was tracked down to the actual file download site now needing a correct HTTP referer header. Likely this is to stop automated downloads, which kind of back-fires as ultimately you want to automate download and installation of things as much as possible.

Anyway: this is the [Archive.is] thread (which cannot be archived as Disqus hates archiving in the WayBack machine, and archive.is often fails with it too):

Graham Bloice a month ago

The recent update to 1.2300 fails for me with a file hash error. The install script has fe3d1135ae0e7b72394a6f3cc137282cb5e6382a55b5ceee72140d28f5ffe961, but the installer as downloaded, and verified via a separate download and hash check has 5A42A24BED5A39ACA44443916E5B2C4C259CE8E843E90FD07F7AB3D26CB237C8
IdealChain Graham Bloice 3 hours agoThis is because the download page has some “anti leeching” logic which checks the referer header and redirects to the homepage in case that check fails.Dear maintainer, please add the header “Referer: https://www.uvnc.com/” to the Install-ChocolateyPackage options!
Maurice Kevenaar IdealChain 2 hours ago
IdealChain Thanks for this hint! I was still looking for a solution and now, thanks to you, I have one.A new version is being build and will be pushed up soon.

Jeroen Pluimers Maurice Kevenaar 23 minutes agoAs per chocolatey.org/packages/ultravnc/1.2300.0.20200105, it looks like these URLs from the .nuspec files have been permanently removed from the UltraVNC site:<releasenotes>http://www.uvnc.com/general/whatsnew.html</releasenotes> <licenseurl>http://www.uvnc.com/general/license.html</licenseurl> ... <docsurl>http://www.uvnc.com/docs.html</docsurl>There is no replacement for `releaseNotes` or `licenseUrl` (not even in their source code repository at sourceforge.net/p/ultravnc/code/HEAD/tree/UltraVNC%20Project%20Root/UltraVNC/)An alternative for `docsUrl` is www.uvnc.com/docs/uvnc-server.html (that’s what `Documentation` at www.uvnc.com points to).
Jeroen Pluimers Graham Bloice 2 days ago
By now the error has changed; could it be that UltraVNC keeps releasing new Version 1.2300 with different hashes?

You have ultravnc v1.2240.0.20190403 installed. Version 1.2300 is available based on your source(s). Progress: Downloading ultravnc 1.2300... 100%
ultravnc v1.2300 [Approved]
ultravnc package files upgrade completed. Performing other installation steps.
File appears to be downloaded already. Verifying with package checksum to determine if it needs to be redownloaded.
Error - hashes do not match. Actual value was '5168CD279B36141B4B5B21CAC449FD4738A0E7C281D19BE99B3EF22968D77B7E'.
Downloading ultravnc 64 bit
from 'https://www.uvnc.eu/download/1230/UltraVNC_1_2_30_X64_Setup.exe'
WARNING: C:\Users\jeroenp\AppData\Local\Temp\chocolatey\ultravnc\1.2300\index.php is of content type text/html; charset=utf-8
Download of index.php (-1 B) completed.
Error - hashes do not match. Actual value was 'D0030DCF7A58166CC96FF5F258D5E6F179F94F412456CD0CE7223561532A3AB2'.
ERROR: Checksum for 'C:\Users\jeroenp\AppData\Local\Temp\chocolatey\ultravnc\1.2300\index.php' did not meet 'fe3d1135ae0e7b72394a6f3cc137282cb5e6382a55b5ceee72140d28f5ffe961' for checksum type 'sha256'. Consider passing the actual checksums through with --checksum --checksum64 once you validate the checksums are appropriate. A less secure option is to pass --ignore-checksums if necessary.
The upgrade of ultravnc was NOT successful.
Error while running 'C:\ProgramData\chocolatey\lib\ultravnc\tools\chocolateyInstall.ps1'.
See log for details.

Related: Chocolatey got more strict on various URLs being correct; see [WayBack] (UltraVNC) Why has the X64 been removed? · Issue #42 · mkevenaar/chocolatey-packages · GitHub.

–jeroen

Posted in Chocolatey, CommandLine, Communications Development, Development, HTTP, Internet protocol suite, Power User, PowerShell, Software Development, TCP, Windows | Leave a Comment »

PowerShell: recovering from corrupt empty *.nupkg files after a disk was accidentally full during update

Posted by jpluimers on 2021/09/09

When you do a choco upgrade all --yes on a system that – during upgrade – becomes low on disk space, you can end up with a lot of empty .nupkg files.

For those package, Chocolatey will not recognise they are installed any more.

The fix is this:

increase disk space so at least 5 gigabytes is free
split the choco upgrade process so it checks before each upgrade that this diskspace is indeed free
list all choco .nupkg files of length zero ordered from oldest to newest
for each package, delete the .nupkg file if it exists, then force install it with the --force parameter before the --yes parameter like in

choco install --force --yes chocolatey
when all packages have been done, then choco upgrade --all --yes

I wrote a few PowerShell scripts assisting me in cleaning up the mess.

`choco-list-installed.bat`

[WayBack] windows – How to list Chocolatey packages already installed and newer version available from the command line – Super User

:: https://superuser.com/questions/890251/how-to-list-chocolatey-packages-already-installed-and-newer-version-available-fr
choco list --localonly %*

`choco-show-installed-package-names.bat`

[WayBack] CommandsList · chocolatey/choco Wiki · GitHub

:: `--limit-output`  does not show Chocolatey version header and count footer.
:: `--id-oonly`      omits the version number, so you only get the package name
choco list --local-only --limit-output --id-only

`choco-show-installed-package-names-and-versions.bat`

:: `--limit-output`  does not show Chocolatey version header and count footer.
choco list --local-only --limit-output %*

`choco-reinstall-empty-nupkg-by-names.ps1`

[WayBack] Powershell – Finding 0-byte Files | Another computer blog
[WayBack] windows – Where is the Chocolatey installation path? – Stack Overflow:

There is an environment variable set on installation, ChocolateyInstall, which is set to C:\Chocolatey by default in versions of Chocolatey less than 0.9.8.27. After that, this defaults to C:\ProgramData\Chocolatey.

NOTE: By default, the C:\ProgramData folder on Windows is hidden. You will either need to enable hidden files and folders through Folder Options | View or you can navigate directly to the path shown above by copy/pasting directly into the Windows Explorer address bar.

In version 0.9.9 of Chocolatey, it actively moves from the old folder location to the new one.
[WayBack] string – Powershell concatenate an Environment variable with path – Stack Overflow
A convenient way to obtain the string value rather than the dictionary entry (which is technically what Get-ChildItem is accessing) is to just use the variable syntax: $Env:USERPROFILE rather than Get-ChildItem Env:USERPROFILE.
```
$localpath = "$env:USERPROFILE\some\path"
```
…

Also, the Join-Path cmdlet is a good way to combine two parts of a path.
```
$localpath = Join-Path $env:USERPROFILE 'some\path'
```

<#
https://learningpcs.blogspot.com/2009/12/powershell-finding-0-byte-files.html

Zero length .nupkg files sorted by oldest first.

These are packages that choco will not show and likekly need a forced reinstall.

Choco does remember the version that was installed (so not all the choco config is hosed).

- https://stackoverflow.com/questions/28235388/where-is-the-chocolatey-installation-path/28239451#28239451
- https://stackoverflow.com/questions/41047123/powershell-concatenate-an-environment-variable-with-path/41047343#41047343

/#>
$LibPath = Join-Path $env:ChocolateyInstall 'lib'
$NuPkgExtension = 'nupkg'
$NupkgFilter = "*.$NuPkgExtension"

## Remove the empty .nupkg files for each argument
$args | ForEach-Object {
    $PackageName = $_ 
    Write-Output "Deleting any empty $PackageName.$NuPkgExtension under $LibPath :"

    Get-ChildItem -Path $LibPath -Recurse -Filter $NupkgFilter | Where-Object {
        ($_.Length -eq 0) -and ($_.BaseName -eq $PackageName)
    } | Sort-Object LastWriteTime | ForEach-Object { 
        $PackageFullName = $_.FullName
        Write-Output "Deleting $PackageFullName"
        Remove-Item $PackageFullName
    }
}

## Force install the chocolatey package for each argument
$args | ForEach-Object {
    $PackageName = $_ 
    Write-Output "Installing $PackageName with Chocolatey:"
    choco install --force --yes $PackageName
}

Link lists

Some more links that helped me solve this:

Some links on errors I encountered while recovering from this:

Checksum errors like[WayBack] (sysinternals) checksum error · Issue #756 · chocolatey-community/chocolatey-coreteampackages · GitHub are often caused by the chocolatey package downloading the most recent installer despite the package version. Two solutions:
1. Pass --ignorechecksum to choco --install (see [WayBack] CommandsInstall · chocolatey/choco Wiki · GitHub)
2. First uninstall using the --force parameter
  [Archive.is] Chocolatey Software | Sysinternals 2019.6.29
  
  Sysinternals Suite is going to be installed in ‘C:\ProgramData\chocolatey\lib\sysinternals\tools’
  File appears to be downloaded already. Verifying with package checksum to determine if it needs to be redownloaded.
  Error – hashes do not match. Actual value was ‘A510C31C2CC591A16F342E7CBA5DC8409EAF08C9B56729CF132C95C69E196787’.
  Downloading sysinternals
  from ‘https://download.sysinternals.com/files/SysinternalsSuite.zip’
  Progress: 100% – Completed download of C:\Users\devCrPhoneDebug\AppData\Local\Temp\2\chocolatey\sysinternals\2018.12.27\SysinternalsSuite.zip (23.51 MB).
  Download of SysinternalsSuite.zip (23.51 MB) completed.
  Error – hashes do not match. Actual value was ‘A510C31C2CC591A16F342E7CBA5DC8409EAF08C9B56729CF132C95C69E196787’.
  ERROR: Checksum for ‘C:\Users\devCrPhoneDebug\AppData\Local\Temp\2\chocolatey\sysinternals\2018.12.27\SysinternalsSuite.zip’ did not meet ‘b14466c6bf3be216ea71610a3f455030e791cd5ad1b42a283886194205d176b0’ for checksum type ‘sha256’. Consider passing the actual checksums through with –checksum –checksum64 once you validate the checksums are appropriate. A less secure option is to pass –ignore-checksums if necessary.
  The install of sysinternals was NOT successful.
  Error while running ‘C:\ProgramData\chocolatey\lib\sysinternals\tools\chocolateyInstall.ps1’.
  See log for details.
  
  Chocolatey installed 0/1 packages. 1 packages failed.
  See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log).
Packages that cannot be found at all:[WayBack] “imagemagick not installed. The package was not found with the source(s) listed” – Google Search
- This means that Chocolatey cannot find a dependency, but will not tell you which one. It also happens during package testing:[WayBack] imagemagick v7.0.9.7 – Failed – Package Tests Results · GitHub
  - Solve this by fixing all other empty .nupkg files first, which will give you an idea on the potential missing dependencies. Retry by forcing reinstall each dependency.
Dependencies that cannot be found, which can be caused by more empty .nupkg files. Example: [WayBack] Unable to resolve dependency · Issue #206 · chocolatey/choco · GitHub
- Solve this by each time a dependency is not found, include on the choco-reinstall-empty-nupkg-by-names.ps1command, then retry.

–jeroen

Posted in Chocolatey, COBOL, Development, Power User, PowerShell, PowerShell, Scripting, Software Development, Windows, Windows 10 | Leave a Comment »

Chocolatey parameter order: `–yes` becomes before `–force`

Posted by jpluimers on 2021/09/08

Not sure why, bit if you want to force install a package, answering yes to all prompts, the chocolaty parameter order needs to be --yes --force instead of --force --yes.

This works:

choco install --yes --force git.install --params "/GitAndUnixToolsOnPath /NoGitLfs /SChannel /NoAutoCrlf /WindowsTerminal"

This fails:

choco install --force --yes git.install --params "/GitAndUnixToolsOnPath /NoGitLfs /SChannel /NoAutoCrlf /WindowsTerminal"

–jeroen

Posted in Chocolatey, Development, DevOps, Power User, Scripting, Software Development, Windows | Leave a Comment »

« Previous Entries

	jpluimers on linux – How can I find a…
	jpluimers on The Windows key has no Unicode…
	sglienke on DUnit with FastMM: Detecting m…
	dummzeuch on Parser generator toolset for D…
	Jürgen Krämer on Space matching with sed is dif…

The Wiert Corner – irregular stream of stuff

Jeroen W. Pluimers on .NET, C#, Delphi, databases, and personal interests

Subscribe

Archives

Recent Comments

Recent Posts

Blog Stats

Meta title

Tag Cloud Title

Top Clicks

Top Posts

My badges

Twitter Updates

My Flickr Stream

Pages

All categories

Email Subscription

Archive for the ‘Chocolatey’ Category

Chocolatey: force install sysinternals after hash mismatch

Notes

Chocolatey: forcing a certain package version and pinning it at that version

Chocolatey: when upgrades or installs keep insisting the hash has changed, and over time the mismatch changes as well

PowerShell: recovering from corrupt empty *.nupkg files after a disk was accidentally full during update

`choco-list-installed.bat`

`choco-show-installed-package-names.bat`

`choco-show-installed-package-names-and-versions.bat`

`choco-reinstall-empty-nupkg-by-names.ps1`

Link lists

Chocolatey parameter order: `–yes` becomes before `–force`

The Wiert Corner – irregular stream of stuff

Jeroen W. Pluimers on .NET, C#, Delphi, databases, and personal interests

Subscribe

Archives

Recent Comments

Recent Posts

Blog Stats

Meta title

Tag Cloud Title

Top Clicks

Top Posts

My badges

Twitter Updates

My Flickr Stream

Pages

All categories

Email Subscription

Archive for the ‘Chocolatey’ Category

Chocolatey: force install sysinternals after hash mismatch

Notes

Rate this:

Share this:

Like this:

Chocolatey: forcing a certain package version and pinning it at that version

Rate this:

Share this:

Like this:

Chocolatey: when upgrades or installs keep insisting the hash has changed, and over time the mismatch changes as well

Rate this:

Share this:

Like this:

PowerShell: recovering from corrupt empty *.nupkg files after a disk was accidentally full during update

choco-list-installed.bat

choco-show-installed-package-names.bat

choco-show-installed-package-names-and-versions.bat

choco-reinstall-empty-nupkg-by-names.ps1

Link lists

Rate this:

Share this:

Like this:

Chocolatey parameter order: `–yes` becomes before `–force`

Rate this:

Share this:

Like this:

`choco-list-installed.bat`

`choco-show-installed-package-names.bat`

`choco-show-installed-package-names-and-versions.bat`

`choco-reinstall-empty-nupkg-by-names.ps1`