Windows Server 2012 R2 boots in CMD after several Restarts

Hi,
I have been facing this problem after i installed some applications on the server and after we did several restarts the server boots up only in cmd.
I am very sure that i installed the OS with GUI since i have logged in with it while i am installing the application.

If you are not in Safe Mode, then you are using Server Core.
As mentined earlier, see
http://blogs.technet.com/b/yungchou/archive/2014/01/16/windows_2d00_server_2d00_2012_2d00_r2_2d00_installation_2d00_options_2d00_and_2d00_features_2d00_on_2d00_demand_2d00_part_2d00_4_2d00_of_2d00_5.aspx

Similar Messages

My 10.9.0.1 internal mac was ruined after the installation of Windows Server 2012 on boot camp

Hi Everyone. I've been trying to install Windows Server 2012 on my boot camp. Well, soon after the 2012 was installed, my mac os 10.9.0.1 was ruined. When I pressed on the option key while the imac was booting, I can see the icon of "10.9.0.1 recovery". But after I chose it, the apple tried very hard to boot it up with a progress bar below the apple icon. The computer shut down itself after the progress bar reached the end. I've tried boot it up with the installation CD and tried to repair the Macintosh HD in Disk Uitilites but no use. It was said the hard drive cannot be repaired and better be reformat. Currently I can only boot up my mac from my SuperDuper external clone drive. Anyone could give me wise advices to fix this problem please?

The "wise advices" I can offer are:
Read the Boot Camp documentation before trying to reinstall Windows Server. Windows Server is not supported by Boot Camp
Erase and reformat your hard drive. Reinstall OSx then restore your data from your backup.
Use a virtual machine like Parallels, Fusion, or VirtualBox to install Windows Server

Windows server 2012 R2 booting problem

I am trying to install windows 2012 R2 standard in Hp ml350 g8 Server. after completing the installation windows is not booting properly . After entering the user name and password only c:\user\administrator display in the screen . if i type exit
on it then only a black screen and mouse pointer display. kindly suggest me what to do.

can any one suggest me what to with this booting problem! is there any hardware problem or it's problem with the media as the media was downloaded from vls.my problem is that After
entering the user name and password only c:\user\administrator display in the screen . if i type exit on it then only a
black screen and mouse pointer display. In my opinion Microsoft need have to provide the media disk along with the licences and also some short of technical support free over phone. but they don't !!!

Windows Server 2012 not booting as a Hyper V guest

Hi all,
As always the best laid plans go to crap and so I need help from the best in the business, aka - all of you.
I am installing Windows 2012 Server Standard as a VM in Hyper V. I initially created it as a Vm in Server 2008 however for some reason the vm would not boot at a certain point . I installed the operating system fine from an ISO from the VLSC - rebooted fine
etc. As soon as I started to create roles (just IIS with .net 3.5 roles etc) - no directory services, its purely operating as a web and sql server... - at some point it wont boot. I start the VM, connect to it - get the windows 2012 splash screen however it
won't boot to the login screen. I can see CPU action for a period of time then NOTHING! - blank screen - no connection - no rdp.
I thought it was because of incompatibility between 2012 guest and 2008 host. So I upgraded the host to 2012 Hyper V Server Core (you know, the free one). That in itself was fine, all worked perfectly - all my 2008 Vm's are fine and operate well. I reinstalled
2012 Standard... Once again rebooted fine, however as soon as I added any roles or services (IIS) it just wont boot past the splash screen. I have installed VM guest drivers etc prior to installing roles and services - Nothing! Same behaviour, boots - see
splash - see CPU activity in Hyper V Manager, then nothing.
I can only think it's a driver issue perhaps or something wrong with the iso - however it does not explain why it boots fine then suddenly stops. Has anyone else experienced this? Anything I can try? I managed to install all updates etc before this happened.
I really dont want to keep re installing. I havent activated yet as I wanted to make sure it worked before I did if that is a factor?

Hi sounds very unusual, the only thing I can think of initially are the integration services installed, and is the network working correctly. if you have a Server physical or virtual on a domain, with network connectivity issues is can take an age to boot.
Try disabling the network adapter from the hardware settings and see if the Virtual server boots. if so, then you need to look at network side.
Also does you system have enough resource, IE, Ram, and CPU.
regards
Mark

