После установки windows server 2012 r2 командная строка

All replies

• 1. it’s usual for server core 

  2. try to run server manager (just type servermanager in cmd)

  3. try to view installed GUI feature using powershell

  type powershell

  get-windowsfeature *GUI*

  verify that you have Server-Gui-Mgmt-Infra and Server-Gui-Shell  installed

  4. if 3 is false , install GUI features

  Install-WindowsFeature Server-Gui-Mgmt-Infra,Server-Gui-Shell -Restart

  ---

  Roman Levchenko, MCITP, MCTS http://www.rlevchenko.com

  • Edited by

    Thursday, February 27, 2014 6:13 AM

  • Proposed as answer by
    R.LevchenkoMVP
    Thursday, February 27, 2014 6:37 AM

• • Proposed as answer by
    Agasthya.S.P
    Wednesday, February 3, 2016 8:23 PM

• hi,

  cmd > powershell

  In powershell:

  Install-WindowsFeature Server-Gui-Mgmt-Infra,Server-Gui-Shell -Restart

• Neither worked, all unrecognized

• it’s installing, I’m must have typed something wrong

• It’s installing now, I must have typed something wrong

• If you found a post to be the answer, please mark it appropriately.  It helps to keep the forums tidy by highlighting which response is the answer to the question.  It helps future readers.  Thanks!

  ---

  — Chris Ream —

  **Remember, if you find a post that is helpful, or is the answer, please mark it appropriately.**

• I’m back to the same place.  I need to remove powershell, so I can install GUI version of Active Directory users and computers

• No, you don’t need to remove PowerShell.

  Do you want a core installation or a GUI installation?  The default installation will be core, i.e. no GUI installed.  But, it is possible to install the GUI using PowerShell or DISM afterwards.  From the difficulties you are experiencing,
  I would recommend that you either re-do your installation one more time, making sure you have selected the option to install with GUI instead of taking the default which is the core installation.

  The fact that you say that the command recommended by Roman returns unrecognized to you, I would ask if you are sure you are installing Windows Server and not Hyper-V Server.  Windows Server would recognize the command Roman provided.  What’s the
  name of the ISO file you are using for installation?

  ---

  .:|:.:|:. tim

  • Proposed as answer by
    Susie Long
    Wednesday, March 5, 2014 9:00 AM

• Hi,

  Do you have any progresses on this issue by now?

  Please feel free to let us know if this issue persists.

  Best Regards,

  Amy Wang

• I want to run Windows Server 2012 normally, with GUI

  It was installed and I was going through installing Active Directory Domain Services and upon finishing I did not see Active Directory Users and Computers, upon rebooting I get the cmd prompt and can’t go any farther

• Look you should install the server fresh but do not chose core as they only installs the basic core of Hyper-V for a server farm

  ---

  The above doesn’t make any sense at all.

• Corret Paul in Hyper-V we can only install basic core.

  Thanks

  NM

  ---

  Warm Regards, Niraj Mehta

• thanks for this info.  worked great!

• hi 

  i am still seeing this problem which i have told you before plz resolve this issue which i am looking on my desktop. i want to say again that when i boot my server microsoft window server 2012 but it still shows me a window where it shows powershell dos
  prompt message still. plz can you explain that which command i must apply that clear my desktop and i may use my server

  Regards

  iffi

• hi 

  i am still seeing this problem which i have told you before plz resolve this issue which i am looking on my desktop. i want to say again that when i boot my server microsoft window server 2012 but it still shows me a window where it shows powershell dos
  prompt message still. plz can you explain that which command i must apply that clear my desktop and i may use my server

  Regards

  iffi

• iffi,

  You have not provided any information about what you installed or your configuration.  Have you tried the various commands that are shown in the responses to this post?  Those commands are what will add the GUI to a Windows Server 2012 R2 core
  installation.  If you have installed Hyper-V Server, there is nothing you can do to create a GUI.  But we don’t have any information about your installation.

  ---

  . : | : . : | : . tim

• I managed to have this happen to me after installing the full GUI version of the OS.  Don’t ask how, its embarrassing! lol

  Anyway, PowerShell would not function so Install-Feature was not an option.  Server manager would not open so, enabling features with the UI was not an option.  In fact, nothing would run from the command prompt except taskmgr.  

  The solution was to run the following command from the command prompt that had opened when I logged into the server:

  Dism /online /enable-feature /featurename:Server-Gui-Mgmt /featurename:Server-Gui-Shell /featurename:ServerCore-FullServer /all

  This installed the GUI features and all the requisites for those features. 

  Once the installation is complete, which will take quite awhile, reboot the server with the command
  shutdown /r /t 0  This shuts the server down for reboot with a wait time of zero (immediate).
  

  You should be back in business after the reboot.

  • Edited by
    EVC
    Tuesday, January 26, 2016 3:23 PM
  • Proposed as answer by
    Vimal Thiagaraj
    Tuesday, February 9, 2016 7:10 AM

• Thanks for the post. This did work out for me perfectly.

• Does anyone know the root cause of this? I have ran into the exact same situation that you described. Currently running the command you listed, and it is working.

• It may be embarrassing, but I’m seeing this issue as well and perhaps I could benefit from the info.

• I think it has something to do with the loss or corruption of the .Net 4 feature. Just my best guess.

• I ran into the same problem and found it easier to download the non-core version and upgrade.

  ---

  R, J

• I ran into the same problem and found it easier to download the non-core version and upgrade.

  ---

  R, J

   Where did you find that? It might be a good idea to include that info.

  ---

  Bill

• thing is, it WAS a full install. I believe the removal of dot net 4.5 is the key. Engineer installing some software removed 4.5 and that’s when the issue happens. The above DISM command cleared it up.

• If my solution worked please put a vote for it so others know to use it.  Someone just mentioned .Net 4 as well.  I’m really thinking this has something to do with .Net 4 being removed.  When this happened to me, I was messing around with
  .Net 4 due to a compatibility issue with a piece of software. 

• i had the same problem here . i tried to remove the .net framework 4.5 on server manager than the server rebooted and came with the same issue. only started in command prompt. nothing is available. not powershell not server manager. if you do ctrl alt end
  you can go to task manager and start firefox.exe for example you can download .netframework install it but after reboot stays the same. you can try install .netframework on prompt command but wont work. i used the command above listed  
  Dism /online /enable-feature /featurename:Server-Gui-Mgmt /featurename:Server-Gui-Shell /featurename:ServerCore-FullServer /all    
  after a few seconds asked if i wanted to rebbot. said yes and voila. everithing is back.

  thank you so much guys…

  • Proposed as answer by
    Tryggr
    Tuesday, June 28, 2016 3:22 PM
  • Unproposed as answer by
    Tryggr
    Tuesday, June 28, 2016 3:23 PM

• Thanks a Lot EVC… It Worked for me ..Appreciate your Help …!!!!!

• I work in a LAB with an MSDN license. I’m probably the wrong person to ask that question. On that note, if you have an MSDN subcription, just download one that isn’t a core and install over the top of the core to give it a GUI (the easy way). As shown
  here, there are other ways. I did not find them particularly convenient other than it forced me to learn a bunch of basic Powershell commands (such as Restart-Computer, Stop-Computer, and so on).

  ---

  R, J

  • Edited by
    Crakdkorn
    Sunday, June 5, 2016 6:57 PM

• Tried the reinstallation of GUI twice and still back at the black screen with cmd window. Restarted several times. The OS in question is Windows Server 2012. Please help.

  Regards,

  AR

• Tried the reinstallation of GUI twice and still back at the black screen with cmd window. Restarted several times. The OS in question is Windows Server 2012. Please help.

  Regards,

  AR

• Have you followed the suggestions in the old post?  By replying to an old post, it is hard to tell what you have done.

  From where did you obtain the distribution you are using?  During the installation, are you sure you did NOT select the default installation option?  There are four selections — Std Core, Std, Datacenter Core, and Datacenter.  If you accept
  the default, you will get core, which means no GUI.

  What steps did you follow?

  ---

  . : | : . : | : . tim

• I had to run the DISM command that EVC proposed, which took an extremely long time to run. It hangs on black screens for 5+ minutes, so it looks concerning. But with patience it finally completed. Once it came back up the Server Manager was very slow
  to load, but did come up. I still didn’t have the full GUI though. Checked via powershell and the 2 gui features were «available» but not installed. Followed the steps from
  R.Levchenko and now everything is back up and running. Thanks everyone.

• This was the one for me. Many thanks!

• Dism /online /enable-feature /featurename:Server-Gui-Mgmt /featurename:Server-Gui-Shell /featurename:ServerCore-FullServer /all

  This resolved my issue thanks Vimalanathan Sigamani T

  ---

  dd

  • Edited by
    Grandotto
    Thursday, August 18, 2016 12:16 AM

• Dism /online /enable-feature /featurename:Server-Gui-Mgmt
  /featurename:Server-Gui-Shell /featurename:ServerCore-FullServer /all

  This worked for me as well.  Thanks guys

• Thanks Vimalanathan,

  This really helped me and fixed the issue.

• This worked perfectly for me. Seems the admin that I gave the server to might have removed dot net 4.5.

  ---

  jimmypi

• I managed to have this happen to me after installing the full GUI version of the OS.  Don’t ask how, its embarrassing! lol

  Anyway, PowerShell would not function so Install-Feature was not an option.  Server manager would not open so, enabling features with the UI was not an option.  In fact, nothing would run from the command prompt except taskmgr.  

  The solution was to run the following command from the command prompt that had opened when I logged into the server:

  Dism /online /enable-feature /featurename:Server-Gui-Mgmt /featurename:Server-Gui-Shell /featurename:ServerCore-FullServer /all

  This installed the GUI features and all the requisites for those features. 

  Once the installation is complete, which will take quite awhile, reboot the server with the command
  shutdown /r /t 0  This shuts the server down for reboot with a wait time of zero (immediate).
  

  You should be back in business after the reboot.

  This seems to be working for me now. The previous commands did not work. But this is actually installing now.

  I agree that it has something to do with the removal of .NET 4.0/4.5. I was trying to uninstall/reinstall IIS because a contractor royally screwed up the server by installing Apache. We use IIS on everything, so I’m trying to undo everything he did. Apparently
  I unintentionally (not knowingly) removed a vital piece of the Server puzzle by uninstalling (removing) .NET 3.5 and .NET 4.5 when I uninstalled IIS. Everything was fine until the reboot.

  TL;DR

  If you blew out .NET 4.5, EVC’s solution is the one you need. Forget everything else in this thread.

  • Edited by
    Kim Dorris
    Saturday, October 15, 2016 4:09 AM
    correct typos

• You’re right, I did remove .NET 4 feature and suddenly all were gone except for Command Prompt. Your answer do the trick. Thanks.

• Wow, it works. The latest release will prompt to restart the server. Someone ruined the .NET Framework 4.5 and after uninstalling the .NET Framework, I ruined the server LOL. Thanks EVC. 

• I agree. same thing happened here too.

• if this does not work. try this:

  https://www.linkedin.com/pulse/20140618170857-12975178-procedure-to-recover-gui-in-windows-2012-and-2012r2-net-framework-feature-dependency-in-windows-2012-2012-r2

• if this does not work,   try this:

  https://www.linkedin.com/pulse/20140618170857-12975178-procedure-to-recover-gui-in-windows-2012-and-2012r2-net-framework-feature-dependency-in-windows-2012-2012-r2

• Thank you for this post!  A year later and it saved me.

• Thanks guys… I was also facing same issue and tried this solution.. It perfectly worked for me.

  Thanks again.

• Thanks a ton for the solution, it saved my day.

• I had this problem today I try the steps Don’t work for me

• Yes, that was exactly what happened to me. Trying to install .NET 3.5 was not working, I thought had something to do with having a newer version and I went and removed .NET 4.0. BOOM no more GUI. Thanks for the solutions. It worked like a charm.

• You can do it in 4 simple steps using powershell.

  Just follow the below instructions and you are done.

  1. c:useradministratoripowershell

  2. c:useradministratorImport-Module
  Servermanager

  3.
  c:useradministratorInstall-WindowsFeature
  Server-Gui-Mgmt-Infra,Server-Gui-Shell –Source wim:d:sourcesinstall.wim:4

  
  4.c:useradministratorshutdown
  /r /t 0 (Restart the server)

  Thank me Later

  • Edited by
    RaviBhati
    Thursday, May 31, 2018 7:33 AM

• The cmd mentioned before 

  cmd > powershell

  In powershell:

  Install-WindowsFeature Server-Gui-Mgmt-Infra,Server-Gui-Shell -Restart

  It worked for me. Just be patient. It takes about 15 minutes after it gets stuck at 68% to process it. Thank you! Nivi

  • Edited by
    TechSuperMario
    Tuesday, October 22, 2019 12:46 AM

All replies

• 1. it’s usual for server core 

  2. try to run server manager (just type servermanager in cmd)

  3. try to view installed GUI feature using powershell

  type powershell

  get-windowsfeature *GUI*

  verify that you have Server-Gui-Mgmt-Infra and Server-Gui-Shell  installed

  4. if 3 is false , install GUI features

  Install-WindowsFeature Server-Gui-Mgmt-Infra,Server-Gui-Shell -Restart

  ---

  Roman Levchenko, MCITP, MCTS http://www.rlevchenko.com

  • Edited by

    Thursday, February 27, 2014 6:13 AM

  • Proposed as answer by
    R.LevchenkoMVP
    Thursday, February 27, 2014 6:37 AM

• • Proposed as answer by
    Agasthya.S.P
    Wednesday, February 3, 2016 8:23 PM

• hi,

  cmd > powershell

  In powershell:

  Install-WindowsFeature Server-Gui-Mgmt-Infra,Server-Gui-Shell -Restart

• Neither worked, all unrecognized

• it’s installing, I’m must have typed something wrong

• It’s installing now, I must have typed something wrong

• If you found a post to be the answer, please mark it appropriately.  It helps to keep the forums tidy by highlighting which response is the answer to the question.  It helps future readers.  Thanks!

  ---

  — Chris Ream —

  **Remember, if you find a post that is helpful, or is the answer, please mark it appropriately.**

• I’m back to the same place.  I need to remove powershell, so I can install GUI version of Active Directory users and computers

• No, you don’t need to remove PowerShell.

  Do you want a core installation or a GUI installation?  The default installation will be core, i.e. no GUI installed.  But, it is possible to install the GUI using PowerShell or DISM afterwards.  From the difficulties you are experiencing,
  I would recommend that you either re-do your installation one more time, making sure you have selected the option to install with GUI instead of taking the default which is the core installation.

  The fact that you say that the command recommended by Roman returns unrecognized to you, I would ask if you are sure you are installing Windows Server and not Hyper-V Server.  Windows Server would recognize the command Roman provided.  What’s the
  name of the ISO file you are using for installation?

  ---

  .:|:.:|:. tim

  • Proposed as answer by
    Susie Long
    Wednesday, March 5, 2014 9:00 AM

• Hi,

  Do you have any progresses on this issue by now?

  Please feel free to let us know if this issue persists.

  Best Regards,

  Amy Wang

• I want to run Windows Server 2012 normally, with GUI

  It was installed and I was going through installing Active Directory Domain Services and upon finishing I did not see Active Directory Users and Computers, upon rebooting I get the cmd prompt and can’t go any farther

• Look you should install the server fresh but do not chose core as they only installs the basic core of Hyper-V for a server farm

  ---

  The above doesn’t make any sense at all.

• Corret Paul in Hyper-V we can only install basic core.

  Thanks

  NM

  ---

  Warm Regards, Niraj Mehta

• thanks for this info.  worked great!

• hi 

  i am still seeing this problem which i have told you before plz resolve this issue which i am looking on my desktop. i want to say again that when i boot my server microsoft window server 2012 but it still shows me a window where it shows powershell dos
  prompt message still. plz can you explain that which command i must apply that clear my desktop and i may use my server

  Regards

  iffi

• hi 

  i am still seeing this problem which i have told you before plz resolve this issue which i am looking on my desktop. i want to say again that when i boot my server microsoft window server 2012 but it still shows me a window where it shows powershell dos
  prompt message still. plz can you explain that which command i must apply that clear my desktop and i may use my server

  Regards

  iffi

