Windows update an error has occurred

Fix Windows Update errors

What does this guided walk-through do?

This guided walk-through provides steps to fix problems with Windows Updates for Windows 8.1 and 7, such as taking a long time to scan, or error codes while installing updates.

For help with Windows Update issues in Windows 10, see Troubleshoot problems updating Windows 10 instead.

A common cause of errors is inadequate drive space. If you need help freeing up drive space, see Tips to free up drive space on your PC.

Common error codes

The steps in this guided walk-through should help with all Windows Update errors and other issues— you don’t need to search for the specific error to solve it. As an example, here are some commonly seen error codes: 0x0xc1900223223; 0x80240034; 0x8007000E, 0x80242006​, 0x80244018​, 0x80D02002​, 0x80246017​, 0x80240438​, 0x80070070​, 0x8007000D​, 0x80246008​, 0x80096004​, 0x80070020.
The steps provided here should help fix any errors that come up during the Windows Update process.

How does it work?

We’ll begin by asking you questions about the Windows version you’re using and the issue you’re experiencing. Next, we’ll take you through a series of troubleshooting steps that are specific to your situation. At the end of each step, you’ll be asked “Did this resolve the issue?” If it’s resolved, select Yes, and you’re done! If it isn’t resolved, select No and continue with the guided walk-through.

«A fatal error has occurred.» error message when you use Windows Update on a Windows 7 or Windows Server 2008 R2-based computer that has a third-party filter driver installed

Symptoms

Assume that you install a third-party filter driver on a computer that is running Windows 7 or Windows Server 2008 R2. When you run Windows Update to check for updates, Windows Update fails and you receive an error message that resembles the following:

A fatal error has occurred.

Cause

This problem occurs because a lock is not released correctly when the computer processes the update sequence number (USN) change journals in the Ntfs.sys driver file.

Resolution

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a «Hotfix download available» section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=supportNote The «Hotfix download available» form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must be running Windows 7 or Windows Server 2008 R2.

Registry information

To use the hotfix in this package, you do not have to make any changes to the registry.

Restart requirement

You may have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The English (United States) version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.

Читайте также:  Forti vpn client mac os
Windows 7 and Windows Server 2008 R2 file information notes

Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under «Windows 7/Windows Server 2008 R2» on the page. Always refer to the «Applies To» section in articles to determine the actual operating system that each hotfix applies to.

The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the «Additional file information for Windows Server 2008 R2 and for Windows 7» section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are very important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.

Полный список всех кодов ошибок Windows Update

При диагностике проблем работы системы обновления Windows довольно часто приходится встречаться с различными кодами ошибок. Как правило, натыкаясь на новую ошибку в логе windowsupdate.log, журнале установки или панели управления приходится идти в Google и собирать по крупицам всю возможную информацию о нужном коде ошибки.

Например, администратор встретился в журнале с ошибкой 0x80070422. Что она означает? Из цифрового кода это абсолютно не понятно. А что если бы вы, получив данную ошибку моментально сконвертировали ее в более человеческий вид ERROR_SERVICE_DISABLED? Т.е. уже четко видно, что проблема связана с одной из отключённых служб Windows, из-за которых клиент не может закачать обновления. И практически сразу приходит на ум проверка статуса службы BITS.

Как вы видите, служба BITS действительно остановлена, из-за чего агент Windows Update не может скачать обновления. Диагностика ошибки обновления довольно сильно упростилась, не так ли?

В следующей таблице перечислен список всех ошибок обновления Windows, с расшифровкой их кодов и кратким описанием, собранный из Windows SDK. Надеюсь, использование этих данных существенно упростит вам диагностику ошибок Windows Update.

Совет. Напомню, что данные коды ошибок могут встретится в разделе Windows Update панели управления либо в текстовом журнале %systemroot%\windowsupdate.log (либо новом формате журнала обновлений Windows 10, основанном на ETW). Для поиска нужного кода воспользуйтесь функцией поиска по странице браузера (CTRL + F).

Windows Update Error 0x80070057

I have been struggling with this for some time now and finally decided to bring it to the forum.

I am running Windows 7 and my Automatic Update will not turn on. It gives me error 0x80070057. I have tried running several FixIt programs, and none of them will initialize. I have also run Security Essentials and Malwarebytes without finding any sign of a virus and without fixing the problem. I am not sure what the issue is. I haven’t installed any new programs, so I thought it might be virus related. I am not sure where to go from here, and I am definitely appreciative of any help anyone can offer.

If you need more information about my machine, I would be happy to give it.

Thank you very much,

Replies (37) 

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

Run the CheckSUR tool and the DISM.

Verify that the time, date/year & time-zone are set correctly

First clear up your Temp File/Cache.

(Important: One of the normal steps in eliminating malicious programs is to entirely delete the contents of all Temp folders.

Click Start > All Programs > Accessories > System Tools > Disk Cleanup

Best and easier to use — CCleaner.

Download the basic (slim) build via

The basic (slim) build does not contain the disgusted Toolbar

DO NOT USE ANY Advanced cleaning options. DO NOT TOUCH THE REGISTRY. At least not for now.

Читайте также:  Ort clock для windows

Description of the System Update Readiness Tool (CheckSUR)

Use Deployment Image Servicing and Management to fix Windows Update errors

  1. Open an elevated command prompt. To do this, click Start, click All Programs, click Accessories , right-click Command Prompt, and then click Run as administrator. If you are prompted for an administrator password or for a confirmation, type the password, or click Allow.
  2. Type the following commands. Press Enter after each command.
    • DISM.exe /Online /Cleanup-image /Scanhealth
    • DISM.exe /Online /Cleanup-image /Restorehealth

  3. Close the command prompt, and then run Windows Update again.

Please let us know if this did or didn’t help to resolve your problem.

The current time and date right now in Baja California, Mexico is 4:57 PM

3 people found this reply helpful

Was this reply helpful?

Sorry this didn’t help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Thank you for the prompt response and your assistance. I tried what you recommended and it doesn’t seem to have worked.

I attempted the CheckSUR and it would not initialize, stating «Installer encountered an error:0x80080005 Server execution failed»

I typed in the commands and received this:

[I typed DISM.exe /online /cleanup-image /scanhealth]
«Error: 87 The scanhealth option is not recognized in this context.» and

[I typed DISM.exe /online /cleanup-image /restorehealth]
«Error: 87 The restorehealth option is not recognized in this context.»

I also tried to run Windows Update again with no success.

214 people found this reply helpful

Was this reply helpful?

Sorry this didn’t help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Error code 0x80080005? To troubleshoot the issue, please first run the following command to scan integrity of all files.:

  • Open an elevated command prompt. To do this, click Start, click All Programs, click Accessories , right-click Command Prompt, and then click Run as administrator. If you are prompted for an administrator password or for a confirmation, type the password, or click Allow.
  • Type the following command.
  • SFC /SCANNOW
  • Close the command prompt, and then run Windows Update again.
  • The current time and date right now in California, United States is

    Was this reply helpful?

    Sorry this didn’t help.

    Great! Thanks for your feedback.

    How satisfied are you with this reply?

    Thanks for your feedback, it helps us improve the site.

    How satisfied are you with this reply?

    Thanks for your feedback.

    I ran the scan and rebooted. Windows Update still does not work. I tried opening the log from the scan and it said Access Is Denied.

    1 person found this reply helpful

    Was this reply helpful?

    Sorry this didn’t help.

    Great! Thanks for your feedback.

    How satisfied are you with this reply?

    Thanks for your feedback, it helps us improve the site.

    How satisfied are you with this reply?

    Thanks for your feedback.

    1 person found this reply helpful

    Was this reply helpful?

    Sorry this didn’t help.

    Great! Thanks for your feedback.

    How satisfied are you with this reply?

    Thanks for your feedback, it helps us improve the site.

    How satisfied are you with this reply?

    Thanks for your feedback.

    I would suggest you to reset Windows Update Components and check if it helps.

    How do I reset Windows Update components?

    Note: This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft article:

    Hope this information helps. Reply to the post with updated status of the issue to assist you further.

    1 person found this reply helpful

    Was this reply helpful?

    Sorry this didn’t help.

    Great! Thanks for your feedback.

    How satisfied are you with this reply?

    Thanks for your feedback, it helps us improve the site.

    How satisfied are you with this reply?

    Thanks for your feedback.

    Was this reply helpful?

    Sorry this didn’t help.

    Great! Thanks for your feedback.

    How satisfied are you with this reply?

    Thanks for your feedback, it helps us improve the site.

    How satisfied are you with this reply?

    Thanks for your feedback.

    Thank you for the idea. I tried to reset the update components. Everything went through fine except the following.

    The module «mshtml.dll» was loaded but the entry-point DllRegisterServer was not found.
    Make sure that «mshtml.dll» is a valid DLL or OCX file and then try again.

    The module «shdocvw.dll» was loaded but the entry-point DllRegisterServer was not found.
    Make sure that «shdocvw.dll» is a valid DLL or OCX file and then try again.

    The module «browseui.dll» was loaded but the entry-point DllRegisterServer was not found.
    Make sure that «browseui.dll» is a valid DLL or OCX file and then try again.

    The module «msxml.dll» was loaded but the entry-point DllRegisterServer was not found.
    Make sure the binary is stored at the specified path or debug it to check for problems with the binary or dependent .DLL files.
    The specified module could not be found.

    The module «gpkcsp.dll» was loaded but the entry-point DllRegisterServer was not found.
    Make sure the binary is stored at the specified path or debug it to check for problems with the binary or dependent .DLL files.
    The specified module could not be found.

    The module «sccbase.dll» was loaded but the entry-point DllRegisterServer was not found.
    Make sure the binary is stored at the specified path or debug it to check for problems with the binary or dependent .DLL files.
    The specified module could not be found.

    The module «slbcsp.dll» was loaded but the entry-point DllRegisterServer was not found.
    Make sure the binary is stored at the specified path or debug it to check for problems with the binary or dependent .DLL files.
    The specified module could not be found.

    The module «initpki.dll» was loaded but the entry-point DllRegisterServer was not found.
    Make sure the binary is stored at the specified path or debug it to check for problems with the binary or dependent .DLL files.
    The specified module could not be found.

    The module «wuaueng1.dll» was loaded but the entry-point DllRegisterServer was not found.
    Make sure the binary is stored at the specified path or debug it to check for problems with the binary or dependent .DLL files.
    The specified module could not be found.

    The module «wucltui.dll» was loaded but the entry-point DllRegisterServer was not found.
    Make sure the binary is stored at the specified path or debug it to check for problems with the binary or dependent .DLL files.
    The specified module could not be found.

    The module «wuweb.dll» was loaded but the entry-point DllRegisterServer was not found.
    Make sure the binary is stored at the specified path or debug it to check for problems with the binary or dependent .DLL files.
    The specified module could not be found.

    The module «qmgr.dll» was loaded but the entry-point DllRegisterServer was not found.
    Make sure that «qmgr.dll» is a valid DLL or OCX file and then try again.

    The module «muweb.dll» was loaded but the entry-point DllRegisterServer was not found.
    Make sure the binary is stored at the specified path or debug it to check for problems with the binary or dependent .DLL files.
    The specified module could not be found.

    The Windows Update service could not be started.
    A system error has occurred.
    System error 1067 has occurred.
    The process terminated unexpectedly.

    I don’t know what any of these are or what it means that there were errors. Any further assistance would be great. Thanks!

    Читайте также:  Как проверить системные библиотеки windows
    Оцените статью