Verifying progress bar on every file?

Discussion in 'OS X El Capitan (10.11)' started by victorhooi, Jul 14, 2015.

  1. victorhooi macrumors member

    Joined:
    Mar 29, 2011
    #1
    I recently updated to OSX 10.11 DP3.

    Now, it seems whenever I open any file (binary or even media files), I get a prompt about "Verifying <filename>"

    [​IMG]

    It eventually disappears after a few seconds, but it is quite annoying that it happens for every file.

    Has anybody else seen this with El Capitan? Any way to get rid of it?
     
  2. MacManiac76 macrumors 65816

    MacManiac76

    Joined:
    Apr 21, 2007
    Location:
    Arizona
    #2
    It looks like it might be a FileVault bug. Do you have it enabled by chance?
     
  3. victorhooi thread starter macrumors member

    Joined:
    Mar 29, 2011
    #3
    Yes, I am using FileVault.

    Hmm, is this a new bug in OSX 10.11 DP3?

    If so, I suppose there's no workaround yet?
     
  4. MacManiac76 macrumors 65816

    MacManiac76

    Joined:
    Apr 21, 2007
    Location:
    Arizona
    #4
    I don't use FileVault so somebody else will have to chime in on whether it is a new bug and if there is any workaround yet.
     
  5. Bilskov macrumors newbie

    Joined:
    Jul 28, 2015
    Location:
    Nørager, Denmark
    #5
    I do not use FileVault either, but it shows up on my mac nearly every time. Sometimes when opening a pdf file, it takes 5 minutes before the verifying process is ended. Very annoying.
     
  6. redheeler macrumors 603

    redheeler

    Joined:
    Oct 17, 2014
    #6
    Not FileVault, Gatekeeper most likely. You can disable it by allowing apps downloaded from anywhere in System Preferences > Security & Privacy.
     
  7. jsamuels macrumors member

    Joined:
    Feb 16, 2008
    Location:
    Roma
    #7
    Gatekeeper is disabled on my B5 system and I still receive the verifying" message. Just started since the update. p.s. I do not use FileVault.
     
  8. yurai macrumors newbie

    Joined:
    Mar 18, 2009
    #8
    Same problem since beta 3 - sometimes the progress bar takes minutes to verify the file...
     
  9. Gjwilly macrumors 68030

    Joined:
    May 1, 2011
    Location:
    SF Bay Area
    #9
    I get around this by opening every file twice.
    In other words, I double-click the file to open it and before the verification bar has a chance to open I double-click the same file again. That will usually make it open.
     
  10. yansun macrumors regular

    Joined:
    Mar 26, 2010
    #10
    Since today I have this issue too... Is there any solution to it by now? I'm on 10.11.4 PB2.
     
  11. KALLT macrumors 601

    Joined:
    Sep 23, 2008
  12. yansun macrumors regular

    Joined:
    Mar 26, 2010
    #12
    Allow apps downloaded from is set to anywhere, firewall is disabled and filevault is disabled too.
     
  13. KALLT macrumors 601

    Joined:
    Sep 23, 2008
    #13
    Does this happen with the same files every time? Does it happen with every file of the same kind or just specific ones? Maybe XProtect verifies such files if they originate from the web.
     
  14. yansun, Feb 13, 2016
    Last edited: Feb 13, 2016

    yansun macrumors regular

    Joined:
    Mar 26, 2010
    #14
    It happens with every file of the same kind every time. Seems to be an issue with certain media files (avi, mkv, mp4, not mp3) and archives. The strange thing is as I said that this was not an issue until today.
    Btw. double clicking the file two times as Gjwilly suggested doesn't help either. This just opens the verifying bar two times.
     
  15. leo.andres.21 macrumors regular

    Joined:
    Oct 14, 2008
    Location:
    Centre of the Attention
    #15
    It's been happening to my macbook too on 10.11.4 beta build 15E39d.
    When I tried to open a mp4 or even calibre, it starts verifying the file. I thought my SSD starts to get slow, but then I remember just updating to the new beta OS and I figured that might just be the problem.
     
  16. yansun macrumors regular

    Joined:
    Mar 26, 2010
    #16
    I went back to an older time machine backup of the same build 15E33e and there is no verifying issue anymore... Really strange. Don't know what caused it.
     
  17. dgdosen macrumors 65816

    dgdosen

    Joined:
    Dec 13, 2003
    Location:
    Seattle
    #17
    I think I see one cause of this - is everyone seeing this happen on a beta build of OSX?
    - yes for me (10.11.4 B3)
     
  18. KALLT macrumors 601

    Joined:
    Sep 23, 2008
    #18
    Then I suggest you put the Feedback Utility to good use. ;-)
     
  19. alfon_sico macrumors member

    alfon_sico

    Joined:
    Oct 3, 2015
    #19
    Beta 4 here. same verifying issue open video files
     
  20. IowaLynn macrumors 6502a

    IowaLynn

    Joined:
    Feb 22, 2015
    #20
    copying jpeg folder 240MB took endless amount of time, had to f.q. Finder. b4 also.

    Is it calling home somehow or reason?
     
  21. abn0rmal macrumors newbie

    abn0rmal

    Joined:
    Feb 23, 2016
    Location:
    Kyiv, Ukraine
    #21
    The same thing happened with me too after updating to 10.11.4 Beta (15E39d).
    The only way to play MOV files without verifying it is using Preview.
    FileVault not enabled in Preferences. Any suggestions how to disable it on a system-level?
     
  22. Eithanius macrumors 65816

    Joined:
    Nov 19, 2005
    #22
    10.11.4 PB4 may have fixed the problem...
     
  23. alfon_sico macrumors member

    alfon_sico

    Joined:
    Oct 3, 2015
  24. wallybally macrumors newbie

    wallybally

    Joined:
    Feb 24, 2016
    #24
    It seems to have something to do with ownership. I had .mp4 files on external drives or on network volumes that gave the same issue. Also, files in one folder on a volume did not trigger the verifying issue, whilst files in another folder on the same volume did. After correcting the ownership, letting everyone read and write, no more verifying.

    This one is solved.
     
  25. leo.andres.21 macrumors regular

    Joined:
    Oct 14, 2008
    Location:
    Centre of the Attention
    #25
    the problem went away after I updated to beta 4 thankfully.
     

Share This Page