chocopkgs's People
Forkers
mattia72 hvindin 9999years squishleheimer anton-latukha ottnorml ethersecagent boxrick timkatje dmxt c22 deldrinov flcdrg lostmsu hadogenes brandondyck atom134 eloston zoullx akirayamamoto thecakeisnaoh brogers5 slycordinatorchocopkgs's Issues
obs-studio package updated but install/portable didn't
version 27.2.0
Update mpv
The 0.35.1 bug fix release of mpv from Jan 28 is not on chocolatey, please update the mpv etc. packages.
Lua installer is 32 bit only
I am seeing failures when the 64 bit Visual Studio compiler is set up. Works OK for the 32bit compiler.
Same problem occurs with andyli/luarocks-choco#1
I assume the problem with this package is due to rjpcomputing/luaforwindows#103
As that probably isnt fixable easily, so perhaps documenting the limitation is the only viable solution atm.
(mpv) mpv: update available
Dear all,
this package is outdated.
Currently, there is Release 0.36.0, mpv/RELEASE_NOTES at master · mpv-player/mpv.
Please, update.
vcxrv package is outdated, 1.19.5.2 is out
vcxrv package is outdated, 1.19.5.2 is out
https://sourceforge.net/projects/vcxsrv/files/vcxsrv/1.19.5.2/
new package: anti micro x
package vcxsrv
http://sourceforge.net/projects/vcxsrv/
more updated than xming. better?
`mpv --version` is wrong in latest mpv packages
Hi, I've been trying to use mpv in a github action for integration test and noticed this issue in the latest mpv/mpvio packages.
> Run mpv --version
mpv 1c9c2f5 Copyright © 2000-2023 mpv/MPlayer/mplayer2 projects
built on Dec 10 2023 12:02:37
libplacebo version: v6.338.0-62-g52314e0-dirty
FFmpeg version: N-112938-g12e25af7a
FFmpeg library versions:
libavutil 58.32.100
libavcodec 60.35.100
libavformat 60.18.100
libswscale 7.6.100
libavfilter 9.14.100
libswresample 4.13.100
The version seems to use the hash from shinchiro/mpv-winbuild-cmake@1c9c2f5 instead of the actual version of mpv.
I've tried the releases from sourceforge on a Windows computer and noticed the same issue on the 0.37.0 build but the latest build at this time (mpv-x86_64-v3-20231231-git-abc2a74.7z) does seem to return a correct version.
Could you update the mpv package to a newer build that doesn't have this issue and maybe also fix it for mpvio although it seems like a slightly more involved fix.
Thanks!
(PS: I also couldn't get it to work with choco install mpv --version=2023.01.28
and I'm not sure why, it seems to still install the latest version)
vim-tux.* packages have high AV counts
On 26 November I sent a message through the 'Contact Maintainers' link on the package page of vim-tux.install
and vim-tux.portable
with no response.
There are currently 9 packages for .install and 8 packages for .portable waiting for you to take action. Please do not submit any further packages to the Chocolatey Community Repository until this issue has been addressed. Please reach out to the moderators in the moderation comments on the package page.
wsltty 3.7.1: ERROR: Cannot bind argument to parameter 'Path' because it is an empty string
Some problem with installing wsltty:
Here is the log file:
2024-03-03 22:55:22,541 2124 [DEBUG] - ---------------------------Script Execution---------------------------
2024-03-03 22:55:22,545 2124 [DEBUG] - Running 'ChocolateyScriptRunner' for wsltty v3.7.1 with packageScript 'C:\ProgramData\chocolatey\lib\wsltty\tools\chocolateyinstall.ps1', packageFolder:'C:\ProgramData\chocolatey\lib\wsltty', installArguments: '', packageParameters: '', preRunHookScripts: '', postRunHookScripts: '',
2024-03-03 22:55:22,562 2124 [DEBUG] - Running package script 'C:\ProgramData\chocolatey\lib\wsltty\tools\chocolateyinstall.ps1'
2024-03-03 22:55:22,636 2124 [DEBUG] - Running Get-OSArchitectureWidth -compare '64'
2024-03-03 22:55:23,832 2124 [DEBUG] - Running Install-ChocolateyShortcut -shortcutFilePath 'C:\ProgramData\Microsoft\Windows\Start Menu\Programs\WSL Generate Shortcuts.lnk' -targetPath 'C:\ProgramData\chocolatey\lib\wsltty\tools\wslttyinstall\install.bat' -workingDirectory 'C:\ProgramData\chocolatey\lib\wsltty\tools\wslttyinstall'
2024-03-03 22:55:23,855 2124 [DEBUG] - Creating Shortcut...
2024-03-03 22:55:24,011 2124 [DEBUG] - Shortcut created.
2024-03-03 22:55:24,043 2124 [ERROR] - ERROR: Cannot bind argument to parameter 'Path' because it is an empty string.
2024-03-03 22:55:24,089 2124 [DEBUG] - Built-in PowerShell host called with ['[System.Threading.Thread]::CurrentThread.CurrentCulture = '';[System.Threading.Thread]::CurrentThread.CurrentUICulture = '';[System.Net.ServicePointManager]::SecurityProtocol = [System.Net.SecurityProtocolType]::SystemDefault; & import-module -name 'C:\ProgramData\chocolatey\helpers\chocolateyInstaller.psm1'; & 'C:\ProgramData\chocolatey\helpers\chocolateyScriptRunner.ps1' -packageScript 'C:\ProgramData\chocolatey\lib\wsltty\tools\chocolateyinstall.ps1' -installArguments '' -packageParameters '' -preRunHookScripts $null -postRunHookScripts $null'] exited with '-1'.
2024-03-03 22:55:24,094 2124 [DEBUG] - Calling command ['"C:\WINDOWS\System32\shutdown.exe" /a']
2024-03-03 22:55:24,151 2124 [DEBUG] - Command ['"C:\WINDOWS\System32\shutdown.exe" /a'] exited with '1116'
2024-03-03 22:55:24,399 2124 [DEBUG] - Capturing package files in 'C:\ProgramData\chocolatey\lib\wsltty'
2024-03-03 22:55:24,411 2124 [DEBUG] - Found 'C:\ProgramData\chocolatey\lib\wsltty\wsltty.nupkg'
with checksum '47F3F0EE087BBD68141971FE00C09C97'
2024-03-03 22:55:24,414 2124 [DEBUG] - Found 'C:\ProgramData\chocolatey\lib\wsltty\wsltty.nuspec'
with checksum 'D1201C2FE22B3EDFF66E367820CF79C0'
2024-03-03 22:55:24,416 2124 [DEBUG] - Found 'C:\ProgramData\chocolatey\lib\wsltty\tools\chocolateyinstall.ps1'
with checksum '038A304A7A66771122B61B3D1B7B4516'
2024-03-03 22:55:24,418 2124 [DEBUG] - Found 'C:\ProgramData\chocolatey\lib\wsltty\tools\chocolateyuninstall.ps1'
with checksum 'FF3013F1063ECB5F5B77452B2E4435CC'
2024-03-03 22:55:24,420 2124 [DEBUG] - Found 'C:\ProgramData\chocolatey\lib\wsltty\tools\LICENSE.mintty.txt'
...
2024-03-03 22:55:24,525 2124 [DEBUG] - Found 'C:\ProgramData\chocolatey\lib\wsltty\tools\wslttyinstall\wslbridge2.exe'
with checksum '7B059F7324E699BD3DEDE1156F432483'
2024-03-03 22:55:24,528 2124 [DEBUG] - Found 'C:\ProgramData\chocolatey\lib\wsltty\tools\wslttyinstall\wsltty home & help.url'
with checksum '46B926975285C5C892C77336B4F718B6'
2024-03-03 22:55:24,530 2124 [DEBUG] - Found 'C:\ProgramData\chocolatey\lib\wsltty\tools\wslttyinstall\zoo.exe'
with checksum 'DA3FC1DBBB51DC2224387C82F68102C3'
2024-03-03 22:55:24,562 2124 [DEBUG] - Attempting to delete file "C:\ProgramData\chocolatey\.chocolatey\wsltty.3.7.1\.arguments".
2024-03-03 22:55:24,564 2124 [DEBUG] - Attempting to delete file "C:\ProgramData\chocolatey\.chocolatey\wsltty.3.7.1\.extra".
2024-03-03 22:55:24,565 2124 [DEBUG] - Attempting to delete file "C:\ProgramData\chocolatey\.chocolatey\wsltty.3.7.1\.version".
2024-03-03 22:55:24,567 2124 [DEBUG] - Attempting to delete file "C:\ProgramData\chocolatey\.chocolatey\wsltty.3.7.1\.sxs".
2024-03-03 22:55:24,568 2124 [DEBUG] - Attempting to delete file "C:\ProgramData\chocolatey\.chocolatey\wsltty.3.7.1\.pin".
2024-03-03 22:55:24,578 2124 [DEBUG] - Attempting to delete directory "C:\ProgramData\chocolatey\lib-bad\wsltty".
2024-03-03 22:55:24,604 2124 [DEBUG] - Sending message 'HandlePackageResultCompletedMessage' out if there are subscribers...
2024-03-03 22:55:24,610 2124 [ERROR] - The install of wsltty was NOT successful.
2024-03-03 22:55:24,654 2124 [ERROR] - Error while running 'C:\ProgramData\chocolatey\lib\wsltty\tools\chocolateyinstall.ps1'.
See log for details.
2024-03-03 22:55:24,678 2124 [DEBUG] - Attempting to create directory "C:\ProgramData\chocolatey\lib-bad\wsltty".
2024-03-03 22:55:24,682 2124 [DEBUG] - Moving C:\ProgramData\chocolatey\lib\wsltty to C:\ProgramData\chocolatey\lib-bad\wsltty\3.7.1
2024-03-03 22:55:24,690 2124 [DEBUG] - Moving 'C:\ProgramData\chocolatey\lib\wsltty'
to 'C:\ProgramData\chocolatey\lib-bad\wsltty\3.7.1'
2024-03-03 22:55:26,724 2124 [WARN ] -
Chocolatey installed 0/1 packages. 1 packages failed.
See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log).
2024-03-03 22:55:26,727 2124 [INFO ] -
2024-03-03 22:55:26,728 2124 [ERROR] - Failures
2024-03-03 22:55:26,731 2124 [ERROR] - - wsltty (exited -1) - Error while running 'C:\ProgramData\chocolatey\lib\wsltty\tools\chocolateyinstall.ps1'.
See log for details.
2024-03-03 22:55:26,736 2124 [DEBUG] - Sending message 'PostRunMessage' out if there are subscribers...
2024-03-03 22:55:26,740 2124 [DEBUG] - Exiting with -1
mpv has a new version (v0.33.0)
Could you please update the Chocolatey package?
possibly create lf package
Installs incorrect version of Nvidia display drivers
The update to 496.13 still downloads 472.12
mpv: Document the user scripts folder
Proof: mpv-player/mpv@bd7ff23
Alright, when people want to customize mpv on Windows, they must open Explorer to the %APPDATA%
folder, and go into (or create) the mpv
folder there. In that folder they place their input.conf, mpv.conf, scripts dir, etc. :-)
Example for me:
%APPDATA%\mpv
is C:\Users\XXXXXXXXXXX\AppData\Roaming\mpv
This needs to be in the Chocolatey package info/description (such as with choco info mpv
). Preferably also as a Write-Host
message after mpv package has been installed. Just a simple note to say where people should place their config files, since mpv is a player that is very focused around "custom configs". :-)
Mpv out of date
https://sourceforge.net/projects/mpv-player-windows/files/stable/ Its at 0.31, if you want to track stable releases.
nvidia-display-driver needs to update
Whatever deployment automation you're using seems to be stuck after NVIDIA's latest driver update, 537.34.
NVidia GeForce Game Ready driver package fails to uninstall
Package: geforce-game-ready-driver
Version: 466.77
Output: Exception calling "GetFullPath" with "1" argument(s): "The path is not of a legal form."
Install Log
2021-06-14 18:57:23,407 11308 [DEBUG] - ---------------------------Script Execution---------------------------
2021-06-14 18:57:23,407 11308 [DEBUG] - Running 'ChocolateyScriptRunner' for geforce-game-ready-driver v466.77 with packageScript 'C:\ProgramData\chocolatey\lib\geforce-game-ready-driver\tools\chocolateyuninstall.ps1', packageFolder:'C:\ProgramData\chocolatey\lib\geforce-game-ready-driver', installArguments: '', packageParameters: '',
2021-06-14 18:57:23,407 11308 [DEBUG] - Running 'C:\ProgramData\chocolatey\lib\geforce-game-ready-driver\tools\chocolateyuninstall.ps1'
2021-06-14 18:57:23,438 11308 [DEBUG] - Running 'Get-UninstallRegistryKey' for 'geforce-game-ready-driver' with SoftwareName:'NVIDIA Graphics Driver*'
2021-06-14 18:57:23,438 11308 [INFO ] - VERBOSE: Retrieving all uninstall registry keys
2021-06-14 18:57:23,891 11308 [DEBUG] - Registry uninstall keys on system: 984
2021-06-14 18:57:23,891 11308 [DEBUG] - Error handling check: 'Get-ItemProperty' fails if a registry key is encoded incorrectly.
2021-06-14 18:57:24,423 11308 [DEBUG] - Found 0 uninstall registry key(s) with SoftwareName:'NVIDIA Graphics Driver*'
2021-06-14 18:57:24,423 11308 [DEBUG] - Running 'Get-UninstallRegistryKey' for 'geforce-game-ready-driver' with SoftwareName:'NVIDIA Graphics Driver*'
2021-06-14 18:57:24,423 11308 [INFO ] - VERBOSE: Retrieving all uninstall registry keys
2021-06-14 18:57:24,844 11308 [DEBUG] - Registry uninstall keys on system: 984
2021-06-14 18:57:24,844 11308 [DEBUG] - Error handling check: 'Get-ItemProperty' fails if a registry key is encoded incorrectly.
2021-06-14 18:57:25,407 11308 [DEBUG] - Found 0 uninstall registry key(s) with SoftwareName:'NVIDIA Graphics Driver*'
2021-06-14 18:57:25,423 11308 [DEBUG] - Running Uninstall-ChocolateyPackage -packageName 'geforce-game-ready-driver' -fileType 'EXE' -validExitCodes '0' -silentArgs ' -silent' -file ''
2021-06-14 18:57:25,438 11308 [INFO ] - Uninstalling geforce-game-ready-driver...
2021-06-14 18:57:25,469 11308 [DEBUG] - Running Start-ChocolateyProcessAsAdmin -validExitCodes '0' -statements ' -silent ' -exeToRun ''
2021-06-14 18:57:25,469 11308 [DEBUG] - Unable to use current location for Working Directory. Using Cache Location instead.
2021-06-14 18:57:25,485 11308 [DEBUG] - Test-ProcessAdminRights: returning True
2021-06-14 18:57:25,485 11308 [DEBUG] - Elevating permissions and running ["" -silent ]. This may take a while, depending on the statements.
2021-06-14 18:57:25,501 11308 [ERROR] - ERROR: Exception calling "GetFullPath" with "1" argument(s): "The path is not of a legal form."
2021-06-14 18:57:25,501 11308 [DEBUG] - Built-in PowerShell host called with ['[System.Threading.Thread]::CurrentThread.CurrentCulture = '';[System.Threading.Thread]::CurrentThread.CurrentUICulture = ''; & import-module -name 'C:\ProgramData\chocolatey\helpers\chocolateyInstaller.psm1'; & 'C:\ProgramData\chocolatey\helpers\chocolateyScriptRunner.ps1' -packageScript 'C:\ProgramData\chocolatey\lib\geforce-game-ready-driver\tools\chocolateyuninstall.ps1' -installArguments '' -packageParameters '''] exited with '-1'.
2021-06-14 18:57:25,501 11308 [DEBUG] - Calling command ['"C:\WINDOWS\System32\shutdown.exe" /a']
2021-06-14 18:57:25,532 11308 [DEBUG] - Command ['"C:\WINDOWS\System32\shutdown.exe" /a'] exited with '1116'
2021-06-14 18:57:25,532 11308 [ERROR] - geforce-game-ready-driver uninstall not successful.
2021-06-14 18:57:25,532 11308 [ERROR] - Error while running 'C:\ProgramData\chocolatey\lib\geforce-game-ready-driver\tools\chocolateyuninstall.ps1'.
See log for details.
2021-06-14 18:57:25,532 11308 [ERROR] - geforce-game-ready-driver not uninstalled. An error occurred during uninstall:
geforce-game-ready-driver uninstall not successful.
2021-06-14 18:57:25,532 11308 [WARN ] - Environment Vars (like PATH) have changed. Close/reopen your shell to
see the changes (or in powershell/cmd.exe just type refreshenv
).
2021-06-14 18:57:25,532 11308 [DEBUG] - Logging of values is not turned on by default because it
could potentially expose sensitive data. If you understand the risk,
please see choco feature -h
for information to turn it on.
2021-06-14 18:57:25,532 11308 [DEBUG] - The following values have been added/changed (may contain sensitive data):
2021-06-14 18:57:25,532 11308 [DEBUG] - * PATHEXT='[REDACTED]' (User)
2021-06-14 18:57:25,548 11308 [WARN ] -
Chocolatey uninstalled 0/1 packages. 1 packages failed.
See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log).
2021-06-14 18:57:25,548 11308 [INFO ] -
2021-06-14 18:57:25,548 11308 [ERROR] - Failures
2021-06-14 18:57:25,548 11308 [ERROR] - - geforce-game-ready-driver (exited -1) - Error while running 'C:\ProgramData\chocolatey\lib\geforce-game-ready-driver\tools\chocolateyuninstall.ps1'.
See log for details.
2021-06-14 18:57:25,548 11308 [WARN ] -
If a package uninstall is failing and/or you've already uninstalled the
software outside of Chocolatey, you can attempt to run the command
with -n
to skip running a chocolateyUninstall script, additionally
adding --skip-autouninstaller
to skip an attempt to automatically
remove system-installed software. This will only remove the packaging
files and not things like software installed to Programs and Features.
If a package is failing because it is a dependency of another package
or packages, then you may first need to consider if it needs removed
as it is typically installed as a dependency for a reason. If you
decide that you still want to remove it, head into
$env:ChocolateyInstall\lib
and find the package folder you want
removed. Then delete the folder for the package. This option should
only be used as a last resort.
2021-06-14 18:57:25,548 11308 [DEBUG] - Sending message 'PostRunMessage' out if there are subscribers...
2021-06-14 18:57:25,563 11308 [DEBUG] - Exiting with -1
[mpv] please use x86-v3 build.
nearly all Windows systems running MPV have x86-v3 instructions that accelerate video processing.
e.g.:
https://sourceforge.net/projects/mpv-player-windows/files/release/mpv-0.37.0-x86_64-v3.7z/download
[NVidia display driver] Option to disable extra components?
The audio driver tends to break integrated audio on my system.
I don't have a USB-C on the card either.
Could you add a "just the display driver" option?
VcXsrv outdated
There is a new version, v21.1.10 available at https://sourceforge.net/projects/vcxsrv/files/vcxsrv/21.1.10/
mpv outdated
latencymon package is outdated
Looks like software author/maintainer has updated the installer package. Probably best to push a new Chocolatey package release. Bypassing with --ignore-checksums works fine.
C:\Users\jdc>choco install latencymon
Chocolatey v1.2.0
Installing the following packages:
latencymon
By installing, you accept licenses for the packages.
Progress: Downloading latencymon 7.00.0.20210128... 100%
latencymon v7.00.0.20210128 [Approved]
latencymon package files install completed. Performing other installation steps.
Downloading LatencyMon
from 'https://www.resplendence.com/download/LatencyMon.exe'
Progress: 100% - Completed download of C:\Users\jdc\AppData\Local\Temp\chocolatey\latencymon\7.00.0.20210128\LatencyMon.exe (3.45 MB).
Download of LatencyMon.exe (3.45 MB) completed.
Error - hashes do not match. Actual value was '7DE921E0D395366AC6CA93C2FEE06DB08D0EF41EAE87FE6C11C75AC8DCD870AF'.
ERROR: Checksum for 'C:\Users\jdc\AppData\Local\Temp\chocolatey\latencymon\7.00.0.20210128\LatencyMon.exe' did not meet '77E90F0F042F9806639DE25C67FA78948696CB635C8F47C4F11E92CD6162A2AE' 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 latencymon was NOT successful.
Error while running 'D:\Util\Chocolatey\lib\latencymon\tools\chocolateyinstall.ps1'.
See log for details.
Chocolatey installed 0/1 packages. 1 packages failed.
See the log for details (D:\Util\Chocolatey\logs\chocolatey.log).
Failures
- latencymon (exited -1) - Error while running 'D:\Util\Chocolatey\lib\latencymon\tools\chocolateyinstall.ps1'.
See log for details.
advanced-renamer outdated and packages broken
Hi, Advanced Renamer 3.77 was released on the same day that the .install
package for 3.76 was approved. Attempting to update an older installation via chocolatey fails because the version downloaded (3.77) does not match the checksum expected (3.76).
Obviously the quick fix is to simply release a new package, but I think there's an opportunity to improve the package to avoid this problem in the future.
According to the chocolatey contribution guidelines it is now recommended to embed the installer in the package where possible. If I understand correctly, Advanced Renamer's license specifically permits this use case. Doing this will mean that the package is decoupled and won't break if upstream releases a new version.
Embedding the installer in the package will also enable the package to support multiple versions, useful for example in case the latest version causes problems then an older version can be installed manually.
If some examples of other packages using this method would be helpful, please see chocolatey-community/chocolatey-packages@c765203 and niks255/ChocolateyPackages@2f27851.
FEATURE REQUEST: Remove old extracted installation files
For a year plus now I've noticed that after the NVIDIA display drivers are installed I'm left with a C:\NVIDIA directory. Currently I have four old versions of the extracted installation files.
When I try to delete the folder to OCDly (I created a new word!) clean up my system volume, I get:
I can't delete it with my normal user/administrative account.
The fact it says SYSTEM is the owner might not be what everyone else gets. It might be due to the drivers being upgraded in the wee hours of the night by my https://chocolatey.org/packages/choco-upgrade-all-at package. I'm really not sure. (Someone please chime in and say if you have the same problem and if you installed manually or via Chocolatey under your normal admin account.)
It would be wonderful if you reset the permissions on the folder after install so that anyone can delete the files. It might be as is easy as changing the owner from SYSTEM to ADMINISTRATORS or USERS. (Needs some testing.)
After that a simple Remove-Item can clean up the files.
If you need help, here are some basic tutorials:
https://blogs.msdn.microsoft.com/johan/2008/10/01/powershell-editing-permissions-on-a-file-or-folder/
http://www.tomsitpro.com/articles/powershell-manage-file-system-acl,2-837.html
https://stackoverflow.com/questions/25779423/powershell-to-set-folder-permissions
Ironically I packaged this up a few months ago: https://chocolatey.org/packages/ntfssecurity-psmodule but haven't implemented it in any of my scripts yet. 😀
OBS Studio 28.0.3
https://github.com/obsproject/obs-studio/releases/tag/28.0.3
The Chocolatey package is currently still on 28.0.1
obs-studio.install failing with latest version of OBS (27.1.1)
ERROR: Running ["C:\ProgramData\chocolatey\lib\obs-studio.install\tools\OBS-Studio-27.1.1-Full-Installer-x64_x64.exe" /S ] was not successful. Exit code was '6'. Exit code indicates the following: Setup process was forcefully terminated by the debugger..
After the failure, Chocolatey thinks the install succeeded as it indicates the package was installed.
Chocolatey is latest version being run from a PowerShell Core prompt (latest version of posh core).
2021-09-29 08:08:15,821 1316 [INFO ] - Installing 64-bit obs-studio.install...
2021-09-29 08:08:15,824 1316 [DEBUG] - Running Start-ChocolateyProcessAsAdmin -validExitCodes '0' -workingDirectory 'C:\ProgramData\chocolatey\lib\obs-studio.install\tools' -statements '/S ' -exeToRun 'C:\ProgramData\chocolatey\lib\obs-studio.install\tools\OBS-Studio-27.1.1-Full-Installer-x64_x64.exe'
2021-09-29 08:08:15,824 1316 [DEBUG] - Test-ProcessAdminRights: returning True
2021-09-29 08:08:15,825 1316 [DEBUG] - Elevating permissions and running ["C:\ProgramData\chocolatey\lib\obs-studio.install\tools\OBS-Studio-27.1.1-Full-Installer-x64_x64.exe" /S ]. This may take a while, depending on the statements.
2021-09-29 08:08:18,386 1316 [DEBUG] - Command ["C:\ProgramData\chocolatey\lib\obs-studio.install\tools\OBS-Studio-27.1.1-Full-Installer-x64_x64.exe" /S ] exited with '6'.
2021-09-29 08:08:18,388 1316 [WARN ] - WARNING: Setup process was forcefully terminated by the debugger.
2021-09-29 08:08:18,583 1316 [ERROR] - ERROR: Running ["C:\ProgramData\chocolatey\lib\obs-studio.install\tools\OBS-Studio-27.1.1-Full-Installer-x64_x64.exe" /S ] was not successful. Exit code was '6'. Exit code indicates the following: Setup process was forcefully terminated by the debugger..
2021-09-29 08:08:18,586 1316 [DEBUG] - Built-in PowerShell host called with ['[System.Threading.Thread]::CurrentThread.CurrentCulture = '';[System.Threading.Thread]::CurrentThread.CurrentUICulture = ''; & import-module -name 'C:\ProgramData\chocolatey\helpers\chocolateyInstaller.psm1'; & 'C:\ProgramData\chocolatey\helpers\chocolateyScriptRunner.ps1' -packageScript 'C:\ProgramData\chocolatey\lib\obs-studio.install\tools\chocolateyinstall.ps1' -installArguments '' -packageParameters '''] exited with '6'.
(nvidia-display-driver) chocolateyInstall.ps1 failing when trying to upgrade
wsltty 3.7.1 update: The install of wsltty was NOT successful.
choco install wsltty
Chocolatey v2.2.2
Installing the following packages:
wsltty
By installing, you accept licenses for the packages.
Progress: Downloading wsltty 3.7.1... 100%
wsltty v3.7.1 [Approved]
wsltty package files install completed. Performing other installation steps.
The package wsltty wants to run 'chocolateyinstall.ps1'.
Note: If you don't run this script, the installation will fail.
Note: To confirm automatically next time, use '-y' or consider:
choco feature enable -n allowGlobalConfirmation
Do you want to run the script?([Y]es/[A]ll - yes to all/[N]o/[P]rint): y
ERROR: Cannot bind argument to parameter 'Path' because it is an empty string.
The install of wsltty was NOT successful.
Error while running 'C:\ProgramData\chocolatey\lib\wsltty\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
- wsltty (exited -1) - Error while running 'C:\ProgramData\chocolatey\lib\wsltty\tools\chocolateyinstall.ps1'.
See log for details.
From the log:
2024-02-29 01:42:03,696 2648 [DEBUG] - ---------------------------Script Execution---------------------------
2024-02-29 01:42:03,698 2648 [DEBUG] - Running 'ChocolateyScriptRunner' for wsltty v3.7.1 with packageScript 'C:\ProgramData\chocolatey\lib\wsltty\tools\chocolateyinstall.ps1', packageFolder:'C:\ProgramData\chocolatey\lib\wsltty', installArguments: '', packageParameters: '', preRunHookScripts: '', postRunHookScripts: '',
2024-02-29 01:42:03,702 2648 [DEBUG] - Running package script 'C:\ProgramData\chocolatey\lib\wsltty\tools\chocolateyinstall.ps1'
2024-02-29 01:42:03,715 2648 [DEBUG] - Running Get-OSArchitectureWidth -compare '64'
2024-02-29 01:42:04,777 2648 [DEBUG] - Running Install-ChocolateyShortcut -shortcutFilePath 'C:\ProgramData\Microsoft\Windows\Start Menu\Programs\WSL Generate Shortcuts.lnk' -targetPath 'C:\ProgramData\chocolatey\lib\wsltty\tools\wslttyinstall\install.bat' -workingDirectory 'C:\ProgramData\chocolatey\lib\wsltty\tools\wslttyinstall'
2024-02-29 01:42:04,780 2648 [DEBUG] - Creating Shortcut...
2024-02-29 01:42:04,817 2648 [DEBUG] - Shortcut created.
2024-02-29 01:42:04,822 2648 [ERROR] - ERROR: Cannot bind argument to parameter 'Path' because it is an empty string.
I ended up editing the install ps1 while it was waiting for my "Y", to get it to install:
# Remove installer
if ($filePath32) { Remove-Item -Force -ea 0 "$filePath32" }
if ($filePath64) { Remove-Item -Force -ea 0 "$filePath64" }
...but I don't know anything about PowerShell to be able to describe in technical detail why it now has an issue.
$PSVersionTable
Name Value
---- -----
PSVersion 7.4.1
PSEdition Core
GitCommitId 7.4.1
OS Microsoft Windows 10.0.19045
Platform Win32NT
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
WSManStackVersion 3.0
choco --version
2.2.2
mupen64plus is outdated
vim-tux is outldated
vim has upgraded to 8.0
Upgrade to Lua 5.3.3
Lua 5.3.3 was released recently. Please update the chocolatey packages for it.
wsltty outdated in chocolatey (but not in this repo)
In this repo, wsltty has been updated to 3.7.0.2
But in chocolatey, the latest version available is 3.6.4
It would be nice if the newer version were pushed to chocolatey.
Thanks
update mpv 0.38.0
(mpv) Old files left behind after package upgrade
Hi. Some files from previous versions are lying around in the lib > mpv.install
folder, like:
mpv-0.32.0-x86_64.7z.txt
mpv-0.33.0-x86_64.7z.txt
and so on. Is it possible to ensure these are deleted when the package is upgraded?
mpv.portable uninstall.ps1 necessary?
I remove the hardlinks I create, but I wonder if chocolatey will think they are shims and automatically remove them.
I need help .
hi,could you help me please?i had bought a used 3DdRudder, need help getting the latest software, upgrade the firmware (my firmware is 1.3.0.6),thank you very much!this is my email,[email protected],thank you for your help.good luck!
package scptoolkit
geforce-game-ready-driver on Win 10 Enterprise tries to install Win 8/7 version
Trying to debug this and adding this to the geforce-game-ready-driver/tools/chocolateyInstall.ps1:
$osversion = [System.Environment]::OSVersion
Write-Host $osversion
Returns Microsoft Windows NT 6.2.9200.0
, but I'm running this on Windows 10 Enterprise 1511. Not sure why the subshell is returning the incorrect version of the OS.
vim-x64: Write-Warning Explorer reboot
vim-tux.install: installation fails with an error
When I try to install vim-tux
the installation fails with ERROR: Operation did not complete successfully because the file contains a virus or potentially unwanted software.
C:\WINDOWS\system32>choco install -y vim-tux
Chocolatey v0.10.15
Installing the following packages:
vim-tux
By installing you accept licenses for the packages.
vim-tux.install v8.1.2333 [Approved]
vim-tux.install package files install completed. Performing other installation steps.
Attempt to use original download file name failed for 'C:\ProgramData\chocolatey\lib\vim-tux.install\tools\complete-x64_x64.exe'.
Copying vim-tux.install
from 'C:\ProgramData\chocolatey\lib\vim-tux.install\tools\complete-x64_x64.exe'
ERROR: Operation did not complete successfully because the file contains a virus or potentially unwanted software.
Error computing hash for 'C:\ProgramData\chocolatey\lib\vim-tux.install\tools\complete-x64_x64.exe'
Hash will be special code for locked file or file too big instead.
Captured error:
Operation did not complete successfully because the file contains a virus or potentially unwanted software.
The install of vim-tux.install was NOT successful.
Error while running 'C:\ProgramData\chocolatey\lib\vim-tux.install\tools\chocolateyinstall.ps1'.
See log for details.
vim-tux v8.1.2333 [Approved]
vim-tux package files install completed. Performing other installation steps.
The install of vim-tux was successful.
Software install location not explicitly set, could be in package or
default install location if installer.
Chocolatey installed 1/2 packages. 1 packages failed.
See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log).
Failures
- vim-tux.install (exited -1) - Error while running 'C:\ProgramData\chocolatey\lib\vim-tux.install\tools\chocolateyinstall.ps1'.
See log for details.
Here are my system information from systeminfo.exe
:
Host Name: XXXX
OS Name: Microsoft Windows 10 Pro
OS Version: 10.0.18363 N/A Build 18363
OS Manufacturer: Microsoft Corporation
OS Configuration: Member Workstation
OS Build Type: Multiprocessor Free
Registered Owner: ....
Registered Organization: ....
Product ID: ....
Original Install Date: 13.06.2019, 10:01:14
System Boot Time: 17.12.2019, 15:50:28
System Manufacturer: Dell Inc.
System Model: OptiPlex 7060
System Type: x64-based PC
Processor(s): 1 Processor(s) Installed.
[01]: Intel64 Family 6 Model 158 Stepping 10 GenuineIntel ~2400 Mhz
BIOS Version: Dell Inc. 1.2.22, 01.11.2018
Windows Directory: C:\WINDOWS
System Directory: C:\WINDOWS\system32
Boot Device: \Device\HarddiskVolume2
System Locale: en-us;English (United States)
Input Locale: en-us;English (United States)
Time Zone: (UTC-08:00) Pacific Time (US & Canada)
Total Physical Memory: 16,180 MB
Available Physical Memory: 10,725 MB
Virtual Memory: Max Size: 18,612 MB
Virtual Memory: Available: 12,800 MB
Virtual Memory: In Use: 5,812 MB
Page File Location(s): C:\pagefile.sys
Domain: ....
Logon Server: \\...
Hotfix(s): 16 Hotfix(s) Installed.
[01]: KB4533002
[02]: KB4498523
[03]: KB4503308
[04]: KB4506933
[05]: KB4508433
[06]: KB4509096
[07]: KB4515383
[08]: KB4515530
[09]: KB4516115
[10]: KB4517245
[11]: KB4520390
[12]: KB4521863
[13]: KB4524569
[14]: KB4525419
[15]: KB4532441
[16]: KB4530684
Network Card(s): 2 NIC(s) Installed.
[01]: Hyper-V Virtual Ethernet Adapter
Connection Name: vEthernet (Default Switch)
DHCP Enabled: No
IP address(es)
[01]: ....
[02]: ....
[02]: Intel(R) Ethernet Connection (7) I219-LM
Connection Name: Ethernet
DHCP Enabled: Yes
DHCP Server: ....
IP address(es)
[01]: ....
[02]: ....
Hyper-V Requirements: A hypervisor has been detected. Features required for Hyper-V will not be displayed.
goggalaxy: install isn't silent
As in title, when I was updating from goggalaxy v2.0.15.43 to 2.0.20.38, graphical installer showed and I had to manually go through install.
Outdated Package: Latencymon (Latest version: 4.70)
Latencymon has been recently updated to version 6.70. http://www.resplendence.com/latencymon
Download link: http://www.resplendence.com/download/LatencyMon.exe
installation fails due to incorrect url
Tried to install the package, but it fails with the following error:
ERROR: The remote file either doesn't exist, is unauthorized, or is forbidden for url 'https://us.download.nvidia.com/Windows/419.35/419.35-desktop-win10-64bit-international-whql.exe'. Exception calling "GetResponse" with "0" argument(s): "The remote server returned an error: (404) Not Found."
Seems the url should be https://us.download.nvidia.com/Windows/419.35/419.35-desktop-win10-64bit-international-whql-rp.exe instead.
(nvidia-display-driver) Need a DCH package.
I think we are going to need a DCH version of the 'nvidia-display-driver' package.
The current 'nvidia-display-driver' package in a clean install of Windows 10 1903 with a nVidia 2080 Ti throws an exit error of -467664896. Tried installing the drivers by hand and the installer said I had the "wrong version of windows".
Downloaded the DCH version of the drivers and they installed with no issue.
(goggalaxy) Outdated
v2.0.73.27 of GOG Galaxy is available. Looks like the AU script might be broken?
qemu
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.