No Windows Server 2012 R2 will continue to be available until 2029 via Azure Arc with the possibility of some cases but locked down
only 64 bits on azure arc and not 32 bits for windows server 2012 r2 I remind you that premium insurance no longer exists since 2018 which was replaced by esu so with the agreement of Azur arc windows server 2012 r2 will continue until 2029 only x64 bits via Azur Arc
I will, now, try again to update everything. If I manage to do so, I will tell u what files to replace, and then make a script to be run in WinRE to actually install the update.
Hi, It's the same issue as the last time. The boot-loader files are generic and are installed no matter if it's Client or Server, however system drivers like win32k.sys are only installed on Server. This leads to mismatches and the boot-loader will reject boot with a BSOD, secure boot failure, or other early error message. I came up with a similar frankenstein script as https://forums.mydigitallife.net/posts/1884142 It's attached. No warranties reserved, expressed, implied, or otherwise. Do not try this on a production system. It is merely a proof-of-concept. Ideally, MUMs could be modded, but a solution has to be found to resign them with the corresponding CATs: https://forums.mydigitallife.net/posts/1884766 My two cents. Thank you. P.S.: See post for only Internet Explorer at: https://forums.mydigitallife.net/posts/1887757
So apparently it is confirmed that KB5063950, this month's cumulative update for Windows Server 2012 R2, has the same issue as last month's KB5062597 and will still cause BSOD when installed on Windows 8.1 x64. So Windows 8.1 x64 has no more security update support as of July 2025 (unless Microsoft changes its mind again), the last update that can be installed on it is the June 2025 cumulative update KB5061018 (I am talking about only the Windows security updates, not others like .NET).
Is this post https://forums.mydigitallife.net/posts/1884132 a method to get back up and running after taking the KB5062597 rollup!?
I think for your "issue 1", it may be intentional, as the OP has stated in the first post in that thread that the Metro apps (and perhaps others?) were intentionally removed from the image to reduce its size.
@NewEraCracker I haven't been able to trigger the automatic recovery and as far as install media i used a kinda hacky method to trigger the restore partition which im not sure has an option to do an in-place repair.
emmmm 1. Copy the *.mum and *.cat with the following file names from the Windows Server 2012 R2 to Windows 8.1 (C:\Windows\servicing\Packages): Code: Microsoft-Windows-ServerCore-SKU-Foundation-Package-drivers Microsoft-Windows-ServerDesktopExperience-drivers Microsoft-Windows-ServerDesktopExperience-multimedia Microsoft-Windows-Server-Drivers-Package-base Microsoft-Windows-Server-Drivers-Package-drivers Microsoft-Windows-Server-Drivers-Package-net Microsoft-Windows-Server-Drivers-Package-printscan Microsoft-Windows-Server-Drivers-Package-termsrv Microsoft-Windows-Server-Features-Package Microsoft-Windows-Server-Features-Package-AutoMerged-admin Microsoft-Windows-Server-Features-Package-AutoMerged-avcore Microsoft-Windows-Server-Features-Package-AutoMerged-base Microsoft-Windows-Server-Features-Package-AutoMerged-com Microsoft-Windows-Server-Features-Package-AutoMerged-drivers Microsoft-Windows-Server-Features-Package-AutoMerged-ds Microsoft-Windows-Server-Features-Package-AutoMerged-enduser Microsoft-Windows-Server-Features-Package-AutoMerged-inetcore Microsoft-Windows-Server-Features-Package-AutoMerged-mergedcomponents Microsoft-Windows-Server-Features-Package-AutoMerged-mincore Microsoft-Windows-Server-Features-Package-AutoMerged-minio Microsoft-Windows-Server-Features-Package-AutoMerged-minkernel Microsoft-Windows-Server-Features-Package-AutoMerged-multimedia Microsoft-Windows-Server-Features-Package-AutoMerged-net Microsoft-Windows-Server-Features-Package-AutoMerged-printscan Microsoft-Windows-Server-Features-Package-AutoMerged-sdktools Microsoft-Windows-Server-Features-Package-AutoMerged-shell Microsoft-Windows-Server-Features-Package-AutoMerged-termsrv Microsoft-Windows-Server-Features-Package-AutoMerged-windows Microsoft-Windows-Server-Features-WOW64-Package-AutoMerged-admin Microsoft-Windows-Server-Features-WOW64-Package-AutoMerged-avcore Microsoft-Windows-Server-Features-WOW64-Package-AutoMerged-base Microsoft-Windows-Server-Features-WOW64-Package-AutoMerged-com Microsoft-Windows-Server-Features-WOW64-Package-AutoMerged-drivers Microsoft-Windows-Server-Features-WOW64-Package-AutoMerged-ds Microsoft-Windows-Server-Features-WOW64-Package-AutoMerged-enduser Microsoft-Windows-Server-Features-WOW64-Package-AutoMerged-inetcore Microsoft-Windows-Server-Features-WOW64-Package-AutoMerged-mergedcomponents Microsoft-Windows-Server-Features-WOW64-Package-AutoMerged-mincore Microsoft-Windows-Server-Features-WOW64-Package-AutoMerged-minio Microsoft-Windows-Server-Features-WOW64-Package-AutoMerged-minkernel Microsoft-Windows-Server-Features-WOW64-Package-AutoMerged-multimedia Microsoft-Windows-Server-Features-WOW64-Package-AutoMerged-net Microsoft-Windows-Server-Features-WOW64-Package-AutoMerged-printscan Microsoft-Windows-Server-Features-WOW64-Package-AutoMerged-sdktools Microsoft-Windows-Server-Features-WOW64-Package-AutoMerged-shell Microsoft-Windows-Server-Features-WOW64-Package-AutoMerged-termsrv Microsoft-Windows-Server-Features-WOW64-Package-AutoMerged-windows Microsoft-Windows-Server-Gui-Mgmt-Package-admin Microsoft-Windows-ServerMediaFoundation-Multimedia Microsoft-Windows-Xps-Foundation-Server-Package 2. Export the registry entries of the above components and import them into the client version. The registry is located at HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages 3.install the latest LCU with fun