Host Process For Windows Taskhostw.exe Stopped Working: Event ID 1000

Anonymous

I noticed upon checking my Event Log Applications and my Reliability Monitor I have been getting this critical error about every 2 to 3 days now on my HP Omen i7 -16 GB Mem - Nvidia GEForce GTX 1070 on Win10 Home 64 bit and this did not start happening until I updated to v1903 on May 30^th^ . My build is 18362.239. Could someone please advise me as how to resolve this or MS deploy a fix for this. It appears I am not the only one getting these. I have reported this through the Feedback Hub. I have run all three DISMs, SFC, Malwarebytes, Norton and I turned on Windows Defender long enough for a quick scan and no problems seen. It appears this is a scheduled task that keeps failing instead of running to completion.

Log Name: Application

Source: Application Error

Date: 6/18/2019 3:04:17 PM

Event ID: 1000

Task Category: (100)

Level: Error

Keywords: Classic

User: N/A

Computer: DESKTOP-JE8LEU6

Description:

Faulting application name: taskhostw.exe, version: 10.0.18362.1, time stamp: 0xe9bfb510

Faulting module name: unbcl.dll, version: 10.0.18362.1, time stamp: 0xe593abbb

Exception code: 0xc0000005

Fault offset: 0x0000000000047b22

Faulting process id: 0x2ea4

Faulting application start time: 0x01d525fefbf28b71

Faulting application path: C:\WINDOWS\system32\taskhostw.exe

Faulting module path: C:\WINDOWS\system32\oobe\unbcl.dll

Report Id: e2410c03-f6bf-462a-8545-72d8480a85b4

Faulting package full name:

Faulting package-relative application ID:

Event Xml:

<Channel>Application</Channel>

<Computer>DESKTOP-JE8LEU6</Computer>

</System>

<Data>taskhostw.exe</Data>

<Data>unbcl.dll</Data>

<Data>01d525fefbf28b71</Data>

<Data>C:\WINDOWS\system32\taskhostw.exe</Data>

<Data>C:\WINDOWS\system32\oobe\unbcl.dll</Data>

<Data>

</Data>

<Data>

</Data>

</EventData>

</Event>

This below is from Notepad about this error

Version=1

EventType=APPCRASH

EventTime=132053582578193450

ReportType=2

Consent=1

UploadTime=132053582584574055

ReportStatus=268435456

ReportIdentifier=00f879cd-2e56-43f0-a4c8-3daabf334e23

IntegratorReportIdentifier=e2410c03-f6bf-462a-8545-72d8480a85b4

Wow64Host=34404

NsAppName=taskhostw.exe

OriginalFilename=taskhostw.exe

AppSessionGuid=00002ea4-0000-0023-718b-f2fbfe25d501

TargetAppId=W:0000f519feec486de87ed73cb92d3cac802400000000!000030a630dd89b9565e4261891cf5b27244f1353bdd!taskhostw.exe

TargetAppVer=2094//04//09:12:37:36!207e3!taskhostw.exe

BootId=4294967295

ServiceSplit=1778118961

TargetAsId=4327

IsFatal=1

EtwNonCollectReason=4

Response.BucketId=bc35effd0d0ebd0863848b41635acba6

Response.BucketTable=4

Response.LegacyBucketId=1406402096602467238

Response.type=4

Sig[0].Name=Application Name

Sig[0].Value=taskhostw.exe

Sig[1].Name=Application Version

Sig[1].Value=10.0.18362.1

Sig[2].Name=Application Timestamp

Sig[2].Value=e9bfb510

Sig[3].Name=Fault Module Name

Sig[3].Value=unbcl.dll

Sig[4].Name=Fault Module Version

Sig[4].Value=10.0.18362.1

Sig[5].Name=Fault Module Timestamp

Sig[5].Value=e593abbb

Sig[6].Name=Exception Code

Sig[6].Value=c0000005

Sig[7].Name=Exception Offset

Sig[7].Value=0000000000047b22

DynamicSig[1].Name=OS Version