Windows Server 2012 Standard Black Parts Windows

Hi,
I have to TURN OFF a VM with Windows Server 2012 because become unresponsive. After rebooting the server, some parts of the windows (taskbar, entry bar) turned black. I tried rebooting again, but it was unsuccessful. I don´t want to reinstall the OS again.
Something similar happened to me with Windows Server 2003 and the only thing I did was to change the registry with the correct entries. I didn´t find any equivalent in 2012.
Regards

Hi,
Do we have anti-virus software installed on the server? If yes, we can scan the server with the anti-virus software. Besides, does the server have enough disk space? We can run
Chkdsk command to check the status of the disk.
Chkdsk
http://technet.microsoft.com/en-us/library/bb491051.aspx
Moreover, we can try to perform a clean boot to troubleshoot the issue.
Regarding how to perform a clean boot and how to use it to troubleshoot, the following article can be referred to for more information.
How to perform a clean boot in Windows
http://support.microsoft.com/kb/929135
Best regards,
Frank Shen

Problems PXE booting Gen 2 Virtual Machines after Upgrading to Windows Server 2012 R2

My Current Setup:
I have two virtual machines set up with Hyper V on my Windows Server 2012 Server.
VM1: Configured to boot from an ISO file and runs Clonezilla server.
VM2: Configured to PXE boot using a legacy network adapter, and with a passthrough 250Gb hard disk.
These two VMs are connected to an external Virtual Switch, which allows physical machines to PXE boot to the Clonezilla server.
For the past few months I have been using this setup for two purposes:
1. To clone physical machines to the Clonezilla virtual server (as a backup).
2. To restore those image to the second VM if I find that need to get access to the files on the original image..
This has worked perfectly, except for the fact that the speed of the legacy network adapter on the second VM (which is required to PXE boot) is very slow. But I know this is because of the limitations in how the legacy adapter works...
Now my problem:
I found out that Gen 2 VMs allow you to PXE boot without having use a legacy network adapter, allowing me to image back to the VM faster. So I upgraded the Server to Server 2012 R2 . I then created the same two virtual machines on the R2 server. I can still
PXE boot the Gen 1 VM to the Clonezilla Server but I cannot get the Gen 2 VMs to PXE boot properly. They get an IP address from the Clonezilla Server but then just stop with the following screen. (note: I have disabled the Secure Boot).
Are Gen 2 VMs unable to pull down images from anything other than a WDS Server?

Hi J,
>>Unfortunately WDS is not a solution for us as it is dependent on the PC being part of a domain
If you would like to make the client not join to the domain, please check the box before “Do not join the client to a domain after an installation.” In addition, make sure not to set the client to the domain in the unattend file and do not prestage
the computer in AD. "
It is quoted from following thread :
https://social.technet.microsoft.com/Forums/windowsserver/en-US/1026c3a9-0a10-4a58-a48f-5391659a96c8/wds-set-unattend-file-for-workgroup?forum=winserversetup
Best Regards
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

New Windows Server 2012 install won't boot after installing Hyper-V role.

