8024402c ошибка обновления windows server 2008 r2

  • Remove From My Forums

  • Question

  • Hi,
    I am getting this error on my Server 2008 SP2 Domain Controller.  I have searched all the sites & have carried out the following:

    Stopped all Sophos Anti Virus services (I even tried uninstalling it at one point)
    Checked Windows firewall — disabled
    Set proxy — netsh winhttp>set proxy proxy-server=»servername:port”
    followed by

    net stop WuAuServ

    net start WuAuServ
    Then I tried renaming the Software Distribution folder, but got an access denied message.
    I was logged in as domain administrator, but couldn’t try local administrator account as there isn’t one on a domain controller.

    Has anyone got any ideas?  I have tried contacting Microsoft as they offer free support on Windows Updates errors, but the reply I got was «due to the nature of the technical query, it has not been possible for me to answer your query» and I was told to try this forum.
    Somebody please help!

    For your information here is the latest log file.  What is odd, is the reference to an old server which no longer exists in the domain: http://cserec/ Is this stuck in the cache somewhere? If so how do I get rid of it & why are all my other servers updating ok?  Please note I have changed the name of my proxy server in the log as it is an external local authority server.

    2009-11-24 09:10:46:474 1012 be4 AU Triggering AU detection through DetectNow API
    2009-11-24 09:10:46:474 1012 be4 AU Triggering Online detection (interactive)
    2009-11-24 09:10:46:490 1012 858 AU #############
    2009-11-24 09:10:46:490 1012 858 AU ## START ##  AU: Search for updates
    2009-11-24 09:10:46:490 1012 858 AU #########
    2009-11-24 09:10:46:490 1012 858 AU <<## SUBMITTED ## AU: Search for updates [CallId = {1B4FC90F-028C-44A9-9418-975614BBE5E0}]
    2009-11-24 09:10:46:490 1012 4ac Agent *************
    2009-11-24 09:10:46:490 1012 4ac Agent ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2009-11-24 09:10:46:490 1012 4ac Agent *********
    2009-11-24 09:10:46:490 1012 4ac Agent   * Online = Yes; Ignore download priority = No
    2009-11-24 09:10:46:490 1012 4ac Agent   * Criteria = «IsInstalled=0 and DeploymentAction=’Installation’ or IsPresent=1 and DeploymentAction=’Uninstallation’ or IsInstalled=1 and DeploymentAction=’Installation’ and RebootRequired=1 or IsInstalled=0 and DeploymentAction=’Uninstallation’ and RebootRequired=1»
    2009-11-24 09:10:46:490 1012 4ac Agent   * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
    2009-11-24 09:10:46:490 1012 4ac Agent   * Search Scope = {Machine}
    2009-11-24 09:10:46:490 1012 4ac Setup Checking for agent SelfUpdate
    2009-11-24 09:10:46:490 1012 4ac Setup Client version: Core: 7.2.6001.788  Aux: 7.2.6001.788
    2009-11-24 09:10:46:490 1012 4ac Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
    2009-11-24 09:10:46:490 1012 4ac Misc  Microsoft signed: Yes
    2009-11-24 09:10:49:110 1012 4ac Misc WARNING: SendRequest failed with hr = 80072ee7. Proxy List used: <proxyservername:8080> Bypass List used : <<local>> Auth Schemes used : <>
    2009-11-24 09:10:49:110 1012 4ac Misc WARNING: WinHttp: SendRequestUsingProxy failed for <http://cserec/selfupdate/wuident.cab>. error 0x8024402c
    2009-11-24 09:10:49:110 1012 4ac Misc WARNING: WinHttp: SendRequestToServerForFileInformation MakeRequest failed. error 0x8024402c
    2009-11-24 09:10:49:110 1012 4ac Misc WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x8024402c
    2009-11-24 09:10:49:110 1012 4ac Misc WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x8024402c
    2009-11-24 09:10:51:404 1012 4ac Misc WARNING: SendRequest failed with hr = 80072ee7. Proxy List used: <proxyservername:8080> Bypass List used : <<local>> Auth Schemes used : <>
    2009-11-24 09:10:51:404 1012 4ac Misc WARNING: WinHttp: SendRequestUsingProxy failed for <http://cserec/selfupdate/wuident.cab>. error 0x8024402c
    2009-11-24 09:10:51:404 1012 4ac Misc WARNING: WinHttp: SendRequestToServerForFileInformation MakeRequest failed. error 0x8024402c
    2009-11-24 09:10:51:404 1012 4ac Misc WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x8024402c
    2009-11-24 09:10:51:404 1012 4ac Misc WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x8024402c
    2009-11-24 09:10:53:697 1012 4ac Misc WARNING: SendRequest failed with hr = 80072ee7. Proxy List used: <proxyservername:8080> Bypass List used : <<local>> Auth Schemes used : <>
    2009-11-24 09:10:53:697 1012 4ac Misc WARNING: WinHttp: SendRequestUsingProxy failed for <http://cserec/selfupdate/wuident.cab>. error 0x8024402c
    2009-11-24 09:10:53:697 1012 4ac Misc WARNING: WinHttp: SendRequestToServerForFileInformation MakeRequest failed. error 0x8024402c
    2009-11-24 09:10:53:697 1012 4ac Misc WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x8024402c
    2009-11-24 09:10:53:697 1012 4ac Misc WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x8024402c
    2009-11-24 09:10:55:990 1012 4ac Misc WARNING: SendRequest failed with hr = 80072ee7. Proxy List used: <proxyservername:8080> Bypass List used : <<local>> Auth Schemes used : <>
    2009-11-24 09:10:55:990 1012 4ac Misc WARNING: WinHttp: SendRequestUsingProxy failed for <http://cserec/selfupdate/wuident.cab>. error 0x8024402c
    2009-11-24 09:10:55:990 1012 4ac Misc WARNING: WinHttp: SendRequestToServerForFileInformation MakeRequest failed. error 0x8024402c
    2009-11-24 09:10:55:990 1012 4ac Misc WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x8024402c
    2009-11-24 09:10:55:990 1012 4ac Misc WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x8024402c
    2009-11-24 09:10:55:990 1012 4ac Misc WARNING: DownloadFileInternal failed for http://cserec/selfupdate/wuident.cab: error 0x8024402c
    2009-11-24 09:10:55:990 1012 4ac Setup WARNING: SelfUpdate check failed to download package information, error = 0x8024402C
    2009-11-24 09:10:55:990 1012 4ac Setup FATAL: SelfUpdate check failed, err = 0x8024402C
    2009-11-24 09:10:55:990 1012 4ac Agent   * WARNING: Skipping scan, self-update check returned 0x8024402C
    2009-11-24 09:10:55:990 1012 4ac Agent   * WARNING: Exit code = 0x8024402C
    2009-11-24 09:10:55:990 1012 4ac Agent *********
    2009-11-24 09:10:55:990 1012 4ac Agent **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2009-11-24 09:10:55:990 1012 4ac Agent *************
    2009-11-24 09:10:55:990 1012 4ac Agent WARNING: WU client failed Searching for update with error 0x8024402c
    2009-11-24 09:10:55:990 1012 de8 AU >>##  RESUMED  ## AU: Search for updates [CallId = {1B4FC90F-028C-44A9-9418-975614BBE5E0}]
    2009-11-24 09:10:55:990 1012 de8 AU   # WARNING: Search callback failed, result = 0x8024402C
    2009-11-24 09:10:55:990 1012 de8 AU   # WARNING: Failed to find updates with error code 8024402C
    2009-11-24 09:10:55:990 1012 de8 AU #########
    2009-11-24 09:10:55:990 1012 de8 AU ##  END  ##  AU: Search for updates [CallId = {1B4FC90F-028C-44A9-9418-975614BBE5E0}]
    2009-11-24 09:10:55:990 1012 de8 AU #############
    2009-11-24 09:10:55:990 1012 de8 AU AU setting next detection timeout to 2009-11-24 14:10:55

