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
Instead of throwing "Path too long" error, Expand-Archive throws errors about removing non-existing items #69
Comments
I am experiencing the same problem exactly; it is amazing that these windows 95 era path limitation problems are still around 20+ years later. |
FYI: There is a workaround for this issue: instead of using
|
We will reopen this issue if it is still persistent. |
This issue still occurs |
@ayousuf23 please reopen |
@SydneyhSmith please reopen |
Ongoing issue for me please resolve |
When expanding an archive that contains long file paths to a location that also has a long path, the files to be expanded may have a resulting path that causes an error because it is too long.
When using "Expand All" from within Windows, this results in
The same should occur when running
Expand-Archive
in PowerShell, but what happens instead is that errors are thrown fromRemove-Item
on this line:Microsoft.PowerShell.Archive/Microsoft.PowerShell.Archive/Microsoft.PowerShell.Archive.psm1
Line 408 in c9fc2b3
It appears that this line of code is meant to clean up after a failed expansion, but it is trying to remove items that it hasn't expanded yet, so this would indicate another issue.
The text was updated successfully, but these errors were encountered: