Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 10/11/2018 in all areas

  1. Could you please provide the link to the new symbols file? EDIT: Nvm, I found them myself. If someone encouters the same issue after the latest cumulative Windows 10 update, you can download the appropriate symbols with this tool: https://github.com/rajkumar-rangaraj/PDB-Downloader Just select the dwmcore.dll in C:\Windows\System32.
    1 point
  2. Well, it isn't really used for DRM content decryption anymore, and Vista users have the Windows Media Framework to fall back on if ffvpx fails them in some way (like the Twitter audio bug). So if you're on Vista, I can't see why you would need or want it. But it is useful on XP. Since the same browser is used by users of both OSes, it probably makes sense to keep it separate. That way XP users can install it if they need it, without bloating the package for Vista users. Besides, like any add-on it gets installed in your profile folder, not the main program folder, so it would be tricky to include in the browser package anyway.
    1 point
  3. For Windows 8, I'll use Windows Defender, alongside on-demand scans with Malwarebytes (I still use v1.75 with current definitions). For Windows Vista, 7 or XP, I'd install Comodo Anti-Virus. It seems complete, and REALLY quick.
    1 point
  4. With the registry entries only TLS 1.0, TLS 1.1 and TLS 1.2 has been activated.
    1 point
  5. Only KB4019276 and current cumulative update for IE8 (KB4462949) is needed! KB3055973 was replaced by KB3081320 and KB3081320 by KB4019276. Following the settings for the registry so that TLS 1.1 and 1.2 can be selected in IE8. Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\AdvancedOptions\CRYPTO\TLS1.2] "OSVersion"=- [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\AdvancedOptions\CRYPTO\TLS1.1] "OSVersion"=- [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings] "SecureProtocols"=dword:00000a80
    1 point
  6. 1 point
  7. KernelEx core update 4.5.2016.18 (beta) - KexBeta.18.7z 206.93 KB VKrnlEx.vxd - System driver KernelEx.dll - Core logic Kexbases.dll - API extensions (Shared) Kexbasen.dll - API extensions (Non-shared) KexCOM.dll - COM extensions Sheet.dll - Property Sheet Handler ApiLog.exe - Debugging console ApiHook.dll - Debugging support Verify.exe - Verify installation is working. Core.ini - Settings for KernelEx.dll LZDLL.reg - Registry support for six missing (98/SE) DLL's LZDLL_ME.reg - Registry support for four missing (ME) DLL's API-MS-Win.reg - Registry support for Win7 API sets 1) Exit Windows or reboot to DOS. 2) Copy all files except KernelEx.dll to existing KernelEx folder. (Kexstubs users: edit Core.ini [BASE] contents= line here.) 3) Reboot to Windows. 4) Run Verify.exe 5) (Optional) Add registry entries as needed. More updates are already nearing completion: Ktree, Kexports; SList, SRW, PowerRequest. Specific API requests welcome.
    1 point
×
×
  • Create New...