How to Remove Failed Updates From the Update History on Windows Vista

Written by tammy clevenger
  • Share
  • Tweet
  • Share
  • Email

Microsoft Windows Vista, as with other Microsoft operating systems, provides access to the automated Windows Update function. The Windows Update may be scheduled to go online to the update site and download and install updates, or the application may be configured to perform only manual updates. This feature may also be disabled by selecting the option to "Not Automatically Download and Install Windows Updates," but Microsoft does not recommend this option. Occasionally, update files will fail. If an update fails, sometimes the update may not be hidden or deleted from within the update application. However, there is a way to remove the failed updates using a simple batch script.

Skill level:


  1. 1

    Click the Windows "Start" button, click on the "Accessories" folder and then click "Notepad" to open the text editor to a blank page.

  2. 2

    Select the following block of text, without quotes, and right-click on the highlighted block. Click "Copy."

    "CD net stop wuauserv

    del% systemroot% \ SoftwareDistribution \ DataStore \ Logs \ edb.log

    net start wuauserv"

  3. 3

    Click inside the blank page in Notepad and right-click. Select "Paste" to paste the code into the page.

  4. 4

    Click "File" from the top navigation menu in Notepad, and select "Save As."

  5. 5

    Click the drop-down box and select the "All Files" option.

  6. 6

    Type a name for the file, and then type ".BAT" for the file extension. Save in an easy-to-find location like the Desktop. Close Notepad.

  7. 7

    Right-click on the newly created file and select "Run as Administrator." The failed update history is removed.

Don't Miss

  • All types
  • Articles
  • Slideshows
  • Videos
  • Most relevant
  • Most popular
  • Most recent

No articles available

No slideshows available

No videos available

By using the site, you consent to the use of cookies. For more information, please see our Cookie policy.