wuauclt.exe has encountered a problem...
Lee@discussions.microsoft.com S Lee
website, I get the error "wuauclt.exe has encountered a problem and needs to
close." This error happens dozens of times. I turned off automatic updates
and still get the error. I can't get the Windows update web page to work,
either. It keeps giving me an error:
The website has encountered a problem and cannot display the page you are
trying to view. Take the following steps to try solving the problem:
Refresh the page.
In Internet Explorer, delete your Temporary Internet Files by going to the
Tools menu and clicking Internet Options.
Here is the web page.
So how do I get wuauclt.exe fixed and working again, how do I get rid of
these errors, and how do I get windows update to work again?
Close and then re-open Internet Explorer
MowGreen [MVP]
http://www.bleepingcomputer.com/tutorials/tutorial62.html#winxp
Using Windows Explorer, navigate to WINDOWS\system32
locate wuauclt.exe
Right click it and choose Properties
Click the Version tab ...
KEEP the Properties window open
Navigate to WINDOWS\system32\dllcache
locate wuauclt.exe
Right click it and choose Properties
Click the Version tab ...
Do the Versions match ?
If yes, what is the Version number ?
If no, what are the Version numbers in both locations ?
> I turned off automatic updates and still get the error.
You 'Turned off Automatic Updates' using the Automatic Updates applet in
Control Panel or you stopped the Automatic Updates Service in the
Services Console ?
MowGreen [MVP 2003-2007]
===============
*-343-* FDNY
Never Forgotten
===============
SithMonkey7
topic. Alas, I am frustrated beyond all imagination. I trying to help a
friend square away a problem that began at the end of July with (from what I
have read) was a MS update gone wrong. I am getting several errors and
migraines.
The first: Generic Host Process for Win32 Services has encountered a problem
and needs to close
The second-infinity: wuauclt.exe has encountered a problem and needs to close
These errors are surrounded by multiple XXXXXXXXXX referenced memory at
XXXXXXXXX. The memory could not be read errors.
My symptoms are noted through several other related posts; windows updates
won't run without crashing, system resources being taxed, unsuspecting
household pets being kicked by their WindowsXP-running owners worldwide, etc.
etc.
I have seen scores of highly complex approaches to the issue, but nothing
useful for a novice who just wants his stupid OS to be easily fixed. Nor
have I seen anything that original poster verified as actually working
(thanks for nothing you non post replying posters!). With the prolific
nature of this issue, I can’t believe there isn’t something from MS that more
directly addresses and fixes this issue – but maybe I am just missing it!?
I applied one suggestion (that was posted in several places). This
suggestion was rooted in MS’s article on the 0x80248011 error (which I also
received) to stop auto update services and rename the SoftwareDistribution
folder to SoftwareDistribution.old and the restart services. After finally
figuring out that I had to uninstall Norton to be able to rename the folder,
this approach seemed to work. I was finally able to connect to windows
update, download many missed updates and install with success. I cracked out
the champagne, rejoiced, until reboot. I was right back to where I started
(in fact it seemed worse). Did I say "AAAAARRRGGGGHHHH" yet?
Most of the posts on this topic end with: 'I scrapped my OS and started from
scratch'. That is really not an option for my friend and I believe someone
out there (smarter than I) may be able to offer some useful direction to once
and all resolve this issue.
This is a desperate cry for help. Anyone? Your time is appreciated.
PA Bear
https://support.microsoft.com/oas/default.aspx?gprid=6527
Support for Windows Update:
http://support.microsoft.com/gp/wusupport
Customers in the U.S. and Canada can receive technical support from
Microsoft Product Support Services at 1-866-PCSAFETY. There is no-charge for
support calls that are associated with security updates. When you call,
clearly state that your problem is related to a Security Update and cite the
update's KB number (e.g., KB931678).
In other countries, see
http://support.microsoft.com/default.aspx?pr=securityhome > "No-Charge
Support...for virus and other security-related" issues in right-hand menu
for localized contact information.
For more information about how to contact Microsoft for support issues,
visit the International Support Web site:
https://support.microsoft.com/common/international.aspx
--
~Robear Dyer (PA Bear)
MS MVP-Windows (IE, OE, Security, Shell/User)
AumHa VSOP & Admin; DTS-L.org
SithMonkey7 wrote:
> I'm not sure where to best post this as there are scores of threads on the
> topic. Alas, I am frustrated beyond all imagination. I trying to help a
> friend square away a problem that began at the end of July with (from what
> I
> have read) was a MS update gone wrong. I am getting several errors and
> migraines.
>
> The first: Generic Host Process for Win32 Services has encountered a
> problem
> and needs to close
> The second-infinity: wuauclt.exe has encountered a problem and needs to
> close These errors are surrounded by multiple XXXXXXXXXX referenced memory
> at XXXXXXXXX. The memory could not be read errors.
>
> My symptoms are noted through several other related posts; windows updates
> won't run without crashing, system resources being taxed, unsuspecting
> household pets being kicked by their WindowsXP-running owners worldwide,
> etc. etc.
>
> I have seen scores of highly complex approaches to the issue, but nothing
> useful for a novice who just wants his stupid OS to be easily fixed. Nor
> have I seen anything that original poster verified as actually working
> (thanks for nothing you non post replying posters!). With the prolific
> nature of this issue, I can’t believe there isn’t something from MS
> that more directly addresses and fixes this issue – but maybe I am just
> missing it!?
>
> I applied one suggestion (that was posted in several places). This
> suggestion was rooted in MS’s article on the 0x80248011 error (which I
Ottmar Freudenberger
> I'm not sure where to best post this as there are scores of threads on the
> topic. Alas, I am frustrated beyond all imagination. I trying to help a
> friend square away a problem that began at the end of July with (from what I
> have read) was a MS update gone wrong. I am getting several errors and
> migraines.
>
> The first: Generic Host Process for Win32 Services has encountered a problem
> and needs to close
> The second-infinity: wuauclt.exe has encountered a problem and needs to close
> These errors are surrounded by multiple XXXXXXXXXX referenced memory at
> XXXXXXXXX. The memory could not be read errors.
http://support.microsoft.com/kb/927891/en-us and installing the latest
version of Windows Update Agent 3.0 may resolve the issue:
http://download.windowsupdate.com/WindowsUpdate/redist/standalone/7.0.6000.381/WindowsUpdateAgent30-x86.exe
Bye,
Freudi
SithMonkey7
downloading the Update Agent again, but when I went to install I received
'Install is not needed since Windows Update Agent is already installed.'
That being the case, I still have the laundry list of errors I mentioned in
my original post. Any other suggestions?
SithMonkey7
received this message 'Install is not needed since Windows Update Agent is
already installed.'
That being said, I still have the problems listed in my original post. Any
other suggestions?
Thanks,
Brian
SithMonkey7
and it was of with no avail. They sent me right back here.
Ottmar Freudenberger
> Thank you Feudi for taking time to help. I tried to apply the solution of
> downloading the Update Agent again, but when I went to install I received
> 'Install is not needed since Windows Update Agent is already installed.'
Cause you've missed the /wuforce parameter.
"[Path to where you've saved the EXE]\WindowsUpdateAgent30-x86.exe" /wuforce
But did you install KB927891 too?
Bye,
Freudi
SithMonkey7
selected 'run' as opposed to save. A
Upon another suggestion, I uninstalled KB927891. I then rebooted seemed ok,
until I restarted again, and it's all right back to where I started.
So are you saying I ought to save as opposed to run? And, I guess I don't
understand how to use the /wuforce parameter (sorry, I'm quite the novice).
Many thanks,
Brian
Ottmar Freudenberger
>I guess what I did was click on the link to windowsUpdateAgent30-x86.exe and
> selected 'run' as opposed to save.
So please read what was been written ;-)
> Upon another suggestion, I uninstalled KB927891.
That's not a solution, it's not even reasonable anyhow. Please reinstall
KB927891.
> So are you saying I ought to save as opposed to run?
Yes.
> And, I guess I don't
> understand how to use the /wuforce parameter (sorry, I'm quite the novice).
Okay, once more:
http://download.windowsupdate.com/WindowsUpdate/redist/standalone/7.0.6000.381/WindowsUpdateAgent30-x86.exe
*Save* the EXE into a folder, let's say "C:\Downloads". After the
download completed, type the following exactly and including every
quote and space under "Run" in the Start menu:
"C:\Downloads\WindowsUpdateAgent30-x86.exe" /wuforce
Hit the [Enter] key afterwards or click on "OK" to start the instal-
lation.
HTH,
Freudi
SithMonkey7
with /wuforce. It initiated just fine. During the install I received two
errors:
The instruction at "0x607500b7" referenced memory at "0x1975012e". The
memory could not be "read".
- I clicked OK to this error and it continued the install. The exact
same error popped up once more. I clicked OK again and it continued the
install. The install was successful and so we rebooted the pc. At restart,
we received these errors (the same as before we started):
"Generic Host Process for Win32 Services has encountered a problem and needs
to close..."
followed by
"wuauclt.exe has encountered a problem and needs to close."
Any ideas? Thanks.
Ottmar Freudenberger
> Hi there again. Well here is what I tried. As instructed I ran the update
> with /wuforce. It initiated just fine. During the install I received two
> errors:
>
> The instruction at "0x607500b7" referenced memory at "0x1975012e". The
> memory could not be "read".
You may want to stop the "Automatic Update" *service* before installing:
Start -> Run -> services.msc [Enter/OK]
Bye,
Freudi
SithMonkey7
"The instruction at "0x607500b7" referenced memory at "0x1975012e" errors
this time, but the outcome was still the same.
I am beginning to see why some folks have just given up and reloaded their
OS at this point, but I really don't want to have to take such measures.
Any other ideas?
Thanks again.
Ottmar Freudenberger
>I stopped all update services, ran the install again. I only received one of
> "The instruction at "0x607500b7" referenced memory at "0x1975012e" errors
> this time, but the outcome was still the same.
Well, I'm almost out of ideas here, especially if the very same happens
in Safe Mode of Windows too.
Which applications are running permanently in the background?
You're running Windows XP SP2, are you? Which version, Home Edition
or Professional/Media Center Edition?
Looking into the registry and the key
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\wuauserv
and its subkeys *may* be of interest too.
Bye,
Freudi
Robert Aldwinckle
news:CEF851F5-9747-4F08...@microsoft.com...
>I stopped all update services, ran the install again. I only received one of
> "The instruction at "0x607500b7" referenced memory at "0x1975012e" errors
> this time, but the outcome was still the same.
In which program? I couldn't be wuauclt.exe (the Subject of this discussion)
because you claim you "stopped all update services".
BTW where are you seeing that message? There should be more detail
showing you the program and module involved.
FWIW I don't have anything loaded at 0x60750000 which one would expect
in order to see a message like that, so I would suspect that you have a third-party
program loaded there which could be interfering and causing your error symtpom.
>
> I am beginning to see why some folks have just given up and reloaded their
> OS at this point, but I really don't want to have to take such measures.
Good. Then you should be willing to do some troubleshooting. ; )
>
> Any other ideas?
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.)
>
> Thanks again.
Good luck
Robert Aldwinckle
---
SithMonkey7
program or module is involved. That is the full extent of the message and
pop-up detail. I did run a couple of procmon files, but they are ginormous
to say the least. I am not really sure what I'm looking for in the log to
snip it out. Additionally, I'm not seeing that I can upload any files to the
forum here (I'm new, maybe I'm missing it). The smallest file I have is
88,012KB uncompressed, 9.55MB zipped. What can I provide that would be
useful and how?
Many Thanks,
Brian
Robert Aldwinckle
> Hi Robert and thanks for your reply. The error does not indicate which
> program or module is involved. That is the full extent of the message and pop-up detail.
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.)
> I did run a couple of procmon files, but they are ginormous
> to say the least. I am not really sure what I'm looking for in the log to
> snip it out.
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.
> Additionally, I'm not seeing that I can upload any files to the
> forum here (I'm new, maybe I'm missing it).
(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.
> [X-Newsreader: Microsoft CDO for Windows 2000]
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.
> The smallest file I have is 88,012KB uncompressed, 9.55MB zipped.
I don't think that much would be accepted as attachments on this server
even if you did post it in a test newsgroup.
> What can I provide that would be useful and how?
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.
>
> Many Thanks,
> Brian
Good luck
Robert
---
drclive
I had exactly the same problem. I disabled the error reporting service
and reinstalled the Windows Update file and all is working fine now.
Clive
galixy5
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.
--
galixy5
------------------------------------------------------------------------
galixy5's Profile: http://forums.techarena.in/members/38902.htm
View this thread: http://forums.techarena.in/windows-update/841321.htm
MowGreen
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.
MowGreen
===============
*-343-* FDNY
Never Forgotten
===============
banthecheck.com
"Security updates should *never* have *non-security content* prechecked"