Mystery app preventing Windows 10 shutdown after update.

Anonymous
2018-02-10T04:10:34+00:00

Since a Windows 10 update a few weeks ago, when I go to shut down, it says it is closing and there is an app running  ------- but there is no app running   So I wait for it to close that nonexistent app, and after a few minutes, I am back to the computer being ready to work, not shutting down. When will a new update fix this?  Yesterday's update did not fix this. It is not a serious problem, but it is annoying to have to click "Shut down anyway" to really shut down.  What is this app that hides itself and won't quit?

[Moved from Windows / Windows 10 / Windows update, recovery, & backup]

Windows for home | Windows 10 | Sleep and Power on, off

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

131 answers

Sort by: Oldest
  1. Anonymous
    2020-03-01T12:00:38+00:00

    Hi. I've had this same issue for some months - a phantom, unnamed app that's preventing shutdown. I'm not interested in a workaround to bypass the message because I'd actually like my PC to shut down normally OR to flag up a genuine app that is stopping it ... perhaps due to unsaved work.

    If there is a Microsoft Tech or other guru on here who can guide me by using the notes below, I'd be very grateful. 

    I've run all the tests recommended on this and other threads (System File Checker, etc) and they all come up clean. Then I checked the Windows Event Log as recommended on another thread. Using that, I believe I've found the problem. I just don't know how to fix it. The log shows an error flag immediately after an abortive shut down attempt.

    Does anyone know if there is a change I can make to remove this error and allow the PC to shut down normally?

    The messages in the log are:

    Activation context generation failed for "C:\Program Files (x86)\Microsoft Office\root\Office16\lync.exe.Manifest".Error in manifest or policy file "C:\Program Files (x86)\Microsoft Office\root\Office16\UccApi.DLL" on line 1. Component identity found in manifest does not match the identity of the component requested. Reference is UccApi,processorArchitecture="AMD64",type="win32",version="16.0.0.0". Definition is UccApi,processorArchitecture="x86",type="win32",version="16.0.0.0". Please use sxstrace.exe for detailed diagnosis.

    System

    Provider

    [ Name]

    SideBySide

    EventID

    35

    [ Qualifiers]

    49409

    Level

    2

    Task

    0

    Keywords

    0x80000000000000

    -

    TimeCreated

    [ SystemTime]

    2020-02-29T21:23:34.207666100Z

    EventRecordID

    1270

    Channel

    Application

    Computer

    DELL-P07N6C3

    Security

    EventData

    UccApi,processorArchitecture="AMD64",type="win32",version="16.0.0.0"

    UccApi,processorArchitecture="x86",type="win32",version="16.0.0.0"

    C:\Program Files (x86)\Microsoft Office\root\Office16\lync.exe.Manifest

    C:\Program Files (x86)\Microsoft Office\root\Office16\UccApi.DLL

    1

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2020-03-01T18:01:42+00:00

    As a retired federal tax software developer, my customers would not have accepted this kind of quality for so long.  

    Step one - don't give me work-arounds - call it what it is A BUG!  Microsoft has more trouble saying "BUG" than "radical Islamic Terrorist"

    Step two - Identify the program in question instead of a generic icon with no identity.

    Step three - FIX IT!

    Follow Up - Give us real problems instead of codes.  There are a lot of users that could fix their own issues if the Microsoft errors weren't so encrypted.  I have been around since before Windows 95.  I don't need (or want) a computer that tries to replicate a smart phone.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  3. Anonymous
    2020-03-07T17:02:59+00:00

    I have had the same problem since an update in 10/2017, so this is unlikely to be addressed now.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2020-03-08T00:46:30+00:00

    I have had the same problem since an update in 10/2017, so this is unlikely to be addressed now.

    It would seem there is no ACTUAL support for bug fixes, only "enhancements."  I suspect Microsoft is now run by robots, there are no humans available by phone, and if you want help, you must contact the "Community."   You may have bought your PC, but you don't own it.  

    Every time they do an upgrade, I loose all my network security and sharing settings.  I have 7 PCs, including 2 laptops & one XP (for Legacy equipment they do not support in Windows 10)  plus a NAS, so it's a pain in the butt to try to keep them all running and talking to each other.  My first PC was an 8080 S-100 based system that I wire-wrapped myself, so I'm not new to the game (almost 50 years).  Microsoft is no longer my friend....

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2020-03-08T02:40:03+00:00

    I have had the same problem since an update in 10/2017, so this is unlikely to be addressed now.

    It would seem there is no ACTUAL support for bug fixes, only "enhancements."  I suspect Microsoft is now run by robots, there are no humans available by phone, and if you want help, you must contact the "Community."   You may have bought your PC, but you don't own it.  

    Every time they do an upgrade, I loose all my network security and sharing settings.  I have 7 PCs, including 2 laptops & one XP (for Legacy equipment they do not support in Windows 10)  plus a NAS, so it's a pain in the butt to try to keep them all running and talking to each other.  My first PC was an 8080 S-100 based system that I wire-wrapped myself, so I'm not new to the game (almost 50 years).  Microsoft is no longer my friend....

    Microsoft has never been anyone's friend ----- unless you count stockholders.

    Was this answer helpful?

    0 comments No comments