verifying progress bar on every file.

There was no anti-virus software installed and FireVault was already turned off. I was happy to do a reinstall because the computer is brand new and I hadn't really done anything with it yet. I think that using the Migration Assistant was a really bad idea, and this time I have set it up more cautiously, without using the Migration Assistant.

Yepp. Activity monitor would show XProtect 99% cpu usage while opening. That’s on new iMac with i7. I even have the ssd.

Instead of exposing the Mac to security issue, I prefer to mount the share directly from Finder (Cmd-K). It works without problem.

My situation: every single file will be "verified" on my Mac Server in my home network. And for media files, it takes minutes to complete before they can be opened.

Opening the same file again time just repeat the same verifying process.

Reinstalled the High Sierra OS a few times, same result.

This time, Apple appears to have done everything possible to make reverting as difficult as possible.

My time machine backup which was fine just before, suddenly "fails" to restore (even it verifies OK, but "not able to transfer volume") and download of Sierra seems impossible too. I have tried even to use App Store framework, but get denied the download.

So, I would need to revert to El Capitan, which is not what I want to do either.

Finally, I am shocked that this kind of issue still has to be handled by the "support community". At times it seems that "support community" will soon need to actually write an OS which "just works", because Mac OS already does not.

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.

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.

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.

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.