Vistapocalypse

Good question. I haven’t investigated this in well over a year, but was once able to figure it out after looking at VistaLover’s screenshot in this post. Polymer v2 also has fewer thumbnails per line, probably with mobile users in mind.

There is no need for that: Chromium 57 does not support Vista either, but Yandex 17.4.1 is a Chromium 57 fork that supports both XP and Vista, i.e. a backport like 360. Anyway, I hope that ArcticFoxie will not be dismissive about any YouTube issues that might be reported here.

I’m sure it works fine with YouTube’s Polymer v1, but if you changed your user agent in order to be served Polymer v2, I believe it would be most unsatisfactory. As I stated above, “Whenever Google deprecates Polymer v1” (which they obviously haven’t done yet), Chromium 49-based and Firefox 52-based browsers (including UXP browsers) will not be able to display YouTube’s homepage. I first learned about this in VistaLover’s February 26, 2020 post (near the bottom of it) and subsequent discussion in that now-dormant thread. I was sufficiently concerned that I actually tried Yandex 17.4.1 on Vista (reluctantly, since it is Russian), and confirmed that this Chromium 57 backport is served Polymer v2 by default. I assume that the same is true for 360 and other Chinese backports (except “Advanced Chrome,” which is known to not work so well with YouTube).

Pardon my intrusion, but YouTube is one of the most popular websites, and their Polymer v2 layout is incompatible with Chromium 49-based and Firefox 52-based browsers. Whenever Google deprecates Polymer v1, YouTube users running XP or vanilla Vista are going to want a good browser for YouTube. If not Extreme Explorer 360 or one of the other Chinese backports, that only leaves Yandex 17.4.1. IF I ever use the browser being discussed in this thread, it would only be my “different browser for YouTube” because 99.9% of websites work fine in Firefox 52-based browsers.

No surprise that the game works on Windows 7 because system requirements say that it should, but do not mention Vista. If that is the same NVIDIA driver version that you were using on Vista, then it is puzzling that the error you posted yesterday said “no appropriate graphics hardware acceleration is available.” If you find a solution, I’m sure you will let us know.

I’m not a gamer, but the driver for the 8600 GT may not support hardware acceleration (although an older driver might).

Thanks for the information @MrMADRYAN! So this thread’s original post is correct about MSE 4.10 functioning normally on 2008 SP2. Of course for Vista, the problem is not installation but rather the April 2017 time bomb that was included in all versions after 4.4. Were it not for that, I’m sure that definitions could be installed with the necessary SHA-2 support. Microsoft has said that definitions will be updated until 2023.

Nothing shocking about that. The last Windows Server that was available in 32 bit was 2008 SP2. In the last six years I’ve never once encountered a Windows 10 32-bit system, or for that matter a Windows 8.1 32-bit system. Is there really still demand for that?

Thanks for that. KB4041778 was also on burd’s list, but @VistaLover may find it puzzling that you were not given the somewhat earlier KB4040973. KB4532932 was simply the final January 2020 (EOL for Server 2008) update, which has probably been superseded by ESU updates. Edit: And yes, having Office installed definitely slowed down the initial check for Microsoft updates on Vista, but did not prevent eventual completion.

The mad scientists at Microsoft must be aware that Cobalt has been a component of doomsday devices in such classics as On the Beach, Dr. Strangelove, Goldfinger and Beneath the Planet of the Apes.

Was Microsoft update selected rather than Windows only, and was .NET 4.6.0 manually installed first? (It wouldn’t deliver updates for 4.6.1 because that version did not officially support 2008 SP2 or Vista.)

Office 2010 was supported for six months longer than expected, but the miracle reportedly ended after April of this year. @Dave-H monitored that situation in a thread in the Windows XP forum: https://msfn.org/board/topic/177946-beware-of-office-2010-updates/?do=findComment&comment=1199509

There has obviously been some sort of drama at Eclipse, so perhaps win32 will return to MSFN, or at least let us know where the future of the extended kernel now lies.

I can confirm that flags are visible now, so perhaps something good came out of MSFN’s 5-day outage.

Does Windows Update now seem to search endlessly for more updates? If so, then this is an old familiar issue that has existed since Windows 10 was released nearly six years ago (and I never thought the timing was just a coincidence). It sounds like you prefer written explanations, and I last wrote about how to solve this on April 29. My Vista x86 was already updated before M$ cut off Windows updates for Vista and earlier last year, but I did take the time to watch the video that i430VX first mentioned February 28 and it does mention the need to manually install the four well-known updates to get Windows Update working for Vista SP2. It is not necessary to manually install IE9 - but if you have already done so, then it is advisable (but not essential) to install a relatively recent update for it to simplify the search for the approximately 200 remaining Windows updates, which might still take a few hours even with all the recommended patches installed. On the other hand, if Windows Update is throwing an error code such as 0x80072EFE in short order, then you would be wasting your time to attempt anything mentioned above.

Thanks for pointing that out. It sounds like final definitions were on May 19: https://knowledge.broadcom.com/external/article/164751/end-of-support-life-for-endpoint-protect.html

It sounds like Logitech isn’t very good at ending support for old Windows versions!? Is installation of 2021.5 blocked on Windows 7? (Maybe they just forgot about Vista?) Keep an eye out for any issues with that version. People will want to know the last usable version and you seem to be MSFN’s leading authority on G HUB.

I wonder if this Chinese company will be able to circumvent the SSE3 requirement introduced with Chrome 89? If not, then support for a majority of XP hardware (and possibly for XP itself) might be reaching its extreme.

I believe Dixel did exactly that with much earlier versions of the extended kernel. Maybe look for his posts way back in this thread for information. If you don’t mind using Chrome or Opera for watching h264 videos, then I believe you could dispense with mfplatsetup if I’m not mistaken.

Yes, see this January 25 post, but only the x86 WMP is affected. (I wonder if any third-party media software is also affected.) But if you want to watch videos using a Firefox version that requires Windows 7, then the Media Foundation files are necessary.

Slightly OT, but can you confirm that version worked on Windows 7 as well as on Vista with extended kernel? I’ve seen reports of difficulties involving 7, although it apparently worked on 8.1. Logitech Support continues to point Windows 7 and 8 users toward version 2021.3.5164, but @Jaguarek62 posted April 15 that it did not work on Windows 7? (I assume that the latest 2021.5.9841 released on May 27 only works on Windows 10.)

Vista creates automatic restore points. If you disabled that, I think your issue would go away.

Of course software that officially supports Vista should not require a .NET version higher than 4.6. Higher versions should be installed only to investigate whether software that officially requires Windows 7 might unofficially work on Vista, but only a small number of success stories are known. I am now convinced that installing .NET 4.8 will break more software than it enables, and suspect that the same is true of 4.7. If @Nandor (or anyone else) is actually running Server 2008, there is something I am very curious about: This thread’s original post states that Microsoft Security Essentials 4.10.209.0 “continues to function normally on Windows Server 2008...” Is that still true? I don’t seem to recall any mention of MSE on Server 2008 since March 2017 when it was shown not to be nagging. I tried to ask @Werewolf about it in December 2019, but he has been inactive since then. MSE did not officially support servers, and I once read somewhere that special installation procedures were necessary.

...or a 4.6.2 installation. (See WinClient5270’s May 16, 2019 post, which also established that 4.6.2 is less likely than 4.8 to cause missing dependency errors on Vista.)

It should still work at YouTube, but I hope you have better luck with your new browser.