Leaderboard

Nobody gets special permissions. I don't even know who is part of Eclipse as I don't frequent their forums, I just don't have time to. To be honest, I'm ready to lock the entire thread. I will keep it open under one condition, please keep it on topic, keep it clean, and nobody will have to have their posts deleted, moderated, or users having to be warned. It truly is just that simple. I don't understand why there's such a problem here.

No, he means Office 2010 works as it is, excluding the issue of having to terminate the .exe process to make it start again. It doesn't mean the issue doesn't happen.

This is userstyle code, so you can either place it inside file: <browser-profile-directory>\chrome\userChrome.css (requires a browser restart to take effect) or use the userstyle manager Stylem to create a new userstyle containing the posted CSS code... FWIW, an "empty" userChrome.css file (aka userChrome-example.css) contains the below code: /* * Edit this file and copy it as userChrome.css into your * profile-directory/chrome/ */ /* * This file can be used to customize the look of Mozilla's user interface * You should consider using !important on rules which you want to * override default settings. */ /* * Do not remove the @namespace line -- it's required for correct functioning */ @namespace url("http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul"); /* set default namespace to XUL */ /* * Some possible accessibility enhancements: */ /* * Make all the default font sizes 20 pt: * * * { * font-size: 20pt !important * } */ /* * Make menu items in particular 15 pt instead of the default size: * * menupopup > * { * font-size: 15pt !important * } */ /* * Give the Location (URL) Bar a fixed-width font * * #urlbar { * font-family: monospace !important; * } */ /* * Eliminate the throbber and its annoying movement: * * #throbber-box { * display: none !important; * } */ /* * For more examples see http://www.mozilla.org/unix/customizing.html */ Hope it helps

THE DRIVER WORKED!!!! THANK YOU SO MUCH!!!! With working WiFi, I can finally ditch Ethernet! Now time to find an internet browser that renders properly as not even Google Chrome does.

TEST page of the nullish coalescing assignment (x ??= y) operator: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Nullish_coalescing_assignment#syntax Expected to perform well in this test are our forks: MiniBrowser, 360Chrome 13.5 and 360Chrome 13 (result: > 50 > 25).

I think @VistaLover and @dmiranda are spot on. Which is: Fade out tab label on overflow instead of ellipsis... although I'm not entirely sure why that is useful. It is Tab Mix Plus that has been broken. Installing the latest https://addons.palemoon.org/addon/tab-mix-plus/ Pale Moon/Basilisk 0.5.8.4 version doesn't help. Which is a shame because TMP is a nice add-on. For the moment I've sort of fixed things with this... .tab-label[pinned] { width: 0 !important; margin-left: 0 !important; margin-right: 0 !important; padding-left: 0 !important; padding-right: 0 !important; } .tab-content { white-space: nowrap !important; overflow: hidden !important; text-overflow: ellipsis !important; } ...but it's by no means perfect especially if you start opening lots of tabs. Ben.

http://blog.livedoor.jp/blackwingcat/archives/2029423.html I creatd it. But it seems to be supported windows 2000 , so I modified inf file only. How about version 9.2 driver ? :3

Try this: Ctrl-Shift-B to open the "All Bookmarks" window. Click "Import and Backup." Click "Export Bookmarks to HTML." Save your bookmarks.html file somewhere. Remember where you saved it. Close that browser; open the other one. Repeat steps 1 and 2. Click "Backup" and save a backup of your bookmarks in case something goes wrong. Click "Import and Backup" again, then "Import Bookmarks from HTML." Select the bookmarks.html file you saved in step 4. If things go haywire, click "Import and Backup," then "Restore" and restore the backup saved in step 7.

