Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

(vcredist140) Unable to install in Windows 24H2 Sandbox: E_ACCESSDENIED #2618

Open
2 tasks done
lostmsu opened this issue Jan 27, 2025 · 3 comments
Open
2 tasks done
Labels

Comments

@lostmsu
Copy link

lostmsu commented Jan 27, 2025

Checklist

  • I have verified that this is the correct repository, and the package is maintained by the chocolatey-community user.
  • I have verified that this is happening in the latest available version of the package.

Chocolatey Version

2.4.1

Chocolatey License

None

Package Version

14.42.34433

Current Behaviour

VERBOSE: Checking Service Pack requirements
ERROR: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))

Expected Behaviour

Should install

Steps To Reproduce

  1. Ensure you are on Windows 24H2
  2. Launch Windows Sandbox, then inside:
  3. Install choco
  4. choco install -y --ignore-dependencies vcredist140

P.S. Without --ignore-dependencies it fails to install KB2919442 with the same error text (but maybe a different step). I assume it is not actually needed inside 24H2 sandbox.

Environment

- Operating System: NT 10.0.26100.0
- PowerShell Version: 5.1.26100.2161
- Shell: PowerShell 5.1

Chocolatey Log

https://gist.github.com/lostmsu/988168c7f56749f952cd416844105a60

Anything else?

No response

@lostmsu lostmsu added the Bug label Jan 27, 2025
Copy link

Thanks for raising this issue!

The packages within this repository are maintained by a small team of volunteer Community Maintainers, in their own time. Their time, like yours is important. Please help them by not wasting it.

This is a community repository where the expectation is that everybody will get involved by raising pull requests to fix problems they find. This will also allow that problem to be fixed more quickly as you don't have to wait for a member of the Community Maintainer Team to pick it up.

If you are unable to fix the issue yourself, the Community Maintainers Team will look at it when time allows. There are no service level agreements, nor should there be any expectation on when people can resolve issues in their own time.

A few dos and don'ts:

  • Do provide as much information as you can in any issue that you raise.
  • Don't complain that an issue has not yet been picked up or resolved. You are expected to help out in this community maintained repository. If you are unable to do so, don't complain when others don't adhere to your timelines. There is no SLA nor should you have any expectation of one.
  • Do read the CONTRIBUTING and COMMITTERS documentation before raising a pull request as it contains valuable information on what automation is used in this repository.
  • Do read the Code of Conduct.
  • Don't post your frustration in comments. The Community Maintainers Team are not a punching bag for your frustration. You will only end up banned from the repository.

Thank you.
(Automatically posted message)

@corbob
Copy link
Contributor

corbob commented Jan 28, 2025

My guess based on the output is that this command is erroring for you: Get-WmiObject -Class Win32_OperatingSystem. Could you try running this command in a PowerShell window in the Sandbox? I can't think of any reason why it wouldn't work, but it is the first command after the last verbose output.

@lostmsu
Copy link
Author

lostmsu commented Jan 28, 2025

@corbob it fails with the same error, yes. Opened microsoft/Windows-Sandbox#67 in case it is on them.

But the installer itself does not need to call it on new versions of Windows. In this particular case I think detecting 10.0.26100.0+ would be enough to skip all dependencies. E.g. [Environment]::OsVersion.Version -ge (New-Object Version "10.0.26100")

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants