0x8007012F Windows Update Error: How to Fix It

Running the Windows Update troubleshooter is the fastest solution

Reading time icon 3 min. read

Readers help support Windows Report. We may get a commission if you buy through our links. Tooltip Icon

Read our disclosure page to find out how can you help Windows Report sustain the editorial team Read more

Key notes

  • The 0x8007012f Windows update error makes it impossible to complete the process.
  • Old update files, corrupt files, or inactive update services are easy causes of this error.

Updating Windows is essential as it helps your computer’s security, stability, and performance. However, errors like 0x8007012F will interrupt the process, leading to a failed update.

It often comes with the notification failed to install. We have researched the error, and in this guide, we introduce the most effective solutions in this article.

What causes the 0x8007012F Windows update error?

We gather that the elements below are the primary causes:

  • Update interruption – This may happen when some vital update services are not running or are poorly configured.
  • Cache-related issues – A few people will experience the error if they have old or corrupted cache files.
  • Old installer files – If you have old download files on your computer, it may cause conflicts when installing new files and trigger the error.
  • Bad system files – For many users, corrupt system files will interfere with the update process and may trigger an error.

The solutions below would come in handy.

How do I fix the 0x8007012f error?

1. Run the Update troubleshooter

  1. Press Windows + I to open the Settings app.
  2. Click on Troubleshoot.
  3. Select Other troubleshooters.
  4. Search for Windows Update and click Run.
  5. Retry the update and verify the error is fixed.

The manual process of troubleshooting your Windows may take longer or don’t fix the issue at all.

However, you have the alternative of using a dedicated system repair tool and entirely restoring corrupted PC files.

2. Reset BITS and other Windows update components

  1. Press Windows + R, type cmd, and hit Ctrl + Shift + Enter.
  2. Type the scripts below and hit Enter after each one to stop vital update components:
    net start wuauserv
    net stop cryptSvc
    net stop bits
    net stop msiserver
  3. Rename the SoftwareDistribution and Catroot2 folders by typing the scripts below and hitting Enter after each one.
    ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
    ren C:\Windows\System32\catroot2 Catroot2.old
  4. Restart the stopped services by running the scripts below:
    net start wauserv
    net start cryptSvc
    net start bits
    net start msiserver

3. Fix system files with a file scan

  1. Press Windows + R, type cmd, and hit Ctrl + Shift + Enter.0x8007012f
  2. Input the script below and hit Enter:
    sfc /scannow
  3. The process may take a while. Follow the sunscreen instructions if any repair is needed, then verify it fixed the 0x8007012f error.

4. Clean the cache folder

  1. Press Windows + R, type services.msc, and hit Enter.
  2. Search for the Windows Update service, double-click on it, and hit Stop if it is running.
  3. Don’t close the Services Windows since you will need to restart the stopped service.
  4. Press Windows + E, then navigate to the path below, select all the items, and delete them.
  5. Repeat the process, deleting all the content in the path below:
  6. Return to the open services Windows and restart the stopped Windows Update service.

5. Remove the residual Pending.xml files

  1. Press Windows + R, type cmd, and hit Ctrl + Shift + Enter.0x8007012f
  2. Type the code below and hit Enter:
    Ren c:\windows\winsxs\pending.xml pending.old
  3. Restart the update and confirm the 0x8007012f error is fixed.

Old updates in this file may stop you from getting new security patches. So, renaming the file forces the computer to create a new Pending.xml file.

Any of the solutions above should fix the update problem. It would be best to try what feels most applicable since they have not been written in any particular order.

Lastly, please update us on the fix that worked using the comments section below.

More about the topics: windows error