При запуске windows server 2012 появляется командная строка - Доктор Windows

Question
I am trying to install windows 2012 R2 standard Server. I completed the installation windows is not booting properly . After entering the user name and password only c:useradministrator display in the screen, if i type exit on it then only a
black screen and mouse pointer display. not sure what to do from here

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

Источник

Question
I am trying to install windows 2012 R2 standard Server. I completed the installation windows is not booting properly . After entering the user name and password only c:useradministrator display in the screen, if i type exit on it then only a
black screen and mouse pointer display. not sure what to do from here

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

Источник

Question
I am trying to install windows 2012 R2 standard Server. I completed the installation windows is not booting properly . After entering the user name and password only c:useradministrator display in the screen, if i type exit on it then only a
black screen and mouse pointer display. not sure what to do from here

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

Источник

Question
I am trying to install windows 2012 R2 standard Server. I completed the installation windows is not booting properly . After entering the user name and password only c:useradministrator display in the screen, if i type exit on it then only a
black screen and mouse pointer display. not sure what to do from here

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

Источник

Question
I am trying to install windows 2012 R2 standard Server. I completed the installation windows is not booting properly . After entering the user name and password only c:useradministrator display in the screen, if i type exit on it then only a
black screen and mouse pointer display. not sure what to do from here

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 2012: Переключение между режимами GUI и Core
Переключение из режима Server Core в GUI
Переключение из GUI режима в Core
Переключение из Windows Server 2012 GUI в Minimal Server interface
Переключение из Core в Minimal Server Interface в Windows 2012
65 основных команд Windows Server
Как запустить команды в терминале Windows Server
Команды для Windows Server
Настройка подключений
Работа в системе
Работа с локальными и виртуальными жесткими дисками
Работа с файлами и папками
Интерфейс командной строки
Заключение

Windows Server 2012: Переключение между режимами GUI и Core

Server Core – особый режим установки Windows Server, это среда, в которой отсутствует графический интерфейс и средства управления, а также некоторые серверные роли и компоненты. Управление Windows Server Core предполагается из командной строки, с помощью PowerShell, или же с других серверов/рабочих станций с установленным RSAT (RSAT для Windows 7, RSAT для Windows 10). Впервые Core-режим работы серверной ОС Microsoft появился еще в Windows Server 2008. Основные преимущества Server Core перед полными инсталляциями Windows Server: экономия системных ресурсов, повышенная стабильность и безопасность за счет меньшего количества компонентов, упрощение обслуживания, меньший даунтайм при установке обновлений, сокращение поверхности атаки злоумышленниками.

Одним из главных недостатков в Windows Server 2008 Core являлась невозможность переключение в режим с графической оболочкой (GUI) или в обратную сторону (из GUI в Core режим). В случае возникновения такой необходимости приходилось целиком переустанавливать ОС.

В Windows Server 2012 Microsoft решила убрать это ограничение, кроме того появился еще один вариант работы сервера — минимальный интерфейс сервера (Minimal Server Interface). В этом режиме отсутствуют проводник, Internet Explorer, рабочий стол и начальный экран).

В Windows Server 2012 теперь можно установить и настроить сервер в знакомом администраторам GUI, после чего перевести сервер в Core режим. Этот подход упрощает процедуру настройки сервера, не вынуждая администраторов разбираться в подчас достаточно сложных консольных командах и командлетах PoSh.

Итак, в Windows Server 2012 возможна работа в нескольких режимах, между которыми в процессе эксплуатирования и настройки сервера может переключаться администратор.

Full Server with GUI – полноценный сервер с GUI
Server Core with GUI Management (Minimal Server Interface) – минимальная интерфейс сервера с Windows Server 2012, включающий графические утилитаты управления сервером
Server Core – режим командной строки

Далее мы разберем способы переключения между данными режимами работа новой серверной платформы от Microsoft

Переключение из режима Server Core в GUI

