This post is a last-ditch effort for ideas.
Windows Server 2012 64-bit. Dedicated hardware.
On reboot, the pre-login screen reports failed patches and attempts recovery. When I log in, the explorer.exe files are missing and I only have a windowed command prompt. Server services appear to be working (SQL, etc). It's acting like it turned itself into Server Core.
- There is no 'last known good' configuration.
- There is no restore point.
sfc /scannow
returns "repair in progress, reboot and scan again".DISM.exe /Online /Cleanup-image /Scanhealth
reports no corruption- All DaRT tools report a failure to run.
I'd love to be able to repair the OS, get a GUI back to use tools, and/or rollback patches.
Edit Powershell files are also missing.
At the command prompt, start the system configuration tool (sconfig) and check if you haven't switched the server to "core" mode. If so, you can re-enabled it.
Alternatively, you can start powershell and run:
Get-WindowsFeature Server*
You should have a feature named
Server-Gui-Shell
and another namedServer-Gui-Mgmt-Infra
To install the GUI shell from the powershell prompt, you can use:
Install-WindowsFeature Server-Gui-Shell, Server-Gui-Mgmt-Infra
Warning If your GUI shell is listed as being installed (i.e. you're not running "core"), you might get the shell back by uninstalling it and then reinstallling it but chances are other parts of the system are toast. A much wiser choice at this point it to reinstall and restore a backup.
If the GUI shell is listed as installed, you can try to uninstall it with the following command:
`Uninstall-WindowsFeature Server-Gui-Shell, Server-Gui-Mgmt-Infra
And then reinstall.
Warning (bis) You will need to reboot for any of the install/uninstall command to take affect.
This is a fairly old post, I know, but I had this problem and wanted to post my solution, just in case I need it later :)
I also had no
explorerer.exe
and nopowershell.exe
start powershell.exe
from the command lineInstall-WindowsFeature Server-Gui-Shell, Server-Gui-Mgmt-Infra
as per @Stepane 's solutionHave you tried using the System File Checker (SFC) and DISM Scan & Restore offline?
If you boot from Windows install disk into command line you can run these tests.
In the next example the OS is available on the D: drive from the installer. And E: is the Windows Installer CD/USB:
My initial thought would be to simply place a copy of EXPLORER.EXE in %Windir%. However, the fact that it's missing in the first place concerns me. It begs the question "what else is missing?".
I think I'd then want to confirm that Windows still thinks it should be using explorer, by running: