Windows Server vNext 2025 v25246 language pack issue
Full package and demo video: https://youtu.be/og9FnlKnBxc Look at the picture and answer the question Already fixed: --------------------------------------------- Boot.wim language pack issue has been resolved. The last raised issue has been fixed. https://techcommunity.microsoft.com/t5/windows-server-insiders/it-s-over-it-s-over-barbie-is-q-boot-wim-is-immune-after-adding/td-p/3291081 To be fixed: --------------------------------------------- 1. There is a part of WinRE that has not been finished. Retry, Cancel, not Chinese. 2. Open the login option and flash back. Component report: Install.wim.report.csv WinRE.wim.report.csv Boot.wim.report.csv
Where can I report a Windows Server bug?
Hi, I'm pretty sure my co-workers and me found a bug that manifests in a kernel memory leak, more specifically leaking "process" objects (those counted by the performance counter "\Objects\Processes"). For Visual Studio I've had very good experiences reporting bugs via the Visual Studio Community but this clearly isn't Visual Studio related so I didn't want to post it there. I don't want to open a paid support case since we don't really require a fix (we have to find a workaround for our product anyway since a lot of Windows Server versions are affected and we cannot restrict our product to fully patched OS versions). I just want to report it so MS can fix it. Can you please point me to the right channel via which I can submit a bug report against Windows Server? Regards, Paul
Windows Admin Center 1910 SMEscripts
While connected to a Hyper-V server the Windows Admin Center creates error logs in the Micrsoft-Server ManagementExperience log from the SMEScripts source. Events are created every few seconds concerning [Get-VirtualMachine] and [Get-VirtualMachineVhds] This is creating a lot of error messages filling the log. [Get-VirtualMachine]: Couldn't get the required CIM namespace root\MSCluster. Error: Could not get objects from namespace root\MSCluster. Invalid namespace [Get-VirtualMachineVhds]: Couldn't get the required CIM namespace root\MSCluster. Error: Could not get objects from namespace root\MSCluster. Invalid namespace
[Bug] Can't connect to cluster or node running WAC
Our environment is a Hyper-V hyper-converged S2D cluster running Windows Server 2016 Datacenter edition. WAC has been installed as a high availability deployment option called wac. WAC is currently running on node 1 in the cluster. When it is on node 1, connecting to node 1 in WAC is really slow and connecting to node 2 in WAC is really fast. If I failover WAC to node 2, then connecting to node 1 in WAC is really fast and connecting to node 2 is really slow. If I try and add the cluster by it's FQDN it says it cannot verify it's network. If I click the blue hyper-link to the cluster from one of the nodes via their WAC page it adds the cluster but it fails to load. It prompts for credentials, using my windows credentials or supplying alternative credentials does not work. It says that the process could not be completed. Kerberos delegation has been done as documented by MSFT for the SSO to work. Winrm is enabled and listening on HTTP on all IPs on all nodes. We have another cluster - cluster2 that is also Hyper-V hyper-converged running Windows Server 2016 Data edition. If I try and access that cluster or it's nodes from the same WAC install it works absolutely fine.
