Event-566, kernel-power event logged when triggering a graceful reboot, system not rebooting

Question

Hi, I am looking for help to resolve this graceful reboot issue that we are facing with Windows Server 2022.

Steps:

1. Boot to Windows Server 2022 OS
2. Below event gets logged in around 30 minutes to 1 hour after boot.
   Event-566, kernel-power
   The system session has transitioned from 0 to 1.
   Reason: 22
3. Issue a graceful reboot of the system from the server cli.
   System doesn't go for a reboot, but the below kernel-power event gets logged:
   Event-566, kernel-power
   The system session has transitioned from 1 to 3.
   Reason: 22
4. Issue another graceful reboot again and the system goes for a reboot.

What is the significance of "Event-566, kernel-power" event? What happens in the system when this event gets generated? which system session transition is happening?

Any help to identify the root cause of this issue and resolution will really help.

Answer 1

Hi PasupathiGayathri-5449,
Thank you for your post.
Correct power state change for Windows computer that supports these power state (such as shutdown, start, sleep, hibernates etc) changes is provided by Kernel Power.
Event ID 566 Kernel power failure pretty much indicates a problem by asking user or the application for permission. Event data permissions and power settings may cause this operation to fail. These error messages can be related to power supply issues, RAM, additional devices, hard disk or file problems. You might fix the problem by checking the OS state and updating the machine. There are useful methods that you can use to successfully troubleshoot Power Kernel problems. They are all listed below:
Change power options.
Update all local drivers.
Disable fast startup.
check for update to install the latest updates.
Update the BIOS.
https://bestpctips.com/fix/how-to-fix-event-id-566-kernel-power-error/
Meanwhile, I suggest that we could check if any event id 41 and 6008 could be found. They always refer to unexpected restart. Than check for the bugcheckcode. Click the detail option to check the bugcheck code, if the codes all are 0. It may be related to the hardware.

If the answer is helpful, please click "Accept Answer" to help other community members find the helpful reply quickly. Thanks.

Best Regards,

Carl