HandBrake 1.1.2 won't open in Win10

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
mjp81
Posts: 12
Joined: Sat Nov 03, 2018 8:25 pm

HandBrake 1.1.2 won't open in Win10

Post by mjp81 » Sat Nov 03, 2018 8:52 pm

Description of problem or question:
HandBrake won't open even after uninstalling, restarting, the reinstalling. Already have latest version of Microsoft .NET Framework installed.

Steps to reproduce the problem (If Applicable):
Trying to open it.

HandBrake version (e.g., 1.0.0):
HandBrake 1.1.2

Operating system and version (e.g., Ubuntu 16.04 LTS, macOS 10.13 High Sierra, Windows 10 Creators Update):
Microsoft Windows 10 Pro, Version 10.0.17134 Build 17134

HandBrake Activity Log ***required*** (see How-to get an activity log)
This is the last activity log used, back in January with an older version.

Code: Select all

HandBrake 1.0.7 (2017040900) - 64bit
OS: Microsoft Windows NT 10.0.16299.0 - 64bit
CPU: Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz
Ram: 7661 MB, 
GPU Information:
  Intel(R) HD Graphics 520 - 22.20.16.4815
Screen: 1366x768
Temp Dir: C:\Users\User\AppData\Local\Temp\
Install Dir: C:\Program Files\HandBrake
Data Dir: C:\Users\User\AppData\Roaming\HandBrake Team\HandBrake\1.0.7.0

User avatar
s55
HandBrake Team
Posts: 9218
Joined: Sun Dec 24, 2006 1:05 pm

Re: HandBrake 1.1.2 won't open in Win10

Post by s55 » Sat Nov 03, 2018 8:56 pm

When installing, becareful that you don't uninstall it after you've installed it.

The prompt on the installer to uninstall, sometimes hides behind the installer so it's easy to inadvertently run that after installing.

mjp81
Posts: 12
Joined: Sat Nov 03, 2018 8:25 pm

Re: HandBrake 1.1.2 won't open in Win10

Post by mjp81 » Sat Nov 03, 2018 8:58 pm

That's a little hard to follow, but I do know what you're talking about and already made sure to click the Uninstall window before installing the latest version. It still won't open. No error messages, no nothing.

mjp81
Posts: 12
Joined: Sat Nov 03, 2018 8:25 pm

Re: HandBrake 1.1.2 won't open in Win10

Post by mjp81 » Sat Nov 03, 2018 9:21 pm

I tried going into HandBrake exe Properties > Compatibility > Clicked Run as Administrator. At the very least, now I get the "Do you want to allow this app to make changes" message, which I click Yes for, but it still does not open.

User avatar
s55
HandBrake Team
Posts: 9218
Joined: Sun Dec 24, 2006 1:05 pm

Re: HandBrake 1.1.2 won't open in Win10

Post by s55 » Sat Nov 03, 2018 9:27 pm

Is there anything in the Windows Event Viewer under Windows Logs > Applications at the timecode you run this?

mjp81
Posts: 12
Joined: Sat Nov 03, 2018 8:25 pm

Re: HandBrake 1.1.2 won't open in Win10

Post by mjp81 » Sat Nov 03, 2018 9:31 pm

Yes, there are multiple Error level events, all relating to Handbrake. I'll post details:

Faulting application name: HandBrake.exe, version: 1.1.2.0, time stamp: 0x5b903422
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00007ff8fffffffe
Faulting process id: 0x3e0
Faulting application start time: 0x01d473bbcc5cafff
Faulting application path: C:\Program Files\HandBrake\HandBrake.exe
Faulting module path: unknown
Report Id: 4e8b44c6-5492-4686-b196-182b041e553b
Faulting package full name:

mjp81
Posts: 12
Joined: Sat Nov 03, 2018 8:25 pm

Re: HandBrake 1.1.2 won't open in Win10

Post by mjp81 » Sat Nov 03, 2018 9:32 pm

This is from the Error event "Details" tab in XML View:

- <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="2018-11-03T21:25:53.282381500Z" />
<EventRecordID>48834</EventRecordID>
<Channel>Application</Channel>
<Computer>Laptop-Win10-38</Computer>
<Security />
</System>
- <EventData>
<Data>HandBrake.exe</Data>
<Data>1.1.2.0</Data>
<Data>5b903422</Data>
<Data>unknown</Data>
<Data>0.0.0.0</Data>
<Data>00000000</Data>
<Data>c0000005</Data>
<Data>00007ff8fffffffe</Data>
<Data>3e0</Data>
<Data>01d473bbcc5cafff</Data>
<Data>C:\Program Files\HandBrake\HandBrake.exe</Data>
<Data>unknown</Data>
<Data>4e8b44c6-5492-4686-b196-182b041e553b</Data>
<Data />
<Data />
</EventData>
</Event>

mjp81
Posts: 12
Joined: Sat Nov 03, 2018 8:25 pm

Re: HandBrake 1.1.2 won't open in Win10

Post by mjp81 » Sat Nov 03, 2018 11:22 pm

Is there anything else I could do?

mjp81
Posts: 12
Joined: Sat Nov 03, 2018 8:25 pm

Re: HandBrake 1.1.2 won't open in Win10

Post by mjp81 » Sat Nov 03, 2018 11:26 pm

Here's a Window Error Reporting event associated with the Error event, also in Windows Event Viewer:

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

Problem signature:
P1: HandBrake.exe
P2: 1.1.2.0
P3: 5b903422
P4: StackHash_76a1
P5: 0.0.0.0
P6: 00000000
P7: PCH_9B
P8: c0000005
P9: 0000000000000008
P10:

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4D9E.tmp.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4EA8.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4EB9.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4EB7.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4EE7.tmp.txt

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

Analysis symbol:
Rechecking for solution: 0
Report Id: 38d1c85d-b985-4196-be91-fa2fdd530b1c
Report Status: 268435456
Hashed bucket: dda28d4499f943f779b23eda74a0daf5

User avatar
s55
HandBrake Team
Posts: 9218
Joined: Sun Dec 24, 2006 1:05 pm

Re: HandBrake 1.1.2 won't open in Win10

Post by s55 » Sat Nov 03, 2018 11:27 pm

Unfortunately, it's not a helpful error.

My guess is there is some kind of missing or corrupted system file, maybe a bad graphics driver that's triggering this

You might want to try running the system file checker (command line sfc) and making sure your fully up-to-date with drivers etc.

Can you also screenshot the installation directory? Would like to make sure all the required files are present.

https://handbrake.fr/nightly.php -> Maybe worth a shot (targets a newer .NET framework again)

mjp81
Posts: 12
Joined: Sat Nov 03, 2018 8:25 pm

Re: HandBrake 1.1.2 won't open in Win10

Post by mjp81 » Sat Nov 03, 2018 11:40 pm

I am running (or trying to run SFC) by typing "SFC" into the search menu, and a DOS like window blinks on the screen and goes away. Is the test that quick? How do I make sure my drivers are updated? Where is that menu?

How do I attach an image from my Desktop to a reply message? I don't see the way.

mjp81
Posts: 12
Joined: Sat Nov 03, 2018 8:25 pm

Re: HandBrake 1.1.2 won't open in Win10

Post by mjp81 » Sat Nov 03, 2018 11:43 pm

Ok, I at least figured how to run SFC /SCANNOW through Windows PowerShell, but still don't know how to attach an image.

mjp81
Posts: 12
Joined: Sat Nov 03, 2018 8:25 pm

Re: HandBrake 1.1.2 won't open in Win10

Post by mjp81 » Sun Nov 04, 2018 3:20 am

The Nightly build didn't run either

User avatar
s55
HandBrake Team
Posts: 9218
Joined: Sun Dec 24, 2006 1:05 pm

Re: HandBrake 1.1.2 won't open in Win10

Post by s55 » Sun Nov 04, 2018 4:49 pm

You'd have to use a 3rd party image hosting site. It should tell you that it completed successfully and if there are any errors, I expect it will offer to resolve them.

Failing that, Do you have RivaTuner, MSI Afterburner or any similar software installed?

rollin_eng
Veteran User
Posts: 2881
Joined: Wed May 04, 2011 11:06 pm

Re: HandBrake 1.1.2 won't open in Win10

Post by rollin_eng » Sun Nov 04, 2018 4:57 pm

Also disable any virus scanners that might be messing with it.

mjp81
Posts: 12
Joined: Sat Nov 03, 2018 8:25 pm

Re: HandBrake 1.1.2 won't open in Win10

Post by mjp81 » Mon Nov 05, 2018 10:47 pm

I do not have RivaTuner, MSI Afterburner installed. Don't even know what those are.
The SFC /SCANNOW detected corrupted files but was unable to repair them.
Here's the link for the directory files image: https://imgur.com/a/xSlZ2PZ

Would Windows Defender need to be disabled? And even if that were the case, does that mean I could only run it by disabling virus scanners? Doesn't sound like a good trade off.