Writing this from Server 2008 R2 x64, and I think I've settled on the ultimate compromise now. I was amazed with Server 2003 x64, the fastest experience I've ever had running Windows XP. However, XP (while still my favorite version of Windows) is in a tougher spot than 7 at the moment when it comes to software. 7, of course, is my second favorite version (and to me, MS's last great OS). So I ended up looking into what 7's equivalent would be, hoping to see if I could reap the same benefits Server 2003 has over the standard XP. Turns out the answer is 'YES'! I can't say enough good things about Server 2008 R2. Just like 2003 it's a true 'thoroughbred' OS that trims out exactly the right amount of fat from standard 7, and carries a more powerful version of 7's already incredible kernel. All the same advantages of Server 2003, and then some, are found here (including support for more physical processors, more RAM and larger hard disks). There are quirks (such as having to enable the audio service and install WiFi support from a built-in manager), but it's still fantastic. It is an idea I wish regular Windows would implement (giving you a base set of features out of the box and a manager tool to add other features when the need arises), but it may irritate casual users, while only advanced users would really, truly, take advantage. After a lot of testing, my journey is, without a doubt, over for now. Unless the incompatibility of newer hardware makes me move up to 10, or the limitations of older hardware bring me back to XP, it's 7 or bust for the foreseeable future. XP's browser situation is just much too dire for my comfort nowadays. I'm currently on Hibbiki's last Chromium 109 build (.120 being the newest available point update at the moment), but I hope there will be more builds as more security updates are released--and of course I'll try to keep track of anything new that comes up on the browser front for Windows 7. The fact that Chromium 109 is still getting security updates is very cool, and I think that version will be perfectly usable at least for a couple more years before it can truly be considered 'obsolete'. And of course, Firefox is still getting updates for the time being, and there is also the option to experiment with older versions of Chromium/Firefox (for example, Chromium 87 and Firefox 78 ESR/84 were the last versions with built-in Flash support, so if you like to play Flash content in a browser and have a modern code base these are still worth revisiting), and to try out other browsers too. Many thanks to everyone who is still using 7, and following what's going on! If I can contribute anything of value, I will try my best.

I see it's been a while since anyone has posted here! Writing this from Server 2003 x64, and having done a lot of testing with older and more modern versions of MAME (for anyone interested in that emulator), here is what I've found. I was not able to get an official 64-bit version newer than 0.204 working in XP x64 or Server 2003 x64...and it seems that based on at least one other source, I'm not alone: https://www.reddit.com/r/MAME/comments/fbz7db/compiled_mame_0217_or_later_that_runs_in_windows/ However, I can confirm that all official 32-bit versions up to and including 0.207 do work fine in all versions of XP (SP2 minimum). Starting with 0.208, the compiler was upgraded from GCC 7 to GCC 8, which broke XP compatibility altogether. https://old.reddit.com/r/emulation/comments/b62rjt/mame_0208/ I am not sure what happened with version 0.205 that broke 64-bit binary compatibility with XP; reviewing the release notes doesn't seem to give much of an answer. So to sum it up: 0.204 is the final official version of MAME with working 32/64-bit binaries in XP x86 (SP2 minimum) AND XP x64 (which ends at SP2). 0.207 is the final official version of MAME with a working 32-bit binary in all versions of XP (SP2 minimum). This means that to take full advantage of XP x64's true 64-bit capabilities, you cannot go any higher than 0.204 officially. While it is possible to go up to 0.207 officially on all versions of XP (SP2 minimum), only the 32-bit binary is universally compatible, and only x86 XP will be able to take full advantage of it. Unofficially, there are efforts being made to this day to restore and maintain XP compatibility through custom builds, which can easily be found at progetto-SNAPS among other sites. However, your mileage will vary. Unless there is a game that was added more recently that you are genuinely curious about, I'd stick with 0.204--even by today's standards, it is a great/reliable version of MAME. Hope this helps someone!

So the AeroGlass for Win8+ would violate the EULA, as the restriction or limitation in this case would be the inability to display Vista/7-style glass. Also there was undoubtedly some disassembly and reverse engineering of internal DWM functions to make it work. And I think this goes for Stardock's assortment of desktop enhancement products as well, but they may have the resources to perform clean-room RE. This also goes for products that may have also violated EULA in this way, such as VMware (which reimplements some kernel mode functions for systems lacking them) and Chromium (which uses undocumented classes of some Native API functions). But these EULA terms are often superseded by exemptions in copyright law. In Canada, we have section 30.6 in the Copyright Act where: (i) would cover the additions to the Vista kernel that make newer drivers run, such as NVIDIA 398.11. Perhaps adding support for newer user mode software also plays a role in "compatibility". Adding support for NVIDIA 398.11 made Windows Vista compatible with a system with a GTX 1080 Ti, then the extended kernel also made new browsers and games compatible; thus, it is now fully compatible with the particular computer, whereas it was not when it could not run the software and device drivers. (ii) would be technically satisfied if the process of installing the extended kernel constituted the adaption or modification of the software, to create the reproduction (Vista with extended kernel installed). I believe this is also valid. I expect most of the world to have similar exemptions, including the EU where MSFN is based. An activation bypass would not usually be essential for compatibility, unless the activation procedure itself made it incompatible. This is not the case with any form of Microsoft Windows.

Hi all ,this topic created to try the Office 2010 in Windows 2000 , you should first to install the latest version of extended kernel from blackwingcat wlu site : http://www.win2k.org/wlu/wluen.htm then you can try to run office 2010 , but unfortunately the installer don't work until now , then what is the solution for now ? the solution exist to run office 2010 but even that it is not perfectly stable. you should to download this version of portable office 2010 exist Here With fcwin2k run the office which you want 'word, power point..' on XP SP3 compatibility mode. Require : msxml 6.0 service pack 2 . Unstable thing: the unstable thing is that when you finished work and you want to close the word as example you should after close it's window with default 'X' to end the process with taskmgr to be capable to run powerpoint in next time as example ,this is video to explain what i mean : https://t.co/46v3mBvOi5 @blackwingcat if you have any news about the installer please tell us here . any one has problem about this topic please post here and you can tag any persone . To resolve this unstable thing you should to use my created program : https://www.mediafire.com/file/882xrdvu886u9u5/O10KWIN2000.zip/file The other issue is the office 2010 with fcwin2k uses with many uses , some time after reboot the office 2010 it will doesn't start , then in this case you should to extract again the office 2010 portable.zip again , and run it with XP sp 3 and save compat.

Ugh, more Bing promotion.

https://www.theverge.com/2023/2/28/23618214/microsoft-windows-11-update-bing-ai-taskbar-touch-improvements-screen-recording-features

Well, please take a picture to confirm people that this works not only with me and encourage them to try it

Not yet, but will do so now.

I did, it works as it should (ignoring the issue mentioned above).

Mypal 68 should work natively with KernelEX version 3.1b and newer. It's still possible to run it with older versions of KEX, but you'll have to refer to this guide.

Actually in this Qt forum thread, some people provided some Windows 7-compatible Qt6 DLLs. With these DLLs you can run some Qt6 application like OBS v28.x (v29 also requires a modification to OBS.dll to change IsWow64Process2 to IsWow64Process). So if your application is based on a version of Qt6 that have custom DLLs (6.2.2, 6.3.0, 6.3.1, 6.4.2 or 6.5.1), just try them. If not, as Qt is open source, maybe you can retrieve the source for the specific version your app uses and modify them create DLLs that works on W7.

You are absolutely right. I mixed up the variables reader.parse-on-load.enabled and reader.parse-on-load.force-enabled. Shi* happens! I already corrected my post. Here is a screenshot of my settings in Serpent 52: Cheers, AstroSkipper

Nice to get it work , and about the browser try maypal 68 and 360 Extreme explorer modified Maypal 68 work if you check these cases , i think

... For me (St52), the default is "false" :

Yes , because "??=" was first implemented in Chromium 85; 360EEv13.x are based on Ch86 and Kafan MiniBrowser on Ch87; but, I suppose, most members here already know this piece of info ; "we" are indeed lucky "we" still have the above forks in "our" arsenal , but, it's easy to realise, "our" luck under XP/Vista32 will run out when Google push out something working only on Chrome88+ ("we" already are hands-off from MV3 extensions ) ... Kind regards

You replying is going off the topic of extended kernels. I was talking about types of extended kernels.

Enjoy your Office 2019 on Windows Vista!

A nice side effect of this change for me is that I can now use GitHub/GitLab in multiprocess mode! (Palefill is incompatible with this mode, and so not installed in my multiprocess profile.) I no longer need to right-click those links and use "Open With" to open them in my single-process profile (and wait for a new Serpent instance to start up); a simple left-click now works as it should. Unfortunately it hasn't fixed everything. Chase.com made a change a couple of weeks ago, after which I could no longer sign in. (It prompts for my user ID and password as always, but when I sign in, I now get the unhelpful message "It looks like this part of our site isn't working right now." I've had to switch to 360EE or MiniBrowser (both Chromium builds) to use Chase.com.

That won't help as the driver also throws this BSOD under Windows XP unless I use the April 2012 driver (the 2013 drivers have problems on Windows XP and 2000), meaning, it's not an Extended Kernel/Core problem. I'm waiting for @blackwingcat to finish modding the 10.0.054 version of the driver from April 2012, which did not produce the BSOD. With a working WiFi card, I can finally ditch Ethernet under 2000!

That could be an advantage: if the "current" script versions contain Googlisms incompatible with UXP, you'd get an "outdated" script that actually runs! Edit: Poking around in the .xpi, it looks like you'd have to hack a few things to make that idea work. Still an interesting idea though.

What @VistaLover said.... but let me add that in the long run, I think it's the opposite! At the moment MiniBrowser (Cr 87 based) leads the pack in rendering the modern Web on pre-Win 7 systems, but I have very little hope of ever seeing a browser based on Cr 88 or later for Vista, let alone XP. Even the Chinese have moved on to Win 7. UXP is still behind 360EE v13/MiniBrowser, lacking dynamic module imports, that worthless ??= Googlism (as I've said before, some Googlisms are quite useful, but this one does nothing that can't easily be done without it: A??=B is clearly equivalent to A=A??B), and I'm sure several other things I've forgotten. And UXP will undoubtedly always be behind, because MCP doesn't have a partnership with Google like Mozilla does. (And they don't want one either, and I don't blame them. I see no reason to develop a browser platform that is just Cr under another name, which is what FF has become.) But here's the difference: Unlike 360EE, MiniBrowser, et al., UXP is still being developed. So, as long as it can be back-ported to XP and Vista, it keeps those OSes "in the game." (Although there are other challenges to those older OSes - I recently started a thread on OAuth2-compatible email clients for them. There are a few that work, but none are really acceptable at present.)

It is still usable and can display modern websites (but, after sometime, some websites may soon require newer Chrome 110+, just like in the last XP/Vista version 49, where they required Chrome 50+), but these security updates will not make Chrome update to the latest version (which is 110, at the moment), they will just improve security.

For the Vista Extended Kernel, the actual intended update path is 2017 EOS + SHA-2 update. The 2018 rollup sometimes suggested is to get a base no updates install up and working with the kernel, but the path that it was changed to however long ago is just the 2017 EOS + SHA-2 update. Also the extended kernel does have some issues with certain applications. I think I prefer the VxKex style of kernel extension where no system files are touched and it redirects functions. Although I think the Vista Extended Kernel type extension would be more compatible with non-native applications.

... Actually, the ball has always been on upstream's court, i.e. MCP... Roy basically makes sure nothing "they" have coded conflicts with his stupendous efforts to maintain XP/Vista compatibility in his UXP forks - of course, genuine platform improvements have been committed to his UXP tree (by backporting stuff from Mozilla and others), but if it's webcompat you're mainly interested in, you'd be in fear of disrespecting MCP, not roytam1 ... ... And that's exactly the crux of the issue: Due to Google's browser monopoly, ALL sites "that matter" are being tailored to work best on latest Chrome ... WebComponents+CustomElements have been fixed to work in the UXP builds released by Roy yesterday ; but sites/Google will always be several steps ahead UXP wrt Web Compatibility ; currently, several of "my" sites are broken due to "??=" (nullish coalescing assignment) ... Regards

... I assume that was a stub/on-line installer, run on your Win8.1 setup, was it not? If that same installer is run under Win10+, it'll fetch the latest stable Chrome release, either v110.0.5481.177 or v111.0.5563.50 at this time... What will be fetched under Win7SP1 if that same installer is run? Probably just v109.0.5414.119/.120 (can't test right now) ... So, I guess, one has to first gain access to a Win8.1 box to grab the v109 security updates, to then install them under Win7SP1... Hopefully, the updated links will be made public to the Win7 communities, as they become available to 8.1/2012R2 users... BTW, one should better archive those v109 installers, because it's widely known Google will remove the builds from their servers , in due course, for being "insecure" ...