Answers

  • Hello

    You’ll not be able to delete the Directory if the service is started.

    If you’re sure the proxy is correct, the WSUS URL is correct (http or https? Certificat’s ok? etc..). you can try this…

    sc stop bits
    sc stop wuauserv

    rmdir /s «%windir%\SoftwareDistribution»
    mkdir /s «%windir%\SoftwareDistribution»
    cacls «%windir%\SoftwareDistribution» /G Everyone:F

    gpupdate /target:computer

    sc start bits
    sc start wuauserv

    wuauclt /detectnow

    Conrad

    • Marked as answer by

      Wednesday, November 25, 2009 10:03 AM

    • Unmarked as answer by
      StBernards
      Wednesday, November 25, 2009 10:04 AM
    • Marked as answer by
      StBernards
      Wednesday, November 25, 2009 10:14 AM

  • Hi,

    Thanks for the info.  I followed your instructions & was able to delete the Software Distribution folder. Then I stopped my antivirus services & checked updates again.
    This time after I received the error I noticed that under the option «check for updates» it said «you receive updates: managed by your system administrator» This is not true because our WSUS server is set up only to install updates to the client machines, not servers — is it the case that server 2008 detects the WSUS server in the domain which makes WSUS the default method of checking for updates?
    Anyway when I clicked «check online for updates from windows update» — not seen this option before either — it successfully downloaded & installed all remaining updates.
    Thanks for your help as I think removing the Software Distribution folder was the key to sorting out this problem

    Many thanks

    • Marked as answer by
      StBernards
      Wednesday, November 25, 2009 10:14 AM

Источник
  • Remove From My Forums

  • Вопрос

  • здравствуйте.На свежеуcтановленных серверах Windows 2008 Standard Edition не ставятся апдейты…с этой ошибкой…перебпробовал очень многое…и выключал файрволл,и сбрасывал настройки для IE. На одном исправилось вроде работает..На остальных повторил операцию
    но все равно не работает…Подскажите пожалуйста в чем может быть дело?Спасибо!

    • Перемещено

      21 апреля 2012 г. 17:28
      merge forums (От:Windows Server 2008)

