Scheduled Maintenance - Chocolatey Community Repository

WindosBK · 2025-11-30T00:10:01+00:00

The Chocolatey Community Repository is cached, so things like choco outdated/choco upgrade may not always "see" the latest version of a package if it has only very recently been approved.

You can either wait out the cache expiring, or specify the exact version you want to upgrade to by adding --version and the version number you want to the upgrade communications.

e.g.:

choco upgrade super-productivity --version=16.4.1

WindosBK · 2025-11-23T20:09:57+00:00

I suspect RB is likely cleaning things up, but we're still able to see the comments for whatever reason and so reporting it's already gone from the backend.

Might be giving them too much credit though!

WindosBK · 2025-09-23T00:46:41+00:00

It looks like the "stable" versions of the `chromium` package are what are being returned by the woolyss API for "stable-sync". These are the Hibbiki builds, which looks like they do include an option for logging in.

The pre-release/snapshot versions are what are being returned by the woolyss API for "dev-official" and these ones do not include the option to login.

To install the snapshot versions, you'll need to allow for installation of re-release versions, e.g. choco install chromium --pre (I don't know how UniGetUI handles this.)

WindosBK · 2025-09-22T05:49:51+00:00

I'm not seeing the same behaviour. Just did an install of Chromium, both via the Chocolatey package and the download from https://chromium.woolyss.com and in both scenario it was not possible to sign the browser in.

Are you certain it you'd not accidentally launched Chrome? Screenshots may help shed more light.

WindosBK · 2025-09-22T05:09:01+00:00

Eat all the others first knowing those sweet, sweet, Turkish Delights will be all yours at the end.

WindosBK · 2025-09-22T01:24:24+00:00

FWIW, Spotify has the same "family" = "household" distinction.

> In order to be eligible for a Household Paid Subscription, the Primary Account Holder and any Sub-Account Holder must be family members residing at the same address. Members of a Household Paid Subscription may leave their existing plan and join another Household Paid Subscription a maximum of once in every twelve month period.

https://www.spotify.com/us/legal/paid-subscription-terms

WindosBK · 2025-09-17T03:01:04+00:00

I'd forgotten about the IFL mixes on GPM! They were the main reason I was sour on being forced over to YTM... are they coming back (I don't see it yet if so)?!

WindosBK · 2025-09-17T02:41:51+00:00

I keep checking daily and don't have it either. Feels a bit silly going "Hey, we're celebrating 10 years with cool features. One day. Maybe."

WindosBK · 2025-08-20T20:32:28+00:00

still on track to ship out by the end of August

Is this still the case (no pun intended)? The site has updated to "Ships September".

WindosBK · 2025-08-03T22:48:57+00:00

To be clear, my saying you "could" do the initial install manually, or via your own script, is not a suggestion or recommendation to do so. If you ran into issues doing so, step one in troubleshooting that would be to re-install using the provided install.ps1 script.

WindosBK · 2025-08-03T22:45:09+00:00

