Skip to content

[Bug]: Installing Vulkan 1.4.313.0 results in a broken install where folders are missing #6805

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

Open
3 tasks done
marovira opened this issue May 9, 2025 · 2 comments · May be fixed by #6808
Open
3 tasks done

[Bug]: Installing Vulkan 1.4.313.0 results in a broken install where folders are missing #6805

marovira opened this issue May 9, 2025 · 2 comments · May be fixed by #6808
Labels
bug Something isn't working

Comments

@marovira
Copy link
Contributor

marovira commented May 9, 2025

Prerequisites

  • I have written a descriptive issue title.
  • I have searched all issues/PRs to ensure it has not already been reported or fixed.
  • I have verified that I am using the latest version of Scoop and corresponding bucket.

Package Name

vulkan

Expected/Current Behaviour

When installing the latest version of Vulkan with scoop install vulkan, the resulting installation folder has the following structure:

scoop/apps/vulkan/1.4.313.0
|- Bin/
|- install-vk-layers.ps1

This is missing the following folders: Config, Helpers, Include, Lib, Licenses, Source, and Templates.

The issue stems from the new Vulkan installer. Attempting to convert the installer into a .7z and extracting it results in only the Bin folder being produced. This is different from previous installers where the entire directory tree could be extracted in this way.

Steps to Reproduce

PS> scoop install vulkan

Possible Solution

The manifest should be updated to run the installer directly instead of attempting to extract it.

Scoop and Buckets Version

PS> scoop --version
Current Scoop version:
859d1db5 (HEAD -> master, tag: v0.5.2, origin/master, origin/HEAD) chore(release): Bump to version 0.5.2 (#6080)

'main' bucket:
4baba6cc2 (HEAD -> master, origin/master, origin/HEAD) signal-cli: Update to version 0.13.15

'extras' bucket:
6ec512ff5e (HEAD -> master, origin/master, origin/HEAD) vscodium: Update to version 1.100.03093

Scoop Config

PS> scoop config

last_update                       scoop_repo                              scoop_branch
-----------                       ----------                              ------------
2025-05-08T20:05:55.4205095-07:00 https://github.com/ScoopInstaller/Scoop master

PowerShell Version

PS> $PSVersionTable

Name                           Value
----                           -----
PSVersion                      5.1.26100.3912
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.26100.3912
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1

Additional Softwares

No response

@HUMORCE
Copy link
Member

HUMORCE commented May 18, 2025

Is it becoming a web-based installer?

@marovira
Copy link
Contributor Author

Yes. For some reason their internal tooling switched to it being a web-based installer instead of having everything bundled like it used to. Per the ticket I mention in the PR, the fact that the installer used to be self-contained was an unintentional side-effect of their tooling and not something they plan to continue or offer support for.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
2 participants