Does anyone know what this version is or have used it? 26100.1.240331-1435.ge_release_SERVERDCAZURE_VOL_x64FRE_en-us.iso I'm currently downloading this to try it out in my Hyper-V lab.
Code: Windows Server Datacenter: Azure Edition is an edition of Windows Server focused on innovation and virtualization optimized to run on Azure. Azure Edition features a Long-Term Servicing Channel (LTSC) and yearly product updates, with two major product updates in the first 3 years. Azure Edition also brings new functionality to Windows Server users faster than the Standard and Datacenter editions of Windows Server.
Thank you very much, I'm installing this now with Desktop Experience. Hopefully it will run like regular Windows Server, there was only DataCenter Azure Edition available.
Added to: https://forums.mydigitallife.net/threads/discussion-windows-server-2025.88013/page-4#post-1837192
https://forums.mydigitallife.net/threads/discussion-windows-server-2025.88013/page-4#post-1837192 Added SVFSFX Repo!
Added: https://forums.mydigitallife.net/threads/discussion-windows-server-2025.88013/page-4#post-1837192
There is a messed up Group Policy in 24H2 which is not specific to the server only, but more commonly applied to server environments. Under Local Computer Policy\Computer Configuration\Administrative Templates\System there is the policy "Specify settings for optional component installation and component repair". This policy has applicability when the updates are configured to be received from an internal server like WSUS and the repair source for dism /online /cleanup-image /restorehealth is required to be online at Windows Update or on an internal server file share. Also when other components like .NET Framework 3.5 or language features are not available on the WSUS server which is common and typical configuration. Until 24H2, this policy had a setting to allow the repair and optional configuration to be configured to Microsoft Update, which now is gone. I think it was moved under \Windows Components\Windows Update\Manage updates offered from Windows Server Update Service\Specify source service for specific classes of Windows Updates. The issue is that the replacement policy configures different registry keys and when the previous policy is set back to Not Configured, it leaves the previously configured registry keys behind, potentially creating unexpected behaviour. This gets even more complicated in mixed environments with 24H2 (Windows 2025 or Windows 11) and older OS. The registry values left behind are specifically found in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Servicing The only solutions which I found are: 1. Configure the policy to Not Configured BEFORE the upgrade, as the new admx template is missing the second option and does not roll back the policy correctly 2. Bring back the old admx which is messy and certainly not recommended. 3. AFTER the upgrade, configure the policy to DISABLED, which will remove all the relevant keys - I think this the preferred option 4. Clean-up the registry manually, which is a complicated task in a larger environment, but still possible by using a Group Policy Preference to delete the left behind keys. 5. For mixed environments for which the old OS still require the old settings, there is a need for filters to be applied and different versions of admx templates used. It was a good thing if Microsoft had left the old admx functionality in the new implementation with the caveat that it applies differently to different versions and mentioned in the notes on the side when configuring the policy. Very annoying for those who have a use for this type of configuration. If this is all too complicated for some who read this, please ignore as it does not apply to you.
Thanks, I downloaded NSudo but I can't seem to find an option to remove anything from it, only run: Spoiler Also 8.2 was the last version I could find as the repo on GitHub seems archived. Is there a hidden mode I have missed?
You have updated ? 26100.712 or 26100.1 server 2025 => launch windows update and after check if missing
Well I have to look into this later, I'm not even sure why I'm doing it in the first place, for science maybe? I have however removed the "LicenseImdsIntegration" ("\Microsoft\Windows\Clip\LicenseImdsIntegration") which runs "C:\Windows\System32\fclip.exe" every time on startup. Spoiler Can't figure this out though: Spoiler
fclip.exe is removed: Spoiler KMS_VL_ALL v51 is running Spoiler Not activated: Spoiler What else is there to do?
No error ... microsoft locked by licence policy :/ Server 2022 lock by fclip ... and later license ( after update license file ) ... Work fine for 2022 .. https://forums.mydigitallife.net/th...s-server-2022-datacenter-azure-edition.85959/ Only hotpatch features not works atm
I updated using .1 and updated to .560. The issue is that the new admx template is missing the old option and as such does not roll it back when set to Not configured. I actually noticed that even when is set to Disabled, the outcome is the same. The old option is no longer functional in build 21600.x, but Microsoft should allow for gracefully roll back of the old functionality.