I just broke my install while copying updated files in SysWOW64. The restore point that was previously working now has no effect. I'll just exploit this opportunity to migrate to Server 2012 R2 and install the 8.1 cursors and themes there.
Is "Version" and "Updated Versions" in About IE correct? After installing 2025-07 IE11 lcu on 8.1, IE's "Version" displays July's IE version number (correct), but "Updated Versions" displays June's version and KB article number (incorrect).
Yeah, it is like this, for some reason. All correct. It is exactly like that on my client Windows 7 as well.
It's so strange. I want to view a screenshot of About IE11 on Server 12r2, 08r2 and Win7 with 2025-07 Windows lcu installed.
Hi, I tested it only on the Client version, click on the post below that will lead you to the thread: Windows 8.1 Hotfix Repository. My two cents. Thank you. Further analysis: Indeed, Microsoft optimized the updates and meant them only for Windows Server 2012 R2. Caused because some of the new update components are only installed for Windows Server and skipped for the Client version, leading to all sorts of mismatches. I conducted further research and the behaviour appears to be intentional. To compare, I took a peak at the shell32 dll component. On the June 2025 KB5061018 update, that component is marked as applicable to both SKUs: Client (wow64 & amd64) and Server, with separate manifests for x86 and x64. On the July 2025 KB5062597 update, they combined the x86 and x64 manifests and made it applicable only to the Server SKU. My two cents. Thank you.
I'll send them shortly. I have both Client Win7 and Srv2012R2 installed, and will be making an updated ISO for the 2008 R2 version, as well as Vista both x86 and x64 (though the IE updates past 2020-01 on Vista x64 are Server exclusive and can only be installed in the live system using a script). This is my Italian Server 2012 R2 install. This is my Italian client Win7 install.
Hi, With Microsoft and products officially out of support, you can expect the unexpected. These legacy operating systems should be virtualized on protected environments, and migration to a new host operating system such as one of the Windows 10 LTSC versions is increasingly warranted. It's a bit technical, you can check the differences on the screenshots of the MUM files I attached to my previous post. My two cents. Thank you.
This is not new to me, with that question I meant: what made you think it was intentional and not a mistake from Microsoft's part? Do you have any source for it? If it happens I'll just do the same thing I did on my laptop, i.e. installing 2008 R2 and using it as if it were 7. I use these OSes just because I want them. I have a PC running Win10 22H2 + Win11 Canary, another one with Server 2025, then the 2012R2 laptop also has Big Sur (it's a hackintosh), and another HP laptop runs macOS 13 Ventura and 26 Tahoe.
Hi, To address the question, I think that the intentional blocking of the July 2025 update (KB5062597) for Windows 8.1 is a deliberate design decision by Microsoft, rather than a mistake. I reached this conclusion by analyzing the differences in the update manifests, which showed changes in applicability and architecture support between the June and July 2025 updates. As for a source, there isn't a direct quote or reference provided. My analysis and insights are based on my own research and testing, as well as information shared by other members in the discussions. I infer that Microsoft has intentionally limited the Windows 8 (8.0 & 8.1) July 2025 updates to Server SKUs, but didn't find a direct source or confirmation from Microsoft. My two cents. Thank you.
It is possible that they just did it to reduce their loss of money caused by client users on 8.1 installing these updates, but what is strange is that Vista and 7 (client) still work. I guess, if next month's updates will work on client builds of 7 and Vista, they aren't going to make the change, especially this late into the support period, but as you previously said, we can expect the unexpected.
It seems like Windows versions go on in couples when talking about ESU development. The browser issue on 2024-11 updates affected Vista and 7 (and corresponding Server versions). I skipped that update on both. The 2025-07 update breakage affects 8.0 and 8.1. 2008 R1 and R2 (Vista and 7) will lose support together on 2026-01-13. 2012 R1 and R2 (8 and 8.1) will lose support together on 2026-10-13 (I know that client Windows 8 and 8.1 are unsupported in this current state).
I should have checked here first but I had already downloaded the 07-25 roll-up and installed it offline...bricked my 8.1 64 bit machine. Any way to get this thing to boot again? Auto repair, restore, none of that works.