Your PC Restarts Instead of Shutting Down — Fast Startup Explained

30 Jul 2026

You select Shut down in Windows 11. The screen goes black, the fans slow down—and then the manufacturer’s logo appears again.

Instead of switching off, the computer has restarted.

On another PC, the machine appears to power down completely but turns itself back on a few seconds later. Some computers remain on a black screen with their lights and fans running, while others briefly display an error before returning to the Windows sign-in screen.

These symptoms may look identical, but they can have very different causes:

Windows Fast Startup
A driver failing during hybrid shutdown
A hidden blue-screen or stop-code error
Automatic restart after a system failure
A keyboard, mouse or network adapter waking the computer
A scheduled wake timer
Windows Update
Incorrect power-button settings
USB devices or docking stations
BIOS or UEFI power settings
A failing power supply, battery or motherboard

Fast Startup is a sensible first place to investigate, but it is not responsible for every restart-after-shutdown problem.

The safest approach is to establish whether Windows is genuinely restarting, failing to complete shutdown or successfully powering off and then being switched back on by another trigger.

First: Work Out What the Computer Is Actually Doing

Watch the complete shutdown process carefully.

Windows immediately begins booting again

You select Shut down, the display turns off briefly and then the manufacturer’s logo or Windows loading animation appears.

This usually points towards:

A shutdown failure
A driver or firmware problem
Fast Startup
An automatic restart after a Windows crash

The computer powers off, pauses and then switches back on

The fans and lights stop completely before returning a few seconds later.

This is more likely to involve:

Wake-on-LAN
A USB wake event
A scheduled wake timer
An automatic power-on setting in the firmware
A faulty power button
A motherboard or power-supply problem

The screen turns off, but the computer remains powered

The monitor goes black, but the fans, keyboard lights or power LED remain active.

This suggests that Windows has started shutting down but a driver, service or connected device is preventing the transition from completing.

A blue or black error screen flashes briefly

Windows may be crashing during shutdown and automatically restarting before you have time to read the stop code.

Microsoft confirms that Windows 11 can restart unexpectedly when it encounters a serious problem, sometimes displaying a stop-code message only briefly. (Microsoft Support⁠)

What Fast Startup Actually Does

Fast Startup is also known as hybrid shutdown.

During a traditional full shutdown, Windows closes user sessions, stops services, unloads drivers and shuts down the Windows kernel.

With Fast Startup enabled, Windows still signs out every user and closes open applications. However, it saves the kernel session, loaded drivers and selected system state into the hibernation file.

The next time the PC starts, Windows reloads that saved state instead of initialising the kernel, drivers and services entirely from the beginning. This can reduce startup time. (Microsoft Learn⁠)

Fast Startup is therefore different from ordinary sleep:

Sleep preserves the current user session in memory.
Hibernate saves the complete current session to storage.
Fast Startup signs users out but preserves part of the Windows system session.
Restart normally performs a complete shutdown and fresh boot.

Microsoft notes that selecting Restart performs a full boot cycle rather than using the saved Fast Startup state. (Microsoft Learn⁠)

Why Fast Startup Can Cause Shutdown Problems

Fast Startup depends on drivers, devices and firmware entering a suitable hibernation-style state.

If a driver does not handle that transition correctly, Windows may:

Hang on a black screen
Fail to power off
Return immediately to the boot screen
Restore a faulty driver state at the next startup
Leave USB, graphics or network hardware behaving incorrectly
Delay the completion of certain updates

Microsoft has documented failures involving Fast Startup, hibernation and shutdown transitions. It also notes that some updates require a full restart because Fast Startup does not perform a traditional full shutdown. (Microsoft Learn⁠)

Fast Startup may expose an existing driver or firmware problem rather than being the underlying fault itself.

Disabling it is therefore a useful diagnostic test.

Test a Full Shutdown Before Changing Settings

Save your work and close all applications.

Open Terminal or Command Prompt as administrator and run:

shutdown /s /t 0

The /s option shuts down the computer, while /t 0 specifies no delay.

Microsoft’s command documentation uses the separate /hybrid option when a shutdown should prepare the system for Fast Startup. Running the command without /hybrid therefore provides a useful full-shutdown test. (Microsoft Learn⁠)

Interpret the result

The PC now stays off

Fast Startup or a component involved in hybrid shutdown is probably contributing to the problem.

Disable Fast Startup and test several normal shutdowns.

It still restarts immediately