DynamicSig[1].Value=10.0.18362.2.0.0.768.101

DynamicSig[2].Name=Locale ID

DynamicSig[2].Value=1033

DynamicSig[22].Name=Additional Information 1

DynamicSig[22].Value=8f64

DynamicSig[23].Name=Additional Information 2

DynamicSig[23].Value=8f64a98f51ee7a1658f393b52b9cfd78

DynamicSig[24].Name=Additional Information 3

DynamicSig[24].Value=638a

DynamicSig[25].Name=Additional Information 4

DynamicSig[25].Value=638a1d22f84447604d2e55bcb40f315c

UI[2]=C:\WINDOWS\system32\taskhostw.exe

UI[5]=Check online for a solution (recommended)

UI[6]=Check for a solution later (recommended)

UI[7]=Close

UI[8]=Host Process for Windows Tasks stopped working and was closed

UI[9]=A problem caused the application to stop working correctly. Windows will notify you if a solution is available.

UI[10]=&Close

LoadedModule[0]=C:\WINDOWS\system32\taskhostw.exe

LoadedModule[1]=C:\WINDOWS\SYSTEM32\ntdll.dll

LoadedModule[2]=C:\WINDOWS\System32\KERNEL32.DLL

LoadedModule[3]=C:\WINDOWS\System32\KERNELBASE.dll

LoadedModule[4]=C:\WINDOWS\System32\msvcrt.dll

LoadedModule[5]=C:\WINDOWS\System32\RPCRT4.dll

LoadedModule[6]=C:\WINDOWS\System32\combase.dll

LoadedModule[7]=C:\WINDOWS\System32\ucrtbase.dll

LoadedModule[8]=C:\WINDOWS\System32\bcryptPrimitives.dll

LoadedModule[9]=C:\WINDOWS\System32\OLEAUT32.dll

LoadedModule[10]=C:\WINDOWS\System32\msvcp_win.dll

LoadedModule[11]=C:\WINDOWS\System32\imm32.dll

LoadedModule[12]=C:\WINDOWS\System32\USER32.dll

LoadedModule[13]=C:\WINDOWS\System32\win32u.dll

LoadedModule[14]=C:\WINDOWS\System32\GDI32.dll

LoadedModule[15]=C:\WINDOWS\System32\gdi32full.dll

LoadedModule[16]=C:\WINDOWS\System32\kernel.appcore.dll

LoadedModule[17]=C:\WINDOWS\System32\sechost.dll

LoadedModule[18]=C:\WINDOWS\System32\clbcatq.dll

LoadedModule[19]=C:\WINDOWS\system32\DeviceDirectoryClient.dll

LoadedModule[20]=C:\WINDOWS\System32\UMPDC.dll

LoadedModule[21]=C:\WINDOWS\System32\shcore.dll

LoadedModule[22]=C:\WINDOWS\System32\powrprof.dll

LoadedModule[23]=C:\WINDOWS\system32\MdmCommon.DLL

LoadedModule[24]=C:\WINDOWS\System32\cryptsp.dll

LoadedModule[25]=C:\WINDOWS\System32\CRYPT32.dll

LoadedModule[26]=C:\WINDOWS\System32\MSASN1.dll

LoadedModule[27]=C:\WINDOWS\system32\PROPSYS.dll

LoadedModule[28]=C:\WINDOWS\system32\netutils.dll

LoadedModule[29]=C:\WINDOWS\system32\samcli.dll

LoadedModule[30]=C:\WINDOWS\system32\WINHTTP.dll

LoadedModule[31]=C:\WINDOWS\SYSTEM32\rmclient.dll

LoadedModule[32]=C:\WINDOWS\SYSTEM32\policymanager.dll

LoadedModule[33]=C:\WINDOWS\System32\advapi32.dll

LoadedModule[34]=C:\WINDOWS\system32\msvcp110_win.dll

LoadedModule[35]=C:\Windows\System32\Windows.Web.dll

LoadedModule[36]=C:\Windows\System32\iertutil.dll

