yoltboy01
Content Type
Profiles
Forums
Events
Posts posted by yoltboy01
-
-
An Opera-developer made an announcement regarding the EOL of Windows 7/8.1.
Quote:
Hey, we are aware that Chrome is dropping support for Windows 7 and 8 but we wanted to keeping those platforms updated as long as it wouldn't require lot of additional maintenance from our side. We will look into this as it didn't show up on our earlier tests before release.
For now we logged some GPU related crash on Windows 8 which is logged under DNA-104227
So, what they basically say is that even tho Chromium based browsers, like Edge and Chrome, dropped support for them, they will continue to port back newer Opera versions to Windows 7/8/8.1, as long as it doesn‘t reach a point, where they would have to put too much effort into it
0 -
Tried it out and it works on Chromium
10 hours ago, UCyborg said:See if --disable-windows10-custom-titlebar changes it.
0 -
9 hours ago, UCyborg said:
See if --disable-windows10-custom-titlebar changes it.
I'll give it a try. Does it work on Spotify?
0 -
10 hours ago, D.Draker said:
Perhaps you all still have some hope, I ported chinese browser Opra 96 (Chrome 110) to Vista.
https://msfn.org/board/topic/184249-chrome-110-based-opera-i-ported-it-to-vista/
Great work!
0 -
1 hour ago, win32 said:
It would be the latter, just like how they tried to remove Aero Glass from Chromium on Vista. Everything going forward is to target Windows 10.
Honestly if they want to break it properly on Windows 8.x, they just have to move some of the DPI functions from being delay-loaded to the main import table.
Yeah I remember. I think they basically ignore Windows 8, since they didn't break compatibility. Right now the --no-sandbox method still works but they could introduce Windows 10+ dll's anytime
0 -
2 hours ago, Jaguarek62 said:
How does it look like?
imgur.com/UlGhgwC
2 -
The current version of Chromium 111 now shows the title bar of Windows 10 on Windows 8.1, just like other apps (e.g. Spotify).
Could be an indicator that compatibility with 8.1 will also be broken in near future (hopefully not too near) or, as I said earlier, that they really dont care about Windows 8 (possible scenario)
0 -
33 minutes ago, FantasyAcquiesce said:
Paintnet 5.0+ no longer supports Windows 7 or 8
https://forums.getpaint.net/topic/120669-paintnet-4312-is-now-available/
Man, this really stinks especially as one who uses 8.1 on low-end devices. Windows 8.1 support is not even officially over yet and vendors are dropping it along with 7 just as they did with Vista/XP...
Yeah that was already a very possible scenario years ago, since Windows 8 and 8.1 usage isn‘t as high as Windows 7. That‘s also the reason why they don‘t offer ESU for 8.1 devices. However, 8.1 is closer to 10 than 7, which makes some things easier to backport to 8.1 than to 7, just like it was the case with XP and Vista. Vista is obviously way more identical to 7 than XP, which made some things much easier
2 -
I think it was quite possible to get 2020 versions of Office 365 working on Windows 7, but those newer versions won‘t run on it (dll/api missing)
0 -
Ironically, to what was mentioned by Google and other users, Chromium has dropped support for Windows 7 and also updated their website, removing Windows 7 from their System Requirements list - BUT - left Windows 8 standing on that list. They also added Windows 11 now, so I‘m curious about why they didn‘t remove 8.
They definitely acknowledged the —no-sandbox hack but maybe they don‘t care so much, until they really add api’s and dll‘s that will break compatibility with 8 too.
0 -
I just saw that Office v2301 is the last one for Windows 8.1
The Office Insider Button is grayed out just like in Windows 7, with the same nag message
0 -
As of now, the freshly released first Chromium 111 Build seems to work on Windows 8.1 with the —no-sandbox hack as well.
0 -
I would love to see a backport of some Windows 10 Apps for Windows 8.1, but even that will surely not happen (anytime soon). On Windows 8.1 even Netflix and Deezer won't work anymore, since they use IE11 to connect to their servers. If there was only a solution to switch it to Edge like Windows 10..
0 -
On 12/7/2022 at 7:42 PM, legacyfan said:
with the extended esu updates ending soon and no extension being made will windows 7 still be usable beyond 2023? with as much as ive seen drivers slowly disappear from compatibility and all the windows 10-11 nag screens I just don't know so my question is will it still be usable in 2023-beyond? (part of the state of windows project)
Sure you can. There are people, who still use Windows XP and Vista.
First, I want to clarify that people come here, in order to help reviving these older operating systems. It‘s in no ones interest to treat them like „abandoned ware“ here. There are masterminds like @win32, who put so much effort into developing Kernels for older systems, so that we can run our favorite OS, no matter how old it is, nowadays. In my opinion, people who do nothing but repeat what the richy rich companies like M$ or Google say and oppositely try to make everyone not use those OS, have nothing to do here. No logic input, only helpless statements. If we wanted to hear „give up, move to Windows 10 everyone“, we wouldn‘t come here!
There are tough times waiting for us now. As far as I know, Chrome 109 is really the last one for Windows 7 and no methods exist to run newer ones. I am not using Windows 7, but 8.1, which can indeed run Chrome 110. It took @win32 also a lot of effort to develop an Extended Kernel for Windows Vista, which made us run newer Chrome versions on it. You have to wait for an extended Kernel for Windows 7 as well and until then, I would simply use Firefox (or Chrome till February 2023). As far as Security Updates, you already mentioned PosReady 76 -
5 hours ago, D.Draker said:
The advice to use --no-sandbox hack may lead to furious whining from "security oriented" users,
not wanting to call them security freaks, so just leave it put very politely put, like I did.
The 110 Chrome asks for GetProcessMitigationPolicy (which is win 10 and up only).
So this is absolutely official - no more Chrome for 7/8/8.1.
Not to mention a gazillion of games that do not start on 7/8/8.1
@Tripredacus, @Dave-H , would be wise to finally retire these OSes from the main section, no ?
Doesn‘t apply to Windows 8.1. Chromium AND Chrome 110 work fine - updating it daily and I‘m definitely not crying over the no-sandbox hack. Happily taking those intense risks you mentioned.
Why should they be removed from the Main section on MSFN? I don‘t think that‘s in anyones interest. Most of the users come here for Windows 7 and 8.1. At least this community here doesn‘t treat them like Legacy, vintage Products. Unnecessary idea
2 -
Although I don‘t think that Microsoft will extend the ESU Program for Windows 7 or make one for Windows 8.1, you could bypass ESU (not explaining how) and install PosReady 7 Updates on Windows 7 till October 2024 (similar to XP and PosReady 2009) and Server 2012 R2 ESU Updates on Windows 8.1 till October 2026. Due to legal reasons I‘m not recommending this, only mentioning its existence.
EVEN Windows Vista AND Internet Explorer 9 (which many forget) can still receive Updates till 01/2023, by installing Server 2008 SP2 ESU on it. However, as my predecessor already said: Does Internet Explorer 9 even count as a liable browser in 2022? It can‘t even load basic websites now, so that extending it with further Security Updates was kind of unnecessary.
1 -
On 11/26/2022 at 12:13 PM, D.Draker said:
They actually might, they read MSFN. I know.
Well who knows?
I have a bad gut feeling. This whole situation reminds me of when Windows XP and Vista were discontinued by Google. While Chrome 49 was really the last one to work on XP, v50 could still be installed and ran on Vista, without any issues. If I am not wrong, you could also install Chrome 51, but that's when they slowly started to also break compatibility with Vista. Chrome 52 would no longer install on Vista and gave the typcial errors, when you tried to launch new Chrome versions on Vanilla Vista.
I mean they could also break compatibility with Windows 8.1 at any time right now, but I think it will definitly not be with newer builds of v110 or 111. They are now free to introduce dll's from Windows 10+ at any time.
The only questions is how other browsers will react to this:
Logically, other Chromium based browsers must also stop supporting Windows 7 and 8.1 after they move on from Chromium v109 to 110, but there are some browsers, like Maxthon, who are based on new Chromium versions, but can be run on older systems. I think Maxthon 5.x was on Chromium version 7x/8x and still supported Windows XP and Vista, whereas the last Yandex Version for Windows Vista was v17.4.1.1026, which was based on Chromium 57 or Slimjet 12.0.15, which was based on Chromium 53. I really have no clue how they managed to make these Chromium versions run on those older systems (no judgement pls), but theoretically those companies could also support Windows 7 and 8.1 for longer if they wanted or?
Curious to know what you guys think. I was just wondering, after I scrolled through the list of Last Versions of Software for Windows Vista and saw some entries that surprised me
2 -
23 hours ago, Old Technology said:
Are you saying Chrome 109 won’t work on a Windows 7 install as well?
No, 109 is the last one that works on Windows 7. They introduced dll‘s that are only available in Windows 8+, but they also broke compatibility with Windows 8. If you try installing Chromium on Win8/8.1, the browser will start and then immediately close again. However, using —no-sandbox allows you to run the latest Chromium (110.5441) on Windows 8.1. I hope they will not break that one too.
4 -
17 hours ago, win32 said:
Now we are on 110.0.5425.0, and it will no longer launch on a regular Windows 7 install. Three functions needed so far:
SetThreadInformation
SetProcessMitigationPolicy
GetProcessMitigationPolicy
These are all wrappers to older ntdll functions, so they should be easy to add, to some extent. If not, this new code is all in the sandbox anyway.
Thanks for checking it win32. You already gave your best with Vista's extended kernel (for which I'm still grateful till this day) and I hope that you will be able to make Chrome run again on Windows 7 after it's final release. Let's also hope that they won't make it harder for Windows 7. Would these functions be easy to add on Vista's extended kernel as well or would you say that we might have to say goodbye to Chrome on Vista, until you manage to add them there too?
0 -
I will basically ignore that this topic was pulled into another topic throughout this long conversation and will now come back to the origins of why I created it:
I just updated Chromium on my Windows 8.1 Laptop and v110 seems to work fine, although the last official version for 7/8.1 will be v109. I have no clue, if the mini-installer will still install that version on Windows 7/8.1, but I just unpacked the latest chromium-zip package and ran it. This could and will possibly change in the future. If I think back to Windows Vista, Chrome 50 could still be installed manually, without any issues and Chromium went up till v51, without any errors. So, we might be able to run v110 and some newer ones unofficially, before they break the support completely, by adding W10/11 specific Api‘s into the game.
[Off topic: I tried installing the latest HP Easy Start for configuring my printer and HP no longer supports 7/8.1 either. However, after unpacking the installer and running it manually, it worked. No dll/api issues. So, some programs seem to not break compatibility in their core, they just show off a warn message. Let‘s hope for some other programs to be like that in the future]
1 -
I‘m sorry guys but I‘m very confused right now. This topic was intended for the future of Chrome on Windows 7 and possibilities of running newer versions soon but I quite don‘t get what you are discussing here right now. It has nothing to do with the upcoming EOL
2 -
Strangely, the nag message on Chrome Dev/Chromium 109 disappeared on Windows 8.1. Three days ago it started showing the same EOL message of XP/Vista for Windows 7/8.1 but today it was gone. I even reinstalled both browsers on Test machines and it showed nothing. The about:chrome Tab also says Up to Date and no warning message at all. Curious if this is a bug or intentionally
0 -
5 hours ago, Sampei.Nihira said:
Hmm.. no surprise but moving Windows 7/8.1 to 102 ESR now is not a good idea in my opinion. They already run a newer version now and that would kinda be a downgrade now. Mozilla should definitly extend support till 114 ESR, so that Firefox remains supported till August-October 2024. It's highly unusual that they drop support on a regular release. It's either gonna be 102 ESR (which I highly doubt) or 114 ESR.
So sad that they don't let any door open for Windows 7 and 8.1 users. Mozilla already has a low market share and they will loose about 15% more, if they discontinue support for 7/8.1. They should re-consider and wait till there are less than 5% left. They always want to keep up with Google, but this time I don't think they should.
So 2023 is going to be a tough year for Windows versions lower than 10. Here is a quick summary:
Google Chrome: EOL February 2023
Opera: EOL February 2023
Edge: EOL February 2023
Vivaldi: EOL February 2023
Brave: EOL February 2023
Firefox: EOL August 2023/August 2024
1 -
I‘m very curious what they will do to break compatibility with Windows 7 and 8.1.
As I previously said in another post, I think that Mozilla will be more graceful when it comes to ending them. They ended support for XP/Vista 10 months after Google did and then pushed out security updates for another year. If v115 will be the next ESR in July, we will continue to receive Security Updates for at least another year. ESR is usually also supported for more than just 12 months (v78 had 16 months). Applying the same stats to Windows 7 would mean that Firefox should at least be supported till July - October 2024, which is still 2 years ahead.
They could also support them for a longer period of time, because Mozilla already has a low usage rate compared to Chrome, so they may be not interested in loosing more users. However, that‘s just a dream scenario, they already limited some things to Windows 10 and 11 only like Firefox VPN
0
List of software that doesn't support Windows 7
in Windows 7
Posted
Yeah I tried v96 on 8.1 and it immediately crashes. With that sandbox hack it opens, gives an error and closes again