The fault is unlikely to be caused solely by Fast Startup.

Check for:

A hidden system crash
Automatic restart after failure
Drivers
Firmware
Wake or power-on settings
Hardware problems

It switches off and powers back on after a pause

Windows may have completed shutdown successfully. Investigate wake devices, timers and firmware power settings.

Disable Fast Startup

Open Control Panel, then select:

Hardware and Sound > Power Options

Select:

Choose what the power buttons do

Then:

Select Change settings that are currently unavailable.
Find Shutdown settings.
Clear Turn on fast startup (recommended).
Select Save changes.
Restart the computer once.
Perform a normal shutdown and test it.

Microsoft’s Power Options interface places shutdown, sleep, hibernate, lid and power-button controls under Choose what the power buttons do. (Microsoft Support⁠)

Test several shutdowns rather than judging the result after only one attempt.

Will disabling Fast Startup damage anything?

No. Windows can operate normally without Fast Startup.

The main difference is that the next cold startup may take slightly longer because Windows performs a more complete initialisation.

Restarting Windows already bypasses the Fast Startup boot path, which is why Restart can sometimes temporarily correct a problem that returns after shutting down and powering on again. (Microsoft Learn⁠)

The Fast Startup Option Is Missing

Fast Startup depends on Windows hibernation support.

Open Terminal or Command Prompt as administrator and run:

powercfg /a

This displays the power states available on the computer.

If hibernation is disabled, the Fast Startup option may not appear. Microsoft’s powercfg utility provides commands for checking available sleep states and enabling or disabling hibernation. (Microsoft Learn⁠)

To enable hibernation:

powercfg /hibernate on

To disable hibernation:

powercfg /hibernate off

Disabling hibernation also prevents Fast Startup from using the hibernation file.

Do not alter Registry values from an unverified guide merely to expose or disable Fast Startup. Use the supported Control Panel and powercfg methods.

Check What the Physical Power Button Does

You may be using the computer’s physical power button rather than the Start menu.

Open:

Control Panel > Hardware and Sound > Power Options > Choose what the power buttons do

Review:

When I press the power button
When I press the sleep button
When I close the lid

Make sure the power button is configured as:

Shut down

rather than:

Sleep

Hibernate

Do nothing

Windows allows laptops and desktops to assign different actions to the power button and laptop lid. (Microsoft Support⁠)

Test shutdown from the Windows Start menu as well as from the physical button. If only one method fails, its configured action may be responsible.

Check for a Hidden Windows Crash

Fast Startup is not the only reason a PC can appear to restart instead of shutting down.

Windows may encounter a stop error during shutdown and immediately reboot.

Disable automatic restart temporarily

Press:

Windows key + R

Enter:

sysdm.cpl

Select OK.

Then:

Open the Advanced tab.
Under Startup and Recovery, select Settings.
Under System failure, clear Automatically restart.
Select OK.
Attempt another shutdown.

If Windows crashes again, it should remain on the error screen long enough for you to record:

The stop code
Any named driver
The displayed error
The time of the failure

This setting does not fix the crash. It prevents the automatic reboot from hiding the diagnostic information.

Review Event Viewer

Open Start and search for:

Event Viewer

Review:

Windows Logs

> System

Look around the time of the failed shutdown for:

BugCheck events
Driver errors
Disk errors
Service failures
Kernel-Power events
Unexpected shutdown entries

Kernel-Power Event ID 41 means Windows detected that the previous session did not shut down cleanly. It confirms that an unexpected power loss, crash or restart occurred, but it does not by itself identify the cause. (Microsoft Learn⁠)

An Event ID 41 can result from:

A Windows crash
The power button being held
A failed power supply
A battery fault
Overheating
A system freeze
Sudden loss of mains power

Treat it as evidence of an abnormal shutdown, not proof that one specific component has failed.

Install Windows and Driver Updates

Shutdown problems can begin after:

A graphics-driver change
A chipset update
A network-driver update
New USB hardware
Docking-station firmware changes
A Windows update
A BIOS or UEFI update

Open:

Settings > Windows Update

Install available updates and restart the computer.

Then check:

Settings > Windows Update > Advanced options > Optional updates

Also obtain model-specific updates from the computer manufacturer for:

Chipset
Graphics
Storage
Network adapters
USB-C and Thunderbolt
Docking stations
Power management
BIOS or UEFI
Embedded-controller firmware

Microsoft recommends updating Windows and drivers when troubleshooting unexpected restarts and stop-code errors. (Microsoft Support⁠)

Avoid generic third-party driver-update utilities.

Pay Particular Attention to Network and Graphics Drivers

Network and graphics adapters frequently participate in power-state transitions.

A driver that works normally while Windows is running may still fail when Windows asks it to enter the state required for Fast Startup or shutdown.

Possible symptoms include:

The screen becoming black while the PC stays on
The PC powering back on immediately
The monitor losing signal but fans continuing
The network adapter waking the machine
Shutdown working in Safe Mode but not normally
The problem beginning after a driver update

Open Device Manager and check for warning symbols.

When the problem began immediately after a driver update, open the device’s Properties > Driver tab and check whether Roll Back Driver is available.

Use the computer manufacturer’s driver where its power-management configuration is specific to the model.

Disconnect External Devices

Before changing advanced settings, test the computer with non-essential hardware disconnected.

Remove:

USB storage
Printers
Scanners
Webcams
USB hubs
External sound devices
Game controllers
Card readers
Docking stations
External drives
Unnecessary monitors
Wireless receiver dongles

Keep connected only:

Power
One display
Keyboard
Mouse

Perform a shutdown.

If the computer stays off, reconnect devices one at a time until the problem returns.

A faulty device, driver or dock can interfere with shutdown or immediately wake a hibernated Fast Startup session.

Check What Woke the Computer

When the PC powers off and then returns, use Windows’ power diagnostics.

Open Terminal or Command Prompt as administrator.

Check the most recent wake source

powercfg /lastwake

This reports information about the source responsible for the last transition out of a sleep or hibernation state.

Check active wake timers

powercfg /waketimers

This lists active timers that have requested permission to wake the computer.

Check devices allowed to wake Windows

powercfg /devicequery wake_armed

Common results may include:

A network adapter
Keyboard
Mouse
USB controller
Bluetooth adapter

Microsoft documents /lastwake, /waketimers and /devicequery wake_armed as supported methods for identifying wake sources and devices. (Microsoft Learn⁠)

These commands are especially relevant when Fast Startup leaves the computer in a hibernation-based power state rather than a traditional complete shutdown.

Stop an Unwanted Device Waking the PC

When powercfg /devicequery wake_armed identifies an unnecessary wake-capable device, open Device Manager.

Find the device, then:

Right-click it.
Select Properties.
Open Power Management, where available.
Clear Allow this device to wake the computer.
Select OK.
Test shutdown again.

You can also disable wake permission from an administrator command prompt:

powercfg /devicedisablewake "Exact device name"

Use the exact name returned by:

powercfg /devicequery wake_armed

Microsoft documents /devicedisablewake as the command for preventing a specified device from waking the system. (Microsoft Learn⁠)

Do not disable wake capability for every device without identifying the actual source. You may still want to wake the computer using its keyboard or network management platform.

Check Wake-on-LAN

A network adapter can be configured to start or wake a computer when it receives a particular network packet.

This is useful for:

Remote IT support
Scheduled patching
Backups
Remote management
Starting office PCs before employees arrive

It can also cause a PC to appear to restart immediately after shutting down.

Open Device Manager, expand Network adapters and open the relevant Ethernet adapter.

Review the Power Management and Advanced tabs for settings such as:

Allow this device to wake the computer
Only allow a magic packet to wake the computer
Wake on Magic Packet
Wake on Pattern Match
Shutdown Wake-On-LAN
Wake from power off

The exact names depend on the network-adapter manufacturer.

For a home PC that does not require remote wake capability, disable the relevant wake setting and test again.

On a business device, ask the IT provider first. Wake-on-LAN may be required for maintenance and support.

Check Scheduled Wake Timers

Windows and installed applications can create tasks that wake a computer from sleep or hibernation.

Run:

powercfg /waketimers

If a task is shown, open:

Task Scheduler

Review the named task and its Conditions tab.

Look for:

Wake the computer to run this task

Possible sources include:

Windows maintenance
Backup applications
Update tools
Manufacturer support software
Media-recording software
Business management agents

Microsoft documents wake timers as requests that can wake a system from supported sleep and hibernation states. (Microsoft Learn⁠)

Do not delete Microsoft or company tasks simply because they can wake the computer. Determine whether the task is required and change only the wake condition where appropriate.

Check BIOS or UEFI Power-On Settings

If Windows appears to shut down fully but the computer powers itself back on, open the BIOS or UEFI setup and review power-management settings.

