Hi, @abbodi1406 Would it be possible to create a similar patch for KB5058529 servicing stack, to allow installing modified MUMs from https://forums.mydigitallife.net/posts/1884766 online? I've seen your post for Windows 10 (1507/1511) at: My two cents. Thank you.
Or just copy the files lol It's a huge load of work either way you do it. Using the MUM method makes you lose Bluetooth. The file copy method should leave all client-exclusive functionality intact.
A system updated by file copy, I guess, will survive SFC, 'cause WinSxS gets replaced. It will maybe not survive DISM /RestoreHealth option, since it will believe the system is still on the June patch; running DISM /RestoreHealth then SFC will bring it back to June patch.
On one of my Client test systems, I also noticed some overall slowdowns after I had installed the 2025-05 Monthly Rollup (and later 2025-06 it seemed the same). Do you know what could be causing this ? At first I thought it might just be psychological but if I'm not the only one noticing it...
Hi, I remember reading on Microsoft's 2025-07 article, on the same day right after the publishing of the Patch Tuesday, that there were performance regressions in 2025-05 and 2025-06 fixed with July's update for Windows Server 2012 R2. That information has since been withdrawn from the article. They are hiding stuff from us. With 2025-05, I had an SSD crash mid-June where it became undetected when resuming from hibernation, really strange. I needed to force shutdown and cold boot, chkdsk, etc... Since then, I stopped hibernating the system. I have recently updated to 2025-06 on my production system. I still do not risk hibernating. It's probably a 1 in 10 scenario. I have "Fast Startup" disabled: https://forums.mydigitallife.net/posts/1881868 My two cents. Thank you.
Me as well. In the period of time right before I switched my laptop to 2012 R2 (for convenience), it was unexpectedly slow. I remembered Win8.1 being even faster than other Windows OSes. 2012 R2 has 12sec boot time with no Fast Startup.
Based on this info, if we are setting up a fresh install of client 8.1, should we only update to 2025-4 to avoid slower performance? Were there any critical vulnerabilities patched in 2025-5 and 2025-6?
Good god, the Monthly Rollups in 2025 have been such a mess for NT6.3. (At least those still officially compatible with W8.1 Client) The 2025-01 one was also not usable due to problems with USB and Digital/Analog converters (which got fixed in 2025-02 thankfully) On my personal rig I'm still using MR 2024-12 and IE CU 2025-04 because it is 100% stable for now.
IMO, we should make some kind of program/script that downloads the update, extracts what is updated, then reboots to WinRE, copies the files, updates the UBR and then you reboot and bam, the OS is updated.
another idea how fix this problem is updated succesfuly one year all relased patches and compresion the iso file install.wim and public the download updated version and 2026 2027 one iso 2028 one iso 2029 ended support last patched iso
He means issuing a ready-to-use patched ISO after each ESU year. Would conflict with our No-Homebrew rule, however.
I wonder. But how work Legacy Update + Bypass Esu Blue + reg ArcEsu ? Still need wsus proxy na Windows 8.1 for updates as server 2012 R2 ? Or WU work like in Server 2012 R2 (original)?
I made activate Massgrave, updated fully system, installed bypass esu blue and added arcesu reg and system (windows server 2012 R2) updated normally. Have actually September updates. And if Legacy Update is type WSUS and if can that replace that proxy from mdl to updates on Windows 8.1 as server 2012 R2.