Question Regarding PendingFileRenameOperations Caused by Microsoft Edge Update

Jimmy Afflick 100 Reputation points
2026-08-21T10:15:05.2466667+00:00

Hi Experts,

We have an automation tool that checks whether a Windows server has a pending reboot before proceeding with the next installation steps.

During our reboot check, we found the following registry value:

HKLM\SYSTEM\CurrentControlSet\Control\Session Manager
PendingFileRenameOperations

The server does not show any other pending reboot indicators:

CBS RebootPending                 : False
Windows Update RebootRequired     : False
PendingFileRenameOperations       : True

When we checked the pending file operations, we found entries related to Microsoft Edge Update:

Source : \??\C:\ProgramData\Microsoft\EdgeUpdate\Log\MicrosoftEdgeUpdate.log Target : \??\C:\ProgramData\Microsoft\EdgeUpdate\Log\MicrosoftEdgeUpdate.log.bak

We also found the following entries:

Source : \??\C:\Program Files (x86)\Microsoft\EdgeUpdate\1.3.251.23
Target :

Source : \??\C:\Program Files (x86)\Microsoft\EdgeUpdate\1.3.255.5
Target :

Source : \??\C:\Program Files (x86)\Microsoft\EdgeUpdate\1.3.257.13
Target :

Based on our understanding:

  • The .log file rename appears to be a log rotation operation.
  • The version folders appear to be old Microsoft Edge Update folders scheduled for deletion.
  • These operations are registered in PendingFileRenameOperations, which causes our automation tool to detect the server as requiring a reboot.

Our question is:

Are these Microsoft Edge Update-related entries considered a genuine "reboot required" condition that should block further software installation or provisioning?

Or, if the only entries in PendingFileRenameOperations are related to Microsoft Edge Update cleanup/log rotation, is it safe for our automation tool to ignore these specific entries and continue ?

We would like guidance on the recommended approach:

  1. Should our tool treat any PendingFileRenameOperations entry as a mandatory reboot requirement?
  2. Can Edge Update-related cleanup/log rename entries be safely excluded from our pending reboot detection?
  3. Is there a recommended way to distinguish between a critical Windows pending reboot and non-critical application cleanup operations?
  4. Is there any permanent fix for this—rename/remove those logs or entries? Should we perform any additional action to clear or complete these Edge update operations, or will they be handled automatically during the next restart?
  5. The system has already been rebooted multiple times (3–4+ times), but the PendingFileRenameOperations entries still exist. Is it expected for Microsoft Edge Update to leave PendingFileRenameOperations entries even after multiple successful reboots?

We want to make sure our automation tool follows the correct Microsoft-recommended behavior rather than simply ignoring a potentially important reboot condition.

Microsoft Edge | Install and update | Windows 11
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Carl-L 20,460 Reputation points Microsoft External Staff Moderator
    2026-08-22T06:53:33.65+00:00

    Hello Jimmy Afflick,

    Welcome to Microsoft Q&A forum.

    PFRO is a generic Windows operations that used by any application (even third-party) to schedules tasks that cannot be completed immediately like rename or deletions. And these operations don't need immediate reboot action and also not really a mandatory operation. It could wait for your next manual reboot without holding anything back, and I'd say you can safely exclude those logs pattern from pending reboot detection. Otherwise, they can come with false positives. Also, no fix is necessary for this. since they will be done in the next reboot.

    Regarding the way to distinguish them, mandatory reboot will include one of these in the block installation:

    • CBS RebootPending
    • Windows Update RebootRequired
    • Pending computer rename/domain join
    • Pending servicing operations
    • Pending MSI reboot flag (if applicable to your deployment tooling)

    For the last questions, this is uncommon, but it can happen if the entries keep being requeued or never compete successfully, but neither of them requires an immediate reboot to keep using your computer correctly.

    If the answer is helpful, please click "Yes". If you have extra questions about this answer, please click "Comment".

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    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.