Here's A Weird One

Discussion in 'other software & services' started by itman, Apr 22, 2021.

  1. itman

    itman Registered Member

    Joined:
    Jun 22, 2010
    Posts:
    8,648
    Location:
    U.S.A.
    Reviewing my Win 10 x(64) 20H2 Event logs yesterday, I observed Win Store app was crashing. Actually, I was alerted to something amiss while monitoring network connections in TCPView, I noticed all the Win Store connections disappear shortly after appearing at system logon time.

    Win Security Maintenance showed one instance on 4/20 due to "Hang type: Quiesce."

    Store_Hang.png

    There were also three more instances on 4/21 corresponding to system logon activity due to "Hang type: cross-process." The strange part is it didn't occur for every logon.

    Fixed the issue, at least so far, by performing a system restart. As best as I can determine this was not related to any system update activity. Never saw this one before.
     
  2. Rasheed187

    Rasheed187 Registered Member

    Joined:
    Jul 10, 2004
    Posts:
    18,178
    Location:
    The Netherlands
    Well, it might be a different issue, but after updating Win 10 1909, I'm having problems with the AppX Deployment Service which is linked to the Windows Store which doesn't launch anymore on my system. And svchost.exe keeps using 10% of CPU time without any good reason, so I will now need to reinstall Windows or upgrade to Win 10 20H2 which may make things even worse, who knows. Thanks a lot M$ for wasting my time! :gack:
     
  3. itman

    itman Registered Member

    Joined:
    Jun 22, 2010
    Posts:
    8,648
    Location:
    U.S.A.
    Refer to below screen shot for possible sources for service non-startup. Also the service doesn't run constantly. It is started and stopped on demand.

    Win_AppX.png
     
    Last edited: Apr 22, 2021
  4. Rasheed187

    Rasheed187 Registered Member

    Joined:
    Jul 10, 2004
    Posts:
    18,178
    Location:
    The Netherlands
    I'm not sure what you mean. The problem was that this service is always running after reboot, so I had to kill it. But the problem with high CPU usage has been solved by uninstalling certain Windows updates. However, certain things are still broken so I will probably need to perform a full system reset.
     
  5. Brummelchen

    Brummelchen Registered Member

    Joined:
    Jan 3, 2009
    Posts:
    6,294
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.