Mac App Store shows pending update for update that was done

Discussion in 'Mac Basics and Help' started by Dozer_Zaibatsu, Mar 16, 2017.

  1. Dozer_Zaibatsu macrumors member


    Mar 16, 2017
    North America
    I'm asking this question here because I am looking outside the box for some solution. I do some back-end things for Macs at our company, and usually answer helpdesk questions when they get stumped. Well, this is stumping me.

    We have a user who is running El Capitain on his system. He is a developer, so he does do a lot of things to change his machine, so we anticipate some things may not make sense. He installed a recent security update, which I believe is this one:

    His App Store is still showing that the update is pending. He can't hide it, and he can't run it again. I'm trying to see what this might be. He is the only user of the machine. The other accounts on it are two local IT tech accounts, and macports. The machine is bound to Windows AD (with his profile as a mobile profile) and is managed by JSS.

    We manage configuration policies through JSS, and they are closely monitored. I don't see anything different about his configurations than anyone else's.

    I've gone through what I would think would normally flush this out. First I had him remove the from the Library. That didn't do it.

    Then the following removals,

    rm -r ~/Library/Caches/
    rm -r ~/Library/Caches/
    rm ~/Library/Preferences/
    rm ~/Library/Preferences/
    rm ~/Library/Cookies/

    Also had him re-index Spotlight, None of these items have remedied the issue.

    With a pending Sierra update we'll be pushing out to users, we reckon that might fix it, too. But I'm wondering if there is something here that we've missed.
  2. chown33 macrumors 604

    Aug 9, 2009
    Sailing beyond the sunset
    There's a command-line tool for managing software updates:

    I'd start with that, and use it to peek and poke around on the errant system.

    I'd also try the App Store using one of the other user accounts on that system, and see if it shows the same misbehavior. This would tell you whether the problem lies in the system-wide domain or the user domain. I would expect a system-wide update to be managed in the system-wide domain, not the user domain. All the files you listed as removing are in the user domain.

    Those are just guesses, so don't be surprised if they're fruitless.

Share This Page