Handbrake fails to run after windows update

HandBrake for Windows support
Forum rules
An Activity Log is required for support requests. Please read How-to get an activity log? for details on how and why this should be provided.
Post Reply
sublime77
Posts: 9
Joined: Sat Aug 06, 2011 2:07 pm

Handbrake fails to run after windows update

Post by sublime77 » Thu Feb 07, 2019 11:48 am

After windows update ran last night handbrake will no longer start. New windows 10 build number is 17763.292.

I click on the handbrake icon (installed version 1.2.0) and the only observable thing that happens is the number of background processes jump from 66 to 68, back to 66. I downloaded 1.2.0 portable and had the same result.

HandBrake version 1.20

windows 10 build number is 17763.292

There is no activity log post windows update.

Any help or suggestions of how to gather additional info would be appreciated.

Woodstock
Veteran User
Posts: 2925
Joined: Tue Aug 27, 2013 6:39 am

Re: Handbrake fails to run after windows update

Post by Woodstock » Thu Feb 07, 2019 1:44 pm

Windows update changed permissions on you. Pretty much any program that writes to your user home area that isn't on a Microsoft white list MAY stop working after recent updates, because the default is to block such access, to protect you against ransomware.

Guess where handbrake stores your configuration data and logs?

Google "windows update ransomware protection exception" for how to add an exception for handbrake, and any other programs that get broken by this. There are a number of Microsoft programs also being blocked, until Microsoft gets around to adding them to their own white list...

sublime77
Posts: 9
Joined: Sat Aug 06, 2011 2:07 pm

Re: Handbrake fails to run after windows update

Post by sublime77 » Thu Feb 07, 2019 2:21 pm

Ransomware protection was off. I turned it on and added an exception, same result...

sublime77
Posts: 9
Joined: Sat Aug 06, 2011 2:07 pm

Re: Handbrake fails to run after windows update

Post by sublime77 » Thu Feb 07, 2019 2:21 pm

I also tried running as admin.

sublime77
Posts: 9
Joined: Sat Aug 06, 2011 2:07 pm

Re: Handbrake fails to run after windows update

Post by sublime77 » Thu Feb 07, 2019 2:26 pm

From the app log

Fault bucket 2138119403448135300, type 5
Event Name: BEX64
Response: Not available
Cab Id: 0

Problem signature:
P1: HandBrake.exe
P2: 1.2.0.0
P3: 5c17b8f5
P4: StackHash_76a1
P5: 0.0.0.0
P6: 00000000
P7: PCH_26
P8: c0000005
P9: 0000000000000008
P10:

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5052.tmp.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER518B.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER519C.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER51AD.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER51BE.tmp.txt
\\?\C:\Users\XXXXX\AppData\Local\Temp\WERA442.tmp.appcompat.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_HandBrake.exe_21f14b9a6ff3df2972fdb42ca8c1b3135bdf5d5_ffd5d7ad_cab_18e7a44e\memory.hdmp

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_HandBrake.exe_21f14b9a6ff3df2972fdb42ca8c1b3135bdf5d5_ffd5d7ad_2073b9ca

Analysis symbol:
Rechecking for solution: 0
Report Id: 93ac9fbd-6e6d-45de-9681-0485f88fb1cb
Report Status: 268435552
Hashed bucket: 547cd5f0dd0caad21dac2044e9e56e84
Cab Guid: 0

sublime77
Posts: 9
Joined: Sat Aug 06, 2011 2:07 pm

Re: Handbrake fails to run after windows update

Post by sublime77 » Thu Feb 07, 2019 2:31 pm

I also tried renaming the handbrake folders location here.
C:\Users\XXX\AppData\Roaming

The folder was recreated when app launch, but generated same error as above.

sublime77
Posts: 9
Joined: Sat Aug 06, 2011 2:07 pm

Re: Handbrake fails to run after windows update

Post by sublime77 » Thu Feb 07, 2019 2:32 pm