В том случае, если сервер был установлен в режиме Windows Server 2012 Core, в установленных компонентах отсутствуют необходимые файлы для установки GUI (концепция минимизации занимаемого места на диске в Core режиме). По умолчанию, если нужные компоненты отсутствуют на диске, система пытается скачать их с сайта Windows Update. Если доступ в интернет у сервера отсутствует, нам придется указать альтернативные источник установки (с помощью команды powershell Install-WindowsFeature с параметром -Source).

Для установки графического интерфейса нам понадобится дистрибутив Windows Server 2012. Допустим, мы вставили (смонтировали iso образа) дистрибутив Windows Server 2012 в устройство, которому назначена буква D:.

Далее нужно определить индекс установленной версии Windows Server 2012 в установочном wim образе. Для этого наберите команду, отображающую информацию о содержимом установочного образа:

Т.к. на сервере установлен Windows Server 2012 Datacenter, нас интересует дистрибутив SERVERDATACENTER, индекс которого 4.

Далее нужно установить недостающие компоненты (Server GUI) из wim файла командой:

Процедура установки займет порядка 5-10 минут. В том случае если при установке будут наблюдаться проблемы, попробуйте отключить сетевые карты, чтобы Windows не пыталась скачать файлы с сайта Windows Update.

После выполнения команды сервер автоматически перезагрузится и загрузится уже в графическом режиме.

Графические компоненты Windows Server 2012 можно также установить и с помощью DISM, ту же самую операцию выполним с помощью двух команд:

В том случае, если сервер изначально был установлен в GUI режиме, который затем отключили, его можно вернуть командой:

Переключение из GUI режима в Core

Удалить GUI режим в Win Server 2012 в Core можно несколькими способами:

С помощью Powershell
Из графического интерфейса консоли Server Manager

Запустите строку PoSh и выполните команду

После выполнения команды сервер автоматически перезагрузится и загрузили уже в Core-режиме.

Аналогом командлета remove-WindowsFeature является Uninstall-WindowsFeature команда, и чтобы перейти из режима Server with GUI в режим Server Core воспользуйтесь командами:

Если вам удобнее пользоваться графическими утилитами, откройте консоль Server Manager:

Выберите пункт Remove Roles or Features
Снимите флажки с Graphical Management Tools and Infrastructure и Server Graphical Shell
После окончания работы мастера перезагрузите сервер

Переключение из Windows Server 2012 GUI в Minimal Server interface

В режиме работы Minimal Server Interface в системе присутствуют все базовые графические инструменты управления сервером (оснастки MMC, консоль Server Manager, элементы панели управления), однако такие компоненты как Windows Explorer, Internet Explorer 10, рабочий стол, начальный экран Start screen отсутствуют.

С помощью Powershell переключиться в режим Minimal Server Interface можно с помощью команды:

Тоже самое в графической консоли Server Manager:

Откройте консоль Server Manager
Выберите Remove Roles or Features
Снимите флажок с элемента Server Graphical Shell
По окончании работы мастера перезагрузите сервер

Переключение из Core в Minimal Server Interface в Windows 2012

Откройте консоль Powershell и выполните команду:

65 основных команд Windows Server

Практически во всех операционных системах множество функций можно запустить не только «кликом», но и с помощью определенной команды. Это касается и версии Windows для серверов. Большинство из тех команд, что используются для управления сервером, схожи с теми, что предназначены для обычной Windows. Я перечислю основные команды, которые в той или иной степени будут полезны при управлении ОС Windows Server.

Как запустить команды в терминале Windows Server

Как и в десктопной версии, все указанные команды можно запустить с помощью командной строки.

Для получения указанных прав нужно действовать следующим образом:

Открыть строку поиска в панели «Пуск».
Ввести в поле запрос «командная строка», можно и cmd.
Когда соответствующее приложение выйдет, нажать на пункт «Запуск от имени администратора».

Команды можно запускать с помощью утилиты Windows PowerShell, которую также можно найти среди предустановленных программ.

Команды для Windows Server

Все указанные команды предназначены для самых разных задач. Я постараюсь рассортировать их по функционалу. В общей сложности вышло 65 команд, без учета дополнительных параметров и атрибутов в некоторых из них.

