Error Details
| Fact | Value | Source | Note |
|---|---|---|---|
| Exact error string | 0x80070BC2 | Intune admin center > Devices > [Device name] > Device configuration | -> |
| Affected build range | Windows 10 / Windows 11 | Microsoft Intune documentation | |
| Registry key involved | HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\PendingFileRenameOperations | Windows Registry Editor | -> |
| Relevant service/endpoint URL | /deviceManagement/reports | Microsoft Graph API | |
| Log line signature | Installation successful with reboot pending flag | Windows Event Viewer > Applications and Services Logs > Microsoft > Windows > WindowsUpdateClient > Operational, Event ID 19 | -> |
Log Files to Check
C:\Windows\CCM\Logs\WUAHandler.logWindows Event Viewer > Applications and Services Logs > Microsoft > Windows > WindowsUpdateClient > Operational
What This Error Actually Means
The error code0x80070BC2, also known as ERROR_SUCCESS_REBOOT_REQUIRED, is raised by the Windows Update Client and indicates that a successful installation of an update or application has left pending file rename operations (PFRO) on the device. This means that while the installation was completed successfully, certain files are still being processed in the background and require a reboot to finalize their installation. The error is commonly encountered when managing devices through Microsoft Intune, as it triggers compliance checks which report non-compliance until the required restart occurs.
Affected Versions and Scope
This issue affects Windows 10 and Windows 11 operating systems managed by Microsoft Intune. It can impact both standalone Intune-managed devices and those co-managed with System Center Configuration Manager (SCCM). The error is particularly relevant in scenarios where update rings are configured to enforce specific update policies, such as setting active hours during which automatic restarts are allowed.Where To Look First: Logs and Event IDs
To diagnose this issue, start by checking the following logs: -C:\Windows\CCM\Logs\WUAHandler.log: This log file is particularly useful for devices co-managed with SCCM. It will contain entries indicating that an update or application installation was successful but requires a reboot.
- Windows Event Viewer > Applications and Services Logs > Microsoft > Windows > WindowsUpdateClient > Operational: Look for event ID 19, which logs the completion of an update installation along with a pending reboot flag.
Additionally, you can use PowerShell cmdlets to query Intune-managed devices for compliance status. For example:
Get-MgDeviceManagementManagedDevice -Filter "deviceEnrollmentType eq 'windowsAutoEnrollment'" | Where-Object { $_.ComplianceStatus -eq 'Noncompliant' }
Root Causes
Cumulative Updates or Application Installations Requiring a Restart
When a cumulative update or application installation is completed, certain files may still be in the process of being renamed or updated. This can leave behind entries in theHKLM\SYSTEM\CurrentControlSet\Control\Session Manager\PendingFileRenameOperations registry key, indicating that a reboot is necessary to finalize these changes.
Stale RebootRequired Registry Key
Sometimes, after an installation or update process, a stale entry in theHKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\RebootRequired registry key can persist. This can occur if a previous installation was interrupted and did not complete successfully.
Services Holding Locks on Files During Installation
The WaasMedicSvc or Windows Module Installer service may hold locks on files during the update process, preventing them from being finalized until the system is restarted. This can be identified by checking which services are running at the time of the installation and whether they have any open file handles.Fix Procedure
To resolve this issue, follow these steps: 1. **Allow the Device to Restart**: The simplest solution is often to allow the device to restart automatically or manually initiate a reboot. - For manual intervention: Instruct users to perform a system restart. 2. **Configure Intune Update Ring Settings**: - Navigate toIntune admin center > Devices > Update rings.
- Select the update ring in question and go to its properties.
- Under User experience settings, ensure that Automatic restart before deadline is enabled and set an appropriate Deadline for feature updates.
3. **Check PendingFileRenameOperations Registry Key**:
- Open regedit.exe and navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\PendingFileRenameOperations.
- Review the entries in this key, which should be empty if no pending operations exist.
4. **Clear Stale RebootRequired Registry Key**:
- Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\RebootRequired and delete any stale entries.
5. **Verify Service Statuses**:
- Use PowerShell cmdlets like Get-Service WaasMedicSvc | Select Name,Status to check the status of services that might be holding file locks.
Error Code Variants
| Error Code | Description | Distinguishing Features |
|---|---|---|
0x80070643 |
ERROR_INSTALL_PACKAGE_REJECTED | This error occurs when an installation package is rejected due to conflicts or prerequisites not being met. |
0x80070BC1 |
ERROR_SUCCESS_REBOOT_INITIATED | This error indicates that a reboot has been initiated but is yet to complete, often seen during update installations. |
Verification
To verify the resolution of this issue: - Check the compliance status in Intune admin center > Devices > [Device name] > Device configuration. - Look for a change from0x80070BC2 to an error-free state or successful completion status.
- Review logs such as C:\Windows\CCM\Logs\WUAHandler.log and the Windows Event Viewer for event ID 19, which should no longer indicate a pending reboot.
Prevention
To prevent this issue from recurring: - Implement policies that enforce regular restarts during maintenance windows. - Use Intune to configure update rings with appropriate active hours and automatic restart settings. - Monitor the health of services likeWaasMedicSvc and ensure they are not holding file locks unnecessarily.
Note: Be cautious when modifying registry keys, as incorrect changes can render devices non-functional. Always back up the registry before making any modifications.
A quick diagnostic trick is to use
This guide provides a comprehensive approach to diagnosing, resolving, and preventing issues related to Get-WinEvent -LogName 'Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider/Admin' -MaxEvents 50 to review recent events related to device management and compliance checks. This can provide immediate insights into the current state of your devices.
0x80070BC2 in Microsoft Intune-managed environments. By following these steps, you can ensure that your organization's devices remain compliant and operational without unnecessary disruptions.