Patches und Workaround verfügbar – es besteht das Risiko demnach nur weil die GPO „Netzwerksicherheit: PKU2U Authentifizierungsanfragen an diesen Computer zur Verwendung von Online Identitäten zulassen“ standardmäßig aktiviert ist sie zu deaktivieren dürfte also vor möglichen Angriffen schützen
Archive for the ‘Windows Server 2025’ Category
Microsoft Windows Server 2008 (R2) / 2012 (R2) / 2016 / 2019 / 2022 / 2025 plus Windows 10 / 11 – SPNEGO Extended Negotiation (NEGOEX) Security Mechanism Remote Code Execution Vulnerability
Mittwoch, Juli 9th, 2025Microsoft Windows Server 2025 – so installieren sie Windows Subsystem for Linux (WSL) 2 unter Windows 11
Freitag, Juli 4th, 2025Microsoft Windows Server 2025 – so aktivieren sie die Virtual Machine Platform in Windows 11 z.B.: Windows Subsystem for Linux (WSL) 2
Mittwoch, Juli 2nd, 2025Microsoft Windows Server 2025 – how to enable Virtual TPM (vTPM) in Hyper-V for your virtual machines making them compatible with security requirements like BitLocker Secure Boot and Windows 11 installation
Montag, Juni 30th, 2025Microsoft Windows Server 2025 – how to Install Ubuntu on Hyper-V Virtual Machine in Windows 11
Sonntag, Juni 29th, 2025Microsoft Server Core 2025 – die installiert man das Windows Admin Center
Mittwoch, Mai 14th, 2025Microsoft Windows Server 2025 – Core Licensing Calculator
Freitag, Mai 2nd, 2025
Microsoft Windows Server 2025 – Hotpatching need a subscription from July 1 2025
Dienstag, April 29th, 2025From July 1 2025 hot patching for Windows Server 2025 will be offered with the start of the subscription at a price of $1.50 per CPU core per month
Microsoft Windows Server 2025 – so erstellen Sie eine Vorlage für virtuelle Maschinen in Hyper-V
Freitag, April 18th, 2025Microsoft Windows Server 2025 – Domain Controller (DC) no longer accessible after restart
Freitag, April 18th, 2025Workaround: Restart the network Adapter
Microsoft has suggested a temporary workaround for those affected and Administrators can restore the expected behavior by restarting the network Adapters this can be done manually in various ways e.g. with the following command via PowerShell
PS C:\> Restart-NetAdapter *
The problem is that the error reoccurs each time the Windows Server 2025 acting as a domain controller is restarted. Microsoft suggests creating the workaround to restart the network adapters as a scheduled task that restarts the network adapter each time the domain controller is restarted