Ответы

  • Добрый день…Нет  она решилась самым необычным образом…Я всегда заходил на сервер через RDP. Как только зашел локально через консоль  и выполнил команду
    netsh winhttp reset proxy, проблема исправилась!Всем большое спасибо..

    не понятно почему?

    • Помечено в качестве ответа
      Nikita Panov
      9 декабря 2010 г. 10:16

Windows 7 Service Pack 1 Windows Server 2008 R2 Service Pack 1 Windows Server 2008 Service Pack 2 More…Less

Introduction

In compliance with the Microsoft Secure Hash Algorithm (SHA)-1 deprecation policy, Windows Update is discontinuing its SHA-1 based endpoints in late July 2020. This means that older Windows devices that have not updated to SHA-2 will no longer receive updates through Windows Update. Your older Windows devices can continue to use Windows Update by manually installing specific SHA-2 enabling updates.

All other Windows platforms will continue to receive updates through Windows Update as they always have because they connect to SHA-2 service endpoints.

Why is this change occurring?

An outdated Windows Update service endpoint used only for older platforms is being discontinued. This change is occurring because of weaknesses in the SHA-1 hashing algorithm and to align to industry standards.

Even though the SHA-1 endpoint is being discontinued, more recent Windows devices will continue receiving updates through Windows Update because those devices use the more secure SHA-2 algorithm. See the table in the «Which Windows devices are impacted» section to determine whether your devices are impacted.

For more information about this change, see 2019 SHA-2 Code Signing Support requirement for Windows and WSUS.

Which Windows devices are impacted?

Most users will not be impacted by this change. Starting with Windows 8 Desktop and Windows Server 2012, connections to Windows Update service endpoints use a more modern algorithm (SHA-256). Older versions of Windows connect to Windows Update service endpoints by using the less secure SHA-1 algorithm.

For most of the impacted versions of Windows, a SHA-2 update will add the support necessary to continue receiving updates through Windows Update. The following table shows the impact on the various versions of Windows. Some platforms are no longer supported, therefore they will not be updated.

Windows Desktop

Support state

Windows 2000

Device is out of support

Windows Updates will no longer be supported.

Windows XP 64-Bit Edition

Windows XP SP3

Windows Vista

Windows Vista SP1

Windows Vista SP2

Windows 7

Windows Update support will be impacted.
Can be mitigated by manually installing KBs.

Windows 7 SP1

Windows 8 and later versions

Not affected
No need to update

Windows Server

Support state

Windows 2000 Server

Device is out of support

Windows Updates will no longer be supported.

Windows Server 2003

Windows Server 2003 SP2

Windows Server 2008

Windows Update support will be impacted.
Can be mitigated by manually installing KBs.

Windows Server 2008 SP2

Windows Server 2008 R2

Windows Server 2008 R2 SP1

Windows 2012 and later versions

Not affected
No need to update

What will occur to impacted devices?

According to the previous table, only older Windows devices which have not updated to SHA-2 are impacted by this change. Impacted devices will no longer be able to receive updates through Windows Update until you manually update them to SHA-2. To manually update your Windows devices, see the «How to update Windows devices to SHA-2» section.

A Windows device that is not updated to SHA-2 will try to scan for updates and will return one of following errors:

  • Error code 80072ee2: The device cannot connect to Windows Update.

    Error code 80072ee2

  • Error code 8024402c: The device is unable to locate Windows Update.

    Error code 8024402c

  • Error code 80244019: The device cannot connect to Windows Update.

    Error code 80244019

Some update scans occur without direct user interaction with the UI such as automatic updates, device drivers, Defender antivirus signatures, Microsoft Office updates, and so on. For these “background” scans, these failures will not be obvious. In that case, you can check the Windows Update log file (c:windowswindowsupdate.log) for the failure codes: 0x8024402c, 8024402c, 0x80072ee2, 80072ee2, 0x80244019, or 80244019.

How to update Windows devices to SHA-2

To continue using Windows Update for your older Windows devices, you must download and install the following two specific updates:

Update 1: SHA-2 Code Signing Support

When you apply this update, support is added to validate signatures by using the more secure SHA-2 hashing algorithms. Apply only the update that is appropriate for your Windows device.

  • KB4474419: SHA-2 code signing support update
    Applies to: Windows 7 SP1, Windows Server 2008 R2 SP1, and Windows Server 2008 SP2

  • KB4484071: SHA2 Support for Windows Server Update Services
    Applies to: Windows Server Update Services 3.0 SP1 and Windows Server Update Services 3.2

Note Most users should only install update KB4474419. Enterprise administrators may also install update KB4484071.

Update 2: SHA-2 Related Servicing Stack Updates

When you apply this update, support is added to the Windows Update servicing stack to validate SHA-2 signatures and directs affected Windows devices to communicate with the modern, SHA-2 based service endpoints in Windows Update. Apply only the update that is appropriate for your Windows device.

  • KB4490628: Servicing stack update
    Applies to: Windows 7 SP1 and Windows Server 2008 R2 SP1

  • KB4493730: WU Service Stack Updates
    Applies to: Windows Server 2008 SP2

Need more help?

