Выключается windows server 2016

Do your Windows 2016 Servers have mysterious shutdown issues?

Картинка с сайта: www.checkyourlogs.net

Today, I tried to troubleshooting windows 2016 mysterious shutdown for my client, I found it was NT Authority\System that shutdown the system because the windows 2016 server license was expired, this is easy enough to solve the issues, I thought.

Картинка с сайта: www.checkyourlogs.net

I went to the system settings and type the product key, but it shows the error message “This edition cannot be change be upgraded”, seriously, I cannot use the MSDN product for upgrading it from evaluation version to Data Center (or Standard) version?????

I don’t believe this, so I tried another way via DISM command for this as follow:

1. Open an elevated command prompt

2. Run DISM /Online /Set-Edition:ServerStandard /ProductKey:your-product-key-here /AcceptEula

   Ps. If you would like to upgrade to Data center version, you just need to change ServerStandard to ServerDatacenter.

3. Reboot server after the operation completed successfully.

Ya! Activated successful. We won’t get any mysterious shutdown now.

Hope you enjoy this post.

Cary

Привет. Недавно столкнулся с очень неприятной ситуацией — часть серверов начала самопроизвольно выключаться. Какой — либо закономерности в выключениях проследить не удавалось. Единственное что объединяло серверы — это то что на них была установлена ОС Windows Server 2012 или выше, и большая их часть имеет роль терминальных. Ах да, еще все эти серверы — виртуальные и работают под управлением Hyper V. Хочу сегодня рассказать, в чем была проблема.

Конечно, любая диагностика должна начинаться с анализа логов. И вот какое событие удалось обнаружить непосредственно перед выключениями серверов – событие 1074, user32:

The process C:\Windows\system32\winlogon.exe (DC) has initiated the power off of computer DC on behalf of user NT AUTHORITY\SYSTEM for the following reason: No title for this reason could be found

 Reason Code: 0x500ff

 Shutdown Type: power off

 Comment:

Картинка с сайта: www.mytechnote.ru

По ним становится понятно, что работа завершается штатно. Что в общем то позволяет исключить влияние железа, хотя оно и так было исключено, т. к. все серверы виртуальные. Под подозрение попал гипервизор, но рысканье вдоль и поперек по логам ни какого результата не дало. События относящиеся к завершениям работы не имели отношения к инициализации завершения работы. Говорят, что виртуальные машины могут в редких случаях произвольно выключаться, если есть проблемы со свободной памятью, но в моем случае памяти было более чем достаточно.

В общем думаю хватит томить, и пора рассказать вам, в чем же в итоге было дело. Подключившись по RDP, я сидел и размышлял, что же может быть причиной подобного завершения работы. И вот из-за бездействия меня выбило на экран ввода пароля, где я обнаружил вот такой экран:

Картинка с сайта: www.mytechnote.ru

Обратите внимание на нижний угол:

Да, это мать его, завершение работы системы. Оказывается с 2012 винды MS сделали эту кнопку доступной при подключении по RDP.

Отвечает за эту кнопку параметр в групповой политике –

Computer Configuration – Policies – Windows Settings – Local Policies – Security Options – Shutdown: Allow system to be shut down without having to log on.

Картинка с сайта: www.mytechnote.ru

Отключаем его и всё, возможности выключить сервер у пользователей не будет.

Почему в моем случае этот параметр оказался включенным – остается загадкой. Скорее всего кто-то когда-то давным-давно его включил. Хотя, не исключаю, что он оказывается включенным при переходе с 2008 домена, проверять, честно говоря, лень. Кто в курсе, напишите в комментариях, в каком состоянии находится этот параметр при добавлении контроллера домена Windows 2012 в домен с уровнем 2008r2 или ниже.

В общем и целом, после изменения этого параметра мистические выключения прекратились.

Картинка с сайта: www.mytechnote.ru

Надеюсь, информация окажется вам полезной.

Картинка с сайта: voltfixer.com

Why Does My Windows Server Keep Restarting?

Is your window server on an uncontrollable loop of restarting? If so, there could be many reasons why this is happening.

Some of the reasons are as follows:

• Hardware failure:
• RAM and deteriorating condition of the slot
• Faulty hardware
• Overheating
• Working conditions of the CPU
• Problem and infestation through external devices