good job mina! (does this mean chrome is still usable on 7?)

Can you please provide/explain the method you employed to obtain those links? How is one on Win7 supposed to get access to similar links until Oct 2023?

There is also a direct download link to the new version that Google has released. Can you test if the links below works and installs? Chrome 109.0.5414.129 64 bit: https://www.google.com/dl/release2/chrome/juzaykgd5e6nyvk27fwtbrjgoa_109.0.5414.129/109.0.5414.129_chrome_installer.exe Chrome 109.0.5414.129 32 bit: https://www.google.com/dl/release2/chrome/kr3ekrngooyu46qwruasnjsjey_109.0.5414.129/109.0.5414.129_chrome_installer.exe

Unfortunately, on Windows 7, it didn't update. It stayed at 109.0.5414.120.

New build of BOC/UXP for XP! Test binary: MailNews Win32 https://o.rthost.win/boc-uxp/mailnews.win32-20230304-485bba73-uxp-33981efb4-xpmod.7z BNavigator Win32 https://o.rthost.win/boc-uxp/bnavigator.win32-20230304-485bba73-uxp-33981efb4-xpmod.7z source repo (excluding UXP): https://github.com/roytam1/boc-uxp/tree/custom * Notice: the profile prefix (i.e. parent folder names) are also changed since 2020-08-15 build, you may rename their names before using new binaries when updating from builds before 2020-08-15. -- New build of HBL-UXP for XP! Test binary: IceDove-UXP(mail) https://o.rthost.win/hbl-uxp/icedove.win32-20230304-id-656ea98-uxp-33981efb4-xpmod.7z IceApe-UXP(suite) https://o.rthost.win/hbl-uxp/iceape.win32-20230304-id-656ea98-ia-93af9a0-uxp-33981efb4-xpmod.7z source repo (excluding UXP): https://github.com/roytam1/icedove-uxp/tree/winbuild https://github.com/roytam1/iceape-uxp/tree/winbuild for UXP changes please see above.

