HT203425: Mac App Store: Unresponsive after clicking Updates icon

Learn about Mac App Store: Unresponsive after clicking Updates icon
ET3333

Q: Cool, that must work. But what are NTFS filesystems?

My Mac App Store is tottally unresponsive. I've seen a way to fix by putting the NTFS filesystems in the privacy tab on Spotlite. Call me ignorant, but I don't know whar NTFS filesystems are, so it is a bit difficult for me to solve my problem.

 

Anyone can help?

MacBook Air, OS X Mavericks (10.9)

Posted on Feb 1, 2014 11:50 AM

Close

Q: Cool, that must work. But what are NTFS filesystems?

  • All replies
  • Helpful answers

  • by Allan Eckert,

    Allan Eckert Allan Eckert Feb 1, 2014 11:52 AM in response to ET3333
    Level 9 (54,050 points)
    Desktops
    Feb 1, 2014 11:52 AM in response to ET3333

    NTFS is a Windows files system

     

    The Mac should be able to read from a disk formated NTFS but not write to it without third party software

     

    Allan

  • by Linc Davis,

    Linc Davis Linc Davis Feb 1, 2014 1:35 PM in response to ET3333
    Level 10 (208,037 points)
    Applications
    Feb 1, 2014 1:35 PM in response to ET3333

    Please describe the problem, rather than your conclusion as to how it should be solved.

  • by ET3333,

    ET3333 ET3333 Feb 1, 2014 2:48 PM in response to ET3333
    Level 1 (0 points)
    Feb 1, 2014 2:48 PM in response to ET3333

    I can't neither access the Mac App Store nor Itunes Store. It is unresponsive, and it doen't show any error messages, it simply can't connect.

  • by Linc Davis,Helpful

    Linc Davis Linc Davis Feb 1, 2014 2:51 PM in response to ET3333
    Level 10 (208,037 points)
    Applications
    Feb 1, 2014 2:51 PM in response to ET3333

    If you haven't already done so, log out or reboot and try again. Otherwise, see below.

     

    Launch the Console application in any of the following ways:

     

    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)

     

    ☞ In the Finder, select Go Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.

     

    ☞ Open LaunchPad. Click Utilities, then Console in the icon grid.

     

    Make sure the title of the Console window is All Messages. If it isn't, select All Messages from the SYSTEM LOG QUERIES menu on the left. If you don't see that menu, select

    View Show Log List

    from the menu bar.

     

    Click the Clear Display icon in the toolbar. Then try the action that you're having trouble with again. Select any messages that appear in the Console window. Copy them to the Clipboard by pressing the key combination command-C. Paste into a reply to this message (command-V).

    When posting a log extract, be selective. In most cases, a few dozen lines are more than enough.

    Please do not indiscriminately dump thousands of lines from the log into this discussion.

    Important: Some private information, such as your name, may appear in the log. Anonymize before posting.

  • by ET3333,

    ET3333 ET3333 Feb 1, 2014 5:52 PM in response to Linc Davis
    Level 1 (0 points)
    Feb 1, 2014 5:52 PM in response to Linc Davis

    Thank you for your help. Here is what happened:

     

    01/02/14 23:38:27,806 com.apple.launchd.peruser.501[157]: (com.apple.appstore.23440[1005]) Exited: Terminated: 15

     

    01/02/14 23:38:36,917 spindump[1009]: Saved hang report for App Store version 1.3 (201) to /Library/Logs/DiagnosticReports/App Store_2014-02-01-233836_MacBook-Air-de-Fellipe.hang

     

    01/02/14 23:42:03,401 com.apple.launchd.peruser.501[157]: (com.apple.appstore.23440[1020]) Exited: Terminated: 15

     

    01/02/14 23:44:08,040 xpcproxy[1038]: assertion failed: 13A603: xpcproxy + 3438 [EE7817B0-1FA1-3603-B88A-BD5E595DA86F]: 0x2

     

    01/02/14 23:45:09,244 com.apple.iCloudHelper[1038]: AOSKit ERROR: Config request failed, url=https://setup.icloud.com/configurations/init, requestHeaders=

    {

        "Accept-Language" = "pt-br";

        "X-Mme-Client-Info" = "<MacBookAir4,2> <Mac OS X;10.9;13A603> <com.apple.AOSKit/176>";

        "X-Mme-Country" = BR;

        "X-Mme-Nac-Version" = 11A457;

        "X-Mme-Timezone" = BRST;

    },

    error=Error Domain=kCFErrorDomainCFNetwork Code=-1001 "Esgotou-se o tempo limite da solicitação." UserInfo=0x7fdb4b63b9f0 {NSErrorFailingURLStringKey=https://setup.icloud.com/configurations/init, NSLocalizedDescription=Esgotou-se o tempo limite da solicitação., NSErrorFailingURLKey=https://setup.icloud.com/configurations/init}, httpStatusCode=-1, responseHeaders=

    (null)

    01/02/14 23:46:09,292 com.apple.iCloudHelper[1038]: AOSKit ERROR: Config request failed, url=https://setup.icloud.com/configurations/init, requestHeaders=

    {

        "Accept-Language" = "pt-br";

        "X-Mme-Client-Info" = "<MacBookAir4,2> <Mac OS X;10.9;13A603> <com.apple.AOSKit/176>";

        "X-Mme-Country" = BR;

        "X-Mme-Nac-Version" = 11A457;

        "X-Mme-Timezone" = BRST;

    },

    error=Error Domain=kCFErrorDomainCFNetwork Code=-1001 "Esgotou-se o tempo limite da solicitação." UserInfo=0x7fdb4b528c90 {NSErrorFailingURLStringKey=https://setup.icloud.com/configurations/init, NSLocalizedDescription=Esgotou-se o tempo limite da solicitação., NSErrorFailingURLKey=https://setup.icloud.com/configurations/init}, httpStatusCode=-1, responseHeaders=

    (null)

    01/02/14 23:46:09,295 com.apple.iCloudHelper[1038]: AOSKit ERROR: Setup request failed, appleID=414023973, url=(null), requestHeaders=

    (null),

    error=Error Domain=AOSErrorDomain Code=1000 "A operação não pôde ser concluída. (AOSErrorDomain erro 1000.)" UserInfo=0x7fdb4b52f250 {HttpStatusCode=0, DialogInfo={

        DialogType = Unknown;

    }}, httpStatusCode=0, responseHeaders=

    (null),

    responseBody=

    (null)

  • by Linc Davis,

    Linc Davis Linc Davis Feb 1, 2014 6:18 PM in response to ET3333
    Level 10 (208,037 points)
    Applications
    Feb 1, 2014 6:18 PM in response to ET3333

    Please read this whole message before doing anything.

     

    This procedure is a test, not a solution. Don’t be disappointed when you find that nothing has changed after you complete it.

     

    Step 1

     

    The purpose of this step is to determine whether the problem is localized to your user account.

     

    Enable guest logins* and log in as Guest. Don't use the Safari-only “Guest User” login created by “Find My Mac.”

     

    While logged in as Guest, you won’t have access to any of your personal files or settings. Applications will behave as if you were running them for the first time. Don’t be alarmed by this; it’s normal. If you need any passwords or other personal data in order to complete the test, memorize, print, or write them down before you begin.

     

    Test while logged in as Guest. Same problem?

     

    After testing, log out of the guest account and, in your own account, disable it if you wish. Any files you created in the guest account will be deleted automatically when you log out of it.

     

    *Note: If you’ve activated “Find My Mac” or FileVault, then you can’t enable the Guest account. The “Guest User” login created by “Find My Mac” is not the same. Create a new account in which to test, and delete it, including its home folder, after testing.

     

    Step 2

     

    The purpose of this step is to determine whether the problem is caused by third-party system modifications that load automatically at startup or login, by a peripheral device, by a font conflict, or by corruption of the file system or of certain system caches.

     

    Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards, if applicable. Start up in safe mode and log in to the account with the problem. You must hold down the shift key twice: once when you boot, and again when you log in.

       

    Note: If FileVault is enabled, or if a firmware password is set, or if the boot volume is a software RAID, you can’t do this. Ask for further instructions.

     

    Safe mode is much slower to boot and run than normal, with limited graphics performance, and some things won’t work at all, including sound output and Wi-Fi on certain models. The next normal boot may also be somewhat slow.

     

    The login screen appears even if you usually log in automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.

     

    Test while in safe mode. Same problem?

     

    After testing, reboot as usual (not in safe mode) and verify that you still have the problem. Post the results of Steps 1 and 2.

  • by ET3333,

    ET3333 ET3333 Feb 1, 2014 6:50 PM in response to Linc Davis
    Level 1 (0 points)
    Feb 1, 2014 6:50 PM in response to Linc Davis

    Didn't work in neither tries.

  • by Linc Davis,Solvedanswer

    Linc Davis Linc Davis Feb 1, 2014 7:40 PM in response to ET3333
    Level 10 (208,037 points)
    Applications
    Feb 1, 2014 7:40 PM in response to ET3333

    Back up all data.

     

    From the menu bar, select

      

    System Preferences Network

      

    If the preference pane is locked, click the lock icon in the lower left corner and enter your password to unlock it. Then click the Advanced button and select the Proxies tab. If any proxy options are selected, make a note of them and then deselect them. You don’t need to change the bypass or FTP settings. Click OK and then Apply. Test. The result may be that you can't connect to any web server. Restore the previous settings if that happens.

  • by ET3333,

    ET3333 ET3333 Feb 1, 2014 11:46 PM in response to Linc Davis
    Level 1 (0 points)
    Feb 1, 2014 11:46 PM in response to Linc Davis

    Solved, thank you very much!

     

    It didn't have anything selected, but there was an exception to which the proxy settings should be ignored. I deleted it and it worked.

     

    Thanks again.