#Upgrade fails

26 messages · Page 1 of 1 (latest)

fallow ether
#

Well my message poofed, so here I go again.

I'm trying to update spicetify on Win11, but get the following error:

❯ spicetify upgrade
spicetify v2.42.9
 info  Latest release: 2.42.10
 success  Downloaded Spicetify
 fatal  The system cannot find the path specified.```
pliant lark
#

Use install script from our documentation then

pliant lark
#

You have env paths fucked up

fallow ether
#

Oh?

#

Just Path?

#

Ah. I'm missing LOCALAPPDATA I think

#

Actually... It can't find param DestinationPath in Install-Spicetify
It's defined by $env:LOCALAPPDATA which I've added to my env now.

pliant lark
#

it can't find it bc it's null lol

fallow ether
#

But how is it null?

#

And yes I've restarted pwsh.

pliant lark
#

localappdata should be set in regedit by windows itself. it's not in "environment variables" per se

#

Your installation is fucked

fallow ether
#

ah yikes

pliant lark
fallow ether
#

would DISM/sfc help..? prolly not right?

pliant lark
#

no

fallow ether
#

hmm...

❯ echo $env:LOCALAPPDATA
C:\Users\CQD\AppData\Local```
#

I am confused...

#

Extra confused... The error leads me to believe my Expand-Archive function has no DestinationPath parameter...

#

Yeah, found the issue. After running Get-Command Expand-Archive | fl * I discovered my Expand-Archive cmdlet came from Pscx, and not Microsoft.PowerShell.Archive.

#

@pliant lark Thanks for the help :)

pliant lark
#

wut

fallow ether
# pliant lark wut

Yeah. This was a confusing one. It wasn't that DestinationPath was null. It was that my Expand-Archive didn't have a DestinationPath parameter at all...

#

I guess I/something installed module Pscx containing a different Expand-Archive definition.

pliant lark
#

why does it even let you overwrite those