mina7601

Hey @msfntor, I hope you didn't take my above post as offending to you! If it looks offending, I am sorry.

Sorry for being off-topic, but glad to see you back, FranceBB. I am sorry you had tough time, though. I hope all is well with you.

Try this fix by @AstroSkipper:

Ask the author him/herself of the ISOs about it. Discussions/Help with modified Windows ISOs here is prohibited.

You can install Windows 11 on unsupported hardware, by using this method from @GD 2W10:

Yeah, good luck with that.

I won't get lost. It doesn't distract me.

@msfntor You misunderstood my reply to @UCyborg, but I still love your response, however, my reply isn't about the year I will stop using Chrome or Windows (XP or Vista or 7, or my main OS, 11), my reply is about my assumption of the year of when I would start getting missing APIs errors when opening Chrome on Win11 (the "Entry Point Not Found" errors) But then, yeah, since you said it, I will also never abandon Chrome and Windows XP and 7.

Yeah, but I mean, they might not have enough time for reading posts/partaking, as they could be busy with other stuff. That's what I meant.

Sorry, I misunderstood because he said "I had to install them from scratch as already embedded in ISO file", which made me think the ISO didn't have extended kernel integrated.

It was an assumption though, I assumed that by 2031, MS will have dropped Win11 support, and that Google would support Chrome on Win11 for 3 more years (like with Win7, which had a large market share).

You mean which version of extended kernel is installed? It depends on the vistaexkernsetup_xxxxxxxx.7z (where x is the version in the date format), for example, if it is 10262021, the extended kernel version you installed is October 26, 2021. Yes, you can upgrade old version to current version. Just run setup of the latest extended kernel version, and then follow the instructions on Command Prompt.

As a Win11 user, it will assumingly take until 2033 or 2034 for me.

@verta You wrote that Legacy Update 1.4.1 crashes for you when you open the setup installer. Can you test version 1.5 as well, and see if the crash persists there?

Studies are my priority, remember? I do get free time, but it's not too much, so it isn't enough for me to check xpforums.com.

Yes, I am. Yeah, I don't have so much time for xpforums.com anyways, only MSFN and Eclipse.

You're welcome! I am fine, and yes, my studies are going well. No, also, my apologies, I don't look at xpforums.com so often, only this forum and https://board.eclipse.cx/.

I hope it passes for you again.

Yes, Legacy Update includes Vista in the supported OSes, which means it can get updates with Legacy Update as well.

@AstroSkipper Hello, there's a new version of Legacy Update available: version 1.5! Includes this fix: "Fixes crash on launch when opening Legacy Update setup on Windows XP SP3.". And also has a new improvement: "While updating root certificates, Legacy Update will now also enable the TLS v1.1 and v1.2 protocols, which are present but disabled by default in Windows 7, 8, and 8.1, as well as in Windows XP with a POSReady 2009 update. This is an additional fix for websites not loading in Internet Explorer and other apps that use the Windows built-in networking functionality.". Available in https://legacyupdate.net/ and https://github.com/kirb/LegacyUpdate/releases

Wow, it's beautiful!

I respect your opinion, and you stand a point about that, but the reason I think it's sad is because when people migrate to another OS (Linux, for example) from Windows completely, they might lose some knowledge and information about Windows.

I was just replying to @AstroSkipper, I wasn't talking about BSOD.

No, that's how the Ignore feature works in the forum: When you add a specific user to your Ignore list, you have the options to block either some or all of that user's contents from showing. (It even says so in the link @Tommy sent!) Ignore feature was never built to prevent a specific user from replying to your posts.

I don't think that's really an issue/a reason of why BSODs are to be expected when using 360Chrome.