epmmis
asked on
Windows 7 does not unzip compressed files
Windows 7 64b ultimate workstation does not extract files from a zip file. It reports that the “destination folder path is invalid”. (See Graphic Below) Attempted extracting files on a mapped network drive and attempted to extract files when the zip file is local on the workstation. No matter the location the extraction fails.
The compressed zip files are not corrupt or bad. They unzip okay-dokay fine on any other computer. We have two Windows 7 ultimate 64b workstations, they both have this problem.
The compressed zip files are not corrupt or bad. They unzip okay-dokay fine on any other computer. We have two Windows 7 ultimate 64b workstations, they both have this problem.
That destination path looks pretty crazy, have you tried changing it to something more reasonable? There was a maximum file/folder name length on XP so you may be up against that if there are a lot of subfolders
Yeah, I would try to extract locally first to narrow down the cause. Maybe to the desktop or something.
I've seen Windows zip report some files as corrupted or errors like you've mentioned. Try 7-zip: http://www.7-zip.org. It's free and it's worked on those .zip files that Windows didn't like.
it looks like you are hitting the 256 character path + filename limit
ASKER
I appreciated all the comments, but everyone missed this part of the write up.
"attempted to extract files when the zip file is local on the workstation. "
The zip file and other test zip files were moved locally onto the workstation.
The Windows 7 workstation reported the same error.
Network or local, it did not matter. The file extraction fails due to a path error.
"attempted to extract files when the zip file is local on the workstation. "
The zip file and other test zip files were moved locally onto the workstation.
The Windows 7 workstation reported the same error.
Network or local, it did not matter. The file extraction fails due to a path error.
Based on the screen shot you provided. Your using a very long path as a starting point for the unzip. The error seems to be saying the path is becoming TOO LONG when trying to unzip. Try exacting to a local drive with a very short shorting path like C:\1. I bet it will complete.
Remember Windows only supports file paths of 256 characters long!
ASKER
File path in the drawing is only 147 characters long.
Had the same extraction error when the file was moved to the desktop.
Had the same extraction error when the file was moved to the desktop.
Even the desktop has a long path C:\1 is three characters. Desktop folder is C:\Users\<username>\Deskto
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
How have you positively identified that it is a GPO causing this? I don't see anything in your attachment that would stopping this. I do see a workstaion_logon.vbs logon script though. What's in there?
ASKER
There is a hot fix for this situation.
http://support.microsoft.com/kb/981603
"The destination folder path is invalid" Error message when you extract a compressed file on a computer that is running Windows 7 or Windows Server 2008 R2
Consider the following scenario:
==> You have a computer that is running Windows 7 or Windows Server 2008 R2.
==> You enable the Remove Run menu from Start Menu Group Policy setting on this computer.
==> You open Windows Explorer, right-click a compressed file, and then click Extract All. You specify a valid path in the Extract Compressed (Zipped) Folders dialog box, and then click Extract to extract the file.
http://support.microsoft.com/kb/981603
"The destination folder path is invalid" Error message when you extract a compressed file on a computer that is running Windows 7 or Windows Server 2008 R2
Consider the following scenario:
==> You have a computer that is running Windows 7 or Windows Server 2008 R2.
==> You enable the Remove Run menu from Start Menu Group Policy setting on this computer.
==> You open Windows Explorer, right-click a compressed file, and then click Extract All. You specify a valid path in the Extract Compressed (Zipped) Folders dialog box, and then click Extract to extract the file.
What specifically was the cause of this for future reference?