Want more options?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.

  • Remove From My Forums

  • Question

  • Hi,
    I am getting this error on my Server 2008 SP2 Domain Controller.  I have searched all the sites & have carried out the following:

    Stopped all Sophos Anti Virus services (I even tried uninstalling it at one point)
    Checked Windows firewall — disabled
    Set proxy — netsh winhttp>set proxy proxy-server=»servername:port”
    followed by

    net stop WuAuServ

    net start WuAuServ
    Then I tried renaming the Software Distribution folder, but got an access denied message.
    I was logged in as domain administrator, but couldn’t try local administrator account as there isn’t one on a domain controller.

    Has anyone got any ideas?  I have tried contacting Microsoft as they offer free support on Windows Updates errors, but the reply I got was «due to the nature of the technical query, it has not been possible for me to answer your query» and I was told to try this forum.
    Somebody please help!

    For your information here is the latest log file.  What is odd, is the reference to an old server which no longer exists in the domain: http://cserec/ Is this stuck in the cache somewhere? If so how do I get rid of it & why are all my other servers updating ok?  Please note I have changed the name of my proxy server in the log as it is an external local authority server.

    2009-11-24 09:10:46:474 1012 be4 AU Triggering AU detection through DetectNow API
    2009-11-24 09:10:46:474 1012 be4 AU Triggering Online detection (interactive)
    2009-11-24 09:10:46:490 1012 858 AU #############
    2009-11-24 09:10:46:490 1012 858 AU ## START ##  AU: Search for updates
    2009-11-24 09:10:46:490 1012 858 AU #########
    2009-11-24 09:10:46:490 1012 858 AU <<## SUBMITTED ## AU: Search for updates [CallId = {1B4FC90F-028C-44A9-9418-975614BBE5E0}]
    2009-11-24 09:10:46:490 1012 4ac Agent *************
    2009-11-24 09:10:46:490 1012 4ac Agent ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2009-11-24 09:10:46:490 1012 4ac Agent *********
    2009-11-24 09:10:46:490 1012 4ac Agent   * Online = Yes; Ignore download priority = No
    2009-11-24 09:10:46:490 1012 4ac Agent   * Criteria = «IsInstalled=0 and DeploymentAction=’Installation’ or IsPresent=1 and DeploymentAction=’Uninstallation’ or IsInstalled=1 and DeploymentAction=’Installation’ and RebootRequired=1 or IsInstalled=0 and DeploymentAction=’Uninstallation’ and RebootRequired=1»
    2009-11-24 09:10:46:490 1012 4ac Agent   * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
    2009-11-24 09:10:46:490 1012 4ac Agent   * Search Scope = {Machine}
    2009-11-24 09:10:46:490 1012 4ac Setup Checking for agent SelfUpdate
    2009-11-24 09:10:46:490 1012 4ac Setup Client version: Core: 7.2.6001.788  Aux: 7.2.6001.788
    2009-11-24 09:10:46:490 1012 4ac Misc Validating signature for C:WindowsSoftwareDistributionSelfUpdatewuident.cab:
    2009-11-24 09:10:46:490 1012 4ac Misc  Microsoft signed: Yes
    2009-11-24 09:10:49:110 1012 4ac Misc WARNING: SendRequest failed with hr = 80072ee7. Proxy List used: <proxyservername:8080> Bypass List used : <<local>> Auth Schemes used : <>
    2009-11-24 09:10:49:110 1012 4ac Misc WARNING: WinHttp: SendRequestUsingProxy failed for <http://cserec/selfupdate/wuident.cab>. error 0x8024402c
    2009-11-24 09:10:49:110 1012 4ac Misc WARNING: WinHttp: SendRequestToServerForFileInformation MakeRequest failed. error 0x8024402c
    2009-11-24 09:10:49:110 1012 4ac Misc WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x8024402c
    2009-11-24 09:10:49:110 1012 4ac Misc WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x8024402c
    2009-11-24 09:10:51:404 1012 4ac Misc WARNING: SendRequest failed with hr = 80072ee7. Proxy List used: <proxyservername:8080> Bypass List used : <<local>> Auth Schemes used : <>
    2009-11-24 09:10:51:404 1012 4ac Misc WARNING: WinHttp: SendRequestUsingProxy failed for <http://cserec/selfupdate/wuident.cab>. error 0x8024402c
    2009-11-24 09:10:51:404 1012 4ac Misc WARNING: WinHttp: SendRequestToServerForFileInformation MakeRequest failed. error 0x8024402c
    2009-11-24 09:10:51:404 1012 4ac Misc WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x8024402c
    2009-11-24 09:10:51:404 1012 4ac Misc WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x8024402c
    2009-11-24 09:10:53:697 1012 4ac Misc WARNING: SendRequest failed with hr = 80072ee7. Proxy List used: <proxyservername:8080> Bypass List used : <<local>> Auth Schemes used : <>
    2009-11-24 09:10:53:697 1012 4ac Misc WARNING: WinHttp: SendRequestUsingProxy failed for <http://cserec/selfupdate/wuident.cab>. error 0x8024402c
    2009-11-24 09:10:53:697 1012 4ac Misc WARNING: WinHttp: SendRequestToServerForFileInformation MakeRequest failed. error 0x8024402c
    2009-11-24 09:10:53:697 1012 4ac Misc WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x8024402c
    2009-11-24 09:10:53:697 1012 4ac Misc WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x8024402c
    2009-11-24 09:10:55:990 1012 4ac Misc WARNING: SendRequest failed with hr = 80072ee7. Proxy List used: <proxyservername:8080> Bypass List used : <<local>> Auth Schemes used : <>
    2009-11-24 09:10:55:990 1012 4ac Misc WARNING: WinHttp: SendRequestUsingProxy failed for <http://cserec/selfupdate/wuident.cab>. error 0x8024402c
    2009-11-24 09:10:55:990 1012 4ac Misc WARNING: WinHttp: SendRequestToServerForFileInformation MakeRequest failed. error 0x8024402c
    2009-11-24 09:10:55:990 1012 4ac Misc WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x8024402c
    2009-11-24 09:10:55:990 1012 4ac Misc WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x8024402c
    2009-11-24 09:10:55:990 1012 4ac Misc WARNING: DownloadFileInternal failed for http://cserec/selfupdate/wuident.cab: error 0x8024402c
    2009-11-24 09:10:55:990 1012 4ac Setup WARNING: SelfUpdate check failed to download package information, error = 0x8024402C
    2009-11-24 09:10:55:990 1012 4ac Setup FATAL: SelfUpdate check failed, err = 0x8024402C
    2009-11-24 09:10:55:990 1012 4ac Agent   * WARNING: Skipping scan, self-update check returned 0x8024402C
    2009-11-24 09:10:55:990 1012 4ac Agent   * WARNING: Exit code = 0x8024402C
    2009-11-24 09:10:55:990 1012 4ac Agent *********
    2009-11-24 09:10:55:990 1012 4ac Agent **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2009-11-24 09:10:55:990 1012 4ac Agent *************
    2009-11-24 09:10:55:990 1012 4ac Agent WARNING: WU client failed Searching for update with error 0x8024402c
    2009-11-24 09:10:55:990 1012 de8 AU >>##  RESUMED  ## AU: Search for updates [CallId = {1B4FC90F-028C-44A9-9418-975614BBE5E0}]
    2009-11-24 09:10:55:990 1012 de8 AU   # WARNING: Search callback failed, result = 0x8024402C
    2009-11-24 09:10:55:990 1012 de8 AU   # WARNING: Failed to find updates with error code 8024402C
    2009-11-24 09:10:55:990 1012 de8 AU #########
    2009-11-24 09:10:55:990 1012 de8 AU ##  END  ##  AU: Search for updates [CallId = {1B4FC90F-028C-44A9-9418-975614BBE5E0}]
    2009-11-24 09:10:55:990 1012 de8 AU #############
    2009-11-24 09:10:55:990 1012 de8 AU AU setting next detection timeout to 2009-11-24 14:10:55

