Interesting approach but isn't this going to create a "Frankenstein" WinSxS folder ? If installing an older update, for one reason or another, some files/folders may get processed twice then, through both the Client and the Server assemblies ? Also the case with future NET Framework updates, so even if it works I'm wondering to what kind of long term effects this could potentially lead to.
Therefore, integrate and solidify the updates, then modify the registry. This can help avoid such issues. Most of the previous updates are fine because these MUM files between Windows Server and Windows 8.1, ultimately point to the same manifest file, performing the same operations. A few may install drivers typically found on servers; as for server components, they won't be installed since the requirements aren't met.
Which configuration you have VMS on VMware? Uefi + secure boot + nvme ? To me that configuration made, when i putted ESU's by proxy that newest updates for server 2012 R2, machine stopped work. Window bsods with errors and bootloop to repair windows and again Black screen.
I'm still using version 17.5.2 Workstation Pro (the first free version released in May 2024) Virtual Machine Hardware Compatibility : Workstation 17.5.x Guest OS : Windows - Server 2012 Firmware : UEFI (SecureBoot disabled) SCSI Controller : LSI Logic SAS Virtual Disk Type : SCSI I haven't tried WSUS Proxy in a while, alternatively you can also use this registry key to connect through WU directly : Code: reg add "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Azure Connected Machine Agent\ArcESU" /v Enabled /t REG_DWORD /d 1 /f The regkey seems to also work with other 2012 R2 Editions such as Storage Server and Foundation
That regkey also works on client 8.1 if you manage to "glitch" WU using the proxy (I think that is still better than the plain proxy cuz it allows you to use a custom, actual WSUS server if you want + enables fully automatic updates). Anyway, right now what is best for client is making an ISO with all updates till June and BypassESU included, and not even bothering about updates after installation. What I did personally, after June I just moved to Server 2012 R2 and made it look like plain Windows 8.1, using the themes, wallpapers and Aero cursors from the client version; I even baked everything into an ISO so that everything is already present on first logon. I'm not losing much over client anyways, since the 8.1 metro apps no longer work and the laptop I'm using for that has literally unhearable audio that makes the absence of the startup sound almost unnoticeable. BTW, that laptop has 6GBs of RAM, and is also dualbooted with macOS Sequoia.