-
Notifications
You must be signed in to change notification settings - Fork 6
[BUG] Files Named Wrong, Nothing Runs #112
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
Comments
Please change an unzip program. This zipfile is packed by powershell |
Did earlier .zip files use the It looks like the path separators are using backslashes when they're supposed to use forward slashes, which is not how .zip files are supposed to be formatted. There was an issue like this that was resolved back in 2017: PowerShell/Microsoft.PowerShell.Archive#95 In the meantime the working solution has been to manually rename and relocate all the files to where they're supposed to be. |
No. Only releases made by me were created by |
Is your version up-to-date, and are you running on a recent .Net Framework? It definitely looks like the issue isn't me, for once. |
I uploaded a new zipfile, have a try? |
Sorry for the slow reply; eventful week. Yes it does; perfect! |
Describe the Bug :
ALL of the files in msl.zip are all on the top directory,and their names are the file paths they were supposed to have. Obviously, MSL does not run.
Obviously, MSL doesn't load.
Steps To Reproduce :
Extract the latest msl.zip and look at the files.
Expected Behavior :
The files are the normal names, in their normal locations, and also MSL loads.
Screenshots if applicable :
You can directly paste screenshots here, no need for external hosting.
Additional Information :
Additional Context :
Add any other context about the problem here.
I am on Pop!_OS 22.04 LTS, using the Archive Manager that comes standard with that build, and I can't recall a time in recent memory in which I've had this issue.
There's a 'quick fix' mentioned in one of the answers to this StackExchange post, which is easier than what I did: manually relocate and rename each file by hand. Also, someone else in 2025 with issue.
The text was updated successfully, but these errors were encountered: