Forum Discussion

bradcope's avatar
bradcope
Copper Contributor
Sep 05, 2021

Windows Server 2022 Unable to restart 'Network Location Awareness' Service

Testing server 2022 (core) GA on two machines; one physical, one virtual. When I attempt to restart the network location awareness service using the command:     restart-service -Name NlaSvc -For...
windows server
Windows Server 2022
NickFranklin's avatar
NickFranklin
Copper Contributor
Aug 16, 2023
Well I have a brand new Server 2022 install, couldn’t restart the NLA service so rebooted, same problem, tried to restart the service it wouldn’t restart. Rebooted again same problem. Enabling and re-enabling IPV6 did fix the issue but a reboot failed again.

Added the registry settings and had 3 consecutive successful reboots.
JimBecher's avatar
JimBecher
Copper Contributor
Sep 08, 2023

NickFranklin The problem isn't with the NLA service. The simple fix to the network type at boot is to make the NLA service dependent on the DNS service. The real problem is with the Network List Service. Has anyone found a fix yet? All 8 of my Server 2022 boxes have the exact same problem and Microsoft Support has become non-existent. I opened a ticket on this two months ago and still have not heard from Microsoft. Their support is way beyond bad. 

  • Rusty2345's avatar
    Rusty2345
    Copper Contributor
    Dec 05, 2023

    Kyle_Hansen 

    I have not had to use this on member servers but it makes sense that it would apply as the fix is telling the server to wait until it sees a Domain. Best guess. 

  • Kyle_Hansen's avatar
    Kyle_Hansen
    Copper Contributor
    Dec 05, 2023
    Clarification; is the above registry entry (and found in other places on this thread) only for DC's? Or member servers also that have this issue? Thanks!
  • JimBecher's avatar
    JimBecher
    Copper Contributor
    Sep 08, 2023
    Ok. I fixed it by making the NLA service dependent on the DNS service. Six to one half dozen of the other. What people are missing is that the NLA service is not the real problem. It is the Network List Service. Try it. Disable the Network List Service and reboot. You can restart the NLA service any number of ways at that point. Applet. command line, whatever. The NLA service is not the issue. Of course you can't leave the Network List Service disabled but it points out where the real problem lies.
  • Rusty2345's avatar
    Rusty2345
    Copper Contributor
    Sep 08, 2023
    I'm saying it eliminated the need to restart the list service.
  • JimBecher's avatar
    JimBecher
    Copper Contributor
    Sep 08, 2023

    Rusty2345 either that or making the NLA service dependent on the DNS service. Both work well but neither address the real underlying issue. The Network List Service can't be stopped or restarted. 

     

    or are you saying that the registry entry fixes the Network List Service?

  • Rusty2345's avatar
    Rusty2345
    Copper Contributor
    Sep 08, 2023

    Adding the DWORD "AlwaysExpectDomainController" in the registry shown further up in this thread has helped me so far .

Resources