Answers

  • Hello

    You’ll not be able to delete the Directory if the service is started.

    If you’re sure the proxy is correct, the WSUS URL is correct (http or https? Certificat’s ok? etc..). you can try this…

    sc stop bits
    sc stop wuauserv

    rmdir /s «%windir%SoftwareDistribution»
    mkdir /s «%windir%SoftwareDistribution»
    cacls «%windir%SoftwareDistribution» /G Everyone:F

    gpupdate /target:computer

    sc start bits
    sc start wuauserv

    wuauclt /detectnow

    Conrad

    • Marked as answer by

      Wednesday, November 25, 2009 10:03 AM

    • Unmarked as answer by
      StBernards
      Wednesday, November 25, 2009 10:04 AM
    • Marked as answer by
      StBernards
      Wednesday, November 25, 2009 10:14 AM

  • Hi,

    Thanks for the info.  I followed your instructions & was able to delete the Software Distribution folder. Then I stopped my antivirus services & checked updates again.
    This time after I received the error I noticed that under the option «check for updates» it said «you receive updates: managed by your system administrator» This is not true because our WSUS server is set up only to install updates to the client machines, not servers — is it the case that server 2008 detects the WSUS server in the domain which makes WSUS the default method of checking for updates?
    Anyway when I clicked «check online for updates from windows update» — not seen this option before either — it successfully downloaded & installed all remaining updates.
    Thanks for your help as I think removing the Software Distribution folder was the key to sorting out this problem

    Many thanks

    • Marked as answer by
      StBernards
      Wednesday, November 25, 2009 10:14 AM

Обновлено май 2023: перестаньте получать сообщения об ошибках и замедлите работу вашей системы с помощью нашего инструмента оптимизации. Получить сейчас в эту ссылку

  1. Скачайте и установите инструмент для ремонта здесь.
  2. Пусть он просканирует ваш компьютер.
  3. Затем инструмент почини свой компьютер.

Вы получаете код ошибки 8024402C при обновлении windows? Эта ошибка может возникать в Windows 10 и других версиях Windows. Это обычный Ошибка обновления Windows.

код ошибки-8024402c-окно

Это появляется на экране вашего компьютера как это сообщение:

Windows не может проверить наличие новых обновлений.
Произошла ошибка при поиске вашего компьютера.
Обнаружена ошибка:
Код 8024402C Windows Update обнаружил неизвестную ошибку.

Эта ошибка обновления Windows 8024402c вызвана неправильными настройками прокси-сервера или брандмауэра, которые не позволяют службам обновления Windows подключаться к Интернету.

Вот несколько методов, которые помогут вам решить эту проблему:

Сброс настроек прокси

ремонт-прокси

Это решение может быть очень полезным, поскольку оно может быть легко выполнено и может решить проблему путем сброса настроек прокси-сервера на вашем компьютере, которые были повреждены с момента последнего обновления. Следуйте инструкциям ниже, чтобы решить проблему.

Используйте Windows + X, чтобы открыть меню, из которого вы должны выбрать параметр командной строки (Admin). Вы также можете щелкнуть правой кнопкой мыши меню «Пуск» для того же эффекта или просто найти командную строку, щелкнуть правой кнопкой мыши и выбрать «Запуск от имени администратора».

Введите команды, перечисленные ниже, и обязательно нажимайте Enter после каждой команды, чтобы выполнить ее правильно.
сеть
ветер
сбросить прокси

Обновление за май 2023 года:

Теперь вы можете предотвратить проблемы с ПК с помощью этого инструмента, например, защитить вас от потери файлов и вредоносных программ. Кроме того, это отличный способ оптимизировать ваш компьютер для достижения максимальной производительности. Программа с легкостью исправляет типичные ошибки, которые могут возникнуть в системах Windows — нет необходимости часами искать и устранять неполадки, если у вас под рукой есть идеальное решение:

  • Шаг 1: Скачать PC Repair & Optimizer Tool (Windows 10, 8, 7, XP, Vista — Microsoft Gold Certified).
  • Шаг 2: Нажмите «Начать сканирование”, Чтобы найти проблемы реестра Windows, которые могут вызывать проблемы с ПК.
  • Шаг 3: Нажмите «Починить все», Чтобы исправить все проблемы.

скачать


Вернитесь в Центр обновления Windows и проверьте, сохраняется ли проблема на вашем компьютере.

Измените свой адрес DNS

Если ваш провайдер действительно вызывает эти проблемы, другие решения могут оказаться бесполезными, поскольку они не могут устранить тот факт, что ваш текущий DNS-адрес просто не совместим с серверами Microsoft. К счастью, изменить DNS-адрес очень просто, если вы будете тщательно следовать этим инструкциям. Вы можете легко отменить операцию, если что-то пойдет не так.

Откройте диалоговое окно «Выполнить», одновременно нажав кнопку с логотипом Windows + кнопку R. Затем введите «ncpa.cpl» и нажмите «ОК».
Теперь, когда окно подключения к Интернету открыто, дважды щелкните активный сетевой адаптер.
Затем нажмите «Свойства» и дважды щелкните «Версия протокола Интернета 4» (TCP / IPv4).
Поиск Используйте следующую опцию для адресов DNS-серверов.
Установите для предпочитаемого DNS-сервера значение 8.8.8.8.8.8.8.8.8.8.8.8.
Установите альтернативный DNS-сервер на 8.8.8.4.4.4.4.4.

Отключить антивирусное программное обеспечение

Disable-антивирусов-окна-10

Временно отключите защитное программное обеспечение и проверьте, сохраняется ли проблема.

a: Нажмите логотип Windows + Q, чтобы открыть поле поиска.

b: Теперь нажмите «Настройки», затем войдите в «Центр поддержки» и нажмите «Ввод».

c: Нажмите на шеврон рядом с безопасностью.

d: отключить антивирусную защиту, установленную на вашем компьютере.

Предупреждение. Антивирусное программное обеспечение может защитить ваш компьютер от вирусов и других угроз безопасности. В большинстве случаев не следует отключать антивирусное программное обеспечение. Если вам необходимо временно отключить его для установки другого программного обеспечения, вы должны активировать его, когда закончите. Если вы подключены к Интернету или сети, когда антивирусное программное обеспечение отключено, ваш компьютер уязвим для атак.

Использование Regedit

Обновить REGEDIT

Очень легко следовать этой процедуре:

Откройте редактор реестра (меню Пуск -> Выполнить -> Regedit).
Найдите следующий путь HKEY_LOCAL_MACHINE SOFTWARE Policies Microsoft Windows WindowsUpdate AU
Установите значение UseWUServer от 1 до 0 (дважды щелкните его, измените значение и нажмите OK).
Перезапустите службу Центра обновления Windows (меню «Пуск» -> Выполнить -> services.msc, найдите службу Центра обновления Windows и нажмите «Перезагрузить»).

Если вы по-прежнему не можете обновить Windows, могут быть другие причины.

ed_moyes

CCNA, веб-разработчик, ПК для устранения неполадок

