Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchStart by finding the first relevant failure in %windir%LogsCBSCBS.log, not by assuming TrustedInstaller is the root cause. A server repeatedly restarting during servicing may be hitting a CBS timeout, stuck in a pending update state, blocked by Group Policy, or restarting because another service initiated it. The phrase “TrustedInstaller restart loop” alone is not enough to diagnose a particular server; match the log signature and error code to the documented recovery path before changing anything.
First determine what is restarting the server
TrustedInstaller is the Windows Modules Installer service, involved in servicing Windows components and updates. A restart that happens while updates are configuring does not by itself prove that TrustedInstaller initiated it. Microsoft documents both servicing failures that lead to rollback and OS-upgrade cases where a third-party process initiates a restart.
As an Amazon Associate I earn from qualifying purchases.
Record the Windows Server version and build, the update or upgrade in progress, whether the server reaches sign-in, the stage at which it restarts, and the exact displayed or logged error. Microsoft’s Windows Server update troubleshooting guidance recommends identifying the failing update and error in Windows Update Agent events and related System and Application events.
Recommended Free Tools
Find the first failure in the logs
Check CBS.log for update and servicing failures
Inspect %windir%LogsCBSCBS.log and persisted CBS logs. Look for the first failure before the restart, rollback, or cancellation—not just the final shutdown-related message. Codes such as 0x800F0920 and 0x80070BC9 point to different documented cases and therefore different recovery steps.
#1 Best Overall
- [MISSING OR FORGOTTEN PASSWORD?] Are you locked out of your computer because of a lost or forgotten password or pin? Don’t’ worry, PassReset USB will reset any Windows User Password or PIN instantly, including Administrator. 100% Success Rate!
- [EASY TO USE] 1: Boot PC from the PassReset USB drive. 2: Select the User account to reset password. 3: Click “Remove Password”. That’s it! Your computer is unlocked.
- [COMPATIBILITY] This USB will reset any user passwords including administrator on all versions of Windows including 11, 10, 8, 7, Vista, Server. Also works on all PC Brands that have Windows as an operating system.
- [SAFE] This USB will reset any Windows User password instantly without having to reinstall your operating system or lose any data. Other Passwords such as Wi-Fi, Email Account, BIOS, Bitlocker, etc are not supported.
For an OS upgrade, check Setupact.log and rollback events
During an OS upgrade, inspect %windir%Windows~BTSourcesPanthersetupact.log and the associated rollback event logs. Microsoft documents an example in which Setupact.log identifies a third-party management process as the restart initiator. If a third-party service is named, confirm its role with the service owner before stopping or disabling it; do not assume TrustedInstaller caused that restart.
Match the error to the documented cause
| Clue | What Microsoft documents | Next action |
|---|---|---|
0x8007045B / ERROR_SHUTDOWN_IN_PROGRESS |
Shutdown was already in progress; this code may follow an earlier servicing error. | Find the original preceding error in CBS.log. Microsoft specifically points to 0x800F0920 as an example, rather than treating 0x8007045B as the root cause. Microsoft’s 0x8007045B guidance |
0x800F0920 / CBS_E_HANG_DETECTED |
In Microsoft’s documented hang case, TrustedInstaller did not complete within its default timeout period; CBS may record rollback and cancellation. Microsoft describes a 15-minute timeout for that case. | Use the Windows Server recovery guidance for this code: Microsoft specifies an in-place upgrade for Windows-based computers. Do not infer that a client-only timeout registry workaround applies to every Server version. Microsoft’s 0x800F0920 guidance |
0x80070BC9 with a pending-transaction message |
Microsoft attributes this documented pending-servicing case to corruption in the Transactional Entries folder, preventing the pending state from being cleared. | Microsoft specifies an in-place upgrade for Windows-based computers. For an Azure VM, back up the OS disk before following the cited recovery process. Microsoft’s 0x80070BC9 guidance |
0x80070BC9 and policy sets TrustedInstaller to Manual |
Microsoft documents a separate policy-related case: Group Policy can prevent TrustedInstaller from starting pending operations. | Correct the policy, then restart. If that specific policy-related path still fails, use the WinRE recovery steps below. Microsoft’s common Windows Update errors guidance |
| Setupact.log identifies a restart-initiating process | For an OS upgrade, the initiating process may be a third-party management or security service rather than TrustedInstaller. | Identify the named service and investigate it with its owner before taking action. Microsoft’s upgrade and restart guidance |
Use only the recovery path that matches your evidence
If the server is simply waiting for a requested restart
When update troubleshooting shows the server has not completed a requested restart, Microsoft’s general guidance is to restart it. First confirm that a restart is appropriate for the workload and maintenance window, and capture the relevant error and logs if the same failure has already recurred.
If Group Policy is blocking TrustedInstaller
- Check the effective policy that configures Windows Modules Installer/TrustedInstaller. In the documented
0x80070BC9policy case, the service is forced to Manual and pending update work cannot start. - Correct the policy so it no longer blocks the pending operation, then restart the server.
- If the pending-action failure persists, use Windows Recovery Environment (WinRE) and follow Microsoft’s documented pending-action recovery for this policy-related case.
From WinRE, Microsoft documents this command for the offline Windows image, assuming the Windows installation is mounted at C::
Rank #2
- Native Windows Server IoT 2025 for Storage Workgroup edition.
- Pre-tested NAS-grade hard drives included with RAID pre-configured.
- No CAL (Client-Access Licenses) required.
- Cost-effective small business NAS with Windows Server enhanced data management and security features.
- Cloud service integration with Azure, OneDrive, and other Microsoft-compatible services enables to create a hybrid cloud for additional security and flexibility.
DISM /Image:C: /Cleanup-Image /RevertPendingActions
The image path must match the actual offline Windows volume in WinRE; verify it before running the command. This is not a universal fix for every restart loop or every 0x80070BC9 occurrence.
If CBS identifies the Transactional Entries pending-state case
For the documented 0x80070BC9 case involving pending transaction content and Transactional Entries corruption, Microsoft names an in-place upgrade as the Windows-based computer resolution. Back up the server and confirm a workable recovery route before undertaking repair. For an Azure VM, the cited Microsoft guidance calls for backing up the OS disk before recovery.
Rank #3
- The Data Recovery Stick requires no technical skills — simply plug it into your Windows computer, click Start, and the software automatically begins scanning and recovering lost files within minutes. Compatible with Windows Vista, 7, 8, 10, & 11, it's designed to be a reliable first step when accidental deletion occurs.
- Recover photos (JPG, BMP, PNG, TIFF), Microsoft Office documents (Word, Excel, PowerPoint, Publisher, Access), Open Office files, MP3 music files, PDFs, RTF documents, AutoCAD files, and HTML web pages. Whether it's personal memories or critical business files, the Data Recovery Stick covers the file types that matter most.
- Works with hard drives, USB drives, SD cards, memory sticks, and other common storage formats that use FAT or NTFS file systems — making it a single solution for hard drive recovery, USB drive recovery, SD card recovery, and more. Note: a media reader is required for micro SD cards and some mass storage devices.
- No Installation Required - The Data Recovery Stick runs entirely from the USB drive with no software installation on your computer — helping prevent new data from overwriting the files you're trying to recover. This also makes it ideal for use across multiple computers or in emergency situations where installation isn't practical.
- Use the Data Recovery Stick on as many computers as often as needed — simply clear the recovered data between uses to free up storage space. Software updates keep the tool compatible with newer systems and devices, backed by 25+ years of data software expertise from Paraben Consumer Software.
If CBS identifies the 0x800F0920 hang case
Microsoft’s Windows Server article describes a TrustedInstaller hang/timeout pattern and specifies an in-place upgrade for Windows-based computers. It documents a 15-minute default timeout in that particular case; that figure is not a fresh measurement of your server. A separate Microsoft article describes changing timeout behavior for supported Windows Client versions, including a three-hour timeout when BlockTimeIncrement is set to hexadecimal 2a30. That client-scoped workaround should not be applied as general Windows Server advice; applicability to every Server version is not established.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Protect the server before attempting more invasive repairs
Do not begin by editing service permissions, CBS registry state, the COMPONENTS hive, Pending.xml, or timeout settings. Microsoft’s common-errors guidance discusses more invasive WinSxS/Pending.xml and COMPONENTS-hive actions only as later fallbacks. Use them only when the server matches the documented failure path and you have secured an appropriate backup and recovery route, such as console or WinRE access. If the server cannot be recovered safely, involve a qualified Windows Server servicing support provider.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
