“Verifying” upon opening every file

[Quu]

Anyone tried the new beta and see if the problem remains?

 

[dolphin842]

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....

Yeah same.. the unquarantine fix doesn't seem to stick. I gotta do it every time...... grrrr.

Correct, all this workaround does is clear out the xattr that the system puts on a file. Aside from disabling Gatekeeper outright, there's nothing we can do to prevent the system or apps from applying the xattr again after you open a file.

 

[CPx]

Correct, all this workaround does is clear out the xattr that the system puts on a file. Aside from disabling Gatekeeper outright, there's nothing we can do to prevent the system or apps from applying the xattr again after you open a file.

Ah, that's a bummer.

 

[SoYoung]

Correct, all this workaround does is clear out the xattr that the system puts on a file. Aside from disabling Gatekeeper outright, there's nothing we can do to prevent the system or apps from applying the xattr again after you open a file.

Thanks for the reply. If thats the case, then I'll wait until a .1 or .2 update to see if Apple will fix it, otherwise, I'll probably have no choice to do a clean install but its really my last option.

 

[Cinder6]

Correct, all this workaround does is clear out the xattr that the system puts on a file. Aside from disabling Gatekeeper outright, there's nothing we can do to prevent the system or apps from applying the xattr again after you open a file.

Odd. Like I said, it seems permanent for me.

 

[tw1ll]

It’s great that posters try and find workarounds but this shouldn’t be necessary. I’m just glad that monitoring this forum made me wary enough to only try the upgrade on a secondary boot disk. That allowed me to quickly revert back when I found out that HS was not for me (which happened the first time I tried opening an MS Word file and watch the “Verifying” pop up for what seemed an age).

 

[Quu]

Reinstalled my Mac today to try and resolve this issue and guess what? It did not fix it at all. Exact same issue with my NAS, verifying comes up on all the files just like before.

I'm officially pissed off with this operating system "upgrade". I had it trying to verify 4GB files yesterday over my network at 440Mb/s - Takes almost a minute just to open one file. Apple better fix this soon before my laptop goes out a window.

 

[SoYoung]

Reinstalled my Mac today to try and resolve this issue and guess what? It did not fix it at all. Exact same issue with my NAS, verifying comes up on all the files just like before.

I'm officially pissed off with this operating system "upgrade". I had it trying to verify 4GB files yesterday over my network at 440Mb/s - Takes almost a minute just to open one file. Apple better fix this soon before my laptop goes out a window.

I completely agree. Like I said before its unacceptable to let a public release go out with big bug like that and its very disappointed that Apple go this way now days. I bough my Mac last year after being a lifetime Windows user thinking I'll have a more bug free experience and honestly, I never experienced such bugs on Windows ever.

Even my mails have problem. I dont receive new mails notification if the app is closed, this bug is there since Sierra last year :/ I'm beginning to be tired of Apple taking years sometime to fix some bugs on both iOS/macOS.

I hope they'll be a fix soon but honestly, I have the feeling we'll have to deal with this for a long time.

 

[Quu]

I upgraded my Mac to the current public beta and the problem persists there too. Just thought I'd let you all know.

 

[dolphin842]

I bough my Mac last year after being a lifetime Windows user thinking I'll have a more bug free experience and honestly, I never experienced such bugs on Windows ever.

Sorry to hear you switched too late :/... I switched in 2004 and the difference between XP on a ThinkPad and 10.3 on a PowerBook was night and day. There was also a good run around 2009-2010... which was the last time Apple admitted they needed to slow down and fix things rather than keep pushing ahead regardless of quality.

I'm still around because of my investment in 3rd-party apps, but I've stopped recommending people active switch to the Mac for a while now.

 

[SoYoung]

Sorry to hear you switched too late :/... I switched in 2004 and the difference between XP on a ThinkPad and 10.3 on a PowerBook was night and day. There was also a good run around 2009-2010... which was the last time Apple admitted they needed to slow down and fix things rather than keep pushing ahead regardless of quality.

I'm still around because of my investment in 3rd-party apps, but I've stopped recommending people active switch to the Mac for a while now.

Yeah I hear you and I agree. I switched because I had already an iPhone, iPad and an Apple TV so just have all my device on the same écosystem was the only reason I wanted an iMac and I though OS X was more polished. I can't say I'm disapointed with my purchase, in fact, I like my iMac and I like macOS and I really enjoy the convenience to sync all my things easily between my devices but I never though OS update can be very buggy and somewhat with unacceptable bugs. Last year it was my mails, and this year is the sync bug everytime I want to open a video file no matter where it come from.

Something that really bugs me is Apple are really quick with iOS update (already on 11.0.2) but when it comes to macOS, we always have to wait months for a single update. It can be really irritating when you wait after one because the last update mess things up. On Windows, update are frequent and I dont remember being stuck with a bug due to an upgrade that last very long until a fix comes out.

I'll stay with Apple, because like you, I invested too much money to change all my things and its not bad products, but yeah, I'll never recommend a Windows user to do the switch because nowadays macOS is not very different than Windows with a lot of little bugs and glitch and the fact that the fix for those take forever to come.

Some user will just say to me to do a clean install to solve my issues, but I think its just not normal to wipe it out the whole system just a year in a half later after the initial install. Upgrade process are there for a reason and this was another reason I bough a mac, to not deal too frequently with disk format and re-installing process every 2 years.

 

[kristoffer4]

I wonder if this bug will be fixed in 0.1....

 

[Cougarcat]

Y.