Updates: You may have recently updated your Windows server. Viruses and other malware may cause your server to keep restarting. Malware infection is one of the leading causes of restarting continuously.

Outdated drivers: Outdated drivers are another cause. They may prompt your Windows server to keep restarting.

Default settings: If an automatic restart is the default setting on your Windows server, then it can keep restarting. People often do not even consider this as a reason and discard it without checking their default settings.

There are already too many problems going on in the world. Your windows server 2012 restarting continuously shouldn’t add to your set of problems.

The easiest way to prevent it from restarting is to find out the reason for the problem.

You can easily fix the constant restarting. Often, the default settings are set on the option of an automatic restart. We don’t even check to see our settings.

Therefore, check and ensure that your automatic restart is not your default setting.

1. Switch on the device.
2. Be alert when you turn on your device.
3. Press and hold the F8 key for a few seconds.
4. Do this before the Windows logo appears on the screen.
5. Doing this will bring up the boot menu.
6. Choose the safe mode from the listed options.
7. Now, boot your device through the safe mode.
8. Next, press the combination of Windows Key and letter R key.
9. This will prompt a run dialog box.
10. In the blank field, enter “sysdmm.cpl” and click OK.
11. Following this, move on to the advanced tab.
12. Click on the settings button. You will find it under the start-up and recovery section.
13. Navigate to the automatic restart option. It is present under system failure.
14. Unselect it if it is the default setting.
15. Make sure to check the box beside, “write an event to the system log.”
16. Selecting it will keep a record of the reoccurring problems in the system.
17. Click on OK and save your changes.

Windows Server 2012 R2 is stuck on restart

If your windows server 2012 r2 keeps on restarting, try checking the method mentioned above.

Method 1: 

1. Check the default settings, as mentioned above.
2. Use the command prompt and press F8. Boot the device under safe mode.

Method 2:

Alternatively, you can use the following method to stop your windows server r2 from restarting.

1. Press the F8 key to launch the command prompt.
2. As the command prompt opens up, type the following in the blank field: “wmic logicaldisk get name.”
3. Following this, type in “dism.exe / image: C:\ /cleanup-image /revertpendingactions.”
4. The device will reveal the image.
5. Most probably, the image will be D:.
6. If this does not work for you, consider seeking a professional opinion.

Windows Server 2012 stuck on installing updates

This is a bit complicated and can even result in some loss. So, alert yourself and read and follow the instructions carefully.

1. Click on the search icon.
2. Input “regedit” into the blank field. (Don’t type in the quotes).
3. Press the enter key.
4. Navigate to the following path:

“HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\CurrentVersion\ProfileList”

1. To begin with, make a backup copy of the registry. You can lose your data, so make sure to create a backup copy.
2. You can easily fix your mistakes, even if you end up losing data.
3. Go through the profile list ID’s.
4. See if you find out some with the profile image path.
5. If you find these, delete them.
6. Exit the registry editor and restart your computer.
7. See if the problem persists.

Windows Server 2012 R2 VM stuck on restarting

Method 1:

1. Begin with checking the default settings.
2. Reboot under the safe mode.

Method 2:

1. Go to the registry editor and navigate to the following path:

“HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\CurrentVersion\ProfileList”

1. Ensure that you have a backup copy of the registry. This way, you will not lose data even if you end up making a mistake.
2. Go through the profile list ID’s and look for the ones with the profile image path.
3. Delete these files as you find them.
4. Exit the registry editor and restart your device.

Check if the problem still exists. If it does, seek a professional opinion.

Windows Server 2012 windows update is stuck

If the Windows server 2012 freezes on the Windows update, the problem may lie in faulty hardware parts. Some of the hardware parts that may cause it to freeze on updates are:

RAM

1. In the case of RAM or Random Access Memory, begin by checking the RAM.
2. Check the condition of the slot.
3. For this, remove the RAM from the slot very carefully. Clean both of them.
4. Insert the RAM back into the slot.
5. See if the problem persists.

CPU

CPU is the most important component of your device. Since it is the computer’s brain, if there is a problem with the CPU, then there could be other problems as well.

Overheating can cause your Windows server 2012 to freeze on windows updates.

1. For this, check if the CPU is working properly.
2. Tidy the CPU.
3. Remove the dust and clean the slots.
4. Ensure that the fans and the surrounding components are clean.
5. Restart your computer.
6. Check to see if the problem persists.

