This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
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]
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.
Yes, I am having the same non-occasional "App still running...' when ever I shut down my HP laptop shortly after one of Microsoft's Windows 10 updates. I'm joining this message stream a little late but I agree 100% that we should not have to choose "Shutdown Anyway" when shutting down!
Your point, in a nutshell, is "Suck it up and live with it".
To me, your assertion that my issue is a "non-issue" of no concern is just another way of saying that you haven't a clue as to what caused it nor a clue as to how to fix it.
Awaiting more helpful responses from others.
Thanks for your contribution to the discussion.
I agree with Alan absolutely This has been irritating me for months and one does wonder whether there may be an adverse effect when having to force close an anonymous application. I despair at the illiteracy of MS personnel who ask "what app?" when clearly told that it is not possible to identify because it arises in the close down routine. MS have clearly lost a lot of goodwill through insisting that they own and control the software we paid for. Every forced "improvement" results in countless wasted hours researching why something else now does not work, often to discover that there are literally millions suffering the same pain.
I had the same issue as you did. I identified the application that was preventing Windows 10 from cleanly restarting or shutting down using your method. The issue is with BESClientUI.exe, which is IBM Endpoint Manager Client, or BigFix. We were using version 9.1.xxxx, which was never supported for Windows 10. The Windows 10 platform was supported in clients as of the 9.2.5 version. You must be at least on that version on the endpoint. I updated to a newer version of BigFix. Problem solved. If the old 9.1.xxxx version was ever installed on a PC, and then you install the new version, the problem persists. A registry entry must be left over somewhere.
Info on the program
From <https://forum.bigfix.com/t/windows-10-compatible-bes-client/17852>
Good compatibility docs
With VOIP Connect, if you go to Tools > Options > Advanced and UN-check the box that says "Start VOIP Connect when I start windows", that should eliminate the problem the next time the computer is turned on.
Since I had had VOIP Connect installed on my computer with no problems until a Windows Update came along, I'd say the problem is with Windows 10 update which is misidentifying a process as an app, and preventing a shutdown.
Thanks for the reply.
Sadly this makes no difference IF the user starts voipconnect manually after windows has started.
I still had his laptop here and did a quick test to make sure.
The user needs the program to be online while he uses his laptop so the issue remains.
With VOIP Connect, if you go to Tools > Options > Advanced and UN-check the box that says "Start VOIP Connect when I start windows", that should eliminate the problem the next time the computer is turned on.
Since I had had VOIP Connect installed on my computer with no problems until a Windows Update came along, I'd say the problem is with Windows 10 update which is misidentifying a process as an app, and preventing a shutdown.
