Your best friend for file transfer.

Fetch application logoFetch

Sierra 10.12.2, Fetch stopped working after updateing the operating system (8 posts)

  • Started 10 months ago by ööö
  • Latest reply 10 months ago from Charlene
  • ööö Member

    I have MacBook 13#, late 2012. Operating system is MacOS Sierra 10.12.2
    I have also Fetch 5.7.1 (5H459, Web Store). Now it does not work any loger, after updating to Sierra. If I try to use/open Fetch, a window appears "MacOS error 67818.
    What should I do?

    Posted 10 months ago #

  • Jim Matthews Administrator

    I'd download Fetch 5.7.6 from

    http://fetchsoftworks.com/fetch/download/latest

    Please let me know if it does not work for you.

    Thanks,

    Jim Matthews
    Fetch Softworks

    Posted 10 months ago #

  • Meow Member

    i'm using iMac, late 2012, Operating system is MacOS Sierra 10.12.2
    When i finished downloading, i click to open and install the software,
    my OS show warning " Image not recognized"
    i cannot install it.
    can u help?

    Posted 10 months ago #

  • ööö Member

    I have already replied: it works after updating it.

    Posted 10 months ago #

  • Jim Matthews Administrator

    Hi Meow,

    Try restarting your Mac and re-downloading from

    http://fetchsoftworks.com/fetch/download/latest

    Let me know if that does not work.

    Thanks,

    Jim Matthews
    Fetch Softworks

    Posted 10 months ago #

  • Charlene Member

    Will fetch v 5.3.1 no longer work? I upgraded to Sierra 10.12.2 and fetch gives me an error:

    "MacOS error 67843"

    I'm also working on a MacBook Pro (Retina, 13-inch, Early 2015)

    Thank you,
    Charlene

    Posted 10 months ago #

  • Charlene Member

    I also restarted my computer and Fetch just freezes with the error code I listed above. I need to force quit Fetch.

    Posted 10 months ago #

  • Charlene Member

    The upgrade to the latest v of Fetch worked.

    Posted 10 months ago #

Reply

  • Or nickname, if you prefer.
  • This will be kept confidential.
  • This is to ensure that you’re a person, not a spambot.