Version=1
EventType=BEX64
EventTime=131940233631909714
ReportType=2
Consent=1
UploadTime=131940233635659968
ReportStatus=268435456
ReportIdentifier=a51911cf-7cc6-4c1b-9414-bc1921a503d0
IntegratorReportIdentifier=fea300e0-df4f-4589-8ec5-0a5f469a0410
Wow64Host=34404
NsAppName=HandBrake.exe
OriginalFilename=HandBrake.exe
AppSessionGuid=00000f70-0001-0004-cfff-3284f1bed401
TargetAppId=W:0006841da1cb9193a655f26fe984fe3e766900000000!00003cd8feca14f696cf08ef2f8a80c3d95bc9639666!HandBrake.exe
TargetAppVer=2018//12//17:14:55:49!0!HandBrake.exe
BootId=4294967295
TargetAsId=1636
IsFatal=1
EtwNonCollectReason=4
Response.BucketId=656bd726ef4210cf12348721de8e331f
Response.BucketTable=5
Response.LegacyBucketId=1311821971009188639
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=HandBrake.exe
Sig[1].Name=Application Version
Sig[1].Value=1.2.0.0
Sig[2].Name=Application Timestamp
Sig[2].Value=5c17b8f5
Sig[3].Name=Fault Module Name
Sig[3].Value=StackHash_76a1
Sig[4].Name=Fault Module Version
Sig[4].Value=0.0.0.0
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=00000000
Sig[6].Name=Exception Offset
Sig[6].Value=PCH_F2
Sig[7].Name=Exception Code
Sig[7].Value=c0000005
Sig[8].Name=Exception Data
Sig[8].Value=0000000000000008
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=10.0.17763.2.0.0.256.48
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=76a1
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=76a173c26a6dc2e3cd83ac8fd9f8bdb9
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=7b3f
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=7b3f634c955ac91fe3f1e745337a968a
UI[2]=C:\Program Files\HandBrake\HandBrake.exe
LoadedModule[0]=C:\Program Files\HandBrake\HandBrake.exe
LoadedModule[1]=C:\WINDOWS\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\WINDOWS\SYSTEM32\MSCOREE.DLL
LoadedModule[3]=C:\WINDOWS\System32\KERNEL32.dll
LoadedModule[4]=C:\WINDOWS\System32\KERNELBASE.dll
LoadedModule[5]=C:\WINDOWS\SYSTEM32\apphelp.dll
LoadedModule[6]=C:\WINDOWS\SYSTEM32\AcLayers.DLL
LoadedModule[7]=C:\WINDOWS\System32\msvcrt.dll
LoadedModule[8]=C:\WINDOWS\System32\USER32.dll
LoadedModule[9]=C:\WINDOWS\System32\win32u.dll
LoadedModule[10]=C:\WINDOWS\System32\GDI32.dll
LoadedModule[11]=C:\WINDOWS\System32\gdi32full.dll
LoadedModule[12]=C:\WINDOWS\System32\msvcp_win.dll
LoadedModule[13]=C:\WINDOWS\System32\ucrtbase.dll
LoadedModule[14]=C:\WINDOWS\System32\SHLWAPI.dll
LoadedModule[15]=C:\WINDOWS\System32\combase.dll
LoadedModule[16]=C:\WINDOWS\System32\RPCRT4.dll
LoadedModule[17]=C:\WINDOWS\System32\bcryptPrimitives.dll
LoadedModule[18]=C:\WINDOWS\System32\ADVAPI32.dll
LoadedModule[19]=C:\WINDOWS\System32\sechost.dll
LoadedModule[20]=C:\WINDOWS\SYSTEM32\sfc.dll
LoadedModule[21]=C:\WINDOWS\SYSTEM32\WINSPOOL.DRV
LoadedModule[22]=C:\WINDOWS\System32\kernel.appcore.dll
LoadedModule[23]=C:\WINDOWS\System32\bcrypt.dll
LoadedModule[24]=C:\WINDOWS\SYSTEM32\PROPSYS.dll
LoadedModule[25]=C:\WINDOWS\System32\OLEAUT32.dll
LoadedModule[26]=C:\WINDOWS\System32\shcore.dll
LoadedModule[27]=C:\WINDOWS\SYSTEM32\IPHLPAPI.DLL
LoadedModule[28]=C:\WINDOWS\SYSTEM32\sfc_os.DLL
LoadedModule[29]=C:\WINDOWS\SYSTEM32\SortWindows61.dll
LoadedModule[30]=C:\WINDOWS\System32\IMM32.DLL
LoadedModule[31]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\mscoreei.dll
LoadedModule[32]=C:\WINDOWS\SYSTEM32\VERSION.dll
LoadedModule[33]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
LoadedModule[34]=C:\WINDOWS\SYSTEM32\MSVCR120_CLR0400.dll
LoadedModule[35]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\mscorlib\d6009efb32eeecfdd2f5855cd2d60c54\mscorlib.ni.dll
LoadedModule[36]=C:\WINDOWS\System32\ole32.dll
LoadedModule[37]=C:\WINDOWS\system32\uxtheme.dll
LoadedModule[38]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\System\cbb21a87000695bce2ac8439aedf2eee\System.ni.dll
LoadedModule[39]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\System.Core\1570ad2bd224c8a7b55348cf062c2895\System.Core.ni.dll
LoadedModule[40]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\WindowsBase\3d9331e60ab4389dd3f6061161d4b305\WindowsBase.ni.dll
LoadedModule[41]=C:\WINDOWS\System32\CRYPTSP.dll
LoadedModule[42]=C:\WINDOWS\system32\rsaenh.dll
LoadedModule[43]=C:\WINDOWS\SYSTEM32\CRYPTBASE.dll
LoadedModule[44]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\PresentationCore\91d213454f5c586bfc95f2214f260f59\PresentationCore.ni.dll
LoadedModule[45]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\Presentatio5ae0f00f#\6eee174c6a192bc015ef60c0d006bcae\PresentationFramework.ni.dll
LoadedModule[46]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\System.Xaml\6176782d79b1f2f384ca308ff2af9966\System.Xaml.ni.dll
LoadedModule[47]=C:\WINDOWS\SYSTEM32\dwrite.dll
LoadedModule[48]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\WPF\wpfgfx_v0400.dll
LoadedModule[49]=C:\WINDOWS\SYSTEM32\MSVCP120_CLR0400.dll
LoadedModule[50]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\WPF\PresentationNative_v0400.dll
LoadedModule[51]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clrjit.dll
LoadedModule[52]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\System.Configuration\f5e6a3cff7182ddde3a4b0ae7960a785\System.Configuration.ni.dll
LoadedModule[53]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\System.Xml\1a9c2b64bf4a7a6bc764deaff97c589a\System.Xml.ni.dll
LoadedModule[54]=C:\WINDOWS\System32\shell32.dll
LoadedModule[55]=C:\WINDOWS\System32\cfgmgr32.dll
LoadedModule[56]=C:\WINDOWS\System32\windows.storage.dll
LoadedModule[57]=C:\WINDOWS\System32\profapi.dll
LoadedModule[58]=C:\WINDOWS\System32\powrprof.dll
LoadedModule[59]=C:\WINDOWS\system32\dwmapi.dll
LoadedModule[60]=C:\WINDOWS\System32\CRYPT32.dll
LoadedModule[61]=C:\WINDOWS\System32\MSASN1.dll
LoadedModule[62]=C:\WINDOWS\System32\MSCTF.dll
LoadedModule[63]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\Presentatioaec034ca#\cb712ce6b3d5db0df321ce72d8116726\PresentationFramework.Aero2.ni.dll
LoadedModule[64]=C:\Program Files\HandBrake\hb.DLL
LoadedModule[65]=C:\WINDOWS\System32\WS2_32.dll
LoadedModule[66]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\System.Runteb92aa12#\c53148c3d44c158ad8b9c9bfb7270b94\System.Runtime.Serialization.ni.dll
LoadedModule[67]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\System.Data\42e9a6b9720338a6c8800877ee53cc5c\System.Data.ni.dll
LoadedModule[68]=C:\WINDOWS\Microsoft.Net\assembly\GAC_64\System.Data\v4.0_4.0.0.0__b77a5c561934e089\System.Data.dll
LoadedModule[69]=C:\Program Files\Intel\Media SDK\libmfxhw64.dll
LoadedModule[70]=C:\WINDOWS\SYSTEM32\dxgi.dll
LoadedModule[71]=C:\WINDOWS\SYSTEM32\dxva2.dll
LoadedModule[72]=C:\WINDOWS\SYSTEM32\d3d11.dll
LoadedModule[73]=C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_24de78387e6208e4\igd10iumd64.dll
LoadedModule[74]=C:\WINDOWS\SYSTEM32\ncrypt.dll
LoadedModule[75]=C:\WINDOWS\SYSTEM32\NTASN1.dll
LoadedModule[76]=C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_24de78387e6208e4\igc64.dll
LoadedModule[77]=C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_24de78387e6208e4\igd11dxva64.dll
LoadedModule[78]=C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_24de78387e6208e4\igdinfo64.dll
LoadedModule[79]=C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e5307a15339dbced\igfx11cmrt64.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=17763
OsInfo[3].Key=ubr
OsInfo[3].Value=292
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=48
OsInfo[9].Key=domain
OsInfo[9].Value=0
OsInfo[10].Key=prodsuite
OsInfo[10].Value=256
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=817
OsInfo[15].Key=osinsty
OsInfo[15].Value=3
OsInfo[16].Key=iever
OsInfo[16].Value=11.253.17763.0-11.0.105
OsInfo[17].Key=portos
OsInfo[17].Value=0
OsInfo[18].Key=ram
OsInfo[18].Value=7862
OsInfo[19].Key=svolsz
OsInfo[19].Value=464
OsInfo[20].Key=wimbt
OsInfo[20].Value=0
OsInfo[21].Key=blddt
OsInfo[21].Value=180914
OsInfo[22].Key=bldtm
OsInfo[22].Value=1434
OsInfo[23].Key=bldbrch
OsInfo[23].Value=rs5_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.17763.292.amd64fre.rs5_release.180914-1434
OsInfo[30].Key=buildflightid
OsInfo[30].Value=14ACDB6A-7AB0-46BF-BE52-3F9CB1B82BE1.1
OsInfo[31].Key=edition
OsInfo[31].Value=Professional
OsInfo[32].Key=ring
OsInfo[32].Value=Retail
OsInfo[33].Key=expid
OsInfo[33].Value=RS:28A8
OsInfo[34].Key=containerid
OsInfo[35].Key=containertype
OsInfo[36].Key=edu
OsInfo[36].Value=0
FriendlyEventName=Stopped working
ConsentKey=BEX64
AppName=HandBrake
AppPath=C:\Program Files\HandBrake\HandBrake.exe
NsPartner=windows
NsGroup=windows8
ApplicationIdentity=5015E13A9E8DFDFD9587362CF6C8FF14
MetadataHash=1378097376

sublime77
Posts: 9
Joined: Sat Aug 06, 2011 2:07 pm

Re: Handbrake fails to run after windows update

Post by sublime77 » Thu Feb 07, 2019 10:44 pm

Handbrake works in safe mode. I tried killing all other processes that would die and weren't critical to OS operation and still nothing. Not sure where to go from here.

sublime77
Posts: 9
Joined: Sat Aug 06, 2011 2:07 pm

Re: Handbrake fails to run after windows update

Post by sublime77 » Fri Feb 08, 2019 12:11 pm

I have no idea what solved the issue. I did uninstall updates and reinstall them. Checked the drivers. This morning it works. Who knows.

Post Reply