Installation issue after Spotify update

[Littery1]

🔍 Have you checked Spicetify.app page for your issue?

• I have checked the FAQ

🔍 Is there already an issue for your problem?

• I have checked older issues, open and closed

ℹ Environment / Computer Info

- Spotify version: Spotify for Windows (64 bit) 1.2.40.599.g606b7f29
- Spicetify version:  v2.36.13

📝 Description

Upon updating Spotify, Spicetify didn't work. Spicetify used to work for me for several months. I tried to look for updates of Spicetify, but still Spicetify wasn't working, meaning I am left with plain Spotify. I wanted to reinstall it then, I uninstalled it as in documentation:
spicetify restore
rmdir -r -fo $env:APPDATA\spicetify
rmdir -r -fo $env:LOCALAPPDATA\spicetify

and then tried to install it again, but I am getting this error:
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.36.13... > OK
Extracting spicetify...Install-Spicetify : A parameter cannot be found that matches parameter name 'DestinationPath'.
At line:188 char:1

• Install-Spicetify

•   + CategoryInfo          : InvalidArgument: (:) [Install-Spicetify], ParameterBindingException
    + FullyQualifiedErrorId : NamedParameterNotFound,Install-Spicetify
  
  

I didn't do anything extraordinary before, on my laptop than this happened in fact I haven't been using it for several days.

📸 Screenshots

No response

[rxri]

Your username has weird characters that are not ASCII or has spaces, or your env is corrupted. That’s not spicetify’s fault.

[Littery1]

but it was working earlier today and my username is: Littery without spaces and any non ASCII symbols its just letters

[Littery1]

nevermind I installed it with chocolatey and it works whatever...

[rxri]

but it was working earlier today and my username is: Littery without spaces and any non ASCII symbols its just letters

It's not our fault then. It says actually it couldn't find the param DestinationPath, so it's powershell's fault.