Task Host Window Preventing Shutdown/Logoff

Topic

New Reply

Having a problem the past 2 or 3 days when I go to either shutdown Windows or logoff my UserID in Windows 10.   Says that “Task Host Window” is preventing shutdown and I can wait for it to finish or return to Windows.  It went a whole night without finishing and shutting down, so something must be wrong.   I can tell windows to shutdown without waiting for program to finish, but not sure if that causes more harm.   A google search says I should try running something called Restoro to check for corrupt files, but can I trust that to fix my file system?   Any suggestions on how to solve this problem?

1 user thanked author for this post.

flyingdutchgirl

Reply | Quote

Replies

I get that all the time on shutdown and there is a selection to cancel. I click cancel and it goes for a little while and shuts down.

Don't take yourself so seriously, no one else does
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).

Reply | Quote

If I click cancel it will bring me back to windows.   Will not shutdown for me.

Reply | Quote

Try this, use command prompt (run as Administrator) and run this command-

DISM /Online /Cleanup-Image /RestoreHealth

If that comes back clean, type in sfc /scannow and see if that fixes anything.

Don't take yourself so seriously, no one else does
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).

Reply | Quote

AJrubin wrote:

A google search says I should try running something called Restoro to check for corrupt files, but can I trust that to fix my file system?

I suggest you read the following Restoro review article, especially the ‘CONS’, before considing using Restoro.

Hope this helps…

Reply | Quote

Is Fast Startup enabled? Fast Startup has caused “hangs” in shutdowns.

Try this to test:

Create a new shortcut on the Desktop.
Make the location shutdown /s /t:30
Name the shortcut Shutdown.

Clicking this shortcut will by pass making the Fast Startup file and gives open programs 30 seconds to shutdown before a forced shutdown occurs.

HTH, Dana:))

HTH, Dana:))

Reply | Quote

Thanks to all the people that gave me very quick replies to this problem. After persisting for 2 to 3 days with about 5 or 6 shutdown attempts, problem just disappeared on its own. I did not do anything specific. As far as I know, I do not have Fast Startup enabled, but will try the above recommendation for a shortcut if it happens again.

1 user thanked author for this post.

flyingdutchgirl

Reply | Quote

Do not worry, this “Task Host Window” hang is a Windows quirk and so far there has not been any damage caused by forcing it to quit, although the warning has persisted until Windows does it normal shutdown operation.

1 user thanked author for this post.

flyingdutchgirl

Reply | Quote

This just happened to me yesterday.  After reading all the posts, especially the one from I’m not a Robot, I clicked the Shut Down Anyway button.  Waited 5 minutes, started the computer with no problem.  (I did a restart for good measure, but probably had no effect.)  Shut down had no Task Host message.  Started up this morning, no problem.

Reply | Quote

I just started having this same problem a couple of days ago.  I usually have a few items that come up before shutdown, but they clear themselves if I wait a minute or so.  The one Task Host Window does not clear after even 5 minutes.  Forced shutdown does seem to work, with no consequences when I later reboot.  However, I wish I could find a way around this.  I hate to do the force shutdown.

By the way, most messages I found on the internet tie this back to a  Windows Update issue.  However, I have not made any updates since Sept 9 when I installed the August updates.  I also tried DISM and sfc, sfc reported it found no issues.  I ran the Windows Update Troubleshooting yesterday.  It said that it made a change, but I still had the issue when I shutdown last evening.  I ran it again today, and it said it could not detect any problems.

Reply | Quote

This problem just disappeared for me a few days ago.   I am not aware that I did anything specific to fix the problem.  I did update Thunderbird, Firefox, and a Logitech driver.   I also applied the September updates, but the problem had already disappeared before I did that.  I guess I just chalk it up to the vagaries of Microsoft.

Reply | Quote