Host Process For Windows Tasks stopped working, Windows 10 1903

RobOss1943 said:

I do like recieve the instructions, so that I might can resolve the problem.

Hi, Rob,

There are two problems to rectify which don't appear to be related to the Host errors. But we stumbled over them as we were researching the problem and they have worked for a couple of us. At the very least they will put right two other problems (if you have them).

Lee

- - - Updated - - -

ONE

1. In the Search Window, type 'Powershell' until you get 'Windows Powershell'. Then right click on 'Windows Powershell' and left click on 'Run as Administrator'. When you get the command line, paste in or type the command (pay attention to the space):

sfc /scannow

The system is scanned. Once it completes, the new error we got was that there were problems that could not be resolved. It gives you a Windows path to a log (CBS.log) where it's been recorded. Go there and open the log file. At the very bottom of the text and scrolling up, you should see numerous errors relating to Windows Defender, stating that the back up image was also corrupt and could not over-write the problem files.

If that's the problem, then proceed with the following.

2. In the Serach Window, type 'Command Prompt' until you get 'Command Prompt'. Then right click on 'Command Prompt' and left click on 'Run as Administrator'. When you get the command line, paste in or type each of the commands, one by one, and let each one run to completion before beginning the next (again, pay attention to the spaces). Some of the processes seem to 'hang' after 100% is reached but be patient and wait:

DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth

This is telling the computer to use the online resources to clean up the system image that Powershell has just tried to use.

It take a few seconds for the percentage counter to begin. When it ends at 100%, WAIT. It looks like it's frozen but it will take a few minutes before it tells you that the process has been completed and a new command prompt appears (like it was in the beginning).

Close the window when completed.

3. WAIT a few minutes (some posters stated that they had to wait before the next would work. I have no idea why).

4. Now repeat point 1, EXCEPT that, at the end of the process, you should get a statement that the files were repaired/over-written.

5. Reboot the computer.

6. Run scannow once more and, this time, there should be nothing found.

.oOo.

This seems a strange way to resolve the original problem but it will resolve the corrupt Windows Defender files and program. Only 5 days of no errors in Reliability Monitor with "Host Process For Windows Tasks" will test whether this really works.

- - - Updated - - -

TWO

Go to Event Viewer (Windows Key + X) then Windows Logs (on the left) and Application. Scroll down (in the middle) and see if you're getting ESENT errors (red circle, white x) with the ID Code 455.

If you are, go and find out the very first Host error you got and then go and see if the first ESENT error you got was within 12-24 hours prior to that time and date. There should be no Host errors prior to the first ESENT error.

I also looked at what .dlls taskhostw.exe accesses and one of them is the ESENT.dll - that's what made the connection with us at first.

So, the solution to rectify the ESENT errors (and, hopefully, the Host errors, too):

Go to Windows\system32\config\systemprofile\AppData\Local\
Create the folder TileDataLayer then inside that folder create Database folder.
In effect, you've just made the directory:

C:\Windows\system32\config\systemprofile\AppData\Local\TileDataLayer\Database

Pay attention to the capitalisation.

The ESENT errors should stop immediately. Again, only numerous days waiting will see whether this solves the Host problem.

A person who found the Windows Defender solution had worked, noted that the files were already present at the time of the scannow run *but* that the system modified one of the folders as part of that resolution. We thought that this could be why the solution worked for him but not for us.

.oOo.

These two workthroughs resolve two different issues but they have resolved the Host problem on some computers. I have no idea why but it's worth a try.

- - - Updated - - -

And there's another possible solution...

THREE

A few people are suggesting that the problem is with .Net Framework (which can't be uninstalled). Some have found this to be a solution, though:

In the search window, begin to type 'Turn Windows Features On or Off' and then select it.

Uncheck .Net framework 4.8 Advanced Services and allow the computer to make the changes.

Reboot. Recheck the item.

It's just a switch off and on again but - what the heck? - it's worth a go.

Lee

daknut said:

Honestly? Do all three. There's a few of us who think that it may be a combination of factors. But at least the first two...

I have done both method 1 and 2; now we wait.

- - - Updated - - -

Update: I'm no longer getting ESENT errors. I looked in the Database folder and can see log files being created; so I can tell that method 2 fixed the ESENT errors. Now I will wait to see if taskhost errors will pop up again or not.