Failure of all updates in Vista Home Premium

I have repeated failures of all updates for Windows Vista Home Premium.
Error codes 80073701, 8024200D, 80070002, 80200010. Have followed the
instructions on 70002 and 00010. I cannot find documentation on the other 2
codes. I have had Microsoft Tech Support escalate problem to Research.
Research has been on my computer for 3 days, and still has no idea why this
computer stopped taking updates. All virus scans and malware/spyware scans
show no infection. Is this an isolated incident or is this something the
community is seeing from others? Any information about others with this
problem would be helpful. Research is scratching their collective heads, as
neither they nor I can find the conflict. All help welcome.

Hello Sirrus8,

See if this thread helps

0x80073701 The referenced assembly could not be found.
ERROR_SXS_ASSEMBLY_MISSING
http://www.google.com/search?hl=en&q...01&btnG=Search

0x8024200D SUS_E_UH_NEEDANOTHERDOWNLOAD The installer requires more data to
be downloaded
http://www.google.com/search?hl=en&q...0D&btnG=Search

Just follow the yellow brick road ;-)

Good luck
- -- ---

"Sirrus8" wrote:

> I have repeated failures of all updates for Windows Vista Home Premium.
> Error codes 80073701, 8024200D, 80070002, 80200010. Have followed the
> instructions on 70002 and 00010. I cannot find documentation on the other 2
> codes. I have had Microsoft Tech Support escalate problem to Research.
> Research has been on my computer for 3 days, and still has no idea why this
> computer stopped taking updates. All virus scans and malware/spyware scans
> show no infection. Is this an isolated incident or is this something the
> community is seeing from others? Any information about others with this
> problem would be helpful. Research is scratching their collective heads, as
> neither they nor I can find the conflict. All help welcome.

I appreciate the site information, but have already been to those. I have
found info on 3 out of 4 of my error codes, followed all instructions for
curing the issue to no avail. I am now on my third Research tech, and have
found out that there are many other people having the same issue. From what
I have learned from the Microsoft research techs, there is a code error that
they are trying to find. The problem does not seem to be related to any
brand computer, security or other software, and does not affect every
computer that is downloading updates, so it is a coding error that is eluding
the Research section of tech support at this time. I have sent multiple logs
to Microsoft, and now have spent several hours each night over the last 5
days letting Research upload and download files and logs to and from my
computer. My entire registry has been raped, and yet there is still no
answer. The tech is going through a large volume of log files, and has yet
to discover the error in the code. I have done my own research on my other
computer, and have followed a similar, yet different path that microsoft is
following in their seach for the problem. I have not found any sign of
malware, spyware, or virus. I am nearing the point of simply wiping the hard
disk and sterilizing the cpu and starting over. I do find it interesting
that the tech reported that the reason I needed to email my logs to him is
that the website that Research uses to provide the key for the diagnostic
tools had crashed, and was unable to provide him with a key to continue his
research on my machine. It is ironic that their own website was unusable,
yet they want to work on my computer.
As I see many others in the forum have similar download update concerns,
if I find the coding error I will let the forum know. Anyone who gets a
break in this scenario, please post to the forum or this thread.

"Engel" wrote:

> Hello Sirrus8,
>
> See if this thread helps
>
> 0x80073701 The referenced assembly could not be found.
> ERROR_SXS_ASSEMBLY_MISSING
> http://www.google.com/search?hl=en&q...01&btnG=Search
>
> 0x8024200D SUS_E_UH_NEEDANOTHERDOWNLOAD The installer requires more data to
> be downloaded
> http://www.google.com/search?hl=en&q...0D&btnG=Search
>
> Just follow the yellow brick road ;-)
>
> Good luck
> - -- ---
>
> "Sirrus8" wrote:
>
> > I have repeated failures of all updates for Windows Vista Home Premium.
> > Error codes 80073701, 8024200D, 80070002, 80200010. Have followed the
> > instructions on 70002 and 00010. I cannot find documentation on the other 2
> > codes. I have had Microsoft Tech Support escalate problem to Research.
> > Research has been on my computer for 3 days, and still has no idea why this
> > computer stopped taking updates. All virus scans and malware/spyware scans
> > show no infection. Is this an isolated incident or is this something the
> > community is seeing from others? Any information about others with this
> > problem would be helpful. Research is scratching their collective heads, as
> > neither they nor I can find the conflict. All help welcome.

I have exactly the same problems it failed to update the service pack 1 I got
the advive to re-install windows vista hamo premium and after that there is
no update downloaded and instaaled properly. I tried all the solutions
available, but now I am annoyed and desperate that it won't update at all!
Teus

"Sirrus8" wrote:

> I have repeated failures of all updates for Windows Vista Home Premium.
> Error codes 80073701, 8024200D, 80070002, 80200010. Have followed the
> instructions on 70002 and 00010. I cannot find documentation on the other 2
> codes. I have had Microsoft Tech Support escalate problem to Research.
> Research has been on my computer for 3 days, and still has no idea why this
> computer stopped taking updates. All virus scans and malware/spyware scans
> show no infection. Is this an isolated incident or is this something the
> community is seeing from others? Any information about others with this
> problem would be helpful. Research is scratching their collective heads, as
> neither they nor I can find the conflict. All help welcome.

"Engel" wrote:

> Hello Sirrus8,
>
> See if this thread helps
>
> 0x80073701 The referenced assembly could not be found.
> ERROR_SXS_ASSEMBLY_MISSING
> http://www.google.com/search?hl=en&q...01&btnG=Search
>
> 0x8024200D SUS_E_UH_NEEDANOTHERDOWNLOAD The installer requires more data to
> be downloaded
> http://www.google.com/search?hl=en&q...0D&btnG=Search
>
> Just follow the yellow brick road ;-)
>
> Good luck
> - -- ---
>
> "Sirrus8" wrote:
>
> > I have repeated failures of all updates for Windows Vista Home Premium.
> > Error codes 80073701, 8024200D, 80070002, 80200010. Have followed the
> > instructions on 70002 and 00010. I cannot find documentation on the other 2
> > codes. I have had Microsoft Tech Support escalate problem to Research.
> > Research has been on my computer for 3 days, and still has no idea why this
> > computer stopped taking updates. All virus scans and malware/spyware scans
> > show no infection. Is this an isolated incident or is this something the
> > community is seeing from others? Any information about others with this
> > problem would be helpful. Research is scratching their collective heads, as
> > neither they nor I can find the conflict. All help welcome.


Thank you for the help, and am sorry I forgot this post. Reasearch found
an error in code process for binary. This subject is closed Thanks to all
for the assist.

I was having the same issue not long ago and was told that there was a
problem in the registry. I received the following simple-fix instructions
from a professional and it worked like a charm:
Corrupted Windows Update Temporary folders--
How to Rename the Windows Update Softwaredistribution folder
==========================================
This problem may occur if the Windows Update, Software distribution folder
has been corrupted. We can refer to the following steps to rename this
folder. Please note that the folder will be re-created the next time we visit
the Windows Update site.

1. Close all the open windows.

2. Click the "Start" Button, click "All programs", and click "Accessories".

3. Right-click "Command Prompt" and click "Run as administrator".

4. In "Administrator: Command Prompt" window, type in "net stop WuAuServ"
(without the quotes) and press Enter.

Note: Please look at the cmd window and make sure it says that it was
successfully stopped before we try to rename the folder. If it fails, do not
perform any further steps. Notify Microsoft of the error messages you
receive.

5. Click the "Start" Button, in the "Start Search" box, type in "%windir%"
(without the quotes) and press Enter.

6. In the opened folder, look for the folder named "SoftwareDistribution".

7. Right-click on the folder, select "Rename" and type "SDold" (without the
quotes) to rename this folder.

8. Still in "Administrator: Command Prompt" window, type the command "net
start WuAuServ" (without the quotes) in the opened window to restart the
Windows Updates service.

Note: Please look at the cmd window and make sure it says that it was
successfully started.
Hope this helps you too.


"Teus Reijmerink" wrote:

> I have exactly the same problems it failed to update the service pack 1 I got
> the advive to re-install windows vista hamo premium and after that there is
> no update downloaded and instaaled properly. I tried all the solutions
> available, but now I am annoyed and desperate that it won't update at all!
> Teus
>
> "Sirrus8" wrote:
>
> > I have repeated failures of all updates for Windows Vista Home Premium.
> > Error codes 80073701, 8024200D, 80070002, 80200010. Have followed the
> > instructions on 70002 and 00010. I cannot find documentation on the other 2
> > codes. I have had Microsoft Tech Support escalate problem to Research.
> > Research has been on my computer for 3 days, and still has no idea why this
> > computer stopped taking updates. All virus scans and malware/spyware scans
> > show no infection. Is this an isolated incident or is this something the
> > community is seeing from others? Any information about others with this
> > problem would be helpful. Research is scratching their collective heads, as
> > neither they nor I can find the conflict. All help welcome.

<snipped>

Eleanor wrote:
> I was having the same issue not long ago and was told that there
> was a problem in the registry. I received the following simple-fix
> instructions from a professional and it worked like a charm:
> Corrupted Windows Update Temporary folders--
> How to Rename the Windows Update Softwaredistribution folder
> ==========================================
> This problem may occur if the Windows Update, Software distribution
> folder has been corrupted. We can refer to the following steps to
> rename this folder. Please note that the folder will be re-created
> the next time we visit the Windows Update site.
>
> 1. Close all the open windows.
>
> 2. Click the "Start" Button, click "All programs", and click
> "Accessories".
>
> 3. Right-click "Command Prompt" and click "Run as administrator".
>
> 4. In "Administrator: Command Prompt" window, type in "net stop
> WuAuServ" (without the quotes) and press Enter.
>
> Note: Please look at the cmd window and make sure it says that it
> was successfully stopped before we try to rename the folder. If it
> fails, do not perform any further steps. Notify Microsoft of the
> error messages you receive.
>
> 5. Click the "Start" Button, in the "Start Search" box, type in
> "%windir%" (without the quotes) and press Enter.
>
> 6. In the opened folder, look for the folder named
> "SoftwareDistribution".
>
> 7. Right-click on the folder, select "Rename" and type "SDold"
> (without the quotes) to rename this folder.
>
> 8. Still in "Administrator: Command Prompt" window, type the
> command "net start WuAuServ" (without the quotes) in the opened
> window to restart the Windows Updates service.
>
> Note: Please look at the cmd window and make sure it says that it
> was successfully started.
> Hope this helps you too.

Time Bubble?

The conversation you have just attempted to assist with started and ended in
2008. Two postings in February 2008 and two in June 2008. It is now March
21, 2010.

The entire conversation properly quoted and archived indefinitely:
http://groups.google.com/group/micro...90f10159e49a3/

I'm sure the original poster (who actually founf the time to come back and
essentially close the issue) and later hijacker might appreciate the
assistance - if they ever happen across this older post again.

--
Shenan Stanley
MS-MVP
--
How To Ask Questions The Smart Way
http://www.catb.org/~esr/faqs/smart-questions.html