Forum Widgets
Latest Discussions
Server 2025 Core ADDS DC, Network Profile Showing as "Public" and not as "DomainAuthenticated"
OS: Windows Server 20225 Standard Core (no GUI), build 26085.1 Role: ADDS, DNS ForestMode: Windows2025Forest DomainMode: Windows2025Domain Platform: Hyper-V guest When standing up a clean Windows Server 2025 using server core and configuring it as a domain controller, the network category (profile) always shows as "public." A clean load of Windows Server 2022 with server core as a domain controller has the same behavior. However, in Server 2022, the fix is to add DNS as a required service to the nlasvc (Network Location Awareness) service. Once that is done, the network category reflects "DomainAuthenticed" and persists between reboots. In Server 2025, the nlasvc service does not have the same requiredservices as Windows Server 2022, and it does not start automatically. Even after configuring the nlasvc service the same way it is in Server 2022 and adding DNS as a required service, the network category still reflects "public." The only way to get the network category to properly reflect the "DomainAuthenticated" status is to disable and reenable the network adapter after each reboot.
Start menu layout cannot be changed
Having just installed an evaluation copy of Windows Server 2019, I cannot make any changes to the start menu layout. For example; unchecking "Show app list in Start menu" from the Start menu settings does nothing. Attempting to choose which folders appear on the start menu does nothing also. Any changes to the tiles lasts until the next reboot where it's reset. Tiles will become unresponsive when attempting to drag them and then become "ghost" tiles that cannot be clicked on or moved/unpinned. This is a completely default and less than hour old install - absolutely no changes have been made thus far.[ISSUE] b20251 b20257 b20262 b20270 b20282 b20287 Formatting a volume fails
affected builds (tested): b20251,b20257,b20262,b20270,b20282 remotely via Server Manager from b20201 initializing as GPT / reset / clean works fine. creating partition works fine formatting volume fails repro steps: reset disk new volume fs refs or ntfs, default settings format will fail (see diskpart and Server Manager) if server manager is used, update cache will run eternally until wizard is closed
WSL 2 not working after installing 20262
Just getting involved with Insider Preview...upgraded 2019 Datacenter (latest official release) to 20262. After the upgrade, downloaded and ran the Linux Kernel update package. When running WSL commands from the command-line, almost every command I run returns the same output that wsl --help enumerates. If I run wsl --set-default-version 2, it enumerates the help context. Did I miss a step to get this to work or is this a known bug?
