Archive for the ‘Chocolatey’ Category
Posted by jpluimers on 2025/09/03
I needed the portable version of [Wayback/Archive] CrystalDiskMark on Chocolatey (unlike the [Wayback/Archive] Chocolatey Software | CrystalDiskMark (Install) package). Luckily I found the auto-update package [Wayback/Archive] Chocolatey Software | CrystalDiskInfo (Portable) and knew both that CrystalDiskMark is from the same author as CrystalDiskInfo, and that their code is on GitHub like the Chocolatey package.
Given I had a the below chocolatey-packages/automatic/crystaldiskinfo.portable as a template, I asked the CrystalDiskInfo (Portable) package maintainer if they were willing to maintain CrystalDiskMark (portable) as well and was glad the response was “yes”: [Wayback/Archive] Portabe CrystalDiskMark similar to the current CrystalDiskInfo? · Issue #159 · mkevenaar/chocolatey-packages
So for my link-archive:
Read the rest of this entry »
Posted in .NET, Chocolatey, CommandLine, Development, Lightweight markup language, MarkDown, Power User, PowerShell, PowerShell, Scripting, Software Development, Windows | Tagged: 159, 16 | Leave a Comment »
Posted by jpluimers on 2025/08/08
Chocolatey extends the NuGet file format .nuspec based XML files as base for their packages with at the time of writing very sparse and limited documentation in what it extends, why it does that and what extra limitations it imposes on the fields used inside .nuspec files.
Hopefully by now that has improved, so this post is a reminder to myself to check that out eventually.
At the time of writing, the NuGet .nuspec documentation was at [Wayback/Archive] .nuspec File Reference for NuGet | Microsoft Learn and the file format at [Wayback/Archive] NuGet.Client/nuspec.xsd at dev · NuGet/NuGet.Client. Most fields are defined as primitive data types xs:boolean, xs:string and xs:anyURI (of the 19 available primitive XML SChema (W3C) types). Some composite data types are are composed from them using local and global complexType, most using xs:all, xs:attribute or single-type unbounded xs:sequence (which all imply no particular order).
Since an XML Schema allows to both use restriction and extension on data types (the eXtensible in XML!), making them more strict is a relatively straight-forward operation and has the benefit of having these in a central place.
In the past for more than 5 years [Wayback/Archive] Is there a specification for the package format? · Issue #379 · chocolatey/choco was just pointing to the NuGet .nuspec format, but after a request to re-open new comments were made pointing to a current issue (basically a stub, but still) and a Chocolatey nuspec.xsd file, yay!
Still it was a quest to figure out the additional rules they have added, especially since the documentation was sparse and sloppy.
Read the rest of this entry »
Posted in Chocolatey, Development, Power User, Windows, Windows 10, Windows 11, Windows 7, Windows 8, Windows 8.1, XML/XSD, XSD | Tagged: 101, 172, 205, 325, 374, 379, 4 | Leave a Comment »
Posted by jpluimers on 2025/08/01
A few notes after I helped updating [Wayback/Archive] Chocolatey Software | SetACL (Portable) 3.0.6.0 to version 3.1.2.0 and [Wayback/Archive] Updates glab from 1.22.0 to 1.24.1; fixes #2 by jpluimers · Pull Request #3 · corbob/ChocoPackages.
As the burden on maintainers (not just Chocolatey ones) is high, not all packages get updated soon after new underlying software versions arrive.
Which means the maintainers are often very happy when an occasional user helps and preferably sends in a pull request.
That brings me to the an important point IN DOCUMENTATION DO NOT LIMIT EXAMPELS TO ONLY ABBREVIATED PARAMETERS OR VERBS as that scares away occasional and novice users of your software.
Chocolatey documentation is no exception on this, hence this blog post meant for people other than maintaining chocolatey packages on a day to day base.
Read the rest of this entry »
Posted in CertUtil, Chocolatey, CommandLine, Conference Topics, Conferences, Development, Event, Power User, PowerShell, PowerShell, Scripting, Software Development, Windows | Tagged: 2, 2850, 3, 309, 561 | Leave a Comment »
Posted by jpluimers on 2025/04/02
Steps for installing Chocolatey on Windows 11 and up or 10 version 1803 and up.
Since I often install Windows on machines where it is not easy to copy/paste longer install commands my steps are slightly different than the ones on [Wayback/Archive] Chocolatey Software | Installing Chocolatey:
- Start a regular command prompt
- Either these two (the options are equivalent, see [Wayback/Archive] curl: transfer a URL | curl Commands | Man Pages | ManKier for
--remote-name and -O):
curl --remote-name https://community.chocolatey.org/install.ps1curl -O https://community.chocolatey.org/install.ps1
Note the cURL pre-installed on Windows 10 since at least 6 years*: release 1803 or insider build 17063 is good enough to download the Chocolatey install script
- Inspect the downloaded
install.ps1 to check if you spot anything you dislike
- Start an elevated (administrator) command prompt
- Start PowerShell
- Execute this command
Set-ExecutionPolicy Bypass -Scope Process -Force
- Execute this command in the folder where you downloaded
install.ps1
- Yup, a custom build of cURL has been pre-installed on Windows 10 and up since more than 6 years:
Read the rest of this entry »
Posted in *nix, *nix-tools, Chocolatey, cURL, Development, Power User, Software Development, Windows, Windows 10, Windows 11, Windows Development | Leave a Comment »
Posted by jpluimers on 2025/03/26
Posted in .NET, C#, Chocolatey, CommandLine, Development, Power User, PowerShell, PowerShell, Scripting, Software Development, Windows | Tagged: 1018 | Leave a Comment »
Posted by jpluimers on 2025/01/07
Since every now and then, like testing software developed with older tools, you need to run older software.
This always works: [Wayback /Archive] Deploy .NET Framework 3.5 by using Deployment Image Servicing and Management (DISM) | Microsoft Learn
DISM /Online /Enable-Feature /FeatureName:NetFx3 /All
Use /All to enable all parent features of the specified feature.
(The /All is needed because software requiring .NET Framework 3.5 also require the parent features).
Notes:
- Tested on Windows 10 and Windows 11 in 2022.
- It can take a really long time (more than just a few minutes!) even on fast connections.
- Installing through Chocolatey with `choco install
dotnet3.5 fails on Windows 11 (have not tried on Windows 10) with the classical red on black PowerShell default error theme*:
ERROR: The term 'wmic' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
The install of DotNet3.5 was NOT successful.
Error while running 'C:\ProgramData\chocolatey\lib\DotNet3.5\Tools\ChocolateyInstall.ps1'.
Read the rest of this entry »
Posted in .NET, .NET 3.0, .NET 3.5, C#, Chocolatey, Development, Power User, PowerShell, Software Development, Windows, Windows 10, Windows 11 | Leave a Comment »
Posted by jpluimers on 2024/09/19
Reminder to check-out of the 2015 issue mentioned in the tweets below has been had any progress.
At the time of tweeting, choco has no notion of [Wayback/Archive] status.chocolatey.org which would be very helpful to point to in case of errors on time-outs on chocolatey server calls especially if it could interrogate and inform of maintenance windows and outages when things fail on the client side.
Read the rest of this entry »
Posted in .NET, Chocolatey, CommandLine, Development, PowerShell, PowerShell, Scripting, Software Development, Windows | Leave a Comment »
Posted by jpluimers on 2024/07/01
This happens a lot with apps that auto-update before package manager contain that update: [Wayback/Archive] MSI installation error 1603 – Windows Server | Microsoft Learn
Cause
You may receive this error message if any one of the following conditions is true:
- Windows Installer is attempting to install an app that is already installed on your PC.
- The folder that you are trying to install the Windows Installer package to is encrypted.
- The drive that contains the folder that you are trying to install the Windows Installer package to is accessed as a substitute drive.
- The SYSTEM account does not have Full Control permissions on the folder that you are trying to install the Windows Installer package to. You notice the error message because the Windows Installer service uses the SYSTEM account to install software.
Query: [Wayback/Archive] Exit code was ‘1603’ – Google Search
--jeroen
Posted in Chocolatey, Power User, Windows | Leave a Comment »
Posted by jpluimers on 2024/03/06
I totally missed this feature got implemented: [Wayback/Archive] Use Remembered Arguments for a Package During Upgrades · Issue #797 · chocolatey/choco. I also seem to be lucky I have not tried it out yet (:
I bumped into it via [Wayback/Archive] Chocolatey Software | Notepad++ 8.4.4, which had this interesting comment:
If you want Notepad++ 32 bit and you want it to stay on 32 bit with upgrades, ensure you are on Chocolatey 0.10.4 (or newer). Then add `-x86` to your installation arguments. Then turn on the remembered arguments feature with ‘choco feature enable -n useRememberedArgumentsForUpgrades‘ – this will ensure that `-x86` gets passed on upgrade when running `choco upgrade all`. For more information on how this works, see https://github.com/chocolat…797
First of all, if you started using Chocolatey at or before 0.14, the useRememberedArgumentsForUpgrades feature is disabled by default and kept that way even after upgrading to the most recent version. You can see executing choco feature list on a system that started with Chocolatey:
Read the rest of this entry »
Posted in Chocolatey, Development, Power User, Scripting, Software Development, Windows | Leave a Comment »
The Wiert Corner - irregular stream of stuff 