• iffi,

  You have not provided any information about what you installed or your configuration.  Have you tried the various commands that are shown in the responses to this post?  Those commands are what will add the GUI to a Windows Server 2012 R2 core
  installation.  If you have installed Hyper-V Server, there is nothing you can do to create a GUI.  But we don’t have any information about your installation.

  ---

  . : | : . : | : . tim

• I managed to have this happen to me after installing the full GUI version of the OS.  Don’t ask how, its embarrassing! lol

  Anyway, PowerShell would not function so Install-Feature was not an option.  Server manager would not open so, enabling features with the UI was not an option.  In fact, nothing would run from the command prompt except taskmgr.  

  The solution was to run the following command from the command prompt that had opened when I logged into the server:

  Dism /online /enable-feature /featurename:Server-Gui-Mgmt /featurename:Server-Gui-Shell /featurename:ServerCore-FullServer /all

  This installed the GUI features and all the requisites for those features. 

  Once the installation is complete, which will take quite awhile, reboot the server with the command
  shutdown /r /t 0  This shuts the server down for reboot with a wait time of zero (immediate).
  

  You should be back in business after the reboot.

  • Edited by
    EVC
    Tuesday, January 26, 2016 3:23 PM
  • Proposed as answer by
    Vimal Thiagaraj
    Tuesday, February 9, 2016 7:10 AM

• Thanks for the post. This did work out for me perfectly.

• Does anyone know the root cause of this? I have ran into the exact same situation that you described. Currently running the command you listed, and it is working.

• It may be embarrassing, but I’m seeing this issue as well and perhaps I could benefit from the info.

• I think it has something to do with the loss or corruption of the .Net 4 feature. Just my best guess.

• I ran into the same problem and found it easier to download the non-core version and upgrade.

  ---

  R, J

• I ran into the same problem and found it easier to download the non-core version and upgrade.

  ---

  R, J

   Where did you find that? It might be a good idea to include that info.

  ---

  Bill

• thing is, it WAS a full install. I believe the removal of dot net 4.5 is the key. Engineer installing some software removed 4.5 and that’s when the issue happens. The above DISM command cleared it up.

• If my solution worked please put a vote for it so others know to use it.  Someone just mentioned .Net 4 as well.  I’m really thinking this has something to do with .Net 4 being removed.  When this happened to me, I was messing around with
  .Net 4 due to a compatibility issue with a piece of software. 

• i had the same problem here . i tried to remove the .net framework 4.5 on server manager than the server rebooted and came with the same issue. only started in command prompt. nothing is available. not powershell not server manager. if you do ctrl alt end
  you can go to task manager and start firefox.exe for example you can download .netframework install it but after reboot stays the same. you can try install .netframework on prompt command but wont work. i used the command above listed  
  Dism /online /enable-feature /featurename:Server-Gui-Mgmt /featurename:Server-Gui-Shell /featurename:ServerCore-FullServer /all    
  after a few seconds asked if i wanted to rebbot. said yes and voila. everithing is back.

  thank you so much guys…

  • Proposed as answer by
    Tryggr
    Tuesday, June 28, 2016 3:22 PM
  • Unproposed as answer by
    Tryggr
    Tuesday, June 28, 2016 3:23 PM

• Thanks a Lot EVC… It Worked for me ..Appreciate your Help …!!!!!

• I work in a LAB with an MSDN license. I’m probably the wrong person to ask that question. On that note, if you have an MSDN subcription, just download one that isn’t a core and install over the top of the core to give it a GUI (the easy way). As shown
  here, there are other ways. I did not find them particularly convenient other than it forced me to learn a bunch of basic Powershell commands (such as Restart-Computer, Stop-Computer, and so on).

  ---

  R, J

  • Edited by
    Crakdkorn
    Sunday, June 5, 2016 6:57 PM

• Tried the reinstallation of GUI twice and still back at the black screen with cmd window. Restarted several times. The OS in question is Windows Server 2012. Please help.

  Regards,

  AR

• Tried the reinstallation of GUI twice and still back at the black screen with cmd window. Restarted several times. The OS in question is Windows Server 2012. Please help.

  Regards,

  AR

• Have you followed the suggestions in the old post?  By replying to an old post, it is hard to tell what you have done.

  From where did you obtain the distribution you are using?  During the installation, are you sure you did NOT select the default installation option?  There are four selections — Std Core, Std, Datacenter Core, and Datacenter.  If you accept
  the default, you will get core, which means no GUI.

  What steps did you follow?

  ---

  . : | : . : | : . tim

• I had to run the DISM command that EVC proposed, which took an extremely long time to run. It hangs on black screens for 5+ minutes, so it looks concerning. But with patience it finally completed. Once it came back up the Server Manager was very slow
  to load, but did come up. I still didn’t have the full GUI though. Checked via powershell and the 2 gui features were «available» but not installed. Followed the steps from
  R.Levchenko and now everything is back up and running. Thanks everyone.

• This was the one for me. Many thanks!

• Dism /online /enable-feature /featurename:Server-Gui-Mgmt /featurename:Server-Gui-Shell /featurename:ServerCore-FullServer /all

  This resolved my issue thanks Vimalanathan Sigamani T

  ---

  dd

  • Edited by
    Grandotto
    Thursday, August 18, 2016 12:16 AM

• Dism /online /enable-feature /featurename:Server-Gui-Mgmt
  /featurename:Server-Gui-Shell /featurename:ServerCore-FullServer /all

  This worked for me as well.  Thanks guys

• Thanks Vimalanathan,

  This really helped me and fixed the issue.

• This worked perfectly for me. Seems the admin that I gave the server to might have removed dot net 4.5.

  ---

  jimmypi

• I managed to have this happen to me after installing the full GUI version of the OS.  Don’t ask how, its embarrassing! lol

  Anyway, PowerShell would not function so Install-Feature was not an option.  Server manager would not open so, enabling features with the UI was not an option.  In fact, nothing would run from the command prompt except taskmgr.  

  The solution was to run the following command from the command prompt that had opened when I logged into the server:

  Dism /online /enable-feature /featurename:Server-Gui-Mgmt /featurename:Server-Gui-Shell /featurename:ServerCore-FullServer /all

  This installed the GUI features and all the requisites for those features. 

  Once the installation is complete, which will take quite awhile, reboot the server with the command
  shutdown /r /t 0  This shuts the server down for reboot with a wait time of zero (immediate).
  

  You should be back in business after the reboot.

  This seems to be working for me now. The previous commands did not work. But this is actually installing now.

  I agree that it has something to do with the removal of .NET 4.0/4.5. I was trying to uninstall/reinstall IIS because a contractor royally screwed up the server by installing Apache. We use IIS on everything, so I’m trying to undo everything he did. Apparently
  I unintentionally (not knowingly) removed a vital piece of the Server puzzle by uninstalling (removing) .NET 3.5 and .NET 4.5 when I uninstalled IIS. Everything was fine until the reboot.

  TL;DR

  If you blew out .NET 4.5, EVC’s solution is the one you need. Forget everything else in this thread.

  • Edited by
    Kim Dorris
    Saturday, October 15, 2016 4:09 AM
    correct typos

• You’re right, I did remove .NET 4 feature and suddenly all were gone except for Command Prompt. Your answer do the trick. Thanks.

• Wow, it works. The latest release will prompt to restart the server. Someone ruined the .NET Framework 4.5 and after uninstalling the .NET Framework, I ruined the server LOL. Thanks EVC. 

• I agree. same thing happened here too.

• if this does not work. try this:

  https://www.linkedin.com/pulse/20140618170857-12975178-procedure-to-recover-gui-in-windows-2012-and-2012r2-net-framework-feature-dependency-in-windows-2012-2012-r2

• if this does not work,   try this:

  https://www.linkedin.com/pulse/20140618170857-12975178-procedure-to-recover-gui-in-windows-2012-and-2012r2-net-framework-feature-dependency-in-windows-2012-2012-r2

• Thank you for this post!  A year later and it saved me.

• Thanks guys… I was also facing same issue and tried this solution.. It perfectly worked for me.

  Thanks again.

• Thanks a ton for the solution, it saved my day.

• I had this problem today I try the steps Don’t work for me

