10

I am trying to add the Wireless LAN Service to my server but I first had to restart it because it installed some updates a while ago. After the restart it came up with the following error:

The request to list features available on the specified server failed.

Server Manager:

enter image description here

Powershell:

enter image description here

What should I do now? I am not very experienced in Windows Server only in C# and some other programming languages.

  • 1
    Did you uh...try restarting it again? Windows has a funny way of sneaking in additional updates after a reboot. – Nathan C Apr 28 '14 at 0:22
  • If there's a pending update, or feature install, you cannot install another feature until it restarts. – Davidw Apr 28 '14 at 5:01
  • 1
    @NathanC I already restarted it 3 times now.... and there are no pending updates. – Nobleleader13245 Apr 28 '14 at 19:18
  • Disregard my last comment, it was for another question... I apologize... – Brad Bouchard May 1 '14 at 19:54
  • Please check the server manager - there should be a flag that tells you why the server wasn't able to proceed. – megamorf Mar 23 '15 at 9:48
0

Is it trying to add prerequisite features and restart first? I had a similar problem adding the WSUS role which was clashing when it also added the Windows Internal Database.

This guy mentions the error, but my solution was different. Instead of changing group policy, I had to actually provide the WID account access to the WID directory:

$WIDService = "MSSQL$MICROSOFT##WID"
$Acl = Get-Acl "D:\WID\Data"
$Acl.SetAccessRule((New-Object System.Security.AccessControl.FileSystemAccessRule($WIDService,"FullControl","Allow")))
Set-Acl "D:\WID\Data" $Acl

This isn't exactly your problem, but the symptom seems the same so it may lead you in the right direction at least.

0

I believe that the feature in powershell is named "wireless-networking", so the command would be "add-windowsfeature wireless-networking -restart"

0

I have received similarly obtuse messages from Windows before, when trying to install a service that is not supported on Windows Server Core.

If you are running Core edition, then the Wireless LAN service is not supported on core.

0

I'm pretty sure it's a stuck pending reboot request.

Go to "C:\Windows\WinSxS" and check if there's a pending.xml file. Delete that file and try rebooting again. If you're unable to delete that file, try deleting it offline. If it's a virtual server, simply map its virtual disk somewhere and delete the file that way.

protected by Community Jun 15 '17 at 19:57

Thank you for your interest in this question. Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).

Would you like to answer one of these unanswered questions instead?

Not the answer you're looking for? Browse other questions tagged or ask your own question.