I was just informing you. I know, no worries. It should work if you use a WSUS server different from Microsoft Update (so an independent one, not a Microsoft proxy). I also know it’s a SSU issue, as it works fine if you search using SSU KB5039341, but then breaks after installing KB5050682 or later. I know it’s gonna stay that way. The best course of action would be installing everything using SSU KB5039341 or older, except 2025 updates, using WU, then manually installing the newest SSU and what follows. Anyway it’s not gonna be a problem since support will end in 1 week from now. Windows Update works fine on x64 versions. Generally, I just run the WUC installer and then BypassESU since I use an already updated ISO.
So few hours divides divides us to last updates for Vista / Server 2008. Interesting what MS give as last gift.
KB5073697 has released for Server 2008. It removes agrsm64.sys, agrsm.sys, smserl64.sys, and smserial.sys. WDS was updated to prepare for removing support for hands-free deployment in insecure channels. Also, WinSqlite3.dll was updated with security fixes. Mediocre update, breaks some modem hardware and adds a security fix to sqlite. WDS can be undone with a registry fix for people actually running Server 2008.
Will the 2026-01 Security Monthly Rollup for Windows Server 2008 x86/x64 be successfully installed on Vista?
KB5073697 Security Monthly Quality Rollup was the only update released today for Windows Vista SP2 64-bit/Windows Server 2008 64-bit. There were no .NET Framework 4.6.2 or Internet Explorer 9.0 or Servicing Stack updates. No changes to the guide in the original post needed to be made. It has been a long and challenging endeavor, and my involvement in this thread has finally come to an end.
It also has x86 versions. But only Year1-6 ESU licensing files can be found in these two rollups' file information lists(.csv files), no Year7. Usually, M$ includes new Years' ESU licensing files in the Monthly Rollups about 3-6 months prior to the first new Years' ESU Monthly Rollup releases (for example, Year4-6 ESU licensing files are included the first time in 2022-07 Monthly Rollups, and Year1-3 ESU licensing files are included the first time in 2019-10 Monthly Rollups). So these two rollups are the last rollups for NT6.0/6.1. The final updates for NT6.0 x86/x64 & NT6.1 x64 are: SSU: 2025-11 IE: 2025-10 NetFX 2.0-4.8: 2025-10 ESU Preparation: 2022-08
We'll see if there's any out-of-band updates. I have a hunch that they'll give a final update in April to complete what they started with the phased disablement of hands-free deployment in Windows Deployment Services; wouldn't make sense to leave a warning in the Event Log for something that will never happen.
Interesting fact. After last ESU (January 2026) on Vista I saw WU client known from Windows 7 updated alone and normally find updates without errors and normally show all updated. I don't know how on Server 2008, because didn't saw. But if that WU client was earlier updated like that, was fully sha 2, tls channels, https, etc. And wasn't problematic with hacks how install Net or IE example.
Did Server 2008 get 3.5.1 and framework 4.6.2 updates during ESU? I am looking to manually install some, but I do not know which ones to install.
Can someone give instructions how make full ESU update (without C8000266) for windows Server 2008 ? I make clean install that windows, make that two updates to sha 2 install manually and later fully update system to end before ESU. Interesting me what after do for WU detect ESU and to not conflict make C8000266 after installing SSU from November 2025, because that make later in WU that error.
I have not been able to get the ESU on Server 2008 to work in months. I noticed that before I install the bypass and the SSU from 11-2025 I was getting an error, but it was intermittent. I also installed the SSU from 11-2025 before running updates and the updates worked but eventually failed. It may be something with the OS itself or Windows Update or a certificate issue. The updates were working as of May 2025. So, what changed? Server 2008 R2 I have not had any issues with Updates or ESU.
Which version bypass worked you then? And normally were updated via Windows update? Mean Server 2008 SP2
Hello, this is my first posting and signed up to the site after finding this thread. As the 32-bit update seems to be broken, would this way update 32 bit with all ESUs?: I updated 64 bit Vista with all post SP2 updates (not ESU updates). I then updated the update engine with the tools in this thread and got the server updates. What I did was got the x86 versions of the server updates that were available. Would doing this get the 32 bit Vista as up to date as possible with all ESUs? Thanks.
I want to quote that from bypass lh 8. " *** Tips to avoid errors C8000266 or 8007000E on initial Windows Update scan - change WU settngs to "Never check for updates" - after each scan result, you can either: install available updates except Monthly Rollup and .NET Rollup or ignore, close WU, and stop the service "wuauserv" to free up memory - install 2020-04 SSU KB4550737 and ESU prep KB4575904, then run WU to check for updates - install 2020-05 SSU KB4555448, then run WU to check for updates - install 2022-07 SSU KB5016129 and ESU prep KB5016891, then run WU to check for updates - install 2023-12 SSU KB5033466, then run WU to check for updates - install 2025-01 SSU KB5050682, then run WU to check for updates - install latest available SSU, then run WU to check for updates - install available updates including Monthly Rollup and .NET Rollup - change WU settngs to your desired choice " But that first error is when have bypass 7 + lh8 (patch wu is only in 7) + SSU November 2025 on Server 2008. How use that instructions with WU to detect ESU after January 2023 via WU without that C8000266? @abbodi1406