I also have a question regarding Install-ChocolateyPinnedTaskBarItem I cant seem to get it to work I receive the following:
You can only use these functions within a Chocolatey package. If you want to use them directly from PowerShell then you can import them using
Import-Module -Name $env:ChocolateyInstall\helpers\chocolateyinstaller.psm1 - your mileage may vary though on how useful they will be outside of choco.
kb2919355to fix the error, but with no success.:
Install-ChocolateyZipPackageis what it uses.
2020-05-21 14:24:55,865 1156 [INFO ] - Attempt to get headers for https://www.moddb.com/downloads/mirror/115776/115/b01122bc16305be9600384db0cc32f05 failed. The remote file either doesn't exist, is unauthorized, or is forbidden for url 'https://www.moddb.com/downloads/mirror/115776/115/b01122bc16305be9600384db0cc32f05'. Exception calling "GetResponse" with "0" argument(s): "The request was aborted: Could not create SSL/TLS secure channel."
refererheader as well
@n3rd4i After a reboot there is the same error. If it's always worked and doesn't work now could be they've changed something so I'd look at what @AdmiringWorm said.
If you don't need some of those KB's (you mentioned you added KB2919355 to get it through the Verifier) please also remove them.
all chocolatey packages will, yes... but that doesn't necessarily mean the thing they're wrapping will be installed to the same place. Typically installers aren't super aware of chocolatey and will do their own thing. That's not 100% avoidable in all cases, but some packages do expose package parameters to adjust the install location options for their installers.
There's also a more widely available option to set the install directory on everything choco knows how to handle properly (~95%+ of installers, give or take) but that's only available in the Pro / Business editions of Chocolatey :)
the chocolatey package itself will be kept in C:\ProgramData -- if the installer it contains installs itself into whatever location it was told to by the chocolatey package, or whatever default was set. Same for its registration in Programs & Features.
As a rule, we don't go out modifying and re-packaging other vendors' binaries or installers; it's very hard to guarantee that's in any way safe for the end user. Instead, Chocolatey wraps the binary/installer in its own package that it can handle and can run any additional required actions on install/uninstall if the installation has specific requirements.
If the vendor intended it to register in Programs and Features, we're not going to pull that out, it's a core part of the Windows ecosystem. if they provide a way to change the default installation directory, then that can be exposed as part of the Chocolatey package's parameters.