I have just installed Windows Server 2012 onto a Dell PowerEdge R310. Everything worked okay until I installed the Hyper-V role. After that, when it tries to boot, I get "Your PC ran into a problem and needs to restart. We're just collecting
some error info, and then we'll restart for you. (0% complete)" for a split second, then the system reboots into Automatic Repair mode.
In Automatic Repair mode, my options are Refresh your system (which tells me the drive that Windows is on is locked), Reset your system (which tells me there is no partition), and Automatically Fix your PC (which tells me it can't fix it).
I have updated to the latest version of the BIOS (1.11.0, which Dell states adds Windows Server 2012 support).
I'm at a loss.. I've tried everything I can think of. Has anyone run into this issue and figured out a solution? The only references I can find to this issue talk about Gigabyte motherboards with USB 3.0, but this server pre-dates USB 3.0 by
quite a bit.

Hi,
Not only the BIOS but the iDRAC and storage part also need to ne up date check, have a look at the following list to see what you need for Server 2012:
http://en.community.dell.com/techcenter/os-applications/w/wiki/3868.dell-bios-support-for-windows-server-2012.aspx
If any info was collected during the error then have a look in the event viewer or look for a kernel/memory dump file so you can try to find the issue, in many cases a driver, anti-virus sofware or 3rd part service can cause these kind of issues.
When you see answers and helpful posts, please click Vote As Helpful, Propose As Answer, and/or Mark As Answer
MCSE:Server Infrastructure, MCSE:Desktop Infrastructure, MCSA Server 2012, Citrix CCIA & CCEE, Cisco CCNA, VMware VCP 3/4/5 Blog: http://www.citrix-guru.com and http://www.rds-support.eu Twitter: @dnyvandam

Unable to Install Windows Server 2012 R2; system aborts and reboots after first blue Windows logo appears

System: Dell PowerEdge sc1420 with dual xeon and Adaptec 2420SA SATA RAID (supported by OS); 10 GB memory (2x4, rank 2, organization x4, in DIMM1 & DIMM2; 2x1, registered, organization x8, in DIMM3 & DIMM4)
This computer is currently running Windows Server 2008 R2 Enterprise which was installed with no problems.
Objective: clean install of Windows Server 2012 R2 Standard on an otherwise unused RAID array disk set.
All attempts to boot from DVD result in loading of files (grey progress bar on bottom of screen), brief dark screen, then black screen with a blue windows logo for about 2 seconds and then a flash of about 10 lines of error notifications on a black screen
for about 1/4 second (unreadable), and then a reboot of the computer.
Coreinfo.exe confirms that cpus DO support NX and PAE; do NOT support VMX (virtual machine enhancements).
Attempts to run memtest.exe from boot disk tool-menu startup result in an error message that the memtest.exe file is corrupt.
Running memtest.exe from Windows 2008 R2 install disk results in all memory tests passed!
Attempted booting with multiple DVD's (some +R, some -R, all verified) burned from .iso. These DVD's were used successfully to install Windows Server 2012 R2 on an HP Pavilion. Also changed DVD drives just to rule out DVD hardware.
Running CHKDSK from Windows 2012 R2 on HP Pavilion shows no problems; running CHKDSK from Windows 2008 R2 on the Dell system on the same disks shows some problems. Running checkdisk on the Windows 2008 R2 install disk from the Windows 2008 R2 installed
system shows no problems. All disks burned and verified on same system.
Also attempted to boot from USB thumbdrive with copy of DVD on it. Same results: system loads files then reboots at first Windows logo. So that would rule out disk quality issues per se??
Started to try an upgrade rather clean install to see if any errors were announced. None were announced as the system went through much of the process. I aborted somewhere along the way before committing to the upgrade because 1) the most likely
outcome was it would not boot after install (I don't really need the practice in restoring); and 2) even if it did reboot, having a system that can't be repaired by booting the install disk is pointless.
All disks and raid arrays are recognized and usable by RAID controller card and by Windows Server 2008 R2. Disks are within spec for use with Adaptec 2420SA (1TB @ 300).
Is VMX (aka VT-x) actaully required for ANY install even though Hyper-V is not intended to be used? If so, it is too bad that the Microsoft system requirements (
http://technet.microsoft.com/en-us/library/dn303418.aspx ) don't make that clear. And lack of VMX support really doesn't explain the memtest.exe "corruption" issue.
Or is it maybe something unique about the files on 2012 R2 disk (or disk image on USB) that are causing some problem with the chipset processing? But why?
My vote would be for the latter of the issues, but I have no clue why or if it is remediable. Suggestions?

So here is what I think is the final understanding of this problem:
First, one additional piece of important information: The computer successfully moves into and through the Windows Boot Loader phase and succeeding phase ONLY for Windows 8.1 32-bit, but NOT for Windows 8.1 64-bit nor for Windows
Server 2012 R2 (only 64-bit).
The Windows Boot Manager phase (which precedes the Windows Boot Loader phase) is either 32-bit or 64-bit (64 –bit for this case) and is loaded by the 16-bit stub program (Bootmgr) which starts in real mode.
Windows Boot Loader of course runs in either 32-bit or 64-bit (64 –bit for this case) according to the product being installed.
By inference, the essential problem is occurring in conjunction with the loading of a WIM file to start the Windows Boot Manager.
The boot manager starts ok and generally shows its essential screens (Windows Boot Manager; Advanced Boot Options) or proceeds to load files for transition into Windows startup in the succeeding Windows Boot Loader phase (that doesn’t “boot” but rather
loads the system). This is best confirmed by the announced corruption of the memtest.exe file when selecting Windows Memory Diagnostic from the Windows Boot Manager Screen.
If allowed to continue loading files to pass control to the Windows Boot Manager, the type of abort and resulting immediate restart that occurs is that which you would associate with unhandled cpu exceptions (invalid instruction, memory out of range,
wild interrupt, etc.) that most of us have not commonly seen for 20 years (since beginning to use well behave OS’s from Windows NT 3.1 and on).
So, the problem obviously is due to a failure to properly mount the WIM file and/or properly access it (probably the latter) when running in 64-bit protected mode.
This is independent of the hardware on which the install disk is actually mounted (DVD or USB-flash), so it is NOT a hardware problem
per se.
Since the WIM is mounted early in the process, Boot Manager may well have loaded it using BIOS routines to access the physical device on which it resides rather than loading 32-bit or 64-bit drivers of its own.
Hence, if the BIOS does not “mount” the WIM in a way that is later fully compatible with access from the 64-bit systems being loaded, it could cause apparent file corruption.
If it is only partially incompatible some functionality may appear quite usable (like loading files) until later detected.
This is vague on my part, because the exact nature of the incompatibility cannot be readily determined from the information available.
But the consequence is the same: the system cannot boot from the install disk, either for initial installation or repairs.
Incidental conclusion: The 64-bit boot manager code for Windows Server 2008 does not exhibit this faulty behavior, but the 64-bit code for Windows Server 2012 does.
So the problem is not inherent with loading 64-bit server OS’s.
Expectations: If the system were to be upgraded using the features of the install disk while running an installed OS, say Windows Server 2008 R2, it might well succeed and yield a fully functional system upgraded to Windows Server 2012
R2 (because the installed operating system is started from discrete files, not from a WIM file).
However, in order to perform a disaster recovery using Windows resources (such as image backups from Windows Server Backup), one would have to presumably boot from a Windows Server 2012 64-bit install disk or Windows Server USB recovery drive.
Of course we know that the Windows Server install disk will not boot and we can be fairly sure that the problem will migrate to any Windows Server USB recovery drive that is created.
My inspection of a Windows 7 System Repair CD shows that is based exclusively on boot.wim, not discrete files!
Of course a generated image for a WIM for Windows 2012 USB recovery drive
might not have the flaw that drives this behavior, but it probably would.
Problem conclusion: A BIOS upgrade would be required for compatibility with Windows Server 2014 clean installation
and any maintenance; and none is available from the OEM.
Problem not resolved, but understood for future reference.
Thanks to Tim whose comments helped me focus my thinking.

Windows 7 Enterprise 32 bit and Windows Server 2012 64 bit successful dual boot.

Client Windows 7 Enterprise 32 bit SP1, Windows Server 2012 64 bit successfully install for dual boot. Even deleted Windows 7 Enterprise from msconfig, moved Windows Server 2012 partition, for dual boot installed Windows 8.1 64 bit (now posting from),
deleted Windows Server 2012 from msconfig, moved Windows 8.1 partition, just for knowledge.

Hi,
After referring to your post, I can understand you are trying to install 32 bit and 64 bit OS on same system. Are you trying to perform that? Here providing you thread link for detail.
dual boot windows 32 bit and 64 bit at same pc
Hope it helps to understand!
Regards.

Windows Server 2012 Hangs After a While

Good day,
My server hangs after a while then I have to hard boot it. I get the error 'Online data retrieval occurs under all my roles. Once I reboot it then the error disappears.
Please help!!
Thanks,
Mao

First of all, you would need to make sure that your server meets the hardware requirements to run Windows Server 2012 + the applications you use.
For Windows Server 2012 System Requirements, you can refer to that: https://technet.microsoft.com/en-us/library/dn303418.aspx
You can also proceed like the following:
Install available Windows Updates (To be tested first)
Install recent versions of your drivers, firmware and BIOS
Uninstall all unused programs
Run chkdsk /r /f and sfc /scannow
Do a clean boot
If this does not help then you can temporary disable security software in use and try again.
This posting is provided AS IS with no warranties or guarantees , and confers no rights.
Ahmed MALEK
My Website Link
My Linkedin Profile
My MVP Profile

Windows Server 2012 R2 Will Support for UEFI boot in WDS.

Hi
Currently we had issue in WDS while deploying the image via UEFI boot in the DELL Optiplex 3010. We already deployed the Windows 8 install image and boot image in the Windows Server 2012 R2. After selecting the Network boot its show Start PXE IPV4 and it
will immediately flicker and get back to Network Boot option. Any one please help me out of this.....
But the same is working in Legacy boot and it doesn't activate the Windows 8.

Hi,
As I cannot confirm the exact settings on your side, please see the suggestions provided in following thread:
WDS: EFI BIOS won't PXE boot into EFI mode
http://social.technet.microsoft.com/Forums/windowsserver/en-US/ceca6149-bedd-4860-8a7f-a1c83bf99aa4/wds-efi-bios-wont-pxe-boot-into-efi-mode?forum=winserversetup
The same issue is discussed a lot in this thread and several possible suggestions are provided. See if it is helpful. If there is anything unclear please just let us know.
If you have any feedback on our support, please send to [email protected]

Windows Server 2012 Standard - HP OfficeJet Pro 8600 Plus printer not working after promoting to Domain Controller / AD Services

An associate and myself installed the built-in drivers for the HP OfficeJet Pro 8600 Plus multi-function (network) printer on a Windows Server 2012 Standard server installation and everything worked fine whenever I want to print anything directly from the
Windows Server machine (there's a reason for this, so please understand that ;) ).
We were able to print without any problems from the Windows Server 2012 machine, using the drivers from Microsoft. Mainly, because HP has not listed any specific support for Windows Server 2012, only Windows Server 2008 R2, however, the drivers that
came with Windows 2012 seem to work very well.
PROBLEM: I later had to promote the Windows Server 2012 to a Domain Controller, and created the Active Directory configurations, even enabled the Print Services. After doing all of that, the HP printer will not print anything. It's like all print
requests directly from the Windows Server go to Nil.
Has anyone encountered a problem like this before? The only thing I can think of is that after perhaps something affected printing directly once we promoted the server to being a DC, and added other features / roles. I even tried installing the
HP drivers for Windows Server 2008 R2, and the results are still the same...nothing prints. Trust me, the printer is set as the Default Printer and even when choosing to print, we make sure the HP OfficeJet Pro is selected, and is on, as other Windows
Client PC's can print to it directly.
Does anyone have any suggestions we could try? Thanks in advance.

While it is quite a while since this was posted - I can concur a similar issue exists.
We have spent the better part of a day trying to work out why other HP printers work fine but our 8620 prints are not printing and going to Nil. The print server is hosted on a shared DC. Comparing to the initial posters details, for some reason
it seems to be most commonly related to the OfficeJet Pro 8600/8610/8620/8630 series printers.
I ended up doing a print server migration from the domain controller to stand alone host and all printers now work from a single server rather than a mix. Domain controller OSes varied from 2008, 2012, 2012 R2 (tested with multiple) and only after
all of those failed then tried a stand alone server os machine as a last resort which worked fine. Printing directly from Win 7 / 8 /8.1 clients to the IP always worked.

Windows server 2012 R2 PXE boot is unworkable slow, I have this exact same set-up working in 2008 R2 What can I do?

Hi there
I'm trying to deploy a windows 7 image through Windows deployment services via PXE boot from a 2012 R2 server.
Issue: PXE boot is extremely slow, it takes up to more than 60 minutes for the device to download download the PXE boot
Things I already tried to get this up and running:
I've tried to change the TFTP block size via command prompt and via regedit
I've changed the settings on the tab of the WDS role (go to WDS role -> properties on server -> Tab "tftp")
Both actions resulted in PXE boot being even slower than it already was.
To make sure this is not because of our environment I’ve set up the same configuration on a windows server 2008 R2, here PXE boot image is downloaded to the machine within 3 minutes.
Both servers are set up through Hyper-V this is the configuration:
2008 R2:
Memory: 4096 MB
1 Virtual processor
IDE controller 2 hard drives
Network adapter
2012 R2:
Memory: 4096 MB
32 virtual processors
SCSI controller 2 hard drives
Network adapter
I can’t imagine that PXE boot is not working because of the differences of the Hard drives controllers or because of the amount of the virtual processors.
Windows server 2012 R2 seems to handle PXE boot TFTP differently in comparison to 2008 R2.
Do you guys know what I can do/try to get this working?

Hi Jacques Rodrigues,
You can run Windows Deployment Services on Hyper-V virtual machines,
that the performance will often be degraded, particularly during the Trivial File Transfer Protocol (TFTP) download phase. This phase is very resource-intensive and may
fail if insufficient resources are available on your server running Hyper-V.
If you are using multicast, Check if IGMP Snooping is enabled i.e. Routers that support multicasting. In particular, Internet Group Membership Protocol (IGMP) snooping should
be enabled on all devices. This will cause your network hardware to forward multicast packets only to those devices that are requesting data. If IGMP snooping is turned off, multicast packets are treated as broadcast packets, and will be sent to every device
in the subnet.
The related KB:
Windows Deployment Services Overview
http://technet.microsoft.com/en-us/library/hh831764.aspx
I’m glad to be of help to you!
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Windows Server 2012 R2 GPO Loginscript is executed with more than 2 minutes delay after login

Hi everybody
A strange problem came up in a new Windows Active Directory Domain (one single DC with Windows Server 2012 R2 Essentials): after configuring a User GPO with a Powershell Loginscript and applying the GPO to an User OU, the following happens: when a
User logs into a PC or Server, the Loginscript does not run within the first 120 - 150 seconds, and then suddenly the Scripts runs and completes within seconds. What could be the reason for such a long delay?
When I run the Powershell Script manually it runs immediately and finishes within seconds. But assigned through a GPO it takes really long to run. I also tried a very "simple" Loginscript with only one command (map a network share) - but this Script
also runs with a long delay. So the script does not seem to be the problem but the Logon Procedure. I even tried the same script with a locally defined GPO on a Windows Server 2012 R2 (just to check whether it might be a NETLOGON/SYSVOL share problem), but
no luck - it takes 2 to 3 minutes until the Script is run. I went a bit further and realized that the problem is only related to the latest OS Windows 8 (8.1) / Windows Server 2012 (R2) but not to older windows system. So what changed in the logon process
of the new Windows versions? Why are GPO applied with a such a long delay?
Any ideas?
Mark

Other people have reported similar issues
http://www.edugeek.net/forums/windows-8/128421-group-policy-logon-scripts-delayed-5-minutes-windows-8-1-design.html
Rgds
Milos

Print Management Console displays no printers after applying Windows Update for Windows Server 2012 R2 (KB2995388)

After installing optional Windows Update for Windows Server 2012 R2 (KB2995388) on a print server upgraded from Windows 2012 to Windows 2012 R2, the Print Management Console wouldn't display locally shared or remotely shared printers. Another print server
could see the printers on this server, but it couldn't see it's own. Removal of the patch resolved the issue.

Hi,
à
Removal of the patch resolved the issue.
Thanks for sharing in the forum. Your time and efforts are highly appreciated.
On current situation, would you please let me confirm something more?
Please check if this update rollup package (KB2995388) install successfully.
Please run sfc /scannow command to scan all protected system files after installed this update.
If be possible, please re-install Print Server feature on the server after installed this update. Any find?
If any update, please feel free to let me know.
Hope this helps.
Best regards,
Justin Gu

Windows Server 2012 R2 boots in CMD after several Restarts

Similar Messages

Maybe you are looking for