Windows Server 2022 Bug
2 TopicsWindows Server 2022 Product Key showing Volume_KMS_WS19 Channel
My firm recently updated SPLA with Microsoft Reseller and got the Windows Server 2022 KMS product keys. However, it doesn't work as expected. The symptom is quite buggy to me. I installed the WinSRV 2022 product key (KMS) with a Windows Server 2022 running KMS volume activation service. It always returns as 'Volume_KMS_WS19 Channel' from the drop-down-list. Nothing can be activated by the KMS server. All activations ended up with error: 0xC004F074. Needless to mention, the Windows Server 2022 KMS server was fully updated and time is synced with clients. If I install the same KMS key with Windows Server 2016 or 2019, the product key returns as the expected 'Volume_KMS_WS22 Channel'. And activation works properly. Why the same key got different results on WinSRV 2022 comparing to 2016/2019? Is this a known issue? Regards, Charles WS6.8KViews0likes1CommentWindows Server 2022 Preview Bug Discovered
Hi, I am running Windows Server 2022 Preview Standard and have discovered a bug. I'm not really sure where to report it, so I'll report it here. Currently running Build 20348.75. If you run secpol.msc, and change Network List Manager Policies/Network/Network Location and change the server to Location Type - Private, when you reboot, the server is unresponsive in terms of for example clicking control panel/Windows Defender. Cant launch Edge etc.....something fundamentally wrong. Thankfully I have a snapshot to rollback to, but this is a pretty big issue for my servers that are not domain joined, but are in fact on a private network, not a public one.3.6KViews1like5Comments