Mystery app preventing Windows 10 shutdown after update.

Well, actually, the update IS part of the problem ----- the update apparently has confused the system into thinking that a process is actually the whole app.  This misidentification of app is what is causing the erroneous message that an app is running, when it is only a process of that app.  In my case, I had SMS Listo running on my Windows 10 with no problems at all ---- but after the update, a background process of SMS Listo was then considered the whole app, which Windows could not shut down, because it was trying to shut down an app, which, of course, was not running.

... and I thought, I got a Trojan/virus with the message unknown app blocking  shut down ...

VHV

I have had exactly the same problem, along with at least the 66 other people who replied they do too. There is no App running in the Task Master. It is an App icon that does not show up when I look for it under my Apps, and only occurred after the update. Very annoying to have to click ignore every time.

Hi Alan

I wish I had an answer for you but after reading through the forum (because I have EXACTLY the same time wasting issue) I just wanted to commend you for keeping your cool (mostly :) while other time wasters gave you the equivalent of 'have you turned it off and on'.

Well done 

Thank you, Ian

you know what, on XP and 7, on occasion, I had that happen, it eventually stopped. I just spent that split 1/2 second to press the button force them/it closed and didn't give it another thought.

That analogy for the car to this, is a little off kilter. But I understand the point you are making.

Thank you for sharing your memories of similar (but nevertheless only occasional) experiences with XP and 7 and for regaling us with the tale of your almost Buddhist-like acceptance in the face of minor adversity.  Happily for you, the occasional experiences eventually stopped. Perhaps you have failed to understand that my experience with this issue is consistent and on-going. It is NOT "occasional" and it has NOT "eventually stopped".

I am mystified by your comment that my analogy is "a little off kilter". In both cases an operation which had formerly required one operation now requires two operations.

I'd be interested to know how many others have experienced this issue with Microsoft's system update of approximately one month ago.  If there are no others, perhaps the fault lies in my computer. If there are others, the fault lies with the update.

Alan,

I am having the exact same issue (including all of your screenshots and the exact same icon you show in your picture).  I completely agree that it is not only annoying, but it hinders any updates or other processes that require a restart. This issue subsequently holds up the restart and shutdown process which at times I have requested in advance through an installation or update process.  Instead of me coming back to my computer with the process completed, I instead have to click the "Shut Down/Restart Anyway" button which should NOT be necessary, and then sit and wait for something that should have been done if this error had not occurred.  This has actually in turn wasted hours of my time so far, and prevented me from both getting tasks done in a reasonable amount of time and even kept me up late at night multiple times when I could have already gone to sleep.  It's not just a "half-a-second", one extra step issue.

As for those that want to waste their time constantly repeating back with how it's no big deal, I request they stop wasting their time and ours, and stop filling up the resolution discussion forum with a bunch of wasted space of junk filled, worthless babble just to act as though they are somehow superior and above the error (which they aren't even experiencing I might add).  An error is an error.  The software is not working properly, essentially the definition of a system error. This forum is here, at least in part, to discuss and discover a solution to errors that are occurring with Microsoft software.  If you cannot be a part of that solution, I respectfully request that you do not waste everyone's time with your reply. How you FEEL about it is not important, useful, and means NOTHING to those experiencing the error which again, by definition, should not be occurring and should be brought to Microsoft's attention so that it can be fixed for all those experiencing it.

Alan, I hope you and everyone else that responded as having the same problem have been successful at getting the issue resolved.  I am waiting for my computer to do the update which was prevented by this error, and hope this update will finally be the solution needed to resolve it.

Thank you Alan for all of the time and effort you have taken to post about this error, and all of the follow-up screenshots to help get to the bottom of it for all of us experiencing it as well.  I am sorry you had the unnecessary, pointless added annoyance and frustration from those discussed above.

Thank you, Nighthawk XO, for your comment. As for the "unnecessary, pointless added annoyance and frustration" from the other contributors, I totally agree . Unfortunately, it's been my experience with this and other "forums" that there are always those that just like to throw in their two-cents worth, even though it may be worth nothing. Thanks again for your comment.