Bug Report: Spicetify Command Not Executable After v2.38.3 Update
Problem Description:
Upon updating the binary to version v2.38.3, the spicetify command is no longer functional nor executable. Note: I am also using SpotX.
OS: Windows 11 Home 26120.1843
Steps Taken:
Initial Installation Attempt:
PS C:\Users\abudd\AppData\Local> iwr -useb https://raw.githubusercontent.com/spicetify/cli/main/install.ps1 | iex
Checking if your PowerShell version is compatible... > OK
Checking if the script is not being run as administrator... > OK
Installing spicetify...
Fetching the latest spicetify version... > OK
Downloading spicetify v2.38.3... > OK
Extracting spicetify... > OK
Making spicetify available in the PATH... > OK
spicetify was successfully installed!
Run spicetify -h to get started
Do you also want to install Spicetify Marketplace? It will become available within the Spotify client, where you can easily install themes and extensions.
[Y] Yes [N] No [?] Help (default is "Y"):
Starting the spicetify Marketplace installation script..
Setting up...
Invoke-Expression:
Line |
210 | Invoke-WebRequest @Parameters | Invoke-Expression
| ~~~~~~~~~~~~~~~~~
| Program 'spicetify.exe' failed to run: An error occurred trying to start process 'C:\Users\abudd\AppData\Local\spicetify\spicetify.exe' with working directory 'C:\Users\abudd\AppData\Local'. Access is denied.
+ spicetify path userdata | Out-Null
Using the Binary from GitHub Releases:
I downloaded the binaries directly from the Spicetify GitHub releases and encountered a similar "Access is denied" error when running the binary.
PS C:\Users\abudd> spicetify
ResourceUnavailable: Program 'spicetify.exe' failed to run: An error occurred trying to start process 'C:\Users\abudd\AppData\Local\spicetify\spicetify.exe' with working directory 'C:\Users\abudd'. Access is denied.
+ spicetify
Alternative Installation Methods:
I also tested installation through Winget, which produced the same error as described above.
Ownership and Permission Checks:
I ensured I have ownership of all necessary files and attempted to install as both administrator and non-administrator. Both attempts yielded the same error.
Administrator Attempt:
PS C:\WINDOWS\system32> iwr -useb https://raw.githubusercontent.com/spicetify/cli/main/install.ps1 | iex
Checking if your PowerShell version is compatible... > OK
Checking if the script is not being run as administrator... > ERROR
WARNING: The script was run as administrator. This can result in problems with the installation process or unexpected behavior.
Do not continue if you do not know what you are doing.
Do you want to abort the installation process?
[Y] Yes [N] No [?] Help (default is "Y"): Y
spicetify installation aborted
Press Enter to continue...:
File Verification Using Attestation:
I used the attestation file to verify spicetify.exe and received a successful verification:
š Have you checked Spicetify.app page for your issue?
š Is there already an issue for your problem?
ā¹ Environment / Computer Info
š Description
Bug Report: Spicetify Command Not Executable After v2.38.3 Update
Problem Description:
Upon updating the binary to version v2.38.3, the
spicetify
command is no longer functional nor executable.Note: I am also using SpotX.
OS: Windows 11 Home 26120.1843
Steps Taken:
Initial Installation Attempt:
Using the Binary from GitHub Releases: I downloaded the binaries directly from the Spicetify GitHub releases and encountered a similar "Access is denied" error when running the binary.
Alternative Installation Methods: I also tested installation through Winget, which produced the same error as described above.
Ownership and Permission Checks:
I ensured I have ownership of all necessary files and attempted to install as both administrator and non-administrator. Both attempts yielded the same error.
Administrator Attempt:
File Verification Using Attestation: I used the attestation file to verify
spicetify.exe
and received a successful verification:Attempted Downgrading:
Additional Troubleshooting Steps:
C:\Users\abudd\AppData\Local\spicetify
folder before reinstalling, which redid the PATH declarations.Next Steps:
Request for Feedback:
Summary of Actions Taken:
spicetify.exe
using the attestation file.spicetify.exe
.spicetify
directory and executable.Not included above:
Edit:
Compiled the exe myself and it is still experiencing the same error.
šø Screenshots