Я компьютерный энтузиаст и практикующий ИТ-специалист. У меня за плечами многолетний опыт работы в области компьютерного программирования, устранения неисправностей и ремонта оборудования. Я специализируюсь на веб-разработке и дизайне баз данных. У меня также есть сертификат CCNA для проектирования сетей и устранения неполадок.

Сообщение Просмотров: 2,327

Windows Update error 8024402C (Windows could not search for new updates – Errors found 8024402C) while checking for updates is commonly caused by invalid network settings or invalid update settings. The problem also occurs if your computer was connected to a local network (LAN) and managed by a Windows Server Update Services (WSUS).

fix Windows Update Error 8024402C

This tutorial contains detailed instructions on how to resolve In order to fix the Windows Update error 0x8024402C in Windows 8, 7 or Vista.

How to fix Error code 0x8024402C in Windows Update.

Solution 1. Run the Windows Update Troubleshooter.

1. Navigate to Windows Control Panel, set the ‘View By’ to Small icons and open Troubleshooting.

image

2. In Troubleshooting options, click View all.

image

3. Open the Windows Update.

image

4. Click Next to troubleshoot Windows update problems.

image

5. When the troubleshooting process is complete, close the troubleshooter.
6. Restart your computer and see if the Error code 8024402C is resolved.

Solution 2. Change the DNS servers.

Some IPS causes errors with Windows Update. So try to manually add a public DNS server (e.g. Google DNS) on your network connection.

1. Press Windows image_thumb8 + R keys to open the run command box.

2. Type ncpa.cpl and press Enter.

image

3. Double click at your active Network Adapter.

4. Click Properties.

image

5. Open ‘Internet Protocol Version 4 (TCP/IPv4)’ Properties.

image

6. Select «Use the following DNS server addresses:» and type the following Google’s public DNS server addresses:

  • 8.8.8.8
  • 8.8.4.4

image

7. Press OK twice to exit Network settings.

8. Restart your computer and check for updates again.

Solution 3. Configure Automatic Updates client to connect directly to the Windows Update site on the Internet.

1. Press Windows image_thumb8 + R keys to open the run command box.

2. Type regedit and press Enter.

regedit

3. In Windows registry editor locate the following key:

HKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftWindowsWindowsUpdateAU

image

Note: If you don’t find the WindowsUpdate key you have to create it: Right click on Windows key (on the left pane) and select New > Key. Give the name: WindowsUpdate. Then right click at «WindowsUpdate’ & perform the same operation to create the AU key.

image_thumb14

4. At the right double click to open the UseWUServer value and change the Value data from 1 to 0.

image

Note: If you don’t find the UseWUServer value you have to create it: Right click on the right pane and select New > DWORD (32-bit) Value. Give the name: UseWUServer.

image_thumb18

5. Press OK to apply changes and exit from Registry Editor.

UseWUServer

That’s all folks! Did it work for you?

Please leave a comment in the comment section below or even better: like and share this blog post in the social networks to help spread the word about this solution.

If this article was useful for you, please consider supporting us by making a donation. Even $1 can a make a huge difference for us.

Источник
  • Remove From My Forums

  • Вопрос

  • здравствуйте.На свежеуcтановленных серверах Windows 2008 Standard Edition не ставятся апдейты…с этой ошибкой…перебпробовал очень многое…и выключал файрволл,и сбрасывал настройки для IE. На одном исправилось вроде работает..На остальных повторил операцию
    но все равно не работает…Подскажите пожалуйста в чем может быть дело?Спасибо!

    • Перемещено

      21 апреля 2012 г. 17:28
      merge forums (От:Windows Server 2008)

Ответы

  • Добрый день…Нет  она решилась самым необычным образом…Я всегда заходил на сервер через RDP. Как только зашел локально через консоль  и выполнил команду
    netsh winhttp reset proxy, проблема исправилась!Всем большое спасибо..

    не понятно почему?

    • Помечено в качестве ответа
      Nikita Panov
      9 декабря 2010 г. 10:16

Источник

Consider the following scenario:

  • The System Center Configuration Manager Administrator manages all updates in the environment.

  • Users have no access to the Windows Update website.

  • The Configuration Manager Software Update Point is configured and synchronizing.

  • The Automatic Deployment Rule for Definition Updates is configured and appears to deliver updates nightly with no problem.

In this scenario, when a new client is deployed and the local Administrator clicks the Update button in the System Center 2012 Endpoint Protection client user interface (SCEP UI), the search for updates eventually times out and the following error is displayed:

0x8024402c – System Center Endpoint Protection couldn’t install the definition updates because the proxy server or target server names can’t be resolved

Analysis of the C:\Windows\WindowsUpdate.log file also indicates that the SCEP client is attempting to access the Microsoft Update Website.

Symptoms

The Updates Distributed from Configuration Manager source setting is not like any of the other definition update source settings in SCEP policies. You cannot pull definitions from this source by clicking Update in the SCEP UI.

Cause

To work around this issue, set up another Definition Update source such as WSUS to fall back to when a client attempts to manually update definitions via the SCEP UI. Alternatively, you can hide the SCEP UI from the end user so they cannot click Update in the client UI using the Disable the client user interface policy setting introduced in System Center 2012 Configuration Manager SP1. The Disable the client user interface option is located in the Advanced area of the Antimalware policy setting in the Configuration Manager administration console.