LoadedModule[37]=C:\WINDOWS\System32\IDStore.dll

LoadedModule[38]=C:\WINDOWS\System32\bcrypt.dll

LoadedModule[39]=C:\WINDOWS\System32\SAMLIB.dll

LoadedModule[40]=C:\WINDOWS\System32\wlidprov.dll

LoadedModule[41]=C:\Windows\System32\LocationFrameworkInternalPS.dll

LoadedModule[42]=C:\Windows\System32\LocationFrameworkPS.dll

LoadedModule[43]=C:\Windows\System32\wuapi.dll

LoadedModule[44]=C:\Windows\System32\wups.dll

LoadedModule[45]=C:\WINDOWS\system32\oobe\SetupCleanupTask.dll

LoadedModule[46]=C:\WINDOWS\System32\WINTRUST.dll

LoadedModule[47]=C:\WINDOWS\SYSTEM32\WDSCORE.dll

LoadedModule[48]=C:\WINDOWS\SYSTEM32\VERSION.dll

LoadedModule[49]=C:\WINDOWS\system32\oobe\unbcl.dll

LoadedModule[50]=C:\WINDOWS\System32\OLE32.dll

LoadedModule[51]=C:\WINDOWS\SYSTEM32\WTSAPI32.dll

LoadedModule[52]=C:\Windows\System32\UpdatePolicy.dll

LoadedModule[53]=C:\WINDOWS\System32\profapi.dll

LoadedModule[54]=C:\Windows\System32\Cabinet.dll

LoadedModule[55]=C:\Windows\System32\usoapi.dll

LoadedModule[56]=C:\WINDOWS\system32\wbem\wbemprox.dll

LoadedModule[57]=C:\WINDOWS\System32\WS2_32.dll

LoadedModule[58]=C:\WINDOWS\SYSTEM32\wbemcomn.dll

LoadedModule[59]=C:\WINDOWS\system32\wbem\wbemsvc.dll

LoadedModule[60]=C:\WINDOWS\system32\wbem\fastprox.dll

LoadedModule[61]=C:\WINDOWS\SYSTEM32\amsi.dll

LoadedModule[62]=C:\WINDOWS\SYSTEM32\USERENV.dll

LoadedModule[63]=C:\Windows\System32\FlightSettings.dll

LoadedModule[64]=C:\WINDOWS\System32\cfgmgr32.dll

LoadedModule[65]=C:\Windows\System32\bcd.dll

LoadedModule[66]=C:\Windows\System32\wosc.dll

LoadedModule[67]=C:\Windows\System32\Windows.Networking.Connectivity.dll

LoadedModule[68]=C:\WINDOWS\System32\npmproxy.dll

LoadedModule[69]=C:\Windows\System32\WinTypes.dll

LoadedModule[70]=C:\Windows\System32\IPHLPAPI.DLL

LoadedModule[71]=C:\WINDOWS\System32\NSI.dll

LoadedModule[72]=C:\Windows\System32\dusmapi.dll

LoadedModule[73]=C:\WINDOWS\System32\windows.storage.dll

LoadedModule[74]=C:\WINDOWS\System32\shlwapi.dll

LoadedModule[75]=C:\WINDOWS\system32\configmanager2.dll

LoadedModule[76]=C:\WINDOWS\system32\DMCmnUtils.dll

LoadedModule[77]=C:\WINDOWS\system32\dmiso8601utils.dll

LoadedModule[78]=C:\WINDOWS\system32\DMOleAutUtils.dll

LoadedModule[79]=C:\WINDOWS\system32\enterpriseresourcemanager.dll

LoadedModule[80]=C:\WINDOWS\system32\dmEnrollEngine.DLL

LoadedModule[81]=C:\WINDOWS\system32\XmlLite.dll

LoadedModule[82]=C:\WINDOWS\system32\DEVOBJ.dll

LoadedModule[83]=C:\Windows\System32\Windows.Devices.Sensors.dll

LoadedModule[84]=C:\Windows\System32\BiWinrt.dll