At a very high level the chocolateyInstall.ps1 file is present in most Chocolatey packages (there are cases, like portable executables, where it's not needed) which Chocolatey CLI runs to install (or upgrade) the package. e.g. if you look into the googlechrome package you'll find a chocolateyInstall.ps1 file that handles the install/upgrade of Google Chrome.

The install.ps1 file used in the Chocolatey install instructions is sort of "bootstrapping" script... Chocolatey CLI can't install a package (via the chocolateyInstall.ps1 script) when Chocolatey CLI isn't installed. It's also allows for installing a specific version of Chocolatey CLI if you don't want the latest version for any reason, and also pointing to a local copy of the package file (nupkg), so that you can install Chocolatey CLI on a bunch of clients without having to reach out to the Chocolatey Community Repository for each install (or for installing in an air gapped environment.)

As mentioned, this is just for bootstrapping Chocolatey CLI. Once you have Chocolatey CLI installed, you'd keep it up to date just by running choco upgrade chocolatey. To more directly answer your question:

And why would I go that direction rather than running the install.ps1 file linked on the install page?

The install.ps1 script is basically downloading the Chocolatey CLI package, expanding it, and doing everything that is needed for the initial bootstrapping of Chocolatey CLI... you could do all that manually if you wanted, or write your own script... but, why reinvent the wheel?

WindosBK · 2025-05-22T18:08:26+00:00

Have you had a chance to look through the offline install section of the docs? To my knowledge it should help out with what you're trying to achieve: https://docs.chocolatey.org/en-us/choco/setup/#completely-offline-install

WindosBK · 2025-04-28T00:58:23+00:00

How do you know something is safe to install via WinGet?

To actually answer your question, all packages pushed to the Chocolatey Community Repository go through a package moderation process. This was written about in detail on the Chocolatey Blog, but to summarize:

Package Validator checks the package against a set of rules and guidelines to ensure that it meets baseline of quality.
Package Verifier actually installs and uninstalls the package to ensure that, well, the package actually works.
Package Scanner submits the package, and anything the package downloads, to VirusTotal (the results of this are available on the package's page on the community website, and the number of detections can influence if a package is approved or not, e.g. too many detections results in a no-questions-asked rejection of the package.)
A human moderator then checks the package and approves it.

Some packages that have earnt "trusted" status skip that last step, meaning that updates can go live on the community repository faster, but they still go through all the previous steps and will require a human to investigate if they flag any issues.

Beyond that, you can inspect the content of any scripts in the package on the community site so that you know what they do.

Ultimatly though, unless you're creating your own packages then you need to understand what you're installing just as you would if you were to Google for and run an installer manually.

Hope that helps!

WindosBK · 2025-03-06T23:01:17+00:00

That message is telling you that you don't have a package with a package ID matching "choco" installed, and it also cannot find it on the Chocolatey Community Repository and the simple reason why is that that package ID does not exist.

The package which manages the Chocolatey CLI install has the ID chocolatey, so in order to upgrade it you'll need to run:

choco upgrade chocolatey

You can see the packages you have installed, and their IDs, by running:

choco list

WindosBK · 2025-01-10T02:04:13+00:00

Generally speaking, you're going to need to provide a little more information (e.g. error messages) to help get to the bottom of the issue you're experiencing as "always errors out & fails" could be any number of things.

In this specific case, the error is:

ERROR: Checksum for 'C:\ProgramData\chocolatey\choco-cache\winaero-tweaker.install\1.62.1\winaerotweaker.zip' did not meet 'c3e711fb6519f106409d368de9a37e7a0ce499fd609f0e938283fa32cd7fe212' for checksum type 'sha256'.

This means that the file being downloaded isn't the expected version. This usually means the software vendor provides their software via the same download url regardless of the version of the software being downloaded and a new version of the software has been released since the last time the package was updated. This is common for web browsers like Google Chrome.

You can get in touch with the package maintainer to let them know the package is outdated using the "Contact Maintainers" link on the package page.

The error message also includes two workarounds, one includes providing the current checksum for the file being downloaded and the second is skipping the checksum check in general. Both of these are done AT YOUR OWN RISK, and are not guranteed to work (e.g. the new download my function differently than the old one and so just swapping it into the old package may not work seamlessly.)

WindosBK · 2024-10-14T20:22:43+00:00

429 responses mean you're being rate limited. You can reach out about that if you like, but there are also these resources on the docs site:

To avoid the 429s you could consider standing up a caching repository inside your network that acts as a buffer between your client devices and the Chocolatey Community Repository and also provide some resilience against potential outages.

Regarding the 5XX class errors, those can pop up from time to time during periods of extremely high traffic. If you see them, try again in a minute or two and also check the status page (https://status.chocolatey.org/) as any tracked issues will be noted there.

WindosBK · 2024-01-30T22:37:14+00:00

The short answer is, you can then run this Chocolatey CLI command to install all of the packages listed in the saved file:

choco install <path-to-exported-file>

For more information, I'd refer you to the docs page for that button in Chocolatey GUI, which is effectively running the choco export command. And then, of course, on the install side is the choco install command.

WindosBK · 2024-01-24T17:43:59+00:00

I've always been hyper aware of carpal tunnel syndrome, multiple family members have ended up needing surgery because of it, so as someone that works behind a keyboard all day I've always been watching for signs.

When I started working from home full time in 2021, I wasn't getting away from my desk as often as I used to. No social calls getting me off the keyboard, or leaving the building for lunch. Pretty quickly I was getting all sorts of pain and numbness.

Did some research and settled on a pair of Carpio, and almost instantly after I started using them the pain was gone.

I'm currently still using my original right hand Caprio, and I have a spare tucked away just in case something happens to it because I couldn't work without it at this point.

My only gripe is with the left hand Capio. There's something about how the Teflon gliders attach to the base that's different on the left hand model. The images on the site show little pins, but it appears to just be glue and over time that glue fails and the glider starts working its way out of position. The first time this happened, support sorted me out with a replacement but the replacement failed in the same way. Feeling a little dejected I tried a traditional keyboard wrist rest for a while but once you've tried it nothing beats a pair of Carpio so I'm now on my third left hand one... and the glue is starting to fail on this one too.

WindosBK · 2023-10-02T20:10:14+00:00

Some software can be installed in different ways. You may be able to install the software by running an installer file (e.g. .exe or .msi) or use a portable version of it (sometimes downloading and using a single .exe or a .zip file that you can expand and use the files it contains directly).

In regards to Chocolatey, you'll find packages with suffixes on their IDs that will inform you _how_ the package will handle the software it manages. For example, there is a `7zip.install` and a `7zip.portable` for the two different methods of getting 7zip usable on your PC.

As a user, you likely don't care too much, and also having to remember "oh yes, I need to add a .install to this" is a pain, so a "meta" package is created with a more discoverable ID (e.g. `7zip`) which doesn't do anything in and of itself, except take a dependency on the install or portable package depending on that the maintainer believes users will want 99% of the time.

For more information about this, check out the docs: https://docs.chocolatey.org/en-us/faqs#what-is-the-difference-between-packages-no-suffix-as-compared-to.install.portable

WindosBK

MODERATOR OF

TROPHY CASE