• Yes, that was exactly what happened to me. Trying to install .NET 3.5 was not working, I thought had something to do with having a newer version and I went and removed .NET 4.0. BOOM no more GUI. Thanks for the solutions. It worked like a charm.

• You can do it in 4 simple steps using powershell.

  Just follow the below instructions and you are done.

  1. c:useradministratoripowershell

  2. c:useradministratorImport-Module
  Servermanager

  3.
  c:useradministratorInstall-WindowsFeature
  Server-Gui-Mgmt-Infra,Server-Gui-Shell –Source wim:d:sourcesinstall.wim:4

  
  4.c:useradministratorshutdown
  /r /t 0 (Restart the server)

  Thank me Later

  • Edited by
    RaviBhati
    Thursday, May 31, 2018 7:33 AM

• The cmd mentioned before 

  cmd > powershell

  In powershell:

  Install-WindowsFeature Server-Gui-Mgmt-Infra,Server-Gui-Shell -Restart

  It worked for me. Just be patient. It takes about 15 minutes after it gets stuck at 68% to process it. Thank you! Nivi

  • Edited by
    TechSuperMario
    Tuesday, October 22, 2019 12:46 AM

All replies

• 1. it’s usual for server core 

  2. try to run server manager (just type servermanager in cmd)

  3. try to view installed GUI feature using powershell

  type powershell

  get-windowsfeature *GUI*

  verify that you have Server-Gui-Mgmt-Infra and Server-Gui-Shell  installed

  4. if 3 is false , install GUI features

  Install-WindowsFeature Server-Gui-Mgmt-Infra,Server-Gui-Shell -Restart

  ---

  Roman Levchenko, MCITP, MCTS http://www.rlevchenko.com

  • Edited by

    Thursday, February 27, 2014 6:13 AM

  • Proposed as answer by
    R.LevchenkoMVP
    Thursday, February 27, 2014 6:37 AM

• • Proposed as answer by
    Agasthya.S.P
    Wednesday, February 3, 2016 8:23 PM

• hi,

  cmd > powershell

  In powershell:

  Install-WindowsFeature Server-Gui-Mgmt-Infra,Server-Gui-Shell -Restart

• Neither worked, all unrecognized

• it’s installing, I’m must have typed something wrong

• It’s installing now, I must have typed something wrong

• If you found a post to be the answer, please mark it appropriately.  It helps to keep the forums tidy by highlighting which response is the answer to the question.  It helps future readers.  Thanks!

  ---

  — Chris Ream —

  **Remember, if you find a post that is helpful, or is the answer, please mark it appropriately.**

• I’m back to the same place.  I need to remove powershell, so I can install GUI version of Active Directory users and computers

• No, you don’t need to remove PowerShell.

  Do you want a core installation or a GUI installation?  The default installation will be core, i.e. no GUI installed.  But, it is possible to install the GUI using PowerShell or DISM afterwards.  From the difficulties you are experiencing,
  I would recommend that you either re-do your installation one more time, making sure you have selected the option to install with GUI instead of taking the default which is the core installation.

  The fact that you say that the command recommended by Roman returns unrecognized to you, I would ask if you are sure you are installing Windows Server and not Hyper-V Server.  Windows Server would recognize the command Roman provided.  What’s the
  name of the ISO file you are using for installation?

  ---

  .:|:.:|:. tim

  • Proposed as answer by
    Susie Long
    Wednesday, March 5, 2014 9:00 AM

• Hi,

  Do you have any progresses on this issue by now?

  Please feel free to let us know if this issue persists.

  Best Regards,

  Amy Wang

• I want to run Windows Server 2012 normally, with GUI

  It was installed and I was going through installing Active Directory Domain Services and upon finishing I did not see Active Directory Users and Computers, upon rebooting I get the cmd prompt and can’t go any farther

• Look you should install the server fresh but do not chose core as they only installs the basic core of Hyper-V for a server farm

  ---

  The above doesn’t make any sense at all.

• Corret Paul in Hyper-V we can only install basic core.

  Thanks

  NM

  ---

  Warm Regards, Niraj Mehta

• thanks for this info.  worked great!

• hi 

  i am still seeing this problem which i have told you before plz resolve this issue which i am looking on my desktop. i want to say again that when i boot my server microsoft window server 2012 but it still shows me a window where it shows powershell dos
  prompt message still. plz can you explain that which command i must apply that clear my desktop and i may use my server

  Regards

  iffi

• hi 

  i am still seeing this problem which i have told you before plz resolve this issue which i am looking on my desktop. i want to say again that when i boot my server microsoft window server 2012 but it still shows me a window where it shows powershell dos
  prompt message still. plz can you explain that which command i must apply that clear my desktop and i may use my server

  Regards

  iffi

• iffi,

  You have not provided any information about what you installed or your configuration.  Have you tried the various commands that are shown in the responses to this post?  Those commands are what will add the GUI to a Windows Server 2012 R2 core
  installation.  If you have installed Hyper-V Server, there is nothing you can do to create a GUI.  But we don’t have any information about your installation.

  ---

  . : | : . : | : . tim

• I managed to have this happen to me after installing the full GUI version of the OS.  Don’t ask how, its embarrassing! lol

  Anyway, PowerShell would not function so Install-Feature was not an option.  Server manager would not open so, enabling features with the UI was not an option.  In fact, nothing would run from the command prompt except taskmgr.  

  The solution was to run the following command from the command prompt that had opened when I logged into the server:

  Dism /online /enable-feature /featurename:Server-Gui-Mgmt /featurename:Server-Gui-Shell /featurename:ServerCore-FullServer /all

  This installed the GUI features and all the requisites for those features. 

  Once the installation is complete, which will take quite awhile, reboot the server with the command
  shutdown /r /t 0  This shuts the server down for reboot with a wait time of zero (immediate).
  

  You should be back in business after the reboot.

  • Edited by
    EVC
    Tuesday, January 26, 2016 3:23 PM
  • Proposed as answer by
    Vimal Thiagaraj
    Tuesday, February 9, 2016 7:10 AM

• Thanks for the post. This did work out for me perfectly.

• Does anyone know the root cause of this? I have ran into the exact same situation that you described. Currently running the command you listed, and it is working.

• It may be embarrassing, but I’m seeing this issue as well and perhaps I could benefit from the info.

• I think it has something to do with the loss or corruption of the .Net 4 feature. Just my best guess.

• I ran into the same problem and found it easier to download the non-core version and upgrade.

  ---

  R, J

• I ran into the same problem and found it easier to download the non-core version and upgrade.

  ---

  R, J

   Where did you find that? It might be a good idea to include that info.

  ---

  Bill

• thing is, it WAS a full install. I believe the removal of dot net 4.5 is the key. Engineer installing some software removed 4.5 and that’s when the issue happens. The above DISM command cleared it up.

• If my solution worked please put a vote for it so others know to use it.  Someone just mentioned .Net 4 as well.  I’m really thinking this has something to do with .Net 4 being removed.  When this happened to me, I was messing around with
  .Net 4 due to a compatibility issue with a piece of software. 

• i had the same problem here . i tried to remove the .net framework 4.5 on server manager than the server rebooted and came with the same issue. only started in command prompt. nothing is available. not powershell not server manager. if you do ctrl alt end
  you can go to task manager and start firefox.exe for example you can download .netframework install it but after reboot stays the same. you can try install .netframework on prompt command but wont work. i used the command above listed  
  Dism /online /enable-feature /featurename:Server-Gui-Mgmt /featurename:Server-Gui-Shell /featurename:ServerCore-FullServer /all    
  after a few seconds asked if i wanted to rebbot. said yes and voila. everithing is back.

  thank you so much guys…

  • Proposed as answer by
    Tryggr
    Tuesday, June 28, 2016 3:22 PM
  • Unproposed as answer by
    Tryggr
    Tuesday, June 28, 2016 3:23 PM

• Thanks a Lot EVC… It Worked for me ..Appreciate your Help …!!!!!

• I work in a LAB with an MSDN license. I’m probably the wrong person to ask that question. On that note, if you have an MSDN subcription, just download one that isn’t a core and install over the top of the core to give it a GUI (the easy way). As shown
  here, there are other ways. I did not find them particularly convenient other than it forced me to learn a bunch of basic Powershell commands (such as Restart-Computer, Stop-Computer, and so on).

  ---

  R, J

  • Edited by
    Crakdkorn
    Sunday, June 5, 2016 6:57 PM

