Share via

Windows Server 2012 R2 Reboot automatically in night every Wednesday 2:30 AM

Jatinder Sandhu 5 Reputation points
2023-06-23T06:29:56.6766667+00:00

no changes done from our side and system is getting reboot every Wednesday night 2:30 AM.

The process C:\WINDOWS\system32\wbem\wmiprvse.exe  has initiated the restart of computer FEI-18-0390 on behalf of user NT AUTHORITY\SYSTEM for the following reason: No title for this reason could be found"

Reason Code: 0x80070015

Shutdown Type: restart

Windows Server 2012
Windows Server 2012
A Microsoft server operating system that supports enterprise-level management, data storage, applications, and communications.
1,552 questions

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Dave Patrick 426.3K Reputation points MVP
    2023-06-23T14:57:55.23+00:00

    WmiPrvSE.exe is Windows Management Instrumentation (WMI) Provider Host process.  Check for clues in \Applications and Service Logs\Microsoft\Windows\WMI-Activity\Operational

    --please don't forget to upvote and Accept as answer if the reply is helpful--

  2. Limitless Technology 44,031 Reputation points
    2023-06-23T15:01:57.4633333+00:00

    Hello Jatinder,

    Thank you for your question and for reaching out with your question today.

    The reason code 0x80070015 indicates a "Device not ready" error. This error typically occurs when there is a problem with accessing or communicating with a device, such as a disk drive, during the reboot process. It could be caused by various factors, including hardware issues, driver problems, or file system corruption.

    To troubleshoot and resolve the automatic reboot issue on your Windows Server 2012 R2, you can try the following steps:

    1. Check Event Viewer: Open the Event Viewer on the server and navigate to the System log. Look for any related events or errors around the time of the automatic reboot. These events may provide more specific information about the cause of the reboot.
    2. Hardware Check: Verify that all hardware components are functioning correctly. Check the server's disks, cables, and connections to ensure there are no physical issues. Run hardware diagnostics or check the server's logs for any hardware-related errors.
    3. Update Drivers and Firmware: Ensure that all device drivers and firmware are up to date. Check the manufacturer's website for the latest driver and firmware versions for your server's hardware components. Update them if necessary.
    4. Scan for Malware: Run a thorough scan for malware and viruses on the server using an updated antivirus software. Malware or viruses can sometimes cause unexpected system behavior, including automatic reboots.
    5. Check Disk Integrity: Perform a disk check to verify the integrity of your server's file system. Open a Command Prompt with administrative privileges and run the following command: 
      
   chkdsk C: /f /r
      This command will check the C: drive and fix any errors it finds. You may need to restart the server for the disk check to complete.
    6. Review Scheduled Tasks: Check if there are any scheduled tasks or scripts configured to run at the specified time (Wednesday 2:30 AM). Make sure that none of these tasks or scripts are initiating the reboot unintentionally.
    7. Windows Updates: Review the Windows Update settings and ensure that the server is not set to automatically install updates and reboot. Check if any updates were installed recently that may have triggered the reboot.
    8. Group Policy Settings: Review the Group Policy settings applied to the server and check if any policies are configured to enforce automatic reboots. Look for policies related to Windows Update or system maintenance.

    I used AI provided by ChatGPT to formulate part of this response. I have verified that the information is accurate before sharing it with you.

    If the reply was helpful, please don’t forget to upvote or accept as answer.