New build of Serpent/UXP for XP! Test binary: Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20230304-3219d2d-uxp-33981efb4-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk52-g4.8.win64-git-20230304-3219d2d-uxp-33981efb4-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.8.win32-git-20230304-3219d2d-uxp-33981efb4-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.6a1.win32-git-20230304-d849524bd-uxp-33981efb4-xpmod.7z Win32 IA32 https://o.rthost.win/palemoon/palemoon-28.10.6a1.win32-git-20230304-d849524bd-uxp-33981efb4-xpmod-ia32.7z Win32 SSE https://o.rthost.win/palemoon/palemoon-28.10.6a1.win32-git-20230304-d849524bd-uxp-33981efb4-xpmod-sse.7z Win64 https://o.rthost.win/palemoon/palemoon-28.10.6a1.win64-git-20230304-d849524bd-uxp-33981efb4-xpmod.7z Official UXP changes picked since my last build: - Issue #2117 - Part 1 - Update Mac DMG platform names to intel64 for Intel and arm64 for Apple Silicon. (8bacb52ca) - Issue #2117 - Part 2 - Revert "Follow up to d0eee8f01 - Run precomplete cmd during package staging" (cbc529bb0) - Issue #1382 - Part 1: Remove assertion that GetPreEffectsVisualOverflowRect is called only by frames whose parent is an anonymous block (691afc8c8) - Issue #1382 - Part 2: Add crash test (ebe27baa2) - Issue #1593 - Follow-up: Fix :host selector matching (edc45f684) - Issue #1344 - (Parser: Java) Don't reset containsHyphen value after finding one (d9b7057ff) - Issue #1344 - (Parser: C++) Don't reset containsHyphen value after finding one (55100bb28) - Issue #2118 - Part 1: Update gfxUtils YuvColorMatrix functions to match upstream mozilla code more closely. (beef43760) - Issue #2118 - Part 2: Add support for Identity YUVColorSpace (3e62b1fc9) - Issue #2101 - Part 1: Add mColorRange info to YCbCrBuffer (c0c76cd45) - Issue #2101 - Part 2: Use stdint.h types instead of uint8 and friends (42f329689) - Issue #2101 - Part 3: Update libyuv (a4d1f57b9) - Issue #2101 - Part 4: Add color range support to gfx/ycbcr (b5f9e9abb) - Issue #2101 - Part 5: Add ColorRange support to video decoders (e59e8c3b2) - Issue #2101 - Part 6: Plumbing of ColorRange between video decoders and YUV convert (2b88f2c9a) - Issue #2101 - Part 7: Add color range support on GPUs (687733f9d) - Merge remote-tracking branch 'origin/tracking' into custom (7c0ddca06) - Issue #1375 - Follow-up: Remove shadow tree hacks in the frame constructor (6a26ce345) - Issue #1375 - Follow-up: Get the insertion point right when reconstructing direct children of a shadow root (b40c87a59) - Issue #1361 - Enable WebComponents by default in the platform. (9b2520249) - No Issue - Enable MSE for WebM on all platforms. (87b94f83c) - No Issue - Remove speech recognition pref and enable TTS API by default. (2d7d00b75) - Issue #1375 - Part 1: Allow moving a reference into nsInterfaceHashtable (53e2e5d8d) - Issue #1375 - Part 2: customElements.define must upgrade custom element in shadow-including tree order (6781f5b6c) - Issue #1361 - Enable WebComponents' getRootNode by default. (52dbe9733) Official Pale-Moon changes picked since my last build: - [Basilisk] SSUAO - Use native mode for Zoho (cf80fbdb7) - [Basilisk] SSUAO - Add pale moon addons slice (b7aac7342) - [Basilisk] Bundle fonts on GTK platforms, not just Linux (42c8c7ff1) - [Basilisk] Remove dailymotion override (3c54aa7eb) - [Basilisk] Fade out tab label on overflow instead of ellipsis (89dd425fd) Official Basilisk changes picked since my last build: - [Pale-Moon] Issue #1908 - Fade tab titles instead of using ellipses (21f0c3de6) - [Pale-Moon] Remove DailyMotion override (apparently no longer needed) (021d76f3a) - [Pale-Moon] Update SSUAOs for known sites no longer needing workarounds. (889dfd882) Update Notice: - You may delete file named icudt58l.dat inside program folder when updating from old releases. * Notice: From now on, UXP rev will point to `custom` branch of my UXP repo instead of MCP UXP repo, while "official UXP changes" shows only `tracking` branch changes.