Настройка подключений

arp – данная команда предназначена для просмотра и изменения записей в кэше ARP. Это протокол, представляющий собой таблицу соответствия IP-адресов с MAC-адресами сетевых устройств.

dnscmd – диагностирует, исправляет ошибки в конфигурациях и еще выполняет множество других действий при администрировании сервера DNS.

ftp – передает туда и обратно файлы на компьютер, в котором запущена служба протокола FTP. У команды есть несколько параметров. Вот некоторые из них, которые будут наиболее полезны:

bye

Завершает сеанс FTP на удаленном компьютере; есть аналогичная этой команда – FTP Quit

delete

Стирает указанные файлы на удаленном компьютере

mget

Копирует файлы с удаленного на локальный компьютер, используя текущий тип перемещения файлов

mkdir

Создает новую папку на удаленном компьютере

open

Подключается к указанному FTP-серверу

rmdir

Стирает выбранный каталог на удаленном ПК

status

Показывает текущее состояние FTP-подключений

ftp trace

Переключает трассировку пакетов, отображает внутренние вызовы функций FTP при запуске команды

type

Задает или отображает тип перемещения файла

user

Указывает пользователя для удаленного компьютера

mdelete

Стирает файлы на удаленном компьютере

getmac – данный запрос определяет mac-адрес компьютера, а еще он используется для отображения mac-адресов сетевых адаптеров.

hostname – показывает наименование узла в полном имени компьютера.

ipconfig – этот параметр отображает актуальные на момент проверки параметры протокола TCP/IP. Он также применяется для обновления некоторых характеристик, задаваемых при автоматической конфигурации сетевых интерфейсов, задействующих протокол DHCP. К данной команде можно добавлять следующие атрибуты:

/all

Выдает все доступные конфигурации IP

/displaydns

Отображает кэш DNS

/flushdns

Сбрасывает кэш DNS

/registerdns

Обновляет и повторно регистрирует параметры DNS

/release

/renew

Обновляет сведения для сетевых адаптеров

/setclassid

Меняет DHCP Class ID

/showclassid

Отображает DHCP Class ID

msg – запускает отправку сообщения указанному удаленному пользователю.

mstsc – запускает подключение к удаленному рабочему столу.

net view – показывает имя компьютера в текущем домене.

netsh – сетевое служебное приложение, позволяет локально или удаленно отображать или изменять конфигурацию сети компьютера. Программу можно запустить как в командной строке, так и в Windows PowerShell.

shadow – удаленное управление активным сеансом другого пользователя.

netstat – показывает состояние TCP-подключений и портов, на которых компьютер прослушивается, статистику Ethernet, таблицу маршрутизации IP-адресов, а без использования параметров команда отображает лишь активные TCP-подключения.

nbtstat – отображает статистику протокола и активных подключений TCP/IP посредством NetBT, причем как для локального, так и для удаленных компьютеров. При использовании без параметров эта команда выдает только справочные данные.

nslookup – выдает сведения, используемые для диагностики DNS. Чаще всего используется для определения IP-адреса по доменному имени.

tracert – производит трассировку. Если говорить проще – показывает путь, по которому проходят пакеты данных при отправке из вашего компьютера в конечную точку. При этом показывает последовательно каждый этап маршрута, позволяет узнать, на каком этапе происходят крупные потери или задержки.

pathping – точно так же, как и tracert, выполняет трассировку, дополнительно предоставляя сведения о задержке сети и сетевой утрате в промежуточных узлах.

ping – проверяет подключение и доступность указанного компьютера на уровне TCP/IP. В результате показывается сообщения с информацией о получении соответствующих ответов, а также время кругового пути. Это основная команда для проверки и устранения неполадок подключения, доступности и разрешения имен.

qappsrv – показывает полный список доступных удаленных рабочих столов в текущем сеансе.

quser – выдает информацию о пользовательских сеансах на удаленный рабочий стол в текущем сеансе. Команда позволяет определить, вошел ли конкретный пользователь на конкретный сервер узла сеансов. После сканирования выдаются следующие сведения:

