superleiw

Use Root Certificate Updater for Windows 7 and higher : https://github.com/asheroto/Root-Certificate-Updater Also, do you have a fully updated Windows 7? Do you have the SHA-2 Patch installed? LINK Maybe you are missing that or the driver doesn't have have a valid SHA-2 certificate.

Looks like support for ESR 115 has been extended until March 2025 with possibility for an additional extension. https://support.mozilla.org/en-US/kb/firefox-users-windows-7-8-and-81-moving-extended-support https://groups.google.com/a/mozilla.org/g/dev-platform/c/ffRCWVVHvAQ/m/PCVKYNnnAAAJ

Even the Bypass by abbodi doesn't work anymore?

Oh that might be why it could be problematic! Well the .NET POSReady updates are available here : https://www.catalog.update.microsoft.com/Search.aspx?q=.NET+Framework+POSReady Some older updates might be missing as I'm not seeing any .NET updates from 2014 to early 2016, so I'm not sure.

Do you have Update KB2999226 or KB3118401 installed? I think you need one or the other for VC redists 2015+ to work on W7/8/8.1 KB2999226 : https://support.microsoft.com/en-us/topic/update-for-universal-c-runtime-in-windows-c0514201-7fe6-95a3-b0a5-287930f3560c or KB3118401 : https://support.microsoft.com/en-us/topic/update-for-universal-c-runtime-in-windows-322bf30f-4735-bb94-3949-49f5c49f4732 For KB3118401 there is only a Server 2012 version but it should work on 8.0 as well.

Indeed, if you want to manually update those certificates on W7 or higher it's possible to use alternative tools. The rootsupd.exe (and the updroots.exe inside of it) are outdated and should not be used (except for XP & Vista) In fact, they break the "Microsoft Root Certificate Authority" root certificate on modern systems (at least Windows 10 1803+). An alternative to use on W7 and higher would be Root Certificate Updater available here (GUI or Powershell Script) : https://github.com/asheroto/Root-Certificate-Updater https://www.powershellgallery.com/packages/UpdateRootCertificates/2.0.0 This tool was originally developed to manually update the root certificates on Windows 10, Server 2012/2016/2019. It seems to also work on W7/8/8.1 if WMF 5.1 is installed.

It works if you spoof the Firefox version to the latest version 128. Spoofing the OS is not needed. The User Agent should look like this : Mozilla/5.0 (Windows NT 6.3; Win64; x64; rv:109.0) Gecko/20100101 Firefox/128.0

Btw, did anyone ever create POSReady .NET Framework addons? I only remeber the unofficial SP4 pack having those updates but what about standalone addons?

That would be a good idea. I also kept a few addons/installers on an old external HDD that I could contibute.

I found this driver for DEV_5916 but it has no installer so I think you have to go through Device Manager and point it to the folder manually ! Driver Version 21.20.16.5077 (2019) https://dl.driverpack.io/driverpacks/repack/Video_Intel-NT/Intel/FORCED/6Xx64/HD600_21.20.16.5077/Intel-FORCED-6Xx64-HD600_21.20.16.5077-drp.zip Driver Version 21.20.16.4565 (2016) https://dl.driverpack.io/driverpacks/repack/Video_Intel-NT/Intel/FORCED/7x64/HD600_21.20.16.4565/Intel-FORCED-7x64-HD600_21.20.16.4565-drp.zip

In your first post you mentionned that you were using Webrender, is this still true? Did you manually enable it? Because most of these settings only work on W10+. In about:config those two options are for W10+ so maybe you can try setting them to False : gfx.webrender.all -> true (Windows 10/11 only) gfx.webrender.software -> true (Uses CPU instead of GPU but requires Windows 10+) The following options might also need to be reset to their default values : gfx.webrender.enabled gfx.webrender.compositor gfx.webrender.compositor.force-enabled

KB2819745 is Powershell 4.0, you don't need to install it You can update directly to PS 5.1 (Win7AndW2K8R2-KB3191566-x64.zip) here : https://www.microsoft.com/en-us/download/details.aspx?id=54616 On Windows 7 the only requirements are NET 4.5 (or higher) and SP1

I'm already below my monitor's default setting but It doesn't change anything for me even with lowest settings. Maybe I have some kind of sensitivity. Anyway I also came across another solution for Firefox : 1) Disable Hardware Acceleration 2) In about:config change "layers.acceleration.force-enabled" to "True" 3) Restart browser and everything works smoothly and colours are the way they should be (even in RGB Limited)

So for someone who has already installed XP (+POSReady) using the English versions of your addons, would it be sufficient to just modify the registry entries post-install? Or is it necessary to have the correct entries during installation? Also compared to 5eraph's original addon, your 5erPOSUP.inf has a lot of references to D:\WINDOWS\ Shouldn't it be C:\WINDOWS\ or something like %systemdrive%\WINDOWS\ ? Maybe the %systemroot% variable could work as well. For example : HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Installations\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.7660_x-ww_936580bb\Codebases\U_KB4490228","URL",0,"D:\WINDOWS\ServicePackFiles\i386/controls.man"

