Host Process For Windows Tasks stopped working, Windows 10 1903

khoi3003 said:

Yeah Idk if I want to go through all that hassle for something that's just more of an annoyance at this point. Performance isn't affected so I'll probably just live with it at this point

Completely understand!

I put aside all of Sunday to set the computer back up again, thinking I'd have to reinstall programs, alter settings and recopy all my data files over.

But it never happened - in fact, I can't believe how non-intrusive it was. It seems to have even sorted out some other problems I was getting (which kinda makes me think that all of us are probably carrying some cumulative bugs that can't be fixed except by MCT).

Keep in touch and let me know if you ever get a full and final solution - I will update my large article on Microsoft's page if ever there is one.

I'm 51 hours into the reinstall and, so far, we're okay. But the wife (who hasn't had her laptop done yet) hasn't had any error messages in the time, either!!! These computers do *not* play fair.

daknut said:

Completely understand!

I put aside all of Sunday to set the computer back up again, thinking I'd have to reinstall programs, alter settings and recopy all my data files over.

But it never happened - in fact, I can't believe how non-intrusive it was. It seems to have even sorted out some other problems I was getting (which kinda makes me think that all of us are probably carrying some cumulative bugs that can't be fixed except by MCT).

Keep in touch and let me know if you ever get a full and final solution - I will update my large article on Microsoft's page if ever there is one.

I'm 51 hours into the reinstall and, so far, we're okay. But the wife (who hasn't had her laptop done yet) hasn't had any error messages in the time, either!!! These computers do *not* play fair.

Yeah, it is nice to know that I'm not the only one experiencing the problem, though

khoi3003 said:

Yeah, it is nice to know that I'm not the only one experiencing the problem, though

There will be thousands, tens of thousands affected. Who looks at Reliability Monitor? Most people I know stick their heads in the sand after they have the computer and don't look at what's going on.

There have been 106 views of the article I put together on the Windows site. And 1754 views of DonT's article that got me corresponding and trying to troubleshoot. Not many if you think about how universal W10 is but that's just the people who are trying to do something about it.

daknut said:

There will be thousands, tens of thousands affected. Who looks at Reliability Monitor? Most people I know stick their heads in the sand after they have the computer and don't look at what's going on.

There have been 106 views of the article I put together on the Windows site. And 1754 views of DonT's article that got me corresponding and trying to troubleshoot. Not many if you think about how universal W10 is but that's just the people who are trying to do something about it.

I agree. I'm just one of those who likes to know what goes on under the hood. But tbh, unless this problem somehow evolves and start affecting performance and usability, I'm not gonna let it bother me that much. As I said, it's more of an annoyance at this point.

daknut said:

There will be thousands, tens of thousands affected. Who looks at Reliability Monitor? Most people I know stick their heads in the sand after they have the computer and don't look at what's going on.

There have been 106 views of the article I put together on the Windows site. And 1754 views of DonT's article that got me corresponding and trying to troubleshoot. Not many if you think about how universal W10 is but that's just the people who are trying to do something about it.

I happened to look at Reliability Monitor and sure enough I am having these errors. No way will I do any of the recommended fixes as this is clearly a Microsoft issue. I never had this problem in the past.

bru said:

No way will I do any of the recommended fixes as this is clearly a Microsoft issue.

There are no recommended fixes - not sure what you're referring to. My article is a compilation of solutions that are claimed to have worked with the conclusion that the only positive way of removing the error is to use the MCT.

I hope you have a lot of patience for a Microsoft solution to appear - they haven't yet acknowledged that it's their problem or that there's anything wrong.

daknut said:

There are no recommended fixes - not sure what you're referring to. My article is a compilation of solutions that are claimed to have worked with the conclusion that the only positive way of removing the error is to use the MCT.

I hope you have a lot of patience for a Microsoft solution to appear - they haven't yet acknowledged that it's their problem or that there's anything wrong.

"fixes" doesn't equal "solutions"? I know neither are ever guaranteed but it seems as if you did supply a potential "fix" or "solution".

And I'm sure there will be disagreement but MS typically never acknowledges anything, they just (hopefully) issue a "fix" in an update down the road. Or not.

bru said:

"fixes" doesn't equal "solutions"? I know neither are ever guaranteed but it seems as if you did supply a potential "fix" or "solution".

I said that there were no *recommended* solutions. I only listed what people had found to work, what I did and how that worked out and concluded by saying that I had to use the MCT. I didn't recommend any method to 'fix' or 'solve' the problem.

Not sure why you are so argumentative. By your own words:
"I have put together a digest of all the possible solutions and actions in a new thread on the Microsoft Forum located at:"

I see "solutions" in your comment. I used fixes, semantics it seems. I wasn't saying what you suggested wasn't working, etc. just that since I know this is a Microsoft issue rather than specific to me I wasn't going to try any of the "solutions".

bru said:

Not sure why you are so argumentative.

I have no problem with you waiting for a Microsoft solution (but the solution to the scannow/Windows Defender issue in the latest Cumulative update didn't fix it on my computer, or another I ran it on - I do not anticipate a full fix of the Host problem without issue). But I applaud your confidence and patience.

But I did not recommend any course of action. This I must make clear - I will not be held liable for 'recommending' any course of action. I am not telling anyone what they should do but collating the solutions that have been claimed, detailing what I did and how I finally solved the problem.

I do not think that the MCT fix, solution or whatever it should be called is the right way to go but if a person wants to be sure of one action that will resolve the mess then that is the best, least time-consuming way. Yet, even using it is thwart with danger as I pointed out.

Finally, I wish you all the best. I hope the solution via Microsoft is quick - as neither you nor I (not anyone in the world, it would appear at this point) actually knows the root problem of the errors that are being recorded.

I am very concerned that any different, future problem that may occur could impound upon the Host error, multiply the malfunction and we end up in a much more impossible place that our computers will find themselves if we don't take what restorative actions that we can now.