Resolution

When you click Update in the SCEP UI, the client looks for a FallbackOrder registry key in HKLM\Software\Policies\Microsoft\Microsoft Antimalware\Signature Updates. The client will check each update source in the FallbackOrder registry key in the order that they are listed until it locates a source that has available definitions. If it goes through all sources without detecting available definitions, it returns an error and the update attempt is unsuccessful. Configuration Manager is never listed in the FallbackOrder registry key, as the SCEP client does not recognize a Configuration Manger Software Update Point agent (and associated infrastructure) as a valid definition source and cannot pull definitions from Configuration Manager. FallbackOrder sources can include InternalDefinitionUpdateServer (WSUS), MicrosoftUpdateServer (Microsoft Update Website), FileShares (One or more UNC file shares whose location is determined by policy), and MMPC (Microsoft Malware Protection Center alternate download location).

Configuration Manager definition updates are handled entirely by the CCM client Software Updates Agent and are downloaded and installed by the CCM software update agent. The schedule for these updates is determined when configuring the deployment rule during server side setup. See http://technet.microsoft.com/en-us/library/jj822983.aspx for more information.

When you select Updates Distributed from Configuration Manager in your SCEP policy, it does not modify the FallbackOrder registry key. Instead, this update source option sets the AuGracePeriod registry key in HKLM\Software\Policies\Microsoft\Microsoft Antimalware\Signature Updates. This registry setting suppresses the SCEP client from attempting to automatically pull definitions from sources defined in the FallbackOrder key for a set length of time determined by SCEP policy which is 72 hours by default, or 4320 minutes. This is designed to give the CCM client Software Update process sufficient time to complete the definition update process independently of the SCEP client.

If Updates Distributed from Configuration Manager is the only update source defined in your policy, then the FallbackOrder registry key will be blank. In this case, clicking Update in the SCEP UI will cause the client to revert to behavior similar to Microsoft Security Essentials and the client will attempt to update from the Microsoft Update website.

More Information

Need more help?

Want more options?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.

Источник

Windows Update error 8024402C (Windows could not search for new updates – Errors found 8024402C) while checking for updates is commonly caused by invalid network settings or invalid update settings. The problem also occurs if your computer was connected to a local network (LAN) and managed by a Windows Server Update Services (WSUS).

fix Windows Update Error 8024402C

This tutorial contains detailed instructions on how to resolve In order to fix the Windows Update error 0x8024402C in Windows 8, 7 or Vista.

How to fix Error code 0x8024402C in Windows Update.

Solution 1. Run the Windows Update Troubleshooter.

1. Navigate to Windows Control Panel, set the ‘View By’ to Small icons and open Troubleshooting.

image

2. In Troubleshooting options, click View all.

image

3. Open the Windows Update.

image

4. Click Next to troubleshoot Windows update problems.

image

5. When the troubleshooting process is complete, close the troubleshooter.
6. Restart your computer and see if the Error code 8024402C is resolved.

Solution 2. Change the DNS servers.

Some IPS causes errors with Windows Update. So try to manually add a public DNS server (e.g. Google DNS) on your network connection.

1. Press Windows image_thumb8 + R keys to open the run command box.

2. Type ncpa.cpl and press Enter.

image

3. Double click at your active Network Adapter.

4. Click Properties.

image

5. Open ‘Internet Protocol Version 4 (TCP/IPv4)’ Properties.

image

6. Select «Use the following DNS server addresses:» and type the following Google’s public DNS server addresses:

  • 8.8.8.8
  • 8.8.4.4

image

7. Press OK twice to exit Network settings.

8. Restart your computer and check for updates again.

Solution 3. Configure Automatic Updates client to connect directly to the Windows Update site on the Internet.

1. Press Windows image_thumb8 + R keys to open the run command box.

2. Type regedit and press Enter.

regedit

3. In Windows registry editor locate the following key:

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU

image

Note: If you don’t find the WindowsUpdate key you have to create it: Right click on Windows key (on the left pane) and select New > Key. Give the name: WindowsUpdate. Then right click at «WindowsUpdate’ & perform the same operation to create the AU key.

image_thumb14

4. At the right double click to open the UseWUServer value and change the Value data from 1 to 0.

image

Note: If you don’t find the UseWUServer value you have to create it: Right click on the right pane and select New > DWORD (32-bit) Value. Give the name: UseWUServer.

image_thumb18

5. Press OK to apply changes and exit from Registry Editor.

UseWUServer

That’s all folks! Did it work for you?

Please leave a comment in the comment section below or even better: like and share this blog post in the social networks to help spread the word about this solution.

If this article was useful for you, please consider supporting us by making a donation. Even $1 can a make a huge difference for us.

Источник

Понравилась статья? Поделить с друзьями:
  • 801411 bmw ошибка
  • 80244022 ошибка обновления windows server 2008 r2
  • 8024402c ошибка обновления windows 7 как исправить
  • 8024402b ошибка обновления windows 7 как исправить
  • 801410 ошибка bmw