Microsoft Knowledge Base Email Alertz
All KB/RSS Links  |  Hot Kb!  |  New Kb!  |  Scott Cate  |  FAQ / KB  |  Web Hosting  |  Unsubscribe  

You receive a 0x8007041D error when you visit the Windows Update Web site

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.
Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

You receive a "0x8007041D" error when you visit the Windows Update Web site

Article ID: 902322 - View products that this article applies to.

SYMPTOMS

When you visit the Microsoft Windows Update Web site, you experience one or more of the following symptoms:
  • The following error code appears in the upper-right corner of the Microsoft Internet Explorer window:
    0x8007041D
  • If you try to stop the Automatic Updates service, you receive the following error message:
    Error 1054: The service did not respond to the start or control request in a timely fashion.
Note Additionally, if you click Express Install (Recommended) or Custom Install to scan the computer for available updates, the scanning process may appear to stop responding. When this issue occurs, the scan operation never finishes.
Back to the top | Give Feedback

CAUSE

This issue may occur if the following conditions are true:
  • The Eset NOD32 antivirus program is running on the computer.
  • The NOD32 antivirus version is earlier than NOD32 version 2.50.23.
Back to the top | Give Feedback

RESOLUTION

To resolve this issue, upgrade the NOD32 program to version 2.50.23 or to a later version. For more information about how to update the NOD32 version, visit the following Eset Web site:
http://www.eset.com/support/support.htm
(http://www.eset.com/support/support.htm)
Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.
Back to the top | Give Feedback

MORE INFORMATION

To determine whether the NOD32 antivirus program is running on the computer, follow these steps:
  1. Click Start, click Run, type appwiz.cpl, and then click OK.
  2. In the Add or Remove Programs dialog box, determine whether the NOD32 antivirus system appears under Currently installed programs.
When this issue occurs, the following information is logged in the %WINDIR%\WindowsUpdate.log file:
<date>   <time>   -0700    932      3a8       Service received SERVICE_CONTROL_STOP control
<date>   <time>            3696     d58       Setup    FATAL: SelfUpdate: Failed to stop service wuauserv, error = 0x8007041D
<date>   <time>            3696     d58       Setup    * WARNING: Exit code = 0x8007041D
<date>   <time>            3696     d58       Setup    *********
<date>   <time>            3696     d58       Setup    **  END  **  Setup: Installing client binaries
<date>   <time>            3696     d58       Setup    *************
<date>   <time>            3696     d58       Setup    FATAL: InstallUpdatedBinaries failed with error 0x8007041d
<date>   <time>            3696     d58       WUWeb    FATAL: InstallUpdatedBinaries failed with error:0x8007041d
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.
Back to the top | Give Feedback

Properties

Article ID: 902322 - Last Review: July 7, 2005 - Revision: 1.4
APPLIES TO
  • Microsoft Windows Update
Keywords: 
kbwindowsupdate kbprb KB902322
Retired KB Content Disclaimer
This article was written about products for which Microsoft no longer offers support. Therefore, this article is offered "as is" and will no longer be updated.
Back to the top | Give Feedback
        

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate

Nick - houstons74 NOSPAM-AT-NOSPAM yahoo.gr Reported as Irrelevant  
Written: 8/10/2005 5:22 AM
Did not solve my problem, either. I have no NOD32 software installed. The computer, next to mine, updated successfully.

God Reported as Irrelevant  
Written: 8/12/2005 5:35 PM
Clean installation of Win2k, nothing else installed, not even video drivers.

mc Reported as Irrelevant  
Written: 8/17/2005 9:08 AM
DIDN"T WORK! MICROSOFT SUPPORT SUCKS!!! I don't have that program installed either

Anonymous User Reported as Irrelevant  
Written: 8/19/2005 11:54 AM
same here. information was not relevant for me.

CJDD Reported as Irrelevant  
Written: 8/21/2005 3:19 PM
WIN2K - NO NOD32 INSTALLED - MS SUX (yes I am aware that I am yelling)

Peter Reported as Irrelevant  
Written: 8/23/2005 3:53 AM
When will a real fix be available for this problem

Anonymous User Reported as Irrelevant  
Written: 8/25/2005 5:02 PM
This did not help me at all.

Anonymous User Reported as Irrelevant  
Written: 8/26/2005 6:13 PM
Same here...clean install of Win2k -> Sp4 Still cannot Update. I have 2 computers here with these symptoms after applying SP4.

Mike Reported as Irrelevant  
Written: 8/31/2005 9:24 AM
MS is still lost - didnt help and cant find a solution that works

Anonymous User Reported as Irrelevant  
Written: 11/22/2005 10:27 AM
I have XP SP2 fresh clean install. This did not help me at all since I don't have NOD32. What IS NOD32?

Anonymous User Reported as Irrelevant  
Written: 12/21/2005 8:07 PM
I have a W2K system and was frustrated with this problem for months. I looked for NOD32, turned off virus scan, unregister/registered DLLs, etc. all to no avil. Today the following solution worked for me. It may help some of you: 1. Run "services.msc" 2. Find "Automatic updates". It was not running for me and I could not start it (says "internal error, ...") 3. Check "COM+ Event System", "Background Intelligent Transfer Service", and "System Event Notification" are running. If not, start them in that order. You may double click on them, and click "Dependency" tab in the pop up to turn on services that need to be on. For me, "Com+" was somehow disabled (I don't recall turning it off), and it set off a chain reaction that auto-update could not start. 4. Start Auto-update, it should start now!

Anonymous User Reported as Irrelevant  
Written: 12/28/2005 8:53 AM
Wow!!!!! That's a useful advice, at last! Thanx

Anonymous User Reported as Irrelevant  
Written: 1/4/2006 7:58 PM
Yes, indeed very useful. Solved the problem for me as well. (Still at a loss why that service stopped running, but that's an other matter.)

Anonymous User Reported as Irrelevant  
Written: 1/7/2006 9:39 AM
Thaks.Perfect,solved the problem

Anonymous User Reported as Irrelevant  
Written: 1/11/2006 9:37 PM
Excellent. I had COM+ and Background Intelligent Transfer Service disabled. Thanks for the help.

Canis Reported as Irrelevant  
Written: 1/17/2006 4:11 AM
I don't seem to have this COM+ thing in the list. Anyone got any idea why? WTF are microsoft up to? The update thing used to work perfectly.

seeker Reported as Irrelevant  
Written: 2/3/2006 7:26 PM
That was great practical advice even though it didn't solve my problem it felt good to actually try something that might work! Thanks.

Questor Reported as Irrelevant  
Written: 2/4/2006 1:58 PM
The Way solved my Problem, even if it had another cause - i did a repair install after rebuilding my harddisk - that changed the Driveletter in Registry for the services! (See Properties for each service in services list).

Anonymous User Reported as Irrelevant  
Written: 2/11/2006 12:48 AM
you can also use net start|stop BITS|wuauserv to start or stop intelligent background transfer or auto update service from commandline

Nate Reported as Irrelevant  
Written: 3/8/2006 3:17 PM
Anonymous User - 12/21/2005 8:07 PM is the man, he's the one with the answers.

Jake Reported as Irrelevant  
Written: 8/13/2006 9:30 AM
Mine is doing the same thing and i dont have NOD32 software. Maybe it can be McAfee doing this???

ELAINE Reported as Irrelevant  
Written: 10/1/2006 6:31 AM
I tried solution outlined by Anonymous User - 12/21/2005 8:07 PM. Automatic Updates still does not work and displays the error message 0x8024d007:0x8024d007. HELP!

Brinkworth K Report As Irrelevant  
Written: 7/2/2007 4:29 AM
Manage Computer, Services COM+ Event System started Automatic Updates started Mine then worked

Anonymous User Report As Irrelevant  
Written: 11/6/2008 3:09 AM
The Windows Update service is launched by the system, under system account credentials, and with the following command line: C:\windows\system32\svchost.exe -k wugroup end process svchost.exe - k wugroup(large) and run Automatic Updates



Copyright © 2002-2007 KBALERTZ.COM.  All Rights Reserved. Terms / Privacy. Discount ASP.NET Hosting