mjp81
Posts: 12
Joined: Sat Nov 03, 2018 8:25 pm

Re: HandBrake 1.1.2 won't open in Win10

Post by mjp81 » Wed Nov 07, 2018 4:24 am

What's left to do or check?

User avatar
s55
HandBrake Team
Posts: 9218
Joined: Sun Dec 24, 2006 1:05 pm

Re: HandBrake 1.1.2 won't open in Win10

Post by s55 » Fri Nov 09, 2018 9:32 pm

My guess if SFC found problems, and wasn't able to repair them, there is a good chance it's related to this problem. A corrupted Operating system isn't good. I'd maybe suggest trying one of the Microsoft or populate windows tech forums to see if folks can better help. It's probably going to involve a
windows install repair / re-install.

I'm assuming 1.0.7 also doesn't work now? (Old versions are still available on the download page)

Unfortunately, I don't have anything else to suggest.

ghinton
Posts: 1
Joined: Tue Nov 13, 2018 7:35 pm

Re: HandBrake 1.1.2 won't open in Win10

Post by ghinton » Tue Nov 13, 2018 8:14 pm

I am experiencing the same issue. Handbrake crashes immediately after opening (doesn't appear to do anything). I have run SFC and it doesn't show any issues. I am on a brand new computer running Windows 10 Home version 1803 (OS build 17134.407) , Intel i7-8086K processor, 16 GB of RAM, and a 8GB nVidia GeForce GTX 1070 Ti graphics card with DirectX 12.0. My main hard drive is a 256 GB SSD drive, with a 2TB secondary normal hard drive. I have even tried the latest nightly build with no success. I didn't have any issues on my old computer. Attached is the info from Event Viewer

Application Error

Code: Select all

Faulting application name: HandBrake.exe, version: 1.1.2.0, time stamp: 0x5b903422
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00007ffafffffffe
Faulting process id: 0x316c
Faulting application start time: 0x01d47b8cd9843393
Faulting application path: C:\Program Files\HandBrake\HandBrake.exe
Faulting module path: unknown
Report Id: c15f546e-16d8-486f-9e43-6911ecea6fa3
Faulting package full name: 
Faulting package-relative application ID: 
Information

Code: Select all

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

Problem signature:
P1: HandBrake.exe
P2: 1.1.2.0
P3: 5b903422
P4: StackHash_76a1
P5: 0.0.0.0
P6: 00000000
P7: PCH_46
P8: c0000005
P9: 0000000000000008
P10: 

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE40C.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE4B8.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE4C9.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE4C7.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE4E7.tmp.txt

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

Analysis symbol: 
Rechecking for solution: 0
Report Id: c15f546e-16d8-486f-9e43-6911ecea6fa3
Report Status: 268435456
Hashed bucket: 2d6b69fb312e4e39de8b9da55a753006
Cab Guid: 0
WER Report

Code: Select all

Version=1
EventType=BEX64
EventTime=131866133984444026
ReportType=2
Consent=1
UploadTime=131866133986658100
ReportStatus=268435456
ReportIdentifier=db201a45-3403-4da0-bcdd-291425e4b47e
IntegratorReportIdentifier=c15f546e-16d8-486f-9e43-6911ecea6fa3
Wow64Host=34404
NsAppName=HandBrake.exe
OriginalFilename=HandBrake.exe
AppSessionGuid=0000316c-0001-001d-9333-84d98c7bd401
TargetAppId=W:00003234c4d2c22b3a57342482a75458e14a0000ffff!000022710bcbec9fe5bab88579a1e0dcfe27f4f51f33!HandBrake.exe
TargetAppVer=2018//09//05:19:53:06!0!HandBrake.exe
BootId=4294967295
TargetAsId=1679
IsFatal=1
Response.BucketId=2d6b69fb312e4e39de8b9da55a753006
Response.BucketTable=5
Response.LegacyBucketId=2201026176413413382
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=HandBrake.exe
Sig[1].Name=Application Version
Sig[1].Value=1.1.2.0
Sig[2].Name=Application Timestamp
Sig[2].Value=5b903422
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_46
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.17134.2.0.0.768.101
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\WINSPOOL.DRV
LoadedModule[19]=C:\Windows\System32\kernel.appcore.dll
LoadedModule[20]=C:\Windows\SYSTEM32\PROPSYS.dll
LoadedModule[21]=C:\Windows\System32\OLEAUT32.dll
LoadedModule[22]=C:\Windows\System32\shcore.dll
LoadedModule[23]=C:\Windows\System32\sechost.dll
LoadedModule[24]=C:\Windows\SYSTEM32\IPHLPAPI.DLL
LoadedModule[25]=C:\Windows\SYSTEM32\bcrypt.dll
LoadedModule[26]=C:\Windows\SYSTEM32\sfc.dll
LoadedModule[27]=C:\Windows\SYSTEM32\sfc_os.DLL
LoadedModule[28]=C:\Windows\SYSTEM32\SortWindows61.dll
LoadedModule[29]=C:\Windows\System32\IMM32.DLL
LoadedModule[30]=C:\Windows\System32\ADVAPI32.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\a6021ef6892ab519b334a17992542017\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\8ff4bf965a60a85a0598226bf67e993a\System.ni.dll
LoadedModule[39]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Core\4db19b6c7622a8939b4a5629cf59c5ff\System.Core.ni.dll
LoadedModule[40]=C:\Windows\assembly\NativeImages_v4.0.30319_64\WindowsBase\393414ebfcd8a64e2f3b267a38832ce0\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\a5b2d65123f574f273f7a1a2920182dd\PresentationCore.ni.dll
LoadedModule[45]=C:\Windows\assembly\NativeImages_v4.0.30319_64\Presentatio5ae0f00f#\9f0feb655b529709fff4e5130ce69f7a\PresentationFramework.ni.dll
LoadedModule[46]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Xaml\cdfeba4bfc8c7fd52fbbeb81ecb25989\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\ed57871eb5218c20f36290299e011a90\System.Configuration.ni.dll
LoadedModule[53]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Xml\96b052a0815a6699986712bec8659f0f\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\FLTLIB.DLL
LoadedModule[60]=C:\Windows\system32\dwmapi.dll
LoadedModule[61]=C:\Windows\System32\MSCTF.dll
LoadedModule[62]=C:\Program Files\HandBrake\hb.DLL
LoadedModule[63]=C:\Windows\System32\WS2_32.dll
LoadedModule[64]=C:\Program Files\Intel\Media SDK\libmfxhw64.dll
LoadedModule[65]=C:\Windows\SYSTEM32\dxva2.dll
LoadedModule[66]=C:\Windows\SYSTEM32\dxgi.dll
LoadedModule[67]=C:\Windows\SYSTEM32\d3d11.dll
LoadedModule[68]=C:\Windows\System32\DriverStore\FileRepository\ki129346.inf_amd64_a660f1f427105485\igd10iumd64.dll
LoadedModule[69]=C:\Windows\SYSTEM32\ncrypt.dll
LoadedModule[70]=C:\Windows\SYSTEM32\NTASN1.dll
LoadedModule[71]=C:\Windows\System32\DriverStore\FileRepository\ki129346.inf_amd64_a660f1f427105485\igc64.dll
LoadedModule[72]=C:\Windows\System32\DriverStore\FileRepository\ki129346.inf_amd64_a660f1f427105485\igd11dxva64.dll
LoadedModule[73]=C:\Windows\System32\DriverStore\FileRepository\ki129346.inf_amd64_a660f1f427105485\igdinfo64.dll
LoadedModule[74]=C:\Windows\System32\DriverStore\FileRepository\ki123931.inf_amd64_750ee5716ca7cecc\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=17134
OsInfo[3].Key=ubr
OsInfo[3].Value=407
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=54681
OsInfo[15].Key=osinsty
OsInfo[15].Value=1
OsInfo[16].Key=iever
OsInfo[16].Value=11.407.17134.0-11.0.95
OsInfo[17].Key=portos
OsInfo[17].Value=0
OsInfo[18].Key=ram
OsInfo[18].Value=16191
OsInfo[19].Key=svolsz
OsInfo[19].Value=221
OsInfo[20].Key=wimbt
OsInfo[20].Value=0
OsInfo[21].Key=blddt
OsInfo[21].Value=180410
OsInfo[22].Key=bldtm
OsInfo[22].Value=1804
OsInfo[23].Key=bldbrch
OsInfo[23].Value=rs4_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.17134.407.amd64fre.rs4_release.180410-1804
OsInfo[30].Key=buildflightid
OsInfo[31].Key=edition
OsInfo[31].Value=Core
OsInfo[32].Key=ring
OsInfo[32].Value=Retail
OsInfo[33].Key=expid
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=5621D2F7361E4577EFB2323F5396C5ED
MetadataHash=-922148448

Post Reply