Possible names include:

Wake on LAN
Power on by PCI-E
Resume by USB device
Wake by keyboard
Wake by mouse
Power on by RTC
Scheduled power on
USB wake support
Restore on AC power loss
After power failure
Automatic power on

The wording and location vary by manufacturer.

Restore after AC power loss

This setting determines what happens when mains power returns after an interruption.

Possible values include:

Stay off
Power on
Last state

A failing extension lead, loose power cable or brief mains interruption combined with Power on or Last state can make the computer appear to restart after shutdown.

Record the original firmware settings before making changes.

Save the BitLocker recovery key before updating firmware or making significant security-related changes.

Check for Windows Update Restarts

Windows updates sometimes require a restart to complete installation. Windows normally attempts to arrange required restarts according to active hours and user activity. (Microsoft Support⁠)

Open:

Settings > Windows Update

Check:

Whether a restart is pending
Update history
Failed installations
A scheduled restart
Active hours

Perform a deliberate Restart to complete pending updates, then test a normal shutdown.

Remember that Fast Startup may prevent some update work from completing through an ordinary shutdown, whereas Restart performs a full boot cycle. (Microsoft Learn⁠)

Perform a Clean Boot

When shutdown works with Fast Startup disabled but fails after it is re-enabled—or when a background program appears responsible—use a clean boot to isolate third-party services.

Press:

Windows key + R

Enter:

msconfig

Then:

Open the Services tab.
Select Hide all Microsoft services.
Select Disable all.
Open the Startup tab.
Select Open Task Manager.
Disable the enabled startup items.
Restart Windows.
Test shutdown.

Always select Hide all Microsoft services before disabling services.

Microsoft describes clean boot as a controlled method for starting Windows with essential components while isolating software conflicts. (Microsoft Support⁠)

Shutdown now works

A third-party service or startup application is contributing.

Re-enable half of the disabled items, restart and test again. Continue narrowing the selection until the responsible software is identified.

Shutdown still fails

The cause is more likely to involve:

A Microsoft or device driver
Windows components
Firmware
Power hardware
A wake source
A motherboard setting

Restore normal startup after the testing is complete.

Check Safe Mode

Safe Mode starts Windows with a limited set of drivers and services.

To enter it:

Open Settings > System > Recovery.
Beside Advanced startup, select Restart now.
Select Troubleshoot.
Select Advanced options.
Select Startup Settings.
Select Restart.
Choose Safe Mode.

Microsoft recommends Safe Mode for determining whether a problem is caused by the normal set of drivers and services. (Microsoft Support⁠)

If the computer shuts down correctly in Safe Mode, investigate third-party drivers, services and security applications.

Repair Windows System Files

When the problem persists after driver and software testing, damaged Windows components may be involved.

Open Terminal or Command Prompt as administrator and run:

DISM.exe /Online /Cleanup-Image /RestoreHealth

After it completes, run:

sfc /scannow

Restart Windows and test shutdown again.

These commands should not be treated as generic performance optimisers. They are appropriate when failed servicing, update problems or damaged Windows components are realistic possibilities.

Consider a Windows Repair Reinstallation

Windows 11 includes a recovery option that can reinstall the current Windows version while preserving files, applications and settings on supported devices.

Open:

Settings > System > Recovery

Look for:

Fix problems using Windows Update

Microsoft describes this option as a way to reinstall the current Windows version and repair system files and components. Availability can depend on the Windows version and organisational management policies. (Microsoft Support⁠)

Back up important data before beginning any repair process.

Do not reset or reinstall Windows before checking wake sources and hardware. A clean Windows installation will not correct a faulty power button, power supply or motherboard.

When the Problem May Be Hardware

Hardware becomes more likely when:

The PC restarts even after a command-line full shutdown.
The issue occurs outside Windows.
It powers on when the case is moved.
The physical power button feels stuck.
The system loses power briefly before restarting.
Kernel-Power events occur during normal use as well.
The computer restarts under heavy load.
There is overheating, burning or electrical noise.
The problem began after installing internal hardware.
Disconnecting USB devices and disabling wake sources makes no difference.

Possible hardware causes include:

A sticking case power button
Incorrect front-panel motherboard wiring
A failing desktop power supply
A damaged laptop battery
A motherboard power-control fault
Unstable memory
Overheating
A faulty graphics card
A short circuit
An unstable overclock

Stop using the machine immediately if you notice smoke, sparking, a burning smell or excessive heat.