LoadedModule[85]=C:\Windows\System32\Windows.Graphics.dll

LoadedModule[86]=C:\Windows\System32\Windows.Devices.Enumeration.dll

LoadedModule[87]=C:\WINDOWS\System32\StructuredQuery.dll

LoadedModule[88]=C:\WINDOWS\System32\MSWB7.dll

LoadedModule[89]=C:\Windows\System32\DevDispItemProvider.dll

LoadedModule[90]=C:\Windows\System32\DDORes.dll

LoadedModule[91]=C:\Windows\System32\DefaultDeviceManager.dll

LoadedModule[92]=C:\WINDOWS\SYSTEM32\dxcore.dll

LoadedModule[93]=C:\WINDOWS\System32\imagehlp.dll

LoadedModule[94]=C:\WINDOWS\system32\rsaenh.dll

LoadedModule[95]=C:\WINDOWS\system32\CRYPTBASE.dll

LoadedModule[96]=C:\WINDOWS\System32\Shell32.dll

LoadedModule[97]=C:\WINDOWS\system32\DdcComImplementationsDesktop.dll

LoadedModule[98]=C:\Windows\System32\taskschd.dll

LoadedModule[99]=C:\Windows\System32\SspiCli.dll

LoadedModule[100]=C:\WINDOWS\system32\dbghelp.dll

LoadedModule[101]=C:\WINDOWS\system32\dbgcore.DLL

State[0].Key=Transport.DoneStage1

State[0].Value=1

OsInfo[0].Key=vermaj

OsInfo[0].Value=10

OsInfo[1].Key=vermin

OsInfo[1].Value=0

OsInfo[2].Key=verbld

OsInfo[2].Value=18362

OsInfo[3].Key=ubr

OsInfo[3].Value=175

OsInfo[4].Key=versp

OsInfo[4].Value=0

OsInfo[5].Key=arch

OsInfo[5].Value=9

OsInfo[6].Key=lcid

OsInfo[6].Value=1033

OsInfo[7].Key=geoid

OsInfo[7].Value=244

OsInfo[8].Key=sku

OsInfo[8].Value=101

OsInfo[9].Key=domain

OsInfo[9].Value=0

OsInfo[10].Key=prodsuite

OsInfo[10].Value=768

OsInfo[11].Key=ntprodtype

OsInfo[11].Value=1

OsInfo[12].Key=platid

OsInfo[12].Value=10

OsInfo[13].Key=sr

OsInfo[13].Value=0

OsInfo[14].Key=tmsi

OsInfo[14].Value=27077

OsInfo[15].Key=osinsty

OsInfo[15].Value=1

OsInfo[16].Key=iever

OsInfo[16].Value=11.175.18362.0-11.0.130

OsInfo[17].Key=portos

OsInfo[17].Value=0

OsInfo[18].Key=ram

OsInfo[18].Value=16319

OsInfo[19].Key=svolsz

OsInfo[19].Value=919

OsInfo[20].Key=wimbt

OsInfo[20].Value=0

OsInfo[21].Key=blddt

OsInfo[21].Value=190318

OsInfo[22].Key=bldtm

OsInfo[22].Value=1202

OsInfo[23].Key=bldbrch

OsInfo[23].Value=19h1_release

OsInfo[24].Key=bldchk

OsInfo[24].Value=0

OsInfo[25].Key=wpvermaj

OsInfo[25].Value=0

OsInfo[26].Key=wpvermin

OsInfo[26].Value=0

OsInfo[27].Key=wpbuildmaj

OsInfo[27].Value=0

OsInfo[28].Key=wpbuildmin

OsInfo[28].Value=0

OsInfo[29].Key=osver

OsInfo[29].Value=10.0.18362.175.amd64fre.19h1_release.190318-1202

OsInfo[30].Key=buildflightid

OsInfo[30].Value=2ABBFE8A-57A7-4ECE-870E-2008A39B7D9D.1

OsInfo[31].Key=edition

OsInfo[31].Value=Core

OsInfo[32].Key=ring

OsInfo[32].Value=Retail

OsInfo[33].Key=expid

OsInfo[33].Value=RS:362F

OsInfo[34].Key=containerid

OsInfo[35].Key=containertype

OsInfo[36].Key=edu

OsInfo[36].Value=0

FriendlyEventName=Stopped working

ConsentKey=APPCRASH

AppName=Host Process for Windows Tasks

AppPath=C:\WINDOWS\system32\taskhostw.exe

NsPartner=windows

NsGroup=windows8

ApplicationIdentity=BD8F58D832D9F05162A8A1E18B36CC06

MetadataHash=-1351433430

Below are links to my reports in the Feedback Hub concerning this problem. Plese go and upvote this problem so the MS engineers can see this and take action.

https://aka.ms/AA5iyv5

https://aka.ms/AA5i6y8

https://aka.ms/AA5iev4

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.

0 comments

167 answers

Anonymous

2019-07-17T19:53:13+00:00

Sorry to put a damper on your diligence in trying to analyze this problem.

I corrected my ESENT errors by creating the missing Tiledatalayer folders on June 30th.

My last Taskhost error was on July 15th. As always for me the Taskhost error occurs when and only when Setupcleanuptask runs. Does anybody else see a similar correlation? Does Setupcleanuptask running cause the error or some other task. I don't know how to analyze TASKSCHD.MSC to find a failure date/time. Windows\logs might contain something.
Was this answer helpful?

0 comments No comments
Anonymous

2019-07-17T19:23:49+00:00

Camilla,

I have something else to try. You've not PMed me so I'm going to post this for you in case you're in a different time zone to me (although I did PM someone I thought might be you on FB but haven't had a reply).

Go to Event Viewer 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 hours prior to that time and date. There should be no Host errors prior to the first ESENT error.

I corrected this 'unrelated' error after my last Host error - but I didn't correct it on my wife's (and she got another Host error this evening). I've rooted around a bit and both hers and mine fault with ESENT a few hours before the very first Host 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 me at first.

So, the solution to rectify the ESENT errors (and, hopefully, the Host errors) - this from another site so it's not my text:

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

The ESENT errors should stop immediately. Mine did. Now I have to wait to see what happens...

Let me know if the errors are as above. Again, this may not be a solution but it will rectify the error in Event Viewer. It does seem a bit of a coincidence about the time, though.
Was this answer helpful?

0 comments No comments
Anonymous

2019-07-17T17:55:41+00:00

Camilla,

I've been trying to work out how to PM you using this forum but I can't work it out. If you know of a way, would you PM me? I don't want to clutter up this thread with some ideas and information that other readers may think are solutions but which aren't. Thanks.
Was this answer helpful?

0 comments No comments
Anonymous

2019-07-17T17:37:26+00:00

Don, Camilla,

The Definition Update is just a list of current viruses that is installed in the Defender Program (it's like the old 'Virus Tables' of Third Party software from yesteryear). They are released more than once a day so, if the last time you turned the computer on was, say, 9pm (that is, you shut it down at this time), the Definition you would have would be the latest release prior to that time (if your computer had updated itself).

If you then boot up at, say, 7am the next morning, you don't download any of the Definition Updates that have been released between 9pm and the one prior to 7am (which is the current one).

You don't need all the ones in between because the latest one is current and replaces all those that have gone before.

If my wife's computer has had the problem resolved then, as remedial action was the same on both laptops, it can't be a common cause that's brought it about.

Camilla talked about an old 'program' and it could be an App that hasn't updated yet (but my wife and I have similar, if not the same, Apps). And the set up of the new computer today had no 'Host' errors but it did have the Defender errors.
Was this answer helpful?

0 comments No comments
Anonymous

2019-07-17T17:07:56+00:00

Hi Don, I don't have that specific definition, but I check for updates manually on a daily basis. The latest definition I have is KB2268602 definition 1.297.1248 from 18.45 today. And I'm still getting that annoying error. If Defender is the issue then it is not because it isn't up to date.
Was this answer helpful?

0 comments No comments