Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
“Verifying” upon opening every file
- Thread starter verdi1987
- Start date
- Sort by reaction score
The directions by dolphin842 on this thread worked for me. It took me a while to figure out how to do it but now that I have it set up, you just right click on all the files that have problems, select the service and done.
- Start Automator.
- Create a new 'Service'. Then look at the screenshot on the previous page (receives 'files or folders' in 'Finder') for the basic setup.
- Then, there is an area that asks you to drag in files. First, on the left side of Automator search for 'run apple script' and drag this functionality to the right side.
- Replace the default code with the one on the previous page here.
- You can now access this service by right clicking a file in finder, right at the bottom of the contextual menu.
1.) Open Automator. It should be in your "Applications" folder. Or hit Command+Spacebar and type automator to find it using Spotlight.
2.) Select "Service":
3.) Select "Run AppleScript" from the column of available actions. Drag "Run AppleScript" to the right empty pane to begin.
4.) Make sure "files or folders" is selected for "Service receives selected". Make sure "Finder" is selected for "in". Paste dolphin842's code in the empty text area shown in the screenshot below (I added "-r" so this is recursive):
4.) Choose File -> Save...
5.) Choose an appropriate name. I chose "Unquarantine" for now.
6.) Select all of the files you want to fix, and right click. You'll see your new service at the bottom of the right click dialog as a selection:
7.) Click "Unquarantine" (or whatever you named it) and it will modify all of the selected files, including files within selected folders.
8.) Quit Terminal after the process finishes and you're returned to the default prompt.
Thanks to dolphin842 and everyone else who helped!
2.) Select "Service":
3.) Select "Run AppleScript" from the column of available actions. Drag "Run AppleScript" to the right empty pane to begin.
4.) Make sure "files or folders" is selected for "Service receives selected". Make sure "Finder" is selected for "in". Paste dolphin842's code in the empty text area shown in the screenshot below (I added "-r" so this is recursive):
Code:
on run {input, parameters}
tell application "Terminal"
activate
set filesString to ""
repeat with file_ in input
set filesString to filesString & " " & quoted form of (POSIX path of file_)
end repeat
do script "xattr -r -d com.apple.quarantine" & filesString
end tell
return input
end run4.) Choose File -> Save...
5.) Choose an appropriate name. I chose "Unquarantine" for now.
6.) Select all of the files you want to fix, and right click. You'll see your new service at the bottom of the right click dialog as a selection:
7.) Click "Unquarantine" (or whatever you named it) and it will modify all of the selected files, including files within selected folders.
8.) Quit Terminal after the process finishes and you're returned to the default prompt.
Thanks to dolphin842 and everyone else who helped!
Last edited:
Looking into this further, I'm noticing that the com.apple.quarantine attribute got applied to files I had opened before the upgrade to 10.13, but not since the upgrade.
I confirmed this by creating a text file with the output of running my automator action (the non-destructive -p version) on the entirety of my user data, then removing lines that contained the string "no such". I found a few MOV files I had opened earlier this summer before the OS upgrade (and not since)... they had the .quarantine xattr and attempting to open them led to the familiar "Verifying..." dialog.
Note that the output of running the automator action on a folder with many files will result in a large output (my text file was north of 15MB!)... you'll need a text editor that can handle documents with as many lines as you have files. Well, you could also grep the output in Terminal before it reaches the file creation stage, but I'm lazy and just set up a BBEdit Text Factory instead
Anyway, I do see some of these other threads about prior OS betas (and release versions?) exhibiting this issue... would also explain why I'm seeing lots of non-Safari .quarantine xattrs applied to files I haven't opened in a long time.
I confirmed this by creating a text file with the output of running my automator action (the non-destructive -p version) on the entirety of my user data, then removing lines that contained the string "no such". I found a few MOV files I had opened earlier this summer before the OS upgrade (and not since)... they had the .quarantine xattr and attempting to open them led to the familiar "Verifying..." dialog.
Note that the output of running the automator action on a folder with many files will result in a large output (my text file was north of 15MB!)... you'll need a text editor that can handle documents with as many lines as you have files. Well, you could also grep the output in Terminal before it reaches the file creation stage, but I'm lazy and just set up a BBEdit Text Factory instead
Anyway, I do see some of these other threads about prior OS betas (and release versions?) exhibiting this issue... would also explain why I'm seeing lots of non-Safari .quarantine xattrs applied to files I haven't opened in a long time.
I'll add my voice to the chorus. 10.13, upgrade install, and this is annoying the hell out of me. Beyond the "verifying' problem, has anyone else noticed that all finder actions are just sliiiiightly delayed? Navigation, info pane, quick view, there's a tiny lag on every action.
Yes, I have some lag as well especially when the computer woke up after an hour or two there are some lag for the first 10 seconds. Also, I use the invert colours shortcut often and now there is a delay when I activate it and it can make crash chrome as well when I do this.
For the files verifying bug I dont test the solution below but I think its a major bug that Apple should be aware of and fix it on the next update because not everyone understand how to fix it manually.
Not just you. Sometimes I even have a full computer lag wherein I'm unable to do anything for about a minute. I have 24GB RAM so this cannot be related to anything but a software snag in the new OS. Seems like I should have waited before I updated.
This worked!!! Huge thanks to you sir...
FYI I'm in the beta and the issue isn't fixed on 10.13.1.
Many thanks! It worked!
But where do you found your saved services? If one day the problem was fixed and want to delete this, where can I see my saved service file?
[doublepost=1506761536][/doublepost]it seems the workaround just work for the first time I open the file, the second time I try to open it, the verifying thing happens again....
So the fix to this issue should come from the developer of some application, not Apple?
In other words, the problem isn't the file (or file type) itself, but the program that creates the file under 10.13?
At least this is how I see it here - an .mkv file created with an application while I was running macOS 10.12 opens fine, there is no hanging verification process. But an .mkv file created under macOS 10.13 with the same application as before does have the problem and needs to be cleaned from the xattr value to open normally.
In other words, the problem isn't the file (or file type) itself, but the program that creates the file under 10.13?
At least this is how I see it here - an .mkv file created with an application while I was running macOS 10.12 opens fine, there is no hanging verification process. But an .mkv file created under macOS 10.13 with the same application as before does have the problem and needs to be cleaned from the xattr value to open normally.
Yeah same.. the unquarantine fix doesn't seem to stick. I gotta do it every time...... grrrr.