Summary
This article explains how to fix Windows Update error 0x800719E4 (ERROR_LOG_FULL) when updates fail on supported Windows Server, Windows client, and Azure virtual machines. It describes common causes such as full or corrupted transaction logs, ghosted network adapters or drivers, and misconfigured update orchestration and provides step-by-step guidance to restore successful Windows Update operations.
Symptoms
When you try to install a Windows update, the installation fails and returns error code 0x800719E4 (ERROR_LOG_FULL). The update might appear to install. However, after the computer restarts at the end of installation, the installation rolls back. The Windows Update history might list repeated failed installations.
When this issue occurs, the System log and Component-Based Servicing (CBS) log might include any of the following error messages:
Failed uninstalling driver updates [HRESULT = 0x800719e4 - ERROR_LOG_FULL]Startup: Failed while processing non-critical driver operations queuepatch not applicableorpatch not reflecting after restart0x80070002 (ERROR_FILE_NOT_FOUND)0x800f0991 (PSFX_E_MISSING_PAYLOAD_FILE)0x800f0982 (PSFX_E_MATCHING_COMPONENT_NOT_FOUND)0x800F0920 (CBS_E_HANG_DETECTED)
Cause
Typically, this issue occurs during the installation or uninstallation of cumulative or driver-related updates. This issue has various possible causes:
- Transaction log exhaustion, corruption, or improper cleanup. Windows transaction logs (.blf files and .regtrans-ms files in \Windows\System32\Config\TxR) become full or corrupted, and then block update processes. Improper cleaning of the transaction logs can cause further system corruption and startup failures.
- "Ghosted" network adapters or drivers. VMs that are frequently deallocated and reallocated in Azure can accumulate "ghosted" or hidden device entries that remain in the system registry but are no longer physically present. This behavior is observed in Mellanox devices. When this behavior occurs, driver update queues increase in size, and logs eventually overflow.
- Misconfigured update orchestration. Incorrect settings for update orchestration (such as not using the Customer Managed option) can contribute to update failures.
Resolution
Important:
- If the affected computer is a Windows VM that can't restart correctly or that you can't access by using SSH, make sure that you can use the Azure Serial Console to access the VM.
- Before you troubleshoot this issue, back up the operating system disk. For information about this process for VMs, see About Azure Virtual Machine restore.
- Use administrative permissions to run all the commands and scripts that are provided in these steps.
Step 1: Check the system health
To check the system health and make any necessary repairs, open an administrative Command Prompt window, and then run the following commands:
DISM /Online /Cleanup-Image /RestoreHealth
SFC /SCANNOW
Review the output for errors or corruption. If these commands make repairs, try again to install the update.
Step 2: Clean up the transaction logs
Important:
Cleaning up transaction incorrectly logs can cause more issues to occur.
Follow these steps:
-
If the affected computer is a VM that can't start, create a rescue VM. Then move the operating system disk from the affected VM to the rescue VM.
-
On the rescue VM or the affected physical computer, open an administrative command prompt window, and then change the working directory to <drive>:\Windows\System32\Config\TxR.
-
To remove the system and hidden attributes from the transaction log files, run the following command:
attrib -h -s * -
To delete the transaction log files, run the following commands:
del *.blf del *.regtrans-ms -
If you're using a rescue VM, move the operating system disk back to the original VM.
-
Start the VM (or restart the physical computer), and then try again to install the update.
Step 3: Check for ghosted network adapters or drivers
For more information about this issue, see Azure VM Ghosted Nic Validation and Cleanup Tools.
Note:
A computer that accumulates ghosted network adapters or drivers might continue to behave in this manner. Consider checking for this issue periodically as part of regular maintenance.
- Download the following scripts:
-
To detect any ghosted network adapters or drivers, open an administrative Windows PowerShell Command Prompt window, and then run the following commands:
Set-ExecutionPolicy Bypass -Force .\Windows_GhostedNIC_Detection.ps1 -
If the script detects ghosted network adapters or drivers, run the following commands:
Set-ExecutionPolicy Bypass -Force .\Windows_GhostedNIC_Removal.ps1 -
If the affected computer has a Mellanox adapter or driver, run the following commands:
Get-PnpDevice | Where-Object { $_.FriendlyName -like "*Mellanox*" } pnputil /remove-device <InstanceID>[!NOTE]
In this command, <InstanceID> represents the instance ID number of the device. -
Restart the computer, and then try again to install the update.
Data collection
If issues persist, consider contacting Microsoft Support. Before you contact Microsoft Support for assistance, use the Trouble Shooting Script (TSS) diagnostic scripts to collect data, as described in Collect data to analyze and troubleshoot Windows servicing, Updates, and Features on Demand scenarios. Attach this information to your support request.
References
Source: Microsoft Learn / IT Pro troubleshooting by Microsoft and contributors. Documentation licensed CC BY 4.0. Code samples are covered by the MIT License. Converted from Markdown, with links normalized and embedded media omitted.