I have been using RGB Limited for years because I have always disliked how White and Deep Black colours looked in RGB Full. I found it to be more strenuous on the eyes and to cause unnecessary visual fatigue (for me). Well I now looked more deeply into this and turns out there is another solution : Using Ycbcr 4:4:4 in the Nvidia Control Panel. This does not cause any problem with HW ACC. enabled in Firefox. The colours in general look more natural (to me) especially white and black on the monitor/graphics card combinations I have tried. I thought Ycbcr was something from the Analogue era and never used that. I was probably confusing it with something like YUV. Here are some interesting links I came across: https://linustechtips.com/topic/82154-what-color-format-looks-better-gaming-ycbcr444-or-rgb/ https://www.nvidia.com/en-us/geforce/forums/discover/144126/rgb-vs-ycbcr444-/ https://hardforum.com/threads/rgb-vs-ycbcr444-in-nvidia-control-panel.1998222/ https://www.overclock.net/threads/which-setting-is-better-for-gaming-rgb-full-limited-or-ycbcr-422-444.1628651/ https://hardforum.com/threads/4-4-4-limited-vs-rgb-full-which-is-preferred-and-hdmi-2-0a-vs-2-0b-switches.1926589/ TLDR : Either RGB Full or Ycbcr 4:4:4 should be used depending on your monitor/graphics card combination and personal colour preference. RGB Limited should be avoided with HW ACC enabled in FF

WOW, thank you for creating this thread and reuploading all of these files ! Feeling very nostalgic about the good old RyanVM forums

I'm having the same colour problem with my GTX 960 (4 GB VRAM) graphics cards on Windows 7 and Windows 8.1 when using : Firefox + Hardware Acceleration and HDMI set to Limited in NVidia Control Panel This problem does not occur in Microsoft Edge. Haven't tested other browsers. I don't remember having this problem with my Nvidia GT 710 or 610M (laptop) but I was using an older driver version with those. Probably pre-400.00 . Need to test it on W10/W11 to see if the problem exists there as well at some point.

Interesting information!! And also your other posts on page8 related to those pseudo/stub DLLs VC Redist 2015-2019 was compatible with XP until version 14.28.29213.0 Thanks for sharing, I'm guessing this is from a x64 Windows ? Is there any difference between x64 and x86 when it comes to these specific DLL files? Just wondering if I could use it on x86 Windows 7 as well.

Ah crap, well it would have been too easy if it worked I guess. I'm gonna keep using the ESR version for now then.

I'm wondering that as well, does Auto-Update work after this modification?

Found some Windows 7 drivers : Have you already tried any of these eMMC drivers by any chance ? https://board.eclipse.cx/download/file.php?id=272 The W7 Braswell drivers from 2015 might be compatible with your laptop.

It might also depend on the version of the eMMC card. Comparison Link HERE The way I understood it is that this hotfix may only be useful for eMMC cards version 4.41 (and higher?). Older cards would not require it. But then again this could be a 8.1 problem only... Edit : I just verified and Windows 8 received updates to dumpsd.sys and sdbus.sys through Security/Cumulative Updates all the way until 2019 !! For some reason Windows 8.1 never received any updates to those files beyond 2015. So I guess this hotfix is indeed only needed for 8.1 then. W8 might have had this problem as well back then, but it probably has long since been fixed through regular Windows Updates ! I do wonder now if it's possible to go the other way around -> using those updated W8 files on W8.1 for better support for the latest eMMC versions. Edit 2 : Those updated dumpsd and sdbus file seem only available in the Server 2012 updates.

On Windows Vista and higher there should be no need to manually update those certificates anymore. Like Draker said, the behaviour on these OS since Vista is the same ; Windows checks for Trusted CTL once a week and the Untrusted CTL every day through Windows Update using the automatic daily update mechanism (CTL updater) ! Disabling WU may prevent those certificates from being updated ( I haven't tested it myself so can't confirm) To modify this behaviour (at your own risk) it's possible to change the following registry keys : Enable or disable the Windows AutoUpdate of the trusted CTL: [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\SystemCertificates\AuthRoot] "DisableRootAutoUpdate"=dword:00000000 0 to enable or 1 to disable. This key is not present by default. Without a key present, the default is enabled. Enable or disable the Windows AutoUpdate of the untrusted CTL: [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\SystemCertificates\AuthRoot] "EnableDisallowedCertAutoUpdate"=dword:00000001 1 to enable or 0 to disable. This key is not present by default. Without a key present, the default is enabled.

Not sure if this is useful as it would need to be backported but Microsoft had released a eMMC Hotfix for W8.1 https://support.microsoft.com/en-us/topic/emmc-device-is-not-detected-as-a-storage-device-by-windows-8-1-or-windows-server-2012-r2-ee95ef54-081c-135c-f38e-142cc4dbbf14 The hotfix can be downloaded from here : https://thehotfixshare.net/board/index.php?/files/file/20824-windows81-kb3078919-x64msu/ (64bit) https://thehotfixshare.net/board/index.php?/files/file/20825-windows81-kb3078919-x86msu/ (32bit) Contains dumpsd.sys and sdbus.sys and sdbus.inf fileversion 6.3.9600.17931 from July 2015

On Windows 8.1 I was able to install I219-V by force-installing it as I219-LM. Not sure if it works on W7 also. Got the info from this website : https://blog.workinghardinit.work/2017/06/19/installing-intel-i211-i217v-i218v-i219v-drivers-windows-server-2016-eufi-boot/