Do not open a power-supply unit. Its internal components can retain dangerous electrical charge after disconnection.

Common Mistakes to Avoid

Assuming Fast Startup is always the cause

It is a useful test, but a genuine system crash or hardware power-on event requires different troubleshooting.

Editing the Registry first

Use supported Power Options and powercfg controls before making low-level changes.

Disabling every wake device

Identify the actual wake source and preserve required remote-management capability.

Deleting scheduled tasks

A task may be required for security, backup, maintenance or business management.

Disabling Windows Update

Complete pending updates and investigate failures instead of removing security patching.

Holding the power button after every shutdown

Forced power-offs can cause file corruption and make the Event Viewer evidence less useful.

Resetting Windows too early

A Windows reset will not repair firmware settings, Wake-on-LAN, a faulty power button or a failing power supply.

Disabling business security tools

Endpoint protection, monitoring and management agents may be controlled by organisational policy. Contact IT before altering them.

A Practical Shutdown Troubleshooting Checklist

When a Windows 11 PC restarts instead of shutting down:

Watch whether it genuinely restarts or powers off and wakes again.
Note whether the fans and lights stop completely.
Check for a briefly displayed stop code.
Test a full shutdown with shutdown /s /t 0.
Disable Fast Startup.
Restart once and test several normal shutdowns.
Check the physical power-button action.
Temporarily disable automatic restart after system failure.
Review Event Viewer around the failed shutdown.
Treat Kernel-Power Event ID 41 as evidence, not a diagnosis.
Install Windows updates.
Update chipset, graphics, network and storage drivers.
Update model-specific firmware where appropriate.
Disconnect USB devices and docks.
Run powercfg /lastwake.
Run powercfg /waketimers.
Run powercfg /devicequery wake_armed.
Disable only unnecessary device wake permissions.
Check Wake-on-LAN.
Review scheduled tasks with wake permission.
Check BIOS or UEFI automatic power-on settings.
Complete pending Windows Update restarts.
Perform a clean boot.
Compare Safe Mode.
Repair Windows components where corruption is suspected.
Investigate hardware when the problem occurs outside Windows.
Contact an experienced IT provider before the fault causes data loss.

How Hamilton Group Can Help

A PC that restarts every time you select Shut down may have a simple Fast Startup conflict—or it may be hiding a driver crash, unwanted wake event or developing hardware failure.

Hamilton Group’s experienced IT team can identify which stage is responsible rather than applying random power-setting changes.

We can help with:

Fast Startup and Power Configuration

We can correctly configure:

Fast Startup
Hibernation
Sleep
Power-button actions
Laptop lid behaviour
Wake timers
Wake-capable devices

Driver and Firmware Troubleshooting

Our engineers can investigate:

Graphics drivers
Network adapters
Storage controllers
Chipset drivers
USB and Thunderbolt
Docking stations
BIOS or UEFI
Embedded-controller firmware

Crash Investigation

Where Windows is secretly crashing during shutdown, we can analyse:

Stop codes
Memory dumps
BugCheck events
Kernel-Power events
Driver failures
Windows Performance Recorder traces

Wake-on-LAN and Business Management

For managed business computers, we can confirm whether the device is intentionally waking for:

Security patching
Backups
Remote monitoring
Endpoint management
Scheduled maintenance
Remote support

We can correct faulty rules without disabling useful management capability.

Hardware Diagnostics

Hamilton Group can test:

Desktop power supplies
Laptop batteries
Motherboards
Memory
Cooling systems
Power buttons
USB devices
Docking stations

Windows Repair

When system files or updates are damaged, we can repair Windows while protecting the user’s files, applications and settings.

Hamilton Group aims to make first contact on IT support requests within 15 minutes, helping businesses resolve recurring shutdown problems before they develop into data corruption, failed updates or a complete device outage.

Get Your Windows 11 PC Shutting Down Properly

Fast Startup is designed to shorten the next Windows startup by saving part of the operating-system state instead of performing a completely fresh boot.

When a driver, device or firmware component does not handle that transition properly, the computer may hang, restart or appear to switch itself back on.

Disabling Fast Startup is a sensible first test—but it is equally important to check for hidden crashes, wake devices, scheduled timers, firmware power settings and hardware faults.

Call 0330 043 0069, book a meeting with one of our experts or visit hgmssp.com for experienced help fixing Windows 11 shutdown, restart and power-management problems.

Previous Next