Fix ERROR_SUCCESS_RESTART_REQUIRED (0X00000BC3) on Windows Server

What triggers this error?

You just installed a Windows Update or a software package — like SQL Server or a security patch — on your Windows Server 2016, 2019, or 2022. The installation finishes, but instead of a clean "success" message, you get 0X00000BC3 with the text "The requested operation is successful. Changes will not be effective until the system is rebooted." It's confusing. You think something broke. Don't panic — it's not a failure. The server is telling you: "Hey, I did the job, but I need to restart to apply changes."

Why does it happen?

This error code is part of Windows's way of saying "success with a caveat." The caveat is that some files or services can't be updated while the system is running. Think of it like swapping a tire on a moving car. You can't. You have to stop the car first. Windows is the car. The update is the tire. The restart is stopping the car to finish the swap.

Common scenarios: installing a .NET Framework update, a driver patch, or a Windows feature (like Hyper-V). Also happens when you run dism /online /add-package or Install-WindowsFeature via PowerShell. The operation completes, but the registry or kernel-level files are locked. A reboot unlocks them.

How to fix it

Here's the fix. It's usually simple. Start with step 1, then move down if it still doesn't work.

1. Restart the server

   This is the fix 90% of the time. Go to Start > Power > Restart. Or use the command line: shutdown /r /t 0. This forces a restart immediately. After reboot, check if the update or software works. If you see the error again, move to step 2.

2. Check for pending file rename operations

   Sometimes Windows queues file operations but doesn't finish them. Open an elevated Command Prompt (Run as Administrator) and run:

   reg query "HKLM\SYSTEM\CurrentControlSet\Control\Session Manager" /v PendingFileRenameOperations

   If you see output with file paths, a reboot is pending. Restart again. If the command returns nothing, you're good.

3. Run Windows Update troubleshooter

   On Server 2019 and 2022, the built-in troubleshooter can clear stuck update states. Go to Settings > Update & Security > Troubleshoot > Additional troubleshooters > Windows Update. Run it. It'll reset update components and clear pending restart flags.

4. Check for stuck services

   Open PowerShell as Admin and run:

   Get-Service | Where-Object {$_.Status -eq 'StartPending'}

   If any services show 'StartPending', restart the server. Use Restart-Service if you don't want to reboot, but it's safer to reboot.

5. Force complete the update

   If all else fails, try:

   dism /online /cleanup-image /startcomponentcleanup

   Then run sfc /scannow. This cleans component store junk and repairs system files. Then restart.

What if it still fails?

If the error persists after a restart, you might have a deeper issue. Check the Application Event log (Event Viewer > Windows Logs > Application). Look for errors from MsiInstaller or Windows Update Client. The log tells you exactly which component refused to complete.

Also check for pending updates: go to Settings > Update & Security > Windows Update > View update history. If you see failed updates, uninstall them via wusa /uninstall /kb:xxxxxx. Then restart and reinstall.

I've seen this error on Server 2022 after installing a printer driver. The fix? A restart. Nothing else. So start simple. Reboot. If it still shows, run the steps above. You'll save hours.

Quick tip: If you're automating updates with scripts, always add Restart-Computer -Force after installing packages that trigger this error. Saves you the headache.