имя пользователя;
наименование сеанса на узле;
идентификатор сеанса;
состояние – активно или отключено;
время простоя – означает промежуток времени с момента последнего нажатия клавиши или перемещения мыши в сеансе;
дата и время входа пользователя.

rpcinfo – выводится список программ, установленных на удаленных компьютерах.

rasphone – инструмент для управления сетевыми подключениями, в основном используется на модемных линиях или в PPPOE, PPPTP.

route – можно просмотреть и изменить записи в локальной таблице маршрутизации IP. Если использовать без параметров, команда даст справку.

telnet – осуществление подключения по протоколу telnet. Позволяет проверять доступность портов. По умолчанию он не установлен, поэтому такая команда не всегда может сработать.

Работа в системе

at – запрос отвечает за планирование выполнения команд или запуска приложений в заданное время. Используется только совместно со службой расписания и с правами администратора.

compmgmt.msc – эта команда откроет инструмент «Управление компьютером», в котором можно просмотреть запланированные задачи, события, общие папки и пользователей. Также там есть инструмент для управления дисками, еще отображается раздел со списком служб и приложений.

control – запускает «Панель управления». Есть множество ее подвидов, позволяющих запустить окна для управления отдельными элементами. Среди них актуальными будут следующие:

control admintools – переход в раздел «Администрирование» в панели управления.
control color – открытие раздела Персонализация» из параметров системы, где можно настроить экран, темы, цвета и так далее.
control folders – параметры «Проводника».
control Userpasswords – свойства локальной учетной записи.

devmgmt.msc – команда запускает «Диспетчер устройств», утилиту для управления основными аппаратными и программными компонентами.

explorer – позволяет открыть «Проводник Windows».

logman – создает сеансы трассировки событий, управляет ими и журналами производительности, а также поддерживает многие функции мониторинга системы из командной строки.

mmc – открывает определенную консоль MMC, можно в режиме автора и с указанием версии – 32 или 64-разрядной.

mode – показывает состояние системы, изменяет параметры, перестраивает порты или устройства. При задаче команды без параметров отображаются все управляемые атрибуты консоли и доступные устройства com.

msconfig – открывает инструмент для тонкой настройки системы, управления загрузкой и автозагрузкой, а также активными службами и сервисами.

msinfo32 – запускает утилиту «Сведения о системе», где отображен полный список установленного оборудования, а также системных и программных компонентов на локальном компьютере.

PowerShell – запуск нового сеанса для утилиты Windows PowerShell через окно командной строки.

PowerShell_ise – запускает сеанс в интегрированной среде сценариев Windows PowerShell (ISE). В таком режиме можно применять необязательные настройки для открытия некоторых файлов, проводить запуск без определенного профиля и так далее.

regedit – открывается редактора реестра.

secedit – анализируется и настраивается безопасность системы, текущая конфигурация сравнивается с актуальными шаблонами безопасности.

services.msc – открывается консоль для работы со службами и сервисами.

shutdown – выключение/перезагрузка локальных или удаленных компьютеров. Для той или иной процедуры стоит использовать соответствующий параметр.

shutdown /r – перезагрузка компьютера после завершения работы.
shutdown /s – полное завершение работы компьютера.

systeminfo – выдача подробной информации о конфигурации компьютера и его операционной системы, включая сведения о безопасности, идентификатор продукта и свойства оборудования.

wuauclt – открывает раздел параметров «Обновления Windows».

Работа с локальными и виртуальными жесткими дисками

attach vdisk – подключает виртуальный жесткий диск с дальнейшим его отображением в меню главного компьютера в качестве локального. Для отключения его отображения должна быть использована команда detach vdisk.

chkdsk – этот запрос запускает утилиту для проверки дисков и метаданных на наличие логических и физических ошибок. При использовании без параметров лишь отображает состояние и не исправляет ошибки. Для устранения ошибок следует дополнительно вводить параметр /f. Параметр /r запустит поиск поврежденных секторов.

cleanmgr – запускает инструмент «Очистка диска», отвечающий за удаление ненужных файлов с жесткого диска компьютера. Введя отдельные параметры, можно настроить утилиту на стирание временных файлов, кэша интернета, а также провести перезапуск файлов bin.

convert – преобразует диск из одного формата в другой.

defrag – выполняет дефрагментацию файловой системы. Определяет также степень фрагментации диска, объединяет файлы для повышения производительности ОС.

dfrg.msc – с помощью этого запроса включается дефрагментатор дисков.

diskpart – открывает одноименный интерпретатор, позволяющий управлять подключенными локальными дисками, разделами, томами компьютера и виртуальными дисками тоже.

expand vdisk – расширяет созданный виртуальный жесткий диск до определенного размера, указанного в параметрах. Предварительно для выполнения данной команды рекомендуется отключить VHD.

ntbackup – запускает из командной строки резервное копирование и восстановление компьютера и файлов.

recover – проводится восстановление данных, доступных для чтения, с поврежденного или дефектного диска. Эта команда считывает файл и сектор, а затем восстанавливает данные.

sfc /scannow – выполняется проверка целостности всех защищенных системных файлов и по возможности восстановление файлов с проблемами.

Работа с файлами и папками

copy – копирует нужный файл из исходного расположение в другое.

del – удаляет один или несколько файлов. Есть аналогичная – erase. Используя определенные параметры, можно активировать запрос для подтверждения удаления, также запустить принудительное стирание файлов, доступных только для чтения.

expand – разархивирует один или несколько сжатых файлов.

fsmgmt.msc – включается консоль с общими папками в системе.

manage-bde – активирует и дезактивирует BitLocker, задает способы разблокировки, обновляет методы восстановления и разблокирует защищенные диски.

md – создает новый каталог или подкаталог. Похожая команда – это mkdir.

mqbkup – запускает инструмент для архивирования и резервного копирования сообщений MSMQ, параметров реестра на запоминающее устройство, также проводит восстановление ранее сохраненных сообщений и параметров.

Интерфейс командной строки

cls – проводит очистку командной строки.

color – меняет цвет и фон утилиты.

exit – закрывает командную строку.

help – отображает полный список команд, доступных для задействования в данном инструменте.

Заключение

Как видно, команды для Windows Server практически ничем не отличаются от тех, что используются в обычной версии системы. Разница состоит лишь в задачах – для серверной версии в ход обычно идут несколько иные запросы – команды для командной строки в Windows Server больше акцентированы на работу с подключениями и дисками.

Источник

13.05.2016, 11:56

#1

Гость форума

Регистрация

30.03.2016

Сообщений

7

Сказал(а) спасибо

1

Поблагодарили 0 раз(а) в 0 сообщениях

server 2012 грузится и выходит в командную строку

После сбоя по питанию server загружается и выходит в командную строку, может войти в диспетчер задач.Подскажите что можно сделать?
12.10.2017, 17:03

#2

Пришел за помощью

Регистрация

28.11.2014

Сообщений

10

Сказал(а) спасибо

0

Поблагодарили 1 раз в 1 сообщении

Re: server 2012 грузится и выходит в командную строку

Попробуй ввести taskmgr.exe
Затем файл-выполнить explorer.exe

Источник

Question

All replies

Question

All replies

Question

All replies

Question

All replies

Question

All replies

Windows Server 2012: Переключение между режимами GUI и Core

Переключение из режима Server Core в GUI

Переключение из GUI режима в Core

Переключение из Windows Server 2012 GUI в Minimal Server interface

Переключение из Core в Minimal Server Interface в Windows 2012

65 основных команд Windows Server

Как запустить команды в терминале Windows Server

Команды для Windows Server

Настройка подключений

Работа в системе

Работа с локальными и виртуальными жесткими дисками

Работа с файлами и папками

Интерфейс командной строки

Заключение

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ruboard.ru/images/icons/icon1.png" alt="По умолчанию" /> server 2012 грузится и выходит в командную строку

server 2012 грузится и выходит в командную строку