Leaderboard

This doesn't have anything to do with Windows 10. I have used the root cert update in that package successfully on Vista.

Greetings , do you , by any chance , have links to other solutions ? As far as I can see, it's just a tool for generating certificates and importing them from windows 10 . Maybe I'm wrong , but I'm looking for a solution where one could be able to update them directly on Vista , whithout any involvement from win10. Vista has a new long life ahead , thanks to the extended kernel project and win32 !

@TECHGEEKusually has the most rare problems , unique problems I'd say , which others don't. I've never had any issues with VLC's Aero on Vista . It worked without any patching , as you can see by my first post in this topic , before your suggestion , but it improved buttons on the newer versions , added some curves to them , so don't cut yourself short , it's definitely the dev's who are to blame. But I wouldn't say "a bit different" , I'd say they are almost invisible . It's hard to see the signs on the buttons.

I just don't understand how can you not see the difference . And yes , I've made everything like you said. Still 3.0.0 and above stick with Win10 buttons and older versions have Vista style buttons . Yes , they became somewhat better after the patch , but not to the point of representing the previous glory. So I agree with the previous poster , VLC devs made something ugly to the buttons. The shot was taken on Vista x64.

I've never had this issue with any of Vista builds (SP or not). And I'm kinda Vista veteran. My first Vista RTM PC had 4GB of RAM , bought in 2007 , reinstalled many times without any issues too . Also, had RTM installed on Haswell back in 2013 with 16GB of RAM , and yes , it was x64. Logon happened from to time , even though I had defender removed since 2007 or so . Later I began to notice slower extraction of huge files with WinRar , when I replaced my mobo in 2010 , but i think it was chipset bound . I still have that mobo with Intel Q45 chipset and the extraction process is like 1.5 times slower , even when SP2 installed. I think it's a weird combination of the mobo's chipset and 2TB/3TB/4TB Seagate HDDs , because I never noticed such problem with other HDD manufacturers. I agree about the VRAM problem , it persists in RTM , that was the reason I moved to SP1 on my gaming PC , in 2009-2010 (approx.). Though , I still think RTM is better in many aspects. P.S. Would be interested in getting back to RTM too.

Yes , Haswell , on my spare PC. Maybe this information will help someone , to make the bug less frequent , you need to disable Windows defender (or better remove it completely with vLite) and manually delay the boot process , yeah , add a ton of startup processes , for example . I've noticed it when booting from an old [slow] HDD makes it boot without the damn error. I don't know if that helps if you installed SP2 . My main PC is with LGA1156 and currently running SP1 , but I want to use RTM , the only thing that prevents me from doing so , that weird VRAM limit. I just don't see any useful things added in service packs , except for DX11 maybe , but yet again , I only have one game that can use it . I honestly don't understand why do I have to install updates too. They just make my PC slower. Vista RTM is the sweet spot between speed and modern windows. I had Windows Millenium before Vista , btw. Also good , despite the common bashing.

New build of Serpent/UXP for XP! Test binary: Win32 https://o.rthost.win/basilisk/basilisk52-g4.7.win32-git-20201212-6d0527a-uxp-4281fcc16-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk52-g4.7.win64-git-20201212-6d0527a-uxp-4281fcc16-xpmod.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/custom IA32 Win32 https://o.rthost.win/basilisk/basilisk52-g4.7.win32-git-20201212-6d0527a-uxp-4281fcc16-xpmod-ia32.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/ia32 NM28XP build: Win32 https://o.rthost.win/palemoon/palemoon-28.10.2a1.win32-git-20201212-31167a236-uxp-4281fcc16-xpmod.7z Win64 https://o.rthost.win/palemoon/palemoon-28.10.2a1.win64-git-20201212-31167a236-uxp-4281fcc16-xpmod.7z Official UXP changes since my last build: - Issue #1694 - Part 1: Use scriptabledateformat for the Cookie Accept dialog. (16a1ff22a) - Issue #1694 - Part 2: Use scriptabledateformat for Update History display. (6cb00e2cf) - Issue #1695 - Fix socket timeout logic. (6b45065f1) - Revert "Issue #1391 - Disable DOM Filesystem/dirpicker APIs by default." (4281fcc16) Official Basilisk changes since my last build: - Issue #31 - Part 1: Use nsIScriptableDateFormat in Page Info. (c7a029f) - Issue #31 - Part 2: Use nsIScriptableDateFormat in feeds. (8a74eeb) - Issue #31 - Part 3: Use nsIScriptableDateFormat in places library window. (5f97253) - Issue #31 - Part 4: Use nsIScriptableDateFormat in cookie preferences. (01c2847) - Issue #31 - Part 5: Update back-end branch pointer for toolkit changes. (6d0527a) Official Pale-Moon changes since my last build: - Back-end branch pointer update (unstable 2020-12-06) (31167a236) My changes since my last build: - Reverted Issue UXP#1694 and Basilisk#31 related changes

A workaround equivalent to downgrading to older version of VLC as far as control styling and DLL hijacking exploits are concerned would be to to search vlc.exe with a hex editor for "SetDefaultDllDirectories" and replace a single letter in that word with something else, just don't insert or delete anything, only replace. At least that works if program doesn't check itself for integrity, I've yet to try it with VLC specifically, though I guess there are good chances that it works.