PC stuck in endless reboot before reaching desktop (file replacement loop)

Patel Vihaan 60 Reputation points
2026-11-09T06:20:28.92+00:00

Hi, got a machine here that's stuck in a boot loop. Every time it turns on, it tries to do some file replacement stuff, fails, and reboots without ever getting to the login screen or desktop.

Does anyone know how I can find out which files it's trying to swap? Also trying to figure out if this is caused by a bad driver/software install or some pending update, but not sure how to check from the recovery screen.

Any quick tips would be huge, thanks!

Windows for business | Windows Server | Performance | Other
0 comments

2 answers

Sort by: Oldest
Most helpful Newest Oldest

  1. AI answer

    2026-11-09T06:20:49.1666667+00:00

    From the recovery screen, the most direct checks are the startup repair log, Event Viewer if Safe Mode works, and servicing logs if the loop is tied to pending update operations.

    1. Run Startup Repair first.
      • Boot from Windows installation media.
      • On Install Windows, select Next > Repair your computer.
      • Go to Troubleshoot > Advanced options > Startup Repair.
      • After it runs, check whether Windows starts normally.
      • Startup Repair writes a log at: %windir%\System32\LogFiles\Srt\Srttrail.txt
      • That log helps identify startup failures and repairs that were attempted.
    2. If the machine can start in Safe Mode or Safe Mode with Networking, use that path next.
      • Go to Settings > Update and Security > Recovery > Advanced startup.
      • Then select Troubleshoot > Advanced Options > Startup Settings > Restart.
      • On Startup Settings, choose option 4, 5, or 6 for Safe Mode.
      • If Safe Mode works, open Event Viewer and review the System log for critical errors around the same time as the reboot loop.
      • Also check Device Manager for devices marked with an exclamation point and review the driver events in the device properties. Update the related driver if one is faulting.
    3. If the issue started after a driver or software change, do a clean start.
      • In System Configuration (msconfig), select Selective startup.
      • Test services one at a time to find the service causing the boot issue.
      • In most cases, the problematic service is third-party.
      • After isolating the faulty service, disable it and try starting again with Normal startup.
    4. If the loop is tied to file corruption, run file-system and system-file checks.
      • Use Scan disk on the affected drive: right-click the drive > Properties > Tools > Check now.
      • Run System File Checker: 
             SFC /scannow
    5. If the problem began after an update or install, use System Restore from recovery.
      • In WinRE, select Troubleshoot > Advanced options > System Restore.
      • Choose a restore point from before the issue started.
    6. If the machine is repeatedly processing pending file operations after an update attempt, inspect servicing logs to confirm the same operation is retrying.
      • Review CBS.log together with archived CbsPersist logs.
      • Look for repeated entries showing the same package, failure code, or transaction sequence across multiple startups.
      • Also review DISM.log and Setup-related event logs to see whether the same package or component is consistently failing.
    7. If none of the above resolves it, back up important files before trying more disruptive recovery options, because some recovery actions can result in data loss.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

  2. Domic Vo 37,000 Reputation points Independent Advisor
    2026-11-09T08:06:00.17+00:00

    Hello,

    This behavior often indicates a failed Windows servicing operation, an incomplete cumulative update, or a driver installation that cannot complete during startup. To identify which files Windows is attempting to replace, boot into Windows Recovery Environment (WinRE), open Troubleshoot > Advanced options > Command Prompt, and identify the Windows installation drive using diskpart followed by list volume, since it may not be C: in recovery mode. Once identified (for example, D:), inspect D:\Windows\Logs\CBS\CBS.log, D:\Windows\Logs\DISM\dism.log, and D:\Windows\INF\setupapi.dev.log for entries containing Failed, Error, or Pending to identify servicing or driver installation failures. You can also run DISM /Image:D:\ /Get-Packages to check for packages in Install Pending or Uninstall Pending states; if a failed servicing operation is preventing startup, run DISM /Image:D:\ /Cleanup-Image /RevertPendingActions from WinRE, targeting the offline Windows installation. Avoid manually deleting pending.xml or replacing system files, as this can further damage Windows servicing.

    Could you share the relevant errors from CBS.log and the output of DISM /Image:D:\ /Get-Packages so we can identify the failing update or driver?

    If my answer is useful for you, please hit Accept the answer to support me.

    Thank you.

    Domic Vo.

    Was this answer helpful?

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.