This repository has been archived by the owner on Jul 18, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 37
Instead of throwing "Path too long" error, Expand-Archive throws errors about removing non-existing items #69
Labels
Milestone
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 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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: