verifying progress bar on every file.

Interesting. So it means Apple support didn't know what they are talking, and their database contains wrong information, obviously.

Now it looks, it's not related to "file type" as they said, but is just a security check (as using xprotect service to do the check would suggest), and Apple just will not do anything about it.

Yes, it works just for once.

If I try to open that same file again, high sierra try to verify it again and again.

I can't understand why QuickTimePlayer open media files without any verification at first.

If the security is very *ucking important, why they do not verify all media files at first?

Unfortunately, after talking with Apple again, it looks like fix is not coming.

Apparently they now understand what is going on with their OS, and it's "intended". When asked who "intended" such a strange behaviour of the OS, they explained that it's "executives" and they are not challenging executive's decisions. Even they said they were "very sorry" for my lost workflow. Go figure.

After that, I was told that they have explained my "options" (to use as it is, or to roll back to El Capitan) and advised me to deal with it. Great advice, I would guess.

I can't replicate this on my two Macs (one SSD and one Fusion drive).

I have tried opening movie files on network shares and locally and they all just open. The network share was a spinning hard drive external disk.

I don't remember seeing any mention of this in the beta.

Maybe there is more to it.

How were the movies created (software, codec)?

Does it happen with any other file types?

Perhaps there is some other software causing interference. Have you tried on a complete erase and reinstall without adding any other software or just in Safe Mode?

The quarantine check will happen with certain types of downloaded files.

This started happening to me once upgraded to High Sierra. I have a network drive shared with smb protocol, which always worked flawlessly. Now every movie I try to play (any type, mkv, avi,...) I have to wait minutes while the application (QuickTime or VLC) "verifies" the file...

fabio56 wrote:

"a complete erase and reinstall" is a Windows habit. I come from Linux and I don't consider it neither as a last resort.

No, it establishes a baseline to test third-party software interference.

At this point and time No One should have to do a complete erase and reinstall.

Sure there is. If you have a problem that only affects a very small subset of users, there is likely something unique about your configuration. Eliminating all possible software conflicts is a necessary troubleshooting step. You can uninstall one-by-one, but it is simpler to just nuke it and test.

I must have missed the post where someone reported doing that. The closest I found was someone tried it on a Mac at an Apple Store. It could be something with the new hardware. As I stated, I do not see the problem on my two older Macs. There also isn't thousands of people piling on with "me too," just a handful. So, the problem may be fixable, but you can't fix it without troubleshooting.

It could be software, it could be hardware, it could be specific file type.

The largest video file I have to test is 4GB and it opened immediately without any "verifying" dialog box. That was on an external spinning hard drive. I tried a 2.5GB file from a NAS mounted via SMB. Same result.

It may not be worth any of your time to troubleshoot, but that's pretty much all you've got if Apple says it works as designed.

I have been lurking for a while, but suffer the same problem everyone else does.

It occurred to me this morning that at one point my Mac Mini ran the "Server" version of MacOS that no longer exists (I think). I wonder if that has something to do with this issue?

Just a thought. Sorry if it doesn't help.

-Richard

fabio56 wrote:

No, it establishes a baseline to test third-party software interference.

Totally disagree. That's just Microsoft's sad empiricism.

On Windows, that is a method to make the computer actually work. It is intended to "fix" something.

This has nothing to do with trying to fix the problem. It is troubleshooting to determine the source of the problem.

I don't imagine it will fix the problem. But you have to establish whether the problem exists absent any third-party system modifications.

I have the same problem, and it happens every time I try to open a video file.

I'm not using FileVault. I do use Time Machine, but it is set not to back up my video workspace folder. I'm on High Sierra, and the problem existed on the original install, and after the recent bug fix install.

I'm using an external Thunderbolt 2 2-bay RAID drive formatting to HFS+. In a typical workflow, I open a video in QT to check the quality, and must wait through the verification process. Then I open the video in Subler to add tag information, and must wait through the process again.

I'm losing a LOT of my day to this bug.

Reply to Barney-15E

Actually, Apple has to determine source of the problem, not user. Not only that, they even have to find the problem during testing phase. Anyway, thanks for checking out that on your system there is no problem.

Now there is another update - by doing a clean install (wiping the drive and reinstalling from internet recovery) I have managed to "fix" the verifying problem on 2 separate machines.

Turns out that Apple support were just telling lies to me, or maybe those were not lies but their creative thoughts. Quite disappointed, because had they told me that there should be no "verifying", could have had a working Mac way sooner.

Actually, Apple has to determine source of the problem, not user.

Only if it is actually a bug in the software that Apple created. Third-party problems are up to the developer to fix.

When you can determine the cause, both the developer and Apple can work together to fix the problem

Apple doesn't test third-party software. They do get reports from users which they pass on to developers, but unless they know what software caused the problem, they can't do anything about it.

Since the problem is limited to a very few users, it is likely third-party software or some obscure configuration. Apple doesn't test for those things. A beta tester may stumble upon it and pass it on to Apple.

As I already stated, if you want to fix the problem, you will have to determine the cause.

Turns out that Apple support were just telling lies to me, or maybe those were not lies but their creative thoughts.

First tier support generally only know enough to read a script. They don't know anything about the underlying code or how it is supposed to work unless their script tells them so.

Even the second tier is merely trying to pass the info to engineering which passes information back to you through them. The results are often the same as you get when playing the telephone game.

Had to recovery mode. Command option r on start up. Then deleted internal HD. Formatted to AFPS. started as new mac. Then had to drag and drop files from time machine backups to new user. It worked out pretty good. All I lost was previous settings. Hope this helps. Kind of a pain.