Every time I shut down my computer, I get the message that an app is preventing it from shut down:
Task Host Window
Task Host is stopping background tasks. Microsoft\Windows\Device Client\RegisterUserDevice
I read that this is possible to happen after an update. In fact, my update status is Checking for updates all the time. The last installed update is on April 6th (about Office 2013).
Is there anything I can do to stop this?
Help can come faster if you include in your post the version of Windows so we don't have to ask and wait for an answer. And then you encounter further delays waiting for us to reply again. And since shutdown issues may be different between a PC and notebook, knowing the type computer can help you get your solution faster too.
If this is Windows 10, I suggest you go to Settings > Update & Security > Troubleshoot > Power > Run the troubleshooter.
QuoteHelp can come faster if you include in your post the version of Windows so we don't have to ask and wait for an answer. And then you encounter further delays waiting for us to reply again. And since shutdown issues may be different between a PC and notebook, knowing the type computer can help you get your solution faster too.
It's true that I'm writing whatever I remember and asking a lot, all the time. I'm sorry for that. It won't happen again (well... only if I get a rootkit). But it's also true that I never asked for a fast reply. Anyway, I'm also sorry about not giving my computer's info in the first post (Windows 10, Dell laptop).
Just writing here to say that the particular problem is solved (by deleting Downloads content in Software Distribution, and restarting the computer).
Thanks.
QuoteIt's true that I'm writing whatever I remember and asking a lot, all the time. I'm sorry for that. It won't happen again
But it's also true that I never asked for a fast reply. Anyway, I'm also sorry about not giving my computer's info in the first post (Windows 10, Dell laptop).
I
never said anything to suggest you "
asking a lot, all the time" is a problem. It's not at all. That's why we are here. But you have to remember we need you to help us help you. We cannot read minds, or be expected to remember each of the 1000s of members who post here, or their computer's specifications - especially when they might have several computers in their homes.
And it is not just about you getting a fast "reply". It is about you getting a fast "
resolution" to your problem
in the most efficient manner. By "most efficient", that includes the most efficient use of our time too. Remember, all the helpers here are volunteers who donate our spare time helping posters. So if we don't have to go back and forth just to get the basic information about the computer or problem, it gives us more time to help you, and others seeking help too.
QuoteJust writing here to say that the particular problem is solved (by deleting Downloads content in Software Distribution, and restarting the computer).
That's great! I am glad you got it sorted out and thanks for coming back and posting your solution! Note by you doing that, it does not leave us dangling wondering what happened. But also, you help make the forum more efficient because new posters with the same problem searching for a solution may see your solution and fix their own computer right away, without having to post or wait for any replies. And that's a very good thing.
Perhaps my words didn't sound properly and I honestly apologize.
All is good.
Have you got this update (KB4093112) without problems?
I had to apply the solution above to let it finally installed in five computers (colleagues and family), although it seems that different solutions can also be applied.
The symptoms were not the same at all computers, but the result was the same: Update failed to install.
Symptoms I noticed:
> Task Host Window issue.
> Updates status: checking for upates all the time.
> Updates awaiting for a restart, and after the restart: Update failed.
> Update's installation stopped at 70%.
KB 4093112 installed fine for me.
KB4093221 - Successfully installed on 4/10/2018 on 3 systems here, on 4/11 on the other 3 systems.