hi NewEraCracker, I'm followed your tutorial of how to install latest Windows Server 2012 R2 ESU updates on windows 8.1 (Out of band update one), Which i have done it on my updated Windows 8.1 VM, And it works like charm. Nice scripts you made, but even tho. your tutorial was a bit tough at the beginning. but still, thanks. and thanks also for helping some people installing Windows Server 2012 R2 ESU updates on windows 8.1 without bricking their devices. (I can't send a screenshot of installed update URL link because this is my first time of posting a reply. But I'm not new on this forum website, it requires 5 reply posts for me) Oh, and btw, I have a quick question, is that ok if I'm gonna use windows update cleanup from disk cleanup or not yet? (After installing the patched LCU update) I know your scripts is still on WIP, But I wanna clean my VM before I wanted to compact it for free up space in VMware Workstation Sorry for my terrible English.
Ok, Thanks for your answer and info, I haven't turned on my VM for 8 months since last time I installed 2025-04 ESU updates. and I forgot to use windows update cleanup before installing the required updates for your special scripts to install latest Server 2012 R2 updates without bricking my VM. (Don't worry I did backup my whole VM before doing your steps So I don't have to worry about System Restore if everything went wrong when I'm installing a patched LCU). Once again, Sorry for my terrible English. Btw, Merry Christmas!
Your English isn’t terrible at all this time Merry Christmas anyway… ehm… Happy New Year as well, since it’s just behind the corner…
@SEBA33 I have said it before on the Windows 7 thread: This issue may be a bug with the SuperUser executable when there are strange symbols on the path the program was extracted to. When you extract it to a simple path like C:\BypassESU it should work fine. When you hit these crashes and it leaves ghost processes, you'll need to reboot. My two cents. Thank you.
The choice menu means SuperUser ran succesfully (unless he modified the script to pass it?) that compatibility issue popup can be dismissed in that case
I putted button "X" and normal installed after. Interesting for me is, I installed December ESU monthly and October Net and I made find updates. First time put error in Windows update. Second time find and good show "is updated". I wonder why in last time is like that.
don't use the windows update check it , just download and modified the KB msu and install with script
Turn secureboot for Windows Server 2012 R2 in VMWare 17.6.4 resolved problems and work normally finally. How few frustrating that small details in VMs
where i download code reviewed_patchSSU this is for not working security updates i do all stage and now shown dism error Deployment Image Servicing and Management tool Version: 6.3.9600.19408 Image Version: 6.3.9600.19397 An error occurred trying to open - package_for_kb5070886_gm~31bf3856ad364e35~amd 64~~9600.22826.1.2.mum Error: 0x8007371e Error: 14110 A component is missing file verification information in its manifest. The DISM log file can be found at C:\Windows\Logs\DISM\dism.log ----------------------------------------------- i need patchssu 8.1
Nice. I installed the KB5073696 update (January 13, 2026). and so far. it works well. I also uninstalled the previous patched LCU update as well. that I did a while ago. Thanks for keeping Windows 8.1 up to date without any bricking the device again! Hopefully you can work on Windows 8.0 as well. BUT it needs more work for this. Because all type of updates got affected in Windows 8.0 (AKA. NT 6.2 Operating System). But it's not the same thing in Windows 8.1 (AKA. NT 6.3 Operating System) expect the LCU update. Which idk why. But once again. Thanks for your hard work. Also. A quick question. is that ok that I uninstalled the previous patched LCU update with patched SSU installed? before I uninstalled it later. or I'm screwed? I mean the uninstalling the update process was fine. Sorry for the stupid question btw. I'm just a bit nervous -Peace.
Hi, Windows 8.0 (NT 6.2) is hard to work with because all update types need patching, so there is no easy way to revert to a clean status if the need arises to run DISM restore health commands and such. There is no problem with what you did there, but the patched SSU should not remain installed forever. Typically, it should be reverted (original servicing stack restored) when the patched update is consolidated after reboot. My two cents. Thank you.
Alright. Thanks for your answer. Yes I know about newer NT 6.2 updates problems that you said. I guess some NT 6.2 users will switch to Windows Server 2012 Non-R2 to continue installing the newer updates with Bypass Blue installed without any problems. It's not big deal for client users but no choice for now but this is only a clean solution. Until one day If someone will manage to make a special patcher for all type of NT 6.2 updates on Windows 8.0. It's ok also If you can't make it. At least you saved Windows 8.1 from bricking the whole Windows in newer updates, Let's just hope it won't affect on Windows 8.1 in upcoming updates. Long Live Windows 8.1! I'm guessing that must be a "Cleanup" Update for ONLY Windows Serer 2012 and 2012 R2 after all, since July 2025 updates and later. the statement isn't always clear about Installing the latest Server/Embedded Updates on client Operating System sometimes. the issue is about metadata and component files not kernel itself. For your two cents. You're welcome.