Something that really bugs me is Apple are really quick with iOS update (already on 11.0.2) but when it comes to macOS, we always have to wait months for a single update. It can be really irritating when you wait after one because the last update mess things up. On Windows, update are frequent and I dont remember being stuck with a bug due to an upgrade that last very long until a fix comes out.

Months? Apple releases MacOS .1 updates consistently less than a month after the initial release. And if you really want it now there’s the public beta.

That said I think it’s good policy to wait for .1 or .2, especially nowadays when the new feature set is so light (but with big internal changes that can cause issues.)

 

[SoYoung]

Months? Apple releases MacOS .1 updates consistently less than a month after the initial release. And if you really want it now there’s the public beta.

That said I think it’s good policy to wait for .1 or .2, especially nowadays when the new feature set is so light (but with big internal changes that can cause issues.)

We have 6-7 update of macOS per year so its about 1-2 months between each. And no, I dont want to install a beta on my computer, but talking of beta's, thats the thing I dont understand...They release like, 9 or 10 HS beta's? and after all that beta versions we still have an obvious bug like this? Seriously, its beyond me.

And yes, I shouldn't update, but when they are new update on my computer, I always want to do it just to have the latest security patches and all.

 

[Cougarcat]

We have 6-7 update of macOS per year so its about 1-2 months between each. And no, I dont want to install a beta on my computer, but talking of beta's, thats the thing I dont understand...They release like, 9 or 10 HS beta's? and after all that beta versions we still have an obvious bug like this? Seriously, its beyond me.

And yes, I shouldn't update, but when they are new update on my computer, I always want to do it just to have the latest security patches and all.

Apple’s annual releases always contain significant internal changes. High Sierra might be low on user features but they rewrote the windowserver for Metal and added a new file system, among other things. It takes time to squash all the bugs.

That’s a good policy for point updates, but Apple continues to release security patches for the previous OS so it’s not necessary to upgrade to the annual releases right away from the standpoint of security.

 

[SoYoung]

Apple’s annual releases always contain significant internal changes. High Sierra might be low on user features but they rewrote the windowserver for Metal and added a new file system, among other things. It takes time to squash all the bugs.

That’s a good policy for point updates, but Apple continues to release security patches for the previous OS so it’s not necessary to upgrade to the annual releases right away from the standpoint of security.

oh really? I didn't know they still patch previous OS with security patches. Thanks for the info, I'll know for the futures updates and I'll definitively wait a couple of months to upgrade to the next major one.

 

[kristoffer4]

Is this fixed in the new update?

 

[anthony.82]

nope

 

[deorex]

Was this a clean install + Migration Assistant, or did you have to reconstruct your environment from scratch?
[doublepost=1506384450][/doublepost]

1) Open up Automator
2) Choose "Service" for the document type
3) Set up the document so it matches the screenshot in my previous post.
4) Save... make a descriptive name for the service
5) Right-click on file(s) you want to strip the quarantine from. Go to the Services menu at the bottom, and your newly-created workflow should be in the sub-menu.
6) Select that workflow and a Terminal window should pop up showing that the files don't have that extended attribute anymore.

This solution worked perfectly, you're a genius, thanks!!
I was scared to use Automator too, for all those novices like me, but if you follow the instructions, and look under the category "Utilities" for "Run AppleScript" it's really very simple and will add a menu item at the bottom of your right-click (or command) menu for each file that is causing the verification wait.

Here's the original post for reference on what code to enter into the Automator window: https://forums.macrumors.com/threads/“verifying”-upon-opening-every-file.2065395/#post-25104903

 

[SoYoung]

Is this fixed in the new update?

Sadly no I was happy when I saw the update this afternoon but not for long when I tried to open a file after the installation
[doublepost=1507252111][/doublepost]

This solution worked perfectly, you're a genius, thanks!!
I was scared to use Automator too, for all those novices like me, but if you follow the instructions, and look under the category "Utilities" for "Run AppleScript" it's really very simple and will add a menu item at the bottom of your right-click (or command) menu for each file that is causing the verification wait.

Here's the original post for reference on what code to enter into the Automator window: https://forums.macrumors.com/threads/“verifying”-upon-opening-every-file.2065395/#post-25104903

You are lucky if it solve the problem permanently for you. For many of us, myself included, it only fix the problem for one time, after that, you always have to re-do the unquarantine service.

 

[Quu]

Bit the bullet today and restored back to Sierra using a Time Machine backup.

If anyone is curious how you do this, restart your mac and hold down CMD + R before and after the startup chime. Once you see the load bar you can release these keys.

This will take you into the recovery system which gives you the option to restore from a Time Machine backup. Select that, click on your Time Machine backup and it will display a list of all your recent backups and the version of macOS present in each backup, select the most recent one that lists Sierra next to it and begin the restore.

For me over WiFi the restore took about 8 hours for ~320GB of data. The restore worked great for me and I'm now back to a working system.

 

[verdi1987]

I did a clean reinstall of 10.13 GM. It did not resolve this bug with Gatekeeper. I spent the last 24 hours recovering my system to a workable state (several reformats/reinstalls, failed migrations).

 

[Str0bes]

Do you guys have custom icons for the files you're trying to open? I stumbled upon this thread on the Apple message boards and it seems when people delete the custom icons, the files work fine.

8085612

 

[verdi1987]

Do you guys have custom icons for the files you're trying to open? I stumbled upon this thread on the Apple message boards and it seems when people delete the custom icons, the files work fine.

8085612

I don't have any custom icons.

 

[F1Mac]

Do you guys have custom icons for the files you're trying to open? I stumbled upon this thread on the Apple message boards and it seems when people delete the custom icons, the files work fine.

I stopped using custom icons 16 years ago.