{"id":19688,"date":"2020-11-04T16:57:49","date_gmt":"2020-11-04T16:57:49","guid":{"rendered":"http:\/\/198.58.113.91\/blog\/?p=19688"},"modified":"2020-11-04T17:19:41","modified_gmt":"2020-11-04T17:19:41","slug":"compressed-zip-folder-error-file-not-found-no-read-permission","status":"publish","type":"post","link":"https:\/\/www.winhelponline.com\/blog\/compressed-zip-folder-error-file-not-found-no-read-permission\/","title":{"rendered":"Compressed (Zipped) Folder Error “File not found or no read permission”"},"content":{"rendered":"

When you try to create a compressed (zipped) folder in Windows 10, the following error occurs:<\/p>\n

Compressed (zipped) Folders Error<\/strong>\r\n\r\nFile not found or no read permission.<\/pre>\n
\"compressed<\/p>\n
You may have noticed that this error doesn’t happen on drives formatted as FAT32.\u00a0This article explains why this problem occurs and how to resolve this error.<\/p>\n
Cause<\/h2>\n
Generally, the error “File not found or no read permission” occurs when you right-click on a folder containing one or more files, click the Send to menu, and click Compressed (zipped) folder<\/strong>. The result would be the same if you use the Zip (ribbon) command in File Explorer’s Share tab.<\/p>\n
This error is caused due to one of the following reasons:<\/p>\n
    \n
  1. One of the files in that folder is locked<\/a> (“Sharing violation” error) by a program or process.<\/li>\n
  2. You don’t have the read permissions (“Access Denied” error) to access some of the files in that folder.<\/li>\n
  3. You don’t have the write permissions (“Access Denied” error) to create a compressed folder in that folder.<\/li>\n<\/ol>\n
    RELATED:<\/strong> Compressed (Zipped) Folder Access Denied Error “Unable to Complete the Operation”<\/a><\/div>\n
    [Fix] Zip error “File not found or no read permission”<\/h2>\n
    Case 1: File is locked by a process<\/h3>\n
    Microsoft Office applications such as Excel or Word create a temporary file (also known as “owner file”) for each file you open. These temporary files start with the ~$<\/code> symbol and have the same name as the original file. These temporary Office files are hidden in File Explorer view even though you’re configured it to show all files.<\/p>\n
    Look at this example below. When running the dir \/a<\/code> command, you can see the two temporary Office files in that folder. These files are exclusively locked by the respective programs. This temporary file holds the login name of the person who opens the file. Attempting to read the owner files in another program would cause an error.<\/p>\n
    Despite this issue, you may be able to zip individual files (except those hidden temporary files) in that folder.<\/em><\/p>\n
    \"compressed<\/p>\n
    So, when you send this entire folder to a compressed (zipped) folder, Windows tries to add these temporary Office files as well (to the zip folder). When doing so, Explorer encounters SHARING VIOLATION<\/code> message internally, and shows the error File not found or no read permission<\/strong> to the user.<\/p>\n
    Fix:<\/strong> If you have open files in that folder, close each one of them and then try creating a Compressed (zipped) folder.<\/p>\n
    \n
    To know which process is having a lock on a file or folder, you can use Microsoft Process Explorer or the built-in Resource Monitor.<\/p>\n
    \"compressed
    Process Explorer tool shows the list of open files located in that folder.<\/figcaption><\/figure>\n
    We’ve written about this topic in these articles:<\/p>\n