I just listed the final versions of Vivaldi, Ungoogled Chromium and Brave that are compatible with Windows 7: https://old.reddit.com/r/windows7/comments/113sf82/final_version_of_vivaldi_browser_for_windows_7/ Basically, Chromium v109 is the last with support for Windows 7 and 8.1, v110 and higher are incompatible. To mirror the information here: Ungoogled Chromium final version for Windows 7: Sourced from chromium.woolyss.com amd64 (64-bit) v109.0.5414.75-r1070088 (Google sync, 11 Jan 2023) [Hibbiki • up-to-date • sync • widevine • all-codecs+ • win64 • Portable • Archive • Installer • Package] v109.0.5414.120-r1070088 (Ungoogled, 25 Jan 2023) [Marmaduke • up-to-date • ungoogled • widevine • all-codecs+ • win64 • Portable • Archive • Installer] x86 (32-bit): 109.0.5414.120 (1070088) (Google sync, 25 Jan 2023) [Hibbiki • sync • widevine • all-codecs+ • win32 • Portable • Archive • Installer • Package] Brave browser final version for Windows 7: Boy, their GitHub releases are a @&%!! mess, and their announcement of Win7/8.1 deprecation doesn't even list the final versions for those operating systems, as has been polite practice for many years (see: all those websites that list "Final version for WinXP"). What an incompetent company. Why is Win7 such a pariah? M$ must have paid someone big bucks. [Brave Stable Release v1.47.186 (Chromium 109.0.5414.119)] (the last Stable Release "with Chromium 109" are iOS only: [Brave Stable Release v1.47.189 (Chromium 109.0.5414.119)] or Android only: [Brave Stable Release v1.47.188 (Chromium 109.0.5414.119)] [Brave Dev v1.48.150 (Chromium 109.0.5414.119)] [Brave Beta v1.48.152 (Chromium 109.0.5414.119)] [Brave Nightly v1.49.62 (Chromium 109.0.5414.119)] (the last version with Chromium 109, [Brave Nightly v1.49.63 (Chromium 109.0.5414.119)], does not have Windows builds) Vivaldi browser final version for Win7 Support deprecation announcement Final snapshot supporting Win7: 10 Jan 2023, v5.7.2901.3 (based off Chromium v108) https://forum.vivaldi.net/topic/82732/happy-new-year-vivaldi-browser-snapshot-2901-3 https://vivaldi.com/blog/desktop/happy-new-year-vivaldi-browser-snapshot-2901-3/ Final stable version supporting Win7: Vivaldi v5.6.2867.62 (based off Chromium v108) https://downloads.vivaldi.com/stable/Vivaldi.5.6.2867.62.x64.exe https://downloads.vivaldi.com/stable/Vivaldi.5.6.2867.62.exe Edgium (Microsoft Edge Chromium) browser final version for Win7 Edgium Offline Installers are available here, but getting the exact final version for Win7 is difficult, as no-one has been keeping an archive. See here for the offline installer for Edgium-based Webview2 You'll also need a registry edit to remove an annoying "unsupported operating system" warning on Edgium and Google Chrome on the final supported versions (not needed for Ungoogled Chromium or Vivaldi) Electron Current version v22 still supports Win7. v23 (pre-release?) bumps Chromium to v110 (see this pull request and v23.1.0 release notes. According to this thread for VSCodium, around May 2023, Electron will stop accepting patches for v22 and will focus only on v23+, so everything built in Electron will slowly stop working on Win7 (just for an idea of timeframe, most Electron stuff still uses v19.x.x, e.g. Nativefier, VSCodium, etc.). As long as it uses Electron v22.x.x or under, it will still work. TODO: node.js Edgium Edge Webview2 Google Chrome Chromedriver/Selenium