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.
I was finally able to update a Client Win8.1 install "the unintended way", as in by copying all the files with a modified date of 11 June or newer from my 2012 R2 laptop's installation. The resulting system shows no signs of breakage and behaves like a regular Win8.1 system, except the fact the Start button is completely black when hovered (this is an issue with the graphics driver in the VM and shows regularly in safe mode). The startup sound also plays. I don't know if Bluetooth works since the VM has no Bluetooth functionality, but bthserv starts up as normal, so I think it will work. Problem solved (at least temporarily). I'm sure there is a more practical way to do this than to copy nearly 9GBs of system files from another install. At least doing it this way retains all bits of client-exclusive functionality. Beware that, as expected, since Windows Update/WUSA don't do anything, the system will think it's still on the June patch (KB5063950 won't show up in Installed Updates). So, avoid WSUS Proxy or the procedure I did to glitch Windows Update by using it. Generally, there is the fact that the Bluetooth stack will no longer be updated (so no more vulnerabilities in it will be patched) since it's not included in Windows Server 2012 [R2].
Ok. I am not alone with that bug after August update on Windows 8.1 as Server 2012 R2. Will be soon some update Bypass with added patch WU ? It was helped finally to can tell bye for wsus proxy tools.
I patched WU using the proxy itself. I "updated" Client by just copying the files (only the ones modified after 11 June) onto the VM. The files came from my Italian 2012R2 install on my ASUS laptop. This has nothing to do with Windows Update.
There is no WU ESU Patcher like the ones for Windows Vista and 7, unfortunately. But even if there was, it would even be threatening because it will eventually lead to a July or newer patch to be installed which in turn will render the install unbootable if done the regular way. Updates after June should be installed the way I did or with similar procedures. To be safe, just resort to manual updates, and stick to April (since the May patch causes slowdowns) or install the June patch then copy the files from a 2012 R2 install with the same language. Even if I linked my folder here, it would only be compatible with Italian systems, since I use the Italian build of Windows. If you want to do it, here is the procedure: - Install a copy of Windows Server 2012 R2 wherever you want (spare PC, spare HDD/SSD, VM, etc). It'd better be in the same language as your client. - With Xcopy, using the /s /d:[the date after the release of the CU you chose] options, copy the Windows folder somewhere else, and then onto a removable media. - Once copying procedure is done plug your media into the destination PC running Windows 8.1 Client. - Boot into WinRE by using Shift while restarting your system, and load the command prompt in there. - Run xcopy in WinRE, position yourself into the root of the folder ON THE REMOVABLE MEDIA, and using those same Xcopy options, copy the Windows folder into C:\Windows. If copying over an install running the June update from the D: directory starting from a media that contains the Windows subfolders in its root, for example, the command should be: xcopy D: C:\Windows /s /d:06-11-2025. This will overwrite all files changed starting from the day after the previously installed CU was released, just like the regular update process does. - Once the copy ends, reboot, and you should get back into your system. Open regedit, and go to HKLM/Software/Microsoft/Windows NT/CurrentVersion. - Change the UBR in there to the one of the latest cumulative, which you can see under your 2012R2 install (anyway, the one for the August LCU is 22725). - Enjoy your patched system, with no server drawbacks. This is a very time-consuming procedure and while it is the best one (as it doesn't make you lose any features since files that are not present won't get overwritten), I'm sure there will be a way more practical way to do this.
Honestly good we gone in that topic. I will be not shocked about if August 2025 update for Windows 8.1 as Server 2012 R2 ESU change structure and that break system and bypass blue. If be September, I am near 100% sure will time to update bypass. WU patcher hadn't nothing with that. I think it only was to let's download updates via WU. But problems is in mechanism August monthly update. Need look in that. Maybe Microsoft changed something in code. Why example on Server 2012 R2 (that original) any problems with that update August. Only on Windows 8.1? It is specially future gave by Microsoft for few cut use ESU on Windows 8.1. It is my opinion after observe situations.
Despite the fact the .msu is no longer able to install on 8.1 in its original state, the files are fully compatible. My 8.1 VM, after doing that hackjob, continues working as a regular client, with no borked strings or branding, and user experience smooth as any previous, officially working version. It’s not activated, and it shows the watermark as it should be doing, displaying “Windows 8.1 Pro build 9600”. Winver shows Windows 8.1 branding. Everything works as normal. The files were not changed, at all, Microsoft just removed from the manifests the ability for the MSU to recognize the packages it has to replace, so it reverts everything back except for ntoskrnl and a couple of other files. The manual copy I did, well, only copies the newer files, leaving the rest as-is, which is almost exactly how any Windows install is updated.