Question did Microsoft restore TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA or did it work again due to VMware? Is this a bug I have noticed, that once you install the latest SSU update, it breaks the Windows update. I was told to have 8 gigs of RAM but I'm on a laptop. I might do 4 gigs of ram even that is tough running Vista inside on vmware. I'm reworking with TLC games here is one example, cnc-ddraw ? (Mohawk engine Might Work) & DDrawcompat 0.6.0 for Vista & 7 now fully Works, despite Broken GDI caused by Virtualizations non-existent apis. Supports All of The Learning Company Games. Can this be fixed? I am away of legacy update but has its problems with Vista. I am also away of WU_DataStore_Fix.zip. i'm Assuming abbodi1406 can't do anything.
Yes, it's restored WU_DataStore_Fix doesn't currently help much to reduce the error rate, you should not install ESU preparation packages KB4538484 or KB4575904, only install latest KB5016891 you may also not install latest SSU directly, install on phases nd run WU scan after each: 2020-05 SSU KB4555448 2022-07 SSU KB5016129 2023-12 SSU KB5033466 2025-01 SSU KB5050682 latest SSU
abbodi1406 Thinks 2020-05 SSU KB4555448 2022-07 SSU KB5016129 2023-12 SSU KB5033466 2025-01 SSU KB5050682 It did help a lot technically 2022-07 SSU works on 1st run with 4 gigs but not x86 windows but still, it is surprising that Microsoft is not optimizing windows update. when it is still getting updates for server 2008. I will be reporting this to legacy update for other people havening issues with ESU updates breaking windows update. as for KB5016891 I'm not sure I think it's more on server 2008.
I have tried these exact steps on 64-Bit, installing the SSUs in stages. But when I get to the point of installing the latest SMQR, it breaks WU for me again with the C800266 error returning. Haven't been able to find a way past that on multiple installs. And 32-Bit seems to not work anymore now.
It worked for me on stages for x64 (although i didn't attempt to install any offered updates) https://forums.mydigitallife.net/threads/bypass-esu-longhorn.89161/#post-1875957 indeed, x86 didn't work for me either with same steps
I wonder which options do you use on Vista_SHA2_WUC? On x64 I always used both categories at once but on x86 I always had to do one category at a time. I hadn't realize until yesterday that the windows update was restored so I am playing around on a VM. Currently I am doing the servicing stack in stages as Abbodi mentioned. I will report back
Yeah, x86 seems to have been broken for the near entirety of 2025. I guess that there is a memory leak when connecting only to the Microsoft server, causing the 8007000e error. You can still update it by connecting to an alternative WSUS server (or maybe using WSUS Proxy). The issue is in the SSU update: it also occurs in the 2020 ISO I have to publish, which has the 2025 SSU and ESU packages already applied.
It's not a memory leak monthly rollups metadata are too big for wu esent engine to handle it's worse in x86 due the 2GB virtual address limitation
I run searches on both x86 and x64 versions on VMs with the same amount of RAM; how can x64 work if x86 doesn't (with the same amount of RAM as I said earlier?)
Because 32-bit applications are limited to 2 GB of RAM by default, but can be configured to use up to 4 GB using the LargeAddressAware flag.