Go Back   TechArena Community > Technical Support > Computer Help > Windows XP > Windows Update
Become a Member!
Forgot your username/password?
Tags Active Topics RSS Search Mark Forums Read

Sponsored Links



wuauclt.exe has encountered a problem...

Windows Update


Reply
 
Thread Tools Search this Thread
  #16  
Old 07-01-2008
Robert Aldwinckle
 
Posts: n/a
Re: wuauclt.exe has encountered a problem...

Have you disabled the Error Reporting Tool? (Ref.

<title>Description and availability of Internet Explorer Error Reporting tool</title>
http://support.microsoft.com/kb/276550

E.g. if there is a [click here] link in the message window use it.
It would lead you to a capturable Error Signature. (E.g. doubleclick
on a word, then Ctrl-a, Ctrl-c there.)

Please pay closer attention to what I said:

>> Run... ProcMon. It will capture an entry for your crash and you will be able
>> to extract from it a list of the modules involved in the call stack at the time
>> of the crash. That could be an easier alternative the more conventional
>> analysis of the Stack Back Trace for the crashing thread (e.g. as found
>> below the FAULT -> line in the associated drwtsn32.log dump.)


I'm suggesting only that you find the one entry which represents your crash event.
Then open that entry and you will see as I wrote: "a list of the modules involved
in the call stack at the time of the crash". The alternative to getting the call stack
that way is the more conventional Stack Back Trace provided by drwtsn32.log

E.g. that would probably be the last instance of wuauclt.exe in your trace,
probably one which contains the crash address (which you are seeing somehow).
BTW you probably also should check the Application tab in the Event Viewer
to see if there is a corresponding crash record in there.
The fact that you do see it means that you have something to search for,
which should make it relatively easy to find. I'm not sure if ProcMon reports
a 0x prefix on all its addresses so omit that when doing your find.

(FYI) You are posting to an NNTP news server. So if you were using a real NNTP
news reader (such as Outlook Express) you could upload files as attachments.
However, that would only be appropriate for small files, unless you posted
them in a message to a test newsgroup and then notified your readers how to find it.

That header line from your post shows that your "news reader"
is MS web interface to NNTP newsgroups. There is no provision
for posting attachments through it. Some such users find web
solutions to that problem and provide links to the files on third-party
servers.

I don't think that much would be accepted as attachments on this server
even if you did post it in a test newsgroup.

I'm still curious to know if you ever get a module loaded at 0x60750000
and if so what it is. ProcMon might help you find that too.
E.g. just capture all wuauclt.exe's activity, then do a find for 60750000.
(Actually, considering how close the crash is to that address perhaps
you should be looking instead for a module which loads at 0x60740000.)
Provided that (hypothetical) module gets loaded and then sticks around
long enough for you to see it loaded before your crash, you could alternatively
obtain that detail using Process Explorer.

I.e. I suspect that the crash address represents an offset in a third-party
module which was previously loaded. As I mentioned previously it is not
a base address that I see used in my wuauclt.exe (via Process Explorer).
If you knew which module it was you might have a better chance of eliminating
it as a source of interference and then at least changing your problem symptom.

However you get a list of the other modules loaded under wuauclt.exe
(but ideally with their routine names in the order that they were used
leading up to the crash--i.e. the call stack) would show us the callers
which were involved in the crash.
Reply With Quote
  #17  
Old 09-01-2008
drclive
 
Posts: n/a
Re: wuauclt.exe has encountered a problem...

I had exactly the same problem. I disabled the error reporting service
and reinstalled the Windows Update file and all is working fine now.
Reply With Quote
  #18  
Old 26-10-2009
Member
 
Join Date: Jan 2008
Posts: 1
Re: wuauclt.exe has encountered a problem...

I had this problem and this is what i did to fix it
http://support.microsoft.com/kb/927385

Step1: Check whether settings for the Automatic Updates service and for the Background Intelligent Transfer Service (BITS) are correct
To do this, follow these steps:
Click Start, point to Run, type services.msc, and then click OK.
In the details pane, locate and double-click Automatic Updates.
Click the Log On tab.
Make sure that the Local System account option is selected and that the Allow service to interact with desktop check box is cleared.
Make sure that this service has been enabled in the Hardware Profile list. If this service has not been enabled, click Enable to enable the service.
Click the General tab, and make sure that the Automatic option is selected in the Startup Type list. Under Service status, click Start to start the service if it is not already running.
Repeat steps 2 through 6 for Background Intelligent Transfer Service (BITS).
Step 2: Reregister Windows Update components
To do this, follow these steps:
Click Start, click Run, type REGSVR32 WUAPI.DLL, and then press ENTER.
When you receive the "DllRegisterServer in WUAPI.DLL succeeded" message, click OK.
Type the following commands in the Open box, one after the other, and then press ENTER after each command:
REGSVR32 WUAUENG.DLL
REGSVR32 WUAUENG1.DLL
REGSVR32 ATL.DLL
REGSVR32 WUCLTUI.DLL
REGSVR32 WUPS.DLL
REGSVR32 WUPS2.DLL
REGSVR32 WUWEB.DLL
Step 3: Rename the Windows Update temporary folder
The temporary folder of Windows Update may be corrupted. In this case, you can rename the temporary folder of Windows Update. To do this, follow these steps:
Click Start, click Run, type cmd, and then press ENTER.
At the command prompt, type net stop Wuauserv, and then press ENTER.
Click Start, click Run, type %windir%, and then press ENTER.
In the folder that opens, locate and rename the SoftwareDistribution folder to SDold.
At the command prompt, type net start Wuauserv, and then press ENTER to start the Automatic Updates service.
Reply With Quote
  #19  
Old 27-10-2009
MowGreen
 
Posts: n/a
Re: wuauclt.exe has encountered a problem...

The steps you listed below are the same ones automated by the Fixit on
this page: How do I reset Windows Update components?
http://support.microsoft.com/kb/971058

One can run the Fixit from the MSKB page, do the manual steps laid out,
or, the *preferred* way since Internet Explorer will *not* be open,
download, save the Fixit and the run it with the installed Security
software (antivirus/security suite/3rd party firewall) temporarily
disabled. A quick method that temp disables the Security software and
other 3rd party software from interfering with running the Fixit is to
Clean boot the system:

How to configure Windows XP to start in a "clean boot" state
http://support.microsoft.com/kb/310353

How to troubleshoot a problem by performing a clean boot in Windows
Vista or in Windows 7
http://support.microsoft.com/kb/929135

The Aggressive mode of the Fixit should *only* be run if running the
Fixit in it's Default mode does not resolve updating issues.
Reply With Quote
Reply

  TechArena Community > Technical Support > Computer Help > Windows XP > Windows Update
Tags: , , , ,



Thread Tools Search this Thread
Search this Thread:

Advanced Search


Similar Threads for: "wuauclt.exe has encountered a problem..."
Thread Thread Starter Forum Replies Last Post
Encountered a problem and needs to close I'm Member Windows Software 3 08-09-2009 10:35 AM
wuauclt.exe problem and 0x800706BE error Craig Windows Update 12 29-08-2009 02:38 AM
nfs.exe has encountered a problem and needs to close? Heavens Video Games 3 22-08-2009 06:31 PM
wuauclt.exe has encountered a problem and needs to close. HELP ME epanning Windows Update 1 30-11-2008 10:42 PM
ps2. exe has encountered a problem and needs to close EllingSon Windows XP Support 1 19-02-2007 10:13 PM


All times are GMT +5.5. The time now is 11:36 AM.