One of the places explaining a more and more frequent error on Windows 7 installations is [Wayback/Archive.is] “You must provide a value expression on the right-hand side of the ‘-‘ operator.” · Issue #29 · shiftkey/chocolatey-beyondcompare:
Archive for the ‘Chocolatey’ Category
Chocolatey on Windows 7: “You must provide a value expression on the right-hand side of the ‘-‘ operator.”
Posted by jpluimers on 2022/06/08
Posted in Chocolatey, CommandLine, Development, Microsoft Surface on Windows 7, Power User, PowerShell, PowerShell, Scripting, Software Development, Windows, Windows 10, Windows 7, Windows 8, Windows 8.1, Windows Server 2003, Windows Server 2003 R2, Windows Server 2008, Windows Server 2008 R2 | Leave a Comment »
Chocolatey 1.0.0 got released last week (chocolatey/choco · GitHub)
Posted by jpluimers on 2022/03/24
Last week finally there was the stable [Wayback/Archive] Release version 1.0.0 · chocolatey/choco · GitHub.
So I fixed the Wikipedia page
- from: [Wayback/Archive] Chocolatey – Wikipedia (only mentioning 0.12.1 preview release)
- to: [Wayback/Archive] Chocolatey – Wikipedia (now including the 1.0.0 stable release)
It was a few days after the 11th birthday “Celebration”: [Wayback/Archive] Chocolatey Software Blog | This One Goes To 11! Celebrating 11 Years Of Chocolatey. Not a really festive post, though it does have a really nice overview of 11 years of Chocolatey history and clearly showing the momentum of it has been a few years behind us.
The thing is: hardly anybody noticed the celebration nor the 1.0.0 release. Being at various 0.* versions for like a decade makes people not follow sudden version bumps closely. I only noticed when updating a bunch of testing VMs of which one had a problem, so I inspected the logs and saw the 1.0.0 version.
So these recent tweets did not gain much attention:
- 20220321: [Wayback/Archive] Chocolatey on Twitter: “Join us in ONE HOUR to mark a milestone in Chocolatey history! No excuses. Take the dog out. Grab a coffee. Sit down. Watch us on Twitch. 4pm UTC. “
- 20220320: [Wayback/Archive] Chocolatey on Twitter: “Join the Chocolatey Team TOMORROW, 21 March, and mark a milestone in Chocolatey history! On Twitch. 4pm UTC. And join our Discord server for a little thank you to our Community. “
- 20220317: [Wayback/Archive] Chocolatey on Twitter: “ICYMI we have a … special event marking a milestone in Chocolatey history this Monday, 21 March at 4pm UTC. Join @pauby, @gep13 and the @chocolateynuget Team. And join our Discord server for a little thank you to our Community. “
Anyway: the release notes indicate a few things scheduled for 2.0.0. Given the sudden 0.12.0 -> 1.0.0 bump, I have no clue far (or near!) in the future that will be.
It is kind of both a saddening and relieved feeling: like for instance Stack Overflow/Stack Exchange (both in the same age cohort as Chocolatey), Chocolatey is just there and mostly works.
–jeroen
Share this:
Posted in .NET, Batch-Files, C#, Chocolatey, CommandLine, Development, Power User, PowerShell, PowerShell, Scripting, Software Development, Windows | Leave a Comment »
Chocolatey Software | NirLauncher
Posted by jpluimers on 2021/12/27
The cool thing about the Chocolatey NirLauncher install, is that it not just installs the launcher in the path, but all the NirSoft tools.
I wanted it in the path initially because I needed InsideClipboard to do some investigation (I wrote a similar tool ages ago, but could not readily find the source or executable, but InsideClipboard is better anyway).
This is cool, as I now can start any of the NirSoft tools from the cmd prompt, including [WayBack] NirLauncher itself, [WayBack] InsideClipboard and [WayBack] NirCmd (so I can now set the sound volume to 25% by running nircmd setsysvolume 16000)
To install:
choco install --yes NirLauncher
An older WayBack link notes a few important issues about anti-virus tools:
Share this:
Posted in Chocolatey, NirSoft, Power User, Windows, Windows 10 | Leave a Comment »
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
/Sysinternalspackage 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
Related:
Share this:
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.
Related:
- [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%\toolsaccording 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
Share this:
Posted in .NET, Chocolatey, CommandLine, Development, Power User, PowerShell, PowerShell, Scripting, Software Development, Windows | Leave a Comment »
The Wiert Corner - irregular stream of stuff 