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

Peer_Sam

Would you please check on the status of getting this error fixed as I and others still continue to get these every other day even after the July updates. There is no excuse for MS to let this keep  happening over and over. Would you please push  this problem higher so action can be taken. This is totally ridiculous since this has gone on for a month and a half. If they cannot fix it then they should make this informational and not critical or keep it from showing up on our Reliability History and dropping our graphs. I am afraid this is going to keep happening until this causes bigger problems with our computers.

Log Name:      Application

Source:        Application Error

Date:          7/11/2019 4:03:38 AM

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.207, time stamp: 0xe593abbb

Exception code: 0xc0000005

Fault offset: 0x0000000000047b22

Faulting process id: 0x21c0

Faulting application start time: 0x01d537bf25313204

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

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

Report Id: 301b69a2-e5ae-4dec-844e-bc9179d9fda2

Faulting package full name:

Faulting package-relative application ID:

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="Application Error" />

    <EventID Qualifiers="0">1000</EventID>

    <Level>2</Level>

    <Task>100</Task>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2019-07-11T08:03:38.540084600Z" />

    <EventRecordID>10096</EventRecordID>

    <Channel>Application</Channel>

    <Computer>DESKTOP-JE8LEU6</Computer>

    <Security />

  </System>

  <EventData>

    <Data>taskhostw.exe</Data>

    <Data>10.0.18362.1</Data>

    <Data>e9bfb510</Data>

    <Data>unbcl.dll</Data>

    <Data>10.0.18362.207</Data>

    <Data>e593abbb</Data>

    <Data>c0000005</Data>

    <Data>0000000000047b22</Data>

    <Data>21c0</Data>

    <Data>01d537bf25313204</Data>

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

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

    <Data>301b69a2-e5ae-4dec-844e-bc9179d9fda2</Data>

    <Data>

    </Data>

    <Data>

    </Data>

  </EventData>

</Event>

Version=1

EventType=APPCRASH

EventTime=132073058186408460

ReportType=2

Consent=1

UploadTime=132073058187733714

ReportStatus=268435456

ReportIdentifier=3655bf77-744d-45cc-a42d-667b160b3d7d

IntegratorReportIdentifier=301b69a2-e5ae-4dec-844e-bc9179d9fda2

Wow64Host=34404

NsAppName=taskhostw.exe

OriginalFilename=taskhostw.exe

AppSessionGuid=000021c0-0000-0046-0432-3125bf37d501

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

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

BootId=4294967295

ServiceSplit=2450780465

TargetAsId=720

IsFatal=1

EtwNonCollectReason=4

Response.BucketId=753942a8ab3e10ecd47dad4a96fb22f0

Response.BucketTable=4

Response.LegacyBucketId=1476526788719616752

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.207

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=5ed1

DynamicSig[25].Name=Additional Information 4

DynamicSig[25].Value=5ed1f45699375d642f570f3f3ed437be

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\oobe\SetupCleanupTask.dll

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

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

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

LoadedModule[23]=C:\WINDOWS\SYSTEM32\WINHTTP.dll

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

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

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

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

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

LoadedModule[29]=C:\WINDOWS\SYSTEM32\msvcp110_win.dll

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

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

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

LoadedModule[33]=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=239

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=59536

OsInfo[15].Key=osinsty

OsInfo[15].Value=1

OsInfo[16].Key=iever

OsInfo[16].Value=11.239.18362.0-11.0.135

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.239.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=-2122472125

update completed this morning at 5.04. Had TWO (2) "host process for windows tasks stopped working" at 5.19 and 5,54. What in gods name is going on at Microsoft?????????????

I just had another one this morning and I am so angry at the lack of  action and response on MS part to correct this error. I submitted a response above to Peer_Sam who is a MS Agent and Moderator about this. Please feel free to send him a reply as well and ask him what the hell is going on. This is something that the fix has to come from MS so beware of people telling you how to fix it as it may cause other problems. Wait for another Update or official word. I know it is aggravating. If they cannot fix this then they need to make this error Informational and not Critical.  Let's please keep in touch with each other Camilla. Have a great day.

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

Hi,

Thank you for writing to Microsoft Community forums.

I see that the faulting module is: C:\WINDOWS\system32\oobe\unbcl.dll. Unbcl.dll is an unmanaged base library. This issue could be caused due to errors in .Net Framework.

Though you have run the System file checker, we would like to know if any integrity violations were returned by SFC scan. Ideally, SFC scan should be able to fix this issue, but since taskhostw process is still throwing the error, I would suggest to try repairing the .Net Framework and let us know the results. Please follow the steps given below.

• Open the Run dialog box by pressing the Windows key and R together.
• Type APPWIZ.CPL and hit the Enter key to open the Programs and features window.
• Click on Turn Windows features on or off.
• Locate and uncheck the checkboxes for .Net framework 3.5 and .Net framework 4.8 Advanced Services.
• Reboot the computer, re-enable the .Net frameworks and let us know if it fixes the issue.

Awaiting your response.

Regards,

Peer Samie

Microsoft Community-Moderator

Dear Peer_Sam,

I have been monitoring this thread as I have exactly the same problem as experienced by DonT5 and others. My reliability index shows the error with taskhostw.exe which occurs every other day at around 6am (UK time). I have a Surface Book i7, with 16 GB Memory and run Win10 Pro 64bit 1903 with the latest build (including the recent updates to .NET). I appreciate that it doesn't appear to cause any performance problems, but the continuous depletion of the reliability index is annoying at best.

Hi,

Thank you for writing to Microsoft Community forums.

I see that the faulting module is: C:\WINDOWS\system32\oobe\unbcl.dll. Unbcl.dll is an unmanaged base library. This issue could be caused due to errors in .Net Framework.

Though you have run the System file checker, we would like to know if any integrity violations were returned by SFC scan. Ideally, SFC scan should be able to fix this issue, but since taskhostw process is still throwing the error, I would suggest to try repairing the .Net Framework and let us know the results. Please follow the steps given below.

• Open the Run dialog box by pressing the Windows key and R together.
• Type APPWIZ.CPL and hit the Enter key to open the Programs and features window.
• Click on Turn Windows features on or off.
• Locate and uncheck the checkboxes for .Net framework 3.5 and .Net framework 4.8 Advanced Services.
• Reboot the computer, re-enable the .Net frameworks and let us know if it fixes the issue.

Awaiting your response.

Regards,

Peer Samie

Microsoft Community-Moderator

Dear Peer_Sam,

I have been monitoring this thread as I have exactly the same problem as experienced by DonT5 and others. My reliability index shows the error with taskhostw.exe which occurs every other day at around 6am (UK time). I have a Surface Book i7, with 16 GB Memory and run Win10 Pro 64bit 1903 with the latest build (including the recent updates to .NET). I appreciate that it doesn't appear to cause any performance problems, but the continuous depletion of the reliability index is annoying at best.

Thank you for your comment to my thread as the more we get the fact out to MS that there are numerous members having this problem the sooner we will get a fix deployed. I totally agree with your statement concerning the annoyance of the continuous depletion of the reliability index. Please keep us all updated if you find a solution and vice versa.

Regards,

Don

Below are links to my bug reports in the Feedback Hub concerning this problem. Please 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

Just throwing my hat into the ring - I have been getting this error for a couple of weeks now. Very, very annoying. Sometime get three on the same day then nothing for a couple of days. Cummon Microsoft, give us a solution!