External Devices

External devices can also create this problem and put your device on a loop of updating your computer.

1. Begin with unplugging all external devices.
2. Restart your computer.
3. Check to see if there is any problem.
4. If there is no further problem, it means that there is a predicament in your external device.
5. You can plug the external devices one by one to identify which is the faulty external device.
6. Remember to restart your computer every time you unplug an external device, or else you might not find the faulty device.

Windows Server 2012 won’t reboot after update

For fixing a Windows server 2012 that won’t reboot after an update, try the following method:

1. Reboot your windows server 2012 without installation of media.
2. For this, press the power button. A loop of white circles will appear on the screen.
3. Press the power button again to power off the server. Switch on using the power button again.
4. Turn it off again when the circles appear. Start the server for the third time.
5. This will initiate the preparing automatic repair option. It will take about 3-5 minutes.
6. Reboot to recovery mode and click on troubleshoot to choose from recovery mode options.
7. Choose an option. Click on troubleshoot.
8. The advanced options screen will appear.
9. Now, click on the command prompt.
10. As the command prompt opens, type to input the following: “dism / image: C: \ /cleanup-image /revertpendingactions”. Press enter.
11. This command will navigate drive C. If it does not exist on drive C, change it to a different letter.
12. If you are not sure about its location, type dir c: and press enter. Try dir d: if you are still unable to locate it.
13. Next, type exit and press enter.
14. Shut down your device.
15. Use the power button to reboot it again.

Windows Server 2012 keeps crashing

If the server keeps on crashing, try the methods mentioned above. Some of them are as follows:

1. Check the hardware components. Clean the components and insert them again.
2. Delete all the unwanted and bad registry files. After doing this, exit the registry and restart the computer to see if the problem persists.
3. You can also try rebooting under the safe mode as instructed above.

Windows Server 2016 keeps shutting down

Your Windows server 2016 can keep shutting down because of an infestation by a virus and other such malware.

1. To check if this is why your server keeps shutting down, run a complete virus scan.
2. You can use Windows Defender or any other famous security virus detection software.
3. The software will go through your system and find malware and harmful viruses.
4. It will delete them for you. Restart your computer.
5. Check to see if the problem still persists.

Windows Server 2016 has an unexpected shutdown

In case of an unexpected shutdown, the problem can be the same.

Method 1:

1. Run a virus scan using Windows Defender or any other virus and malware detection software.
2. After the software looks through your system and finds and deletes them, restart your device to see if the problem persists.

How to Fix Windows Server 2016 that keeps crashing

To fix a Windows server 2016 that keeps crashing, try restoring from recovery environment.

Method 1

Before you use this method, remember that you can only use it if you have enabled a system restoration before the Windows server keeps crashing.

Furthermore, it is important to have a valid restore point.

1. Boot your server to the recover environment.
2. Choose the desired option from the screen. Then, click on troubleshoot.
3. When the advanced options appear on the screen, select system image recovery.
4. The screen will display user profiles. Choose the user that has administrative privilege.
5. Type in the password and click on continue.
6. Select a restore point and use the wizard to restore the server.
7. Reboot the system finally.

Windows Server 2012 update is stuck

1. Consider updating your drivers. Outdated drivers can cause a loop of updates or freeze on updates.
2. This can point to the fact that your hardware and software components are unable to communicate well. You can manually update the drivers.
3. Go to the manufacturer’s website.
4. Look for drive installers.
5. Install the right one for your device.

Windows Server 2016 keeps checking for updates

1. Again, this could be because of outdated drives.
2. Update them, as mentioned above.
3. You can also check the hardware components and see if they work properly and to the best of their abilities.

Why won’t Windows server 2016 install updates?

Your Windows server 2016 is probably not installing updates because of the Windows update agent’s incompatible RTM version. Fix this by installing the latest version.

1. Locate the file in the Windows update catalog and download it.
2. Also, you can access the latest version from the cumulative security update.

Windows Server 2016 is not activated

1. Go to Run.
2. Type “slui”.

SLUI 1 shows the activation status window.

SLUI 2 displays the activation window.

SLUI 3 displays the “change product key” window.

SLUI 4 displays the “call Microsoft and manually activate” window.

1. Enter your product key