• Tried the reinstallation of GUI twice and still back at the black screen with cmd window. Restarted several times. The OS in question is Windows Server 2012. Please help.

  Regards,

  AR

• Tried the reinstallation of GUI twice and still back at the black screen with cmd window. Restarted several times. The OS in question is Windows Server 2012. Please help.

  Regards,

  AR

• Have you followed the suggestions in the old post?  By replying to an old post, it is hard to tell what you have done.

  From where did you obtain the distribution you are using?  During the installation, are you sure you did NOT select the default installation option?  There are four selections — Std Core, Std, Datacenter Core, and Datacenter.  If you accept
  the default, you will get core, which means no GUI.

  What steps did you follow?

  ---

  . : | : . : | : . tim

• I had to run the DISM command that EVC proposed, which took an extremely long time to run. It hangs on black screens for 5+ minutes, so it looks concerning. But with patience it finally completed. Once it came back up the Server Manager was very slow
  to load, but did come up. I still didn’t have the full GUI though. Checked via powershell and the 2 gui features were «available» but not installed. Followed the steps from
  R.Levchenko and now everything is back up and running. Thanks everyone.

• This was the one for me. Many thanks!

• Dism /online /enable-feature /featurename:Server-Gui-Mgmt /featurename:Server-Gui-Shell /featurename:ServerCore-FullServer /all

  This resolved my issue thanks Vimalanathan Sigamani T

  ---

  dd

  • Edited by
    Grandotto
    Thursday, August 18, 2016 12:16 AM

• Dism /online /enable-feature /featurename:Server-Gui-Mgmt
  /featurename:Server-Gui-Shell /featurename:ServerCore-FullServer /all

  This worked for me as well.  Thanks guys

• Thanks Vimalanathan,

  This really helped me and fixed the issue.

• This worked perfectly for me. Seems the admin that I gave the server to might have removed dot net 4.5.

  ---

  jimmypi

• I managed to have this happen to me after installing the full GUI version of the OS.  Don’t ask how, its embarrassing! lol

  Anyway, PowerShell would not function so Install-Feature was not an option.  Server manager would not open so, enabling features with the UI was not an option.  In fact, nothing would run from the command prompt except taskmgr.  

  The solution was to run the following command from the command prompt that had opened when I logged into the server:

  Dism /online /enable-feature /featurename:Server-Gui-Mgmt /featurename:Server-Gui-Shell /featurename:ServerCore-FullServer /all

  This installed the GUI features and all the requisites for those features. 

  Once the installation is complete, which will take quite awhile, reboot the server with the command
  shutdown /r /t 0  This shuts the server down for reboot with a wait time of zero (immediate).
  

  You should be back in business after the reboot.

  This seems to be working for me now. The previous commands did not work. But this is actually installing now.

  I agree that it has something to do with the removal of .NET 4.0/4.5. I was trying to uninstall/reinstall IIS because a contractor royally screwed up the server by installing Apache. We use IIS on everything, so I’m trying to undo everything he did. Apparently
  I unintentionally (not knowingly) removed a vital piece of the Server puzzle by uninstalling (removing) .NET 3.5 and .NET 4.5 when I uninstalled IIS. Everything was fine until the reboot.

  TL;DR

  If you blew out .NET 4.5, EVC’s solution is the one you need. Forget everything else in this thread.

  • Edited by
    Kim Dorris
    Saturday, October 15, 2016 4:09 AM
    correct typos

• You’re right, I did remove .NET 4 feature and suddenly all were gone except for Command Prompt. Your answer do the trick. Thanks.

• Wow, it works. The latest release will prompt to restart the server. Someone ruined the .NET Framework 4.5 and after uninstalling the .NET Framework, I ruined the server LOL. Thanks EVC. 

• I agree. same thing happened here too.

• if this does not work. try this:

  https://www.linkedin.com/pulse/20140618170857-12975178-procedure-to-recover-gui-in-windows-2012-and-2012r2-net-framework-feature-dependency-in-windows-2012-2012-r2

• if this does not work,   try this:

  https://www.linkedin.com/pulse/20140618170857-12975178-procedure-to-recover-gui-in-windows-2012-and-2012r2-net-framework-feature-dependency-in-windows-2012-2012-r2

• Thank you for this post!  A year later and it saved me.

• Thanks guys… I was also facing same issue and tried this solution.. It perfectly worked for me.

  Thanks again.

• Thanks a ton for the solution, it saved my day.

• I had this problem today I try the steps Don’t work for me

• Yes, that was exactly what happened to me. Trying to install .NET 3.5 was not working, I thought had something to do with having a newer version and I went and removed .NET 4.0. BOOM no more GUI. Thanks for the solutions. It worked like a charm.

• You can do it in 4 simple steps using powershell.

  Just follow the below instructions and you are done.

  1. c:useradministratoripowershell

  2. c:useradministratorImport-Module
  Servermanager

  3.
  c:useradministratorInstall-WindowsFeature
  Server-Gui-Mgmt-Infra,Server-Gui-Shell –Source wim:d:sourcesinstall.wim:4

  
  4.c:useradministratorshutdown
  /r /t 0 (Restart the server)

  Thank me Later

  • Edited by
    RaviBhati
    Thursday, May 31, 2018 7:33 AM

• The cmd mentioned before 

  cmd > powershell

  In powershell:

  Install-WindowsFeature Server-Gui-Mgmt-Infra,Server-Gui-Shell -Restart

  It worked for me. Just be patient. It takes about 15 minutes after it gets stuck at 68% to process it. Thank you! Nivi

  • Edited by
    TechSuperMario
    Tuesday, October 22, 2019 12:46 AM

All replies

• 1. it’s usual for server core 

  2. try to run server manager (just type servermanager in cmd)

  3. try to view installed GUI feature using powershell

  type powershell

  get-windowsfeature *GUI*

  verify that you have Server-Gui-Mgmt-Infra and Server-Gui-Shell  installed

  4. if 3 is false , install GUI features

  Install-WindowsFeature Server-Gui-Mgmt-Infra,Server-Gui-Shell -Restart

  ---

  Roman Levchenko, MCITP, MCTS http://www.rlevchenko.com

  • Edited by

    Thursday, February 27, 2014 6:13 AM

  • Proposed as answer by
    R.LevchenkoMVP
    Thursday, February 27, 2014 6:37 AM

• • Proposed as answer by
    Agasthya.S.P
    Wednesday, February 3, 2016 8:23 PM

• hi,

  cmd > powershell

  In powershell:

  Install-WindowsFeature Server-Gui-Mgmt-Infra,Server-Gui-Shell -Restart

• Neither worked, all unrecognized

• it’s installing, I’m must have typed something wrong

• It’s installing now, I must have typed something wrong

• If you found a post to be the answer, please mark it appropriately.  It helps to keep the forums tidy by highlighting which response is the answer to the question.  It helps future readers.  Thanks!

  ---

  — Chris Ream —

  **Remember, if you find a post that is helpful, or is the answer, please mark it appropriately.**

• I’m back to the same place.  I need to remove powershell, so I can install GUI version of Active Directory users and computers

• No, you don’t need to remove PowerShell.

  Do you want a core installation or a GUI installation?  The default installation will be core, i.e. no GUI installed.  But, it is possible to install the GUI using PowerShell or DISM afterwards.  From the difficulties you are experiencing,
  I would recommend that you either re-do your installation one more time, making sure you have selected the option to install with GUI instead of taking the default which is the core installation.

  The fact that you say that the command recommended by Roman returns unrecognized to you, I would ask if you are sure you are installing Windows Server and not Hyper-V Server.  Windows Server would recognize the command Roman provided.  What’s the
  name of the ISO file you are using for installation?

  ---

  .:|:.:|:. tim

  • Proposed as answer by
    Susie Long
    Wednesday, March 5, 2014 9:00 AM

• Hi,

  Do you have any progresses on this issue by now?

  Please feel free to let us know if this issue persists.

  Best Regards,

  Amy Wang

• I want to run Windows Server 2012 normally, with GUI

  It was installed and I was going through installing Active Directory Domain Services and upon finishing I did not see Active Directory Users and Computers, upon rebooting I get the cmd prompt and can’t go any farther

• Look you should install the server fresh but do not chose core as they only installs the basic core of Hyper-V for a server farm

  ---

  The above doesn’t make any sense at all.

• Corret Paul in Hyper-V we can only install basic core.

  Thanks

  NM

  ---

  Warm Regards, Niraj Mehta

• thanks for this info.  worked great!

• hi 

  i am still seeing this problem which i have told you before plz resolve this issue which i am looking on my desktop. i want to say again that when i boot my server microsoft window server 2012 but it still shows me a window where it shows powershell dos
  prompt message still. plz can you explain that which command i must apply that clear my desktop and i may use my server

  Regards

  iffi

• hi 

  i am still seeing this problem which i have told you before plz resolve this issue which i am looking on my desktop. i want to say again that when i boot my server microsoft window server 2012 but it still shows me a window where it shows powershell dos
  prompt message still. plz can you explain that which command i must apply that clear my desktop and i may use my server

  Regards

  iffi

• iffi,

  You have not provided any information about what you installed or your configuration.  Have you tried the various commands that are shown in the responses to this post?  Those commands are what will add the GUI to a Windows Server 2012 R2 core
  installation.  If you have installed Hyper-V Server, there is nothing you can do to create a GUI.  But we don’t have any information about your installation.

  ---

  . : | : . : | : . tim

• I managed to have this happen to me after installing the full GUI version of the OS.  Don’t ask how, its embarrassing! lol

  Anyway, PowerShell would not function so Install-Feature was not an option.  Server manager would not open so, enabling features with the UI was not an option.  In fact, nothing would run from the command prompt except taskmgr.  

  The solution was to run the following command from the command prompt that had opened when I logged into the server:

  Dism /online /enable-feature /featurename:Server-Gui-Mgmt /featurename:Server-Gui-Shell /featurename:ServerCore-FullServer /all

  This installed the GUI features and all the requisites for those features. 

  Once the installation is complete, which will take quite awhile, reboot the server with the command
  shutdown /r /t 0  This shuts the server down for reboot with a wait time of zero (immediate).
  

  You should be back in business after the reboot.

  • Edited by
    EVC
    Tuesday, January 26, 2016 3:23 PM
  • Proposed as answer by
    Vimal Thiagaraj
    Tuesday, February 9, 2016 7:10 AM

• Thanks for the post. This did work out for me perfectly.

• Does anyone know the root cause of this? I have ran into the exact same situation that you described. Currently running the command you listed, and it is working.

• It may be embarrassing, but I’m seeing this issue as well and perhaps I could benefit from the info.

• I think it has something to do with the loss or corruption of the .Net 4 feature. Just my best guess.

• I ran into the same problem and found it easier to download the non-core version and upgrade.

  ---

  R, J

• I ran into the same problem and found it easier to download the non-core version and upgrade.

  ---

  R, J

   Where did you find that? It might be a good idea to include that info.

  ---

  Bill

• thing is, it WAS a full install. I believe the removal of dot net 4.5 is the key. Engineer installing some software removed 4.5 and that’s when the issue happens. The above DISM command cleared it up.

• If my solution worked please put a vote for it so others know to use it.  Someone just mentioned .Net 4 as well.  I’m really thinking this has something to do with .Net 4 being removed.  When this happened to me, I was messing around with
  .Net 4 due to a compatibility issue with a piece of software. 

• i had the same problem here . i tried to remove the .net framework 4.5 on server manager than the server rebooted and came with the same issue. only started in command prompt. nothing is available. not powershell not server manager. if you do ctrl alt end
  you can go to task manager and start firefox.exe for example you can download .netframework install it but after reboot stays the same. you can try install .netframework on prompt command but wont work. i used the command above listed  
  Dism /online /enable-feature /featurename:Server-Gui-Mgmt /featurename:Server-Gui-Shell /featurename:ServerCore-FullServer /all    
  after a few seconds asked if i wanted to rebbot. said yes and voila. everithing is back.

  thank you so much guys…

  • Proposed as answer by
    Tryggr
    Tuesday, June 28, 2016 3:22 PM
  • Unproposed as answer by
    Tryggr
    Tuesday, June 28, 2016 3:23 PM

• Thanks a Lot EVC… It Worked for me ..Appreciate your Help …!!!!!

• I work in a LAB with an MSDN license. I’m probably the wrong person to ask that question. On that note, if you have an MSDN subcription, just download one that isn’t a core and install over the top of the core to give it a GUI (the easy way). As shown
  here, there are other ways. I did not find them particularly convenient other than it forced me to learn a bunch of basic Powershell commands (such as Restart-Computer, Stop-Computer, and so on).

  ---

  R, J

  • Edited by
    Crakdkorn
    Sunday, June 5, 2016 6:57 PM

• Tried the reinstallation of GUI twice and still back at the black screen with cmd window. Restarted several times. The OS in question is Windows Server 2012. Please help.

  Regards,

  AR

• Tried the reinstallation of GUI twice and still back at the black screen with cmd window. Restarted several times. The OS in question is Windows Server 2012. Please help.

  Regards,

  AR

• Have you followed the suggestions in the old post?  By replying to an old post, it is hard to tell what you have done.

  From where did you obtain the distribution you are using?  During the installation, are you sure you did NOT select the default installation option?  There are four selections — Std Core, Std, Datacenter Core, and Datacenter.  If you accept
  the default, you will get core, which means no GUI.

  What steps did you follow?

  ---

  . : | : . : | : . tim

• I had to run the DISM command that EVC proposed, which took an extremely long time to run. It hangs on black screens for 5+ minutes, so it looks concerning. But with patience it finally completed. Once it came back up the Server Manager was very slow
  to load, but did come up. I still didn’t have the full GUI though. Checked via powershell and the 2 gui features were «available» but not installed. Followed the steps from
  R.Levchenko and now everything is back up and running. Thanks everyone.

• This was the one for me. Many thanks!

• Dism /online /enable-feature /featurename:Server-Gui-Mgmt /featurename:Server-Gui-Shell /featurename:ServerCore-FullServer /all

  This resolved my issue thanks Vimalanathan Sigamani T

  ---

  dd

  • Edited by
    Grandotto
    Thursday, August 18, 2016 12:16 AM

• Dism /online /enable-feature /featurename:Server-Gui-Mgmt
  /featurename:Server-Gui-Shell /featurename:ServerCore-FullServer /all

  This worked for me as well.  Thanks guys

• Thanks Vimalanathan,

  This really helped me and fixed the issue.

• This worked perfectly for me. Seems the admin that I gave the server to might have removed dot net 4.5.

  ---

  jimmypi

• I managed to have this happen to me after installing the full GUI version of the OS.  Don’t ask how, its embarrassing! lol

  Anyway, PowerShell would not function so Install-Feature was not an option.  Server manager would not open so, enabling features with the UI was not an option.  In fact, nothing would run from the command prompt except taskmgr.  

  The solution was to run the following command from the command prompt that had opened when I logged into the server:

  Dism /online /enable-feature /featurename:Server-Gui-Mgmt /featurename:Server-Gui-Shell /featurename:ServerCore-FullServer /all

  This installed the GUI features and all the requisites for those features. 

  Once the installation is complete, which will take quite awhile, reboot the server with the command
  shutdown /r /t 0  This shuts the server down for reboot with a wait time of zero (immediate).
  

  You should be back in business after the reboot.

  This seems to be working for me now. The previous commands did not work. But this is actually installing now.

  I agree that it has something to do with the removal of .NET 4.0/4.5. I was trying to uninstall/reinstall IIS because a contractor royally screwed up the server by installing Apache. We use IIS on everything, so I’m trying to undo everything he did. Apparently
  I unintentionally (not knowingly) removed a vital piece of the Server puzzle by uninstalling (removing) .NET 3.5 and .NET 4.5 when I uninstalled IIS. Everything was fine until the reboot.

  TL;DR

  If you blew out .NET 4.5, EVC’s solution is the one you need. Forget everything else in this thread.

  • Edited by
    Kim Dorris
    Saturday, October 15, 2016 4:09 AM
    correct typos

• You’re right, I did remove .NET 4 feature and suddenly all were gone except for Command Prompt. Your answer do the trick. Thanks.

• Wow, it works. The latest release will prompt to restart the server. Someone ruined the .NET Framework 4.5 and after uninstalling the .NET Framework, I ruined the server LOL. Thanks EVC. 

• I agree. same thing happened here too.

• if this does not work. try this:

  https://www.linkedin.com/pulse/20140618170857-12975178-procedure-to-recover-gui-in-windows-2012-and-2012r2-net-framework-feature-dependency-in-windows-2012-2012-r2

• if this does not work,   try this:

  https://www.linkedin.com/pulse/20140618170857-12975178-procedure-to-recover-gui-in-windows-2012-and-2012r2-net-framework-feature-dependency-in-windows-2012-2012-r2

• Thank you for this post!  A year later and it saved me.

• Thanks guys… I was also facing same issue and tried this solution.. It perfectly worked for me.

  Thanks again.

• Thanks a ton for the solution, it saved my day.

• I had this problem today I try the steps Don’t work for me

• Yes, that was exactly what happened to me. Trying to install .NET 3.5 was not working, I thought had something to do with having a newer version and I went and removed .NET 4.0. BOOM no more GUI. Thanks for the solutions. It worked like a charm.

• You can do it in 4 simple steps using powershell.

  Just follow the below instructions and you are done.

  1. c:useradministratoripowershell

  2. c:useradministratorImport-Module
  Servermanager

  3.
  c:useradministratorInstall-WindowsFeature
  Server-Gui-Mgmt-Infra,Server-Gui-Shell –Source wim:d:sourcesinstall.wim:4

  
  4.c:useradministratorshutdown
  /r /t 0 (Restart the server)

  Thank me Later

  • Edited by
    RaviBhati
    Thursday, May 31, 2018 7:33 AM

• The cmd mentioned before 

  cmd > powershell

  In powershell:

  Install-WindowsFeature Server-Gui-Mgmt-Infra,Server-Gui-Shell -Restart

  It worked for me. Just be patient. It takes about 15 minutes after it gets stuck at 68% to process it. Thank you! Nivi

  • Edited by
    TechSuperMario
    Tuesday, October 22, 2019 12:46 AM

All replies

• 1. it’s usual for server core 

  2. try to run server manager (just type servermanager in cmd)

  3. try to view installed GUI feature using powershell

  type powershell

  get-windowsfeature *GUI*

  verify that you have Server-Gui-Mgmt-Infra and Server-Gui-Shell  installed

  4. if 3 is false , install GUI features

  Install-WindowsFeature Server-Gui-Mgmt-Infra,Server-Gui-Shell -Restart

  ---

  Roman Levchenko, MCITP, MCTS http://www.rlevchenko.com

  • Edited by

    Thursday, February 27, 2014 6:13 AM

  • Proposed as answer by
    R.LevchenkoMVP
    Thursday, February 27, 2014 6:37 AM

• • Proposed as answer by
    Agasthya.S.P
    Wednesday, February 3, 2016 8:23 PM

• hi,

  cmd > powershell

  In powershell:

  Install-WindowsFeature Server-Gui-Mgmt-Infra,Server-Gui-Shell -Restart

• Neither worked, all unrecognized

• it’s installing, I’m must have typed something wrong

• It’s installing now, I must have typed something wrong

• If you found a post to be the answer, please mark it appropriately.  It helps to keep the forums tidy by highlighting which response is the answer to the question.  It helps future readers.  Thanks!

  ---

  — Chris Ream —

  **Remember, if you find a post that is helpful, or is the answer, please mark it appropriately.**

• I’m back to the same place.  I need to remove powershell, so I can install GUI version of Active Directory users and computers

• No, you don’t need to remove PowerShell.

  Do you want a core installation or a GUI installation?  The default installation will be core, i.e. no GUI installed.  But, it is possible to install the GUI using PowerShell or DISM afterwards.  From the difficulties you are experiencing,
  I would recommend that you either re-do your installation one more time, making sure you have selected the option to install with GUI instead of taking the default which is the core installation.

  The fact that you say that the command recommended by Roman returns unrecognized to you, I would ask if you are sure you are installing Windows Server and not Hyper-V Server.  Windows Server would recognize the command Roman provided.  What’s the
  name of the ISO file you are using for installation?

  ---

  .:|:.:|:. tim

  • Proposed as answer by
    Susie Long
    Wednesday, March 5, 2014 9:00 AM

• Hi,

  Do you have any progresses on this issue by now?

  Please feel free to let us know if this issue persists.

  Best Regards,

  Amy Wang

• I want to run Windows Server 2012 normally, with GUI

  It was installed and I was going through installing Active Directory Domain Services and upon finishing I did not see Active Directory Users and Computers, upon rebooting I get the cmd prompt and can’t go any farther

• Look you should install the server fresh but do not chose core as they only installs the basic core of Hyper-V for a server farm

  ---

  The above doesn’t make any sense at all.

• Corret Paul in Hyper-V we can only install basic core.

  Thanks

  NM

  ---

  Warm Regards, Niraj Mehta

• thanks for this info.  worked great!

• hi 

  i am still seeing this problem which i have told you before plz resolve this issue which i am looking on my desktop. i want to say again that when i boot my server microsoft window server 2012 but it still shows me a window where it shows powershell dos
  prompt message still. plz can you explain that which command i must apply that clear my desktop and i may use my server

  Regards

  iffi

• hi 

  i am still seeing this problem which i have told you before plz resolve this issue which i am looking on my desktop. i want to say again that when i boot my server microsoft window server 2012 but it still shows me a window where it shows powershell dos
  prompt message still. plz can you explain that which command i must apply that clear my desktop and i may use my server

  Regards

  iffi

• iffi,

  You have not provided any information about what you installed or your configuration.  Have you tried the various commands that are shown in the responses to this post?  Those commands are what will add the GUI to a Windows Server 2012 R2 core
  installation.  If you have installed Hyper-V Server, there is nothing you can do to create a GUI.  But we don’t have any information about your installation.

  ---

  . : | : . : | : . tim

• I managed to have this happen to me after installing the full GUI version of the OS.  Don’t ask how, its embarrassing! lol

  Anyway, PowerShell would not function so Install-Feature was not an option.  Server manager would not open so, enabling features with the UI was not an option.  In fact, nothing would run from the command prompt except taskmgr.  

  The solution was to run the following command from the command prompt that had opened when I logged into the server:

  Dism /online /enable-feature /featurename:Server-Gui-Mgmt /featurename:Server-Gui-Shell /featurename:ServerCore-FullServer /all

  This installed the GUI features and all the requisites for those features. 

  Once the installation is complete, which will take quite awhile, reboot the server with the command
  shutdown /r /t 0  This shuts the server down for reboot with a wait time of zero (immediate).
  

  You should be back in business after the reboot.

  • Edited by
    EVC
    Tuesday, January 26, 2016 3:23 PM
  • Proposed as answer by
    Vimal Thiagaraj
    Tuesday, February 9, 2016 7:10 AM

• Thanks for the post. This did work out for me perfectly.

• Does anyone know the root cause of this? I have ran into the exact same situation that you described. Currently running the command you listed, and it is working.

• It may be embarrassing, but I’m seeing this issue as well and perhaps I could benefit from the info.

• I think it has something to do with the loss or corruption of the .Net 4 feature. Just my best guess.

• I ran into the same problem and found it easier to download the non-core version and upgrade.

  ---

  R, J

• I ran into the same problem and found it easier to download the non-core version and upgrade.

  ---

  R, J

   Where did you find that? It might be a good idea to include that info.

  ---

  Bill

• thing is, it WAS a full install. I believe the removal of dot net 4.5 is the key. Engineer installing some software removed 4.5 and that’s when the issue happens. The above DISM command cleared it up.

• If my solution worked please put a vote for it so others know to use it.  Someone just mentioned .Net 4 as well.  I’m really thinking this has something to do with .Net 4 being removed.  When this happened to me, I was messing around with
  .Net 4 due to a compatibility issue with a piece of software. 

• i had the same problem here . i tried to remove the .net framework 4.5 on server manager than the server rebooted and came with the same issue. only started in command prompt. nothing is available. not powershell not server manager. if you do ctrl alt end
  you can go to task manager and start firefox.exe for example you can download .netframework install it but after reboot stays the same. you can try install .netframework on prompt command but wont work. i used the command above listed  
  Dism /online /enable-feature /featurename:Server-Gui-Mgmt /featurename:Server-Gui-Shell /featurename:ServerCore-FullServer /all    
  after a few seconds asked if i wanted to rebbot. said yes and voila. everithing is back.

  thank you so much guys…

  • Proposed as answer by
    Tryggr
    Tuesday, June 28, 2016 3:22 PM
  • Unproposed as answer by
    Tryggr
    Tuesday, June 28, 2016 3:23 PM

• Thanks a Lot EVC… It Worked for me ..Appreciate your Help …!!!!!

• I work in a LAB with an MSDN license. I’m probably the wrong person to ask that question. On that note, if you have an MSDN subcription, just download one that isn’t a core and install over the top of the core to give it a GUI (the easy way). As shown
  here, there are other ways. I did not find them particularly convenient other than it forced me to learn a bunch of basic Powershell commands (such as Restart-Computer, Stop-Computer, and so on).

  ---

  R, J

  • Edited by
    Crakdkorn
    Sunday, June 5, 2016 6:57 PM

• Tried the reinstallation of GUI twice and still back at the black screen with cmd window. Restarted several times. The OS in question is Windows Server 2012. Please help.

  Regards,

  AR

• Tried the reinstallation of GUI twice and still back at the black screen with cmd window. Restarted several times. The OS in question is Windows Server 2012. Please help.

  Regards,

  AR

• Have you followed the suggestions in the old post?  By replying to an old post, it is hard to tell what you have done.

  From where did you obtain the distribution you are using?  During the installation, are you sure you did NOT select the default installation option?  There are four selections — Std Core, Std, Datacenter Core, and Datacenter.  If you accept
  the default, you will get core, which means no GUI.

  What steps did you follow?

  ---

  . : | : . : | : . tim

• I had to run the DISM command that EVC proposed, which took an extremely long time to run. It hangs on black screens for 5+ minutes, so it looks concerning. But with patience it finally completed. Once it came back up the Server Manager was very slow
  to load, but did come up. I still didn’t have the full GUI though. Checked via powershell and the 2 gui features were «available» but not installed. Followed the steps from
  R.Levchenko and now everything is back up and running. Thanks everyone.

• This was the one for me. Many thanks!

• Dism /online /enable-feature /featurename:Server-Gui-Mgmt /featurename:Server-Gui-Shell /featurename:ServerCore-FullServer /all

  This resolved my issue thanks Vimalanathan Sigamani T

  ---

  dd

  • Edited by
    Grandotto
    Thursday, August 18, 2016 12:16 AM

• Dism /online /enable-feature /featurename:Server-Gui-Mgmt
  /featurename:Server-Gui-Shell /featurename:ServerCore-FullServer /all

  This worked for me as well.  Thanks guys

• Thanks Vimalanathan,

  This really helped me and fixed the issue.

• This worked perfectly for me. Seems the admin that I gave the server to might have removed dot net 4.5.

  ---

  jimmypi

• I managed to have this happen to me after installing the full GUI version of the OS.  Don’t ask how, its embarrassing! lol

  Anyway, PowerShell would not function so Install-Feature was not an option.  Server manager would not open so, enabling features with the UI was not an option.  In fact, nothing would run from the command prompt except taskmgr.  

  The solution was to run the following command from the command prompt that had opened when I logged into the server:

  Dism /online /enable-feature /featurename:Server-Gui-Mgmt /featurename:Server-Gui-Shell /featurename:ServerCore-FullServer /all

  This installed the GUI features and all the requisites for those features. 

  Once the installation is complete, which will take quite awhile, reboot the server with the command
  shutdown /r /t 0  This shuts the server down for reboot with a wait time of zero (immediate).
  

  You should be back in business after the reboot.

  This seems to be working for me now. The previous commands did not work. But this is actually installing now.

  I agree that it has something to do with the removal of .NET 4.0/4.5. I was trying to uninstall/reinstall IIS because a contractor royally screwed up the server by installing Apache. We use IIS on everything, so I’m trying to undo everything he did. Apparently
  I unintentionally (not knowingly) removed a vital piece of the Server puzzle by uninstalling (removing) .NET 3.5 and .NET 4.5 when I uninstalled IIS. Everything was fine until the reboot.

  TL;DR

  If you blew out .NET 4.5, EVC’s solution is the one you need. Forget everything else in this thread.

  • Edited by
    Kim Dorris
    Saturday, October 15, 2016 4:09 AM
    correct typos

• You’re right, I did remove .NET 4 feature and suddenly all were gone except for Command Prompt. Your answer do the trick. Thanks.

• Wow, it works. The latest release will prompt to restart the server. Someone ruined the .NET Framework 4.5 and after uninstalling the .NET Framework, I ruined the server LOL. Thanks EVC. 

• I agree. same thing happened here too.

• if this does not work. try this:

  https://www.linkedin.com/pulse/20140618170857-12975178-procedure-to-recover-gui-in-windows-2012-and-2012r2-net-framework-feature-dependency-in-windows-2012-2012-r2

• if this does not work,   try this:

  https://www.linkedin.com/pulse/20140618170857-12975178-procedure-to-recover-gui-in-windows-2012-and-2012r2-net-framework-feature-dependency-in-windows-2012-2012-r2

• Thank you for this post!  A year later and it saved me.

• Thanks guys… I was also facing same issue and tried this solution.. It perfectly worked for me.

  Thanks again.

• Thanks a ton for the solution, it saved my day.

• I had this problem today I try the steps Don’t work for me

• Yes, that was exactly what happened to me. Trying to install .NET 3.5 was not working, I thought had something to do with having a newer version and I went and removed .NET 4.0. BOOM no more GUI. Thanks for the solutions. It worked like a charm.

• You can do it in 4 simple steps using powershell.

  Just follow the below instructions and you are done.

  1. c:useradministratoripowershell

  2. c:useradministratorImport-Module
  Servermanager

  3.
  c:useradministratorInstall-WindowsFeature
  Server-Gui-Mgmt-Infra,Server-Gui-Shell –Source wim:d:sourcesinstall.wim:4

  
  4.c:useradministratorshutdown
  /r /t 0 (Restart the server)

  Thank me Later

  • Edited by
    RaviBhati
    Thursday, May 31, 2018 7:33 AM

• The cmd mentioned before 

  cmd > powershell

  In powershell:

  Install-WindowsFeature Server-Gui-Mgmt-Infra,Server-Gui-Shell -Restart

  It worked for me. Just be patient. It takes about 15 minutes after it gets stuck at 68% to process it. Thank you! Nivi

  • Edited by
    TechSuperMario
    Tuesday, October 22, 2019 12:46 AM

Содержание:

• Настройка Windows Server Core с помощью SCONFIG
• Основные команды PowerShell для настройки Server Core
• Установка обновлений в Server Core
• Часто используемые команды в Server Core

Напомним, что Server Core это особый режим установки Windows Server без большинства графических инструментов и оболочек. Управление таким сервером выполняется из командной строки или удаленно.

Преимущества Windows Serve Core:

• Меньшие требования к ресурсам;
• Повышенная стабильность, безопасность, требует установки меньшего количества обновлений (за счет меньшего количества кода и используемых компонентов);
• Идеально подходит для использования в качестве сервера для инфраструктурных ролей (контроллер домена Active Directory, DHCP сервер, Hyper-V сервер, файловый сервер и т.д.).

Server Core лицензируется как обычный физический или виртуальный экземпляр Windows Server (в отличии от Hyper-V Server, который полностью бесплатен).

Если вы случайно закрыли окно командной строки, нажмите сочетание клавиш Ctrl+Alt+Delete, запустите Task Manager -> File -> Run -> выполните
cmd.exe
(или
PowerShell.exe
).

Если нужно сбросить IP адрес и вернуться к получению адреса от DHCP, выполните:

Set-DnsClientServerAddress –InterfaceIndex 4 –ResetServerAddresses
Set-NetIPInterface –InterfaceIndex 4 -Dhcp Enabled

Текущие настройки:

Configure-SMRemoting.exe -Get