Re: FYI:Stealth Windows update prevents XP repair

"Doug" <> schrieb:

> http://windowssecrets.com/comp/070927/#story1

Once again BS coming from that site.
See http://support.microsoft.com/kb/916259/en-us for your reference.

Bye,
Freudi

The reason that the .dll files need to be reregistered is because '3rd
party software' is guarding/locking reg entries and system files, thus
preventing one or some of them, from registering when they are
installing. If one checks the WindowsUpdate.log one can see where the
registration of said .dll's is taking place:

2007-08-21 09:13:28:270 984 444 Setup Starting registry operations for
section wuapi
2007-08-21 09:13:28:270 984 444 Misc Registering binary:
D:\WINDOWS\system32\regsvr32.exe /s "D:\WINDOWS\system32\wuapi.dll"
2007-08-21 09:13:31:174 984 444 Setup Completed registration operations
for section wuapi: status 0
2007-08-21 09:13:31:174 984 444 Setup Starting registry operations for
section wuauclt
2007-08-21 09:13:31:174 984 444 Setup Completed registration operations
for section wuauclt: status 0
2007-08-21 09:13:31:174 984 444 Setup Starting registry operations for
section wuaucpl
2007-08-21 09:13:31:174 984 444 Setup Completed registration operations
for section wuaucpl: status 0
2007-08-21 09:13:31:174 984 444 Setup Starting registry operations for
section wuaueng_SelfUpdate
2007-08-21 09:13:31:835 984 444 Setup Completed registration operations
for section wuaueng_SelfUpdate: status 0
2007-08-21 09:13:31:835 984 444 Setup Starting registry operations for
section wucltui
2007-08-21 09:13:31:835 984 444 Misc Registering binary:
D:\WINDOWS\system32\regsvr32.exe /s "D:\WINDOWS\system32\wucltui.dll"
2007-08-21 09:13:32:376 984 444 Setup Completed registration operations
for section wucltui: status 0
2007-08-21 09:13:32:386 984 444 Setup Starting registry operations for
section wups
2007-08-21 09:13:32:386 984 444 Setup Completed registration operations
for section wups: status 0
2007-08-21 09:13:32:386 984 444 Setup Starting registry operations for
section wups2
2007-08-21 09:13:32:396 984 444 Setup Completed registration operations
for section wups2: status 0
2007-08-21 09:13:32:396 984 444 Setup Starting registry operations for
section wuweb
2007-08-21 09:13:32:396 984 444 Misc Registering binary:
D:\WINDOWS\system32\regsvr32.exe /s "D:\WINDOWS\system32\wuweb.dll"
2007-08-21 09:13:33:758 984 444 Setup Completed registration operations
for section wuweb: status 0
2007-08-21 09:13:33:768 984 444 Setup Processing registry operations
completed. Deleting backup files.

Said .dll files are included in latest Version of the Windows Update
Agent/Client.

To reregister the .dll files in XP open a Command Prompt, type in these
commands, pressing Enter after each command:

net stop wuauserv
regsvr32 wuapi.dll
regsvr32 wuaueng1.dll
regsvr32 wuaueng.dll
regsvr32 wucltui.dll
regsvr32 wups2.dll
regsvr32 wups.dll
regsvr32 wuweb.dll
net start wuauserv
exit

Restart the system.

MowGreen [MVP 2003-2007]
===============
*-343-* FDNY
Never Forgotten
===============


Doug wrote:

> "Ottmar Freudenberger" <> wrote in message
> news:...
>
>>"Doug" <> schrieb:
>>
>>
>>>http://windowssecrets.com/comp/070927/#story1
>>
>>Once again BS coming from that site.
>>See http://support.microsoft.com/kb/916259/en-us for your reference.
>>
>>Bye,
>>Freudi
>
>
> BS coming from somewhere to be certain.
>
> The "reference" you posted involves a scenario where Windows will not scan
> for updates, throws 0x800700B6 error code in the log and is related to an
> activeX control version conflict .
>
> The topic on which I posted involves a scenario were WUD does scan for
> updates and fails to install them do to a problem with a number of
> unregistered DLL files.
>
> Not exactly the same. (or at all
>
> Comically the post you replied to right before this one "Updates fail after
> upgrade from XP-Home to XP-Pro." was solved by the OP using the information
> you refer to as, "....BS coming from that site."
>
> See "[solved] Updates fail after upgrade from XP-Home to XP-Pro."
>

"Doug" <> schrieb:
> "Ottmar Freudenberger" <> wrote in message
> news:...
>> "Doug" <> schrieb:
>>
>>> http://windowssecrets.com/comp/070927/#story1
>>
>> Once again BS coming from that site.
>> See http://support.microsoft.com/kb/916259/en-us for your reference.

> BS coming from somewhere to be certain.

From Windows Secrets site, yup.

> The "reference" you posted involves a scenario where Windows will not scan
> for updates, throws 0x800700B6 error code in the log and is related to an
> activeX control version conflict .

Ignore the title, deal with the workaround/solution for the problem
and you're done.

> Comically the post you replied to right before this one "Updates fail after
> upgrade from XP-Home to XP-Pro." was solved by the OP using the information
> you refer to as, "....BS coming from that site."

It's BS in it's analysis and cause for the issue.

Bye,
Freudi

"MowGreen [MVP]" <> schrieb:

> The reason that the .dll files need to be reregistered is because '3rd
> party software' is guarding/locking reg entries and system files, thus
> preventing one or some of them, from registering when they are
> installing.

Ehm, not really. It's a DLL version conflict arousing with WUA 3.0
(which version so ever) installed and executing a "Repair installation"
of Windows XP SP2 afterwards. While I still find the following instal-
lation of WUA 3.0 with paramenter /wuforce easier and more targeting
(since every machine now needs to download and install WUA 3.0 to get
Auto/Windows Update to work anyway), you can for sure try to reregister
some DLLs and let WUA 3.0 redownload afterwards automatically.

I'm pretty sure about that this problem doesn't target us any longer
when SP3 for Windows XP will be released sometime next year.

Bye,
Freudi

According to MS, it's only one .dll causing the issue:

Updates are not installed successfully from Windows Update, from
Microsoft Update, or by using Automatic Updates after you repair a
Windows XP installation
http://support.microsoft.com/kb/943144

> This problem occurs because of how the Windows XP repair operation replaces Windows system
> files. When you repair a Windows installation by using a Windows XP CD, the repair
> operation performs both of the following operations:
> • It replaces all the Windows system files with the corresponding files from the CD.
>
> Note This includes the Windows Update files.
> • It restores the Windows registry.
> The latest version of Windows Update includes a file that was not available in the
> release version of Windows XP. This file is named Wups2.dll. Therefore, after the repair
> operation is complete, the following situation exists:
> • The Wups2.dll file remains on the computer.
> • The registry entries that correspond to this file are missing.
> Because the registry files that correspond to the Wups2.dll file are missing, update
> installations are unsuccessful.

Blogged:
http://windowsvistablog.com/blogs/wi...rom-xp-cd.aspx
http://blogs.technet.com/mu/archive/...airing-xp.aspx
http://www.bleepingcomputer.com/blog...showentry=1170

It would be NICE if MS updated the link to the WUA. Then folks wouldn't
have to needlessly install the PREVIOUS version and *hope* that AU/WU/MU
can install the latest V. <sigh>
That's where 3rd party 'software' comes in, Freudi.

MowGreen [MVP 2003-2007]
===============
*-343-* FDNY
Never Forgotten
===============




Ottmar Freudenberger wrote:

> "MowGreen [MVP]" <> schrieb:
>
>
>>The reason that the .dll files need to be reregistered is because '3rd
>>party software' is guarding/locking reg entries and system files, thus
>>preventing one or some of them, from registering when they are
>>installing.
>
>
> Ehm, not really. It's a DLL version conflict arousing with WUA 3.0
> (which version so ever) installed and executing a "Repair installation"
> of Windows XP SP2 afterwards. While I still find the following instal-
> lation of WUA 3.0 with paramenter /wuforce easier and more targeting
> (since every machine now needs to download and install WUA 3.0 to get
> Auto/Windows Update to work anyway), you can for sure try to reregister
> some DLLs and let WUA 3.0 redownload afterwards automatically.
>
> I'm pretty sure about that this problem doesn't target us any longer
> when SP3 for Windows XP will be released sometime next year.
>
> Bye,
> Freudi

Freudi ... another MVP dug around in the wuredist.cab and came up with:

x86-based versions of Windows [32 bit]
http://download.windowsupdate.com/Wi...gent30-x86.exe

x64-based versions of Windows [64 bit]
http://download.windowsupdate.com/Wi...gent30-x64.exe

Itanium-based versions of Windows
http://download.windowsupdate.com/Wi...ent30-ia64.exe

Feel free to spread the URLs around <w>

MowGreen [MVP 2003-2007]
===============
*-343-* FDNY
Never Forgotten
===============







MowGreen [MVP] wrote:

> According to MS, it's only one .dll causing the issue:
>
> Updates are not installed successfully from Windows Update, from
> Microsoft Update, or by using Automatic Updates after you repair a
> Windows XP installation
> http://support.microsoft.com/kb/943144
>
>> This problem occurs because of how the Windows XP repair operation
>> replaces Windows system
>> files. When you repair a Windows installation by using a Windows XP
>> CD, the repair operation performs both of the following operations:
>> • It replaces all the Windows system files with the corresponding
>> files from the CD.
>>
>> Note This includes the Windows Update files.
>> • It restores the Windows registry.
>> The latest version of Windows Update includes a file that was not
>> available in the release version of Windows XP. This file is named
>> Wups2.dll. Therefore, after the repair operation is complete, the
>> following situation exists:
>> • The Wups2.dll file remains on the computer.
>> • The registry entries that correspond to this file are missing.
>> Because the registry files that correspond to the Wups2.dll file are
>> missing, update installations are unsuccessful.
>
>
> Blogged:
> http://windowsvistablog.com/blogs/wi...rom-xp-cd.aspx
>
> http://blogs.technet.com/mu/archive/...airing-xp.aspx
>
> http://www.bleepingcomputer.com/blog...showentry=1170
>
> It would be NICE if MS updated the link to the WUA. Then folks wouldn't
> have to needlessly install the PREVIOUS version and *hope* that AU/WU/MU
> can install the latest V. <sigh>
> That's where 3rd party 'software' comes in, Freudi.
>
> MowGreen [MVP 2003-2007]
> ===============
> *-343-* FDNY
> Never Forgotten
> ===============
>
>
>
>
> Ottmar Freudenberger wrote:
>
>> "MowGreen [MVP]" <> schrieb:
>>
>>
>>> The reason that the .dll files need to be reregistered is because
>>> '3rd party software' is guarding/locking reg entries and system
>>> files, thus preventing one or some of them, from registering when
>>> they are installing.
>>
>>
>>
>> Ehm, not really. It's a DLL version conflict arousing with WUA 3.0
>> (which version so ever) installed and executing a "Repair installation"
>> of Windows XP SP2 afterwards. While I still find the following instal-
>> lation of WUA 3.0 with paramenter /wuforce easier and more targeting
>> (since every machine now needs to download and install WUA 3.0 to get
>> Auto/Windows Update to work anyway), you can for sure try to reregister
>> some DLLs and let WUA 3.0 redownload afterwards automatically.
>>
>> I'm pretty sure about that this problem doesn't target us any longer
>> when SP3 for Windows XP will be released sometime next year.
>>
>> Bye,
>> Freudi

...winston
MS-MVP Windows Live Mail

"MowGreen [MVP]" <> wrote in message
news:...
> Freudi ... another MVP dug around in the wuredist.cab and came up
> with:
>
> x86-based versions of Windows [32 bit]
> http://download.windowsupdate.com/Wi...gent30-x86.exe
>
> x64-based versions of Windows [64 bit]
> http://download.windowsupdate.com/Wi...gent30-x64.exe
>
> Itanium-based versions of Windows
> http://download.windowsupdate.com/Wi...ent30-ia64.exe
>
> Feel free to spread the URLs around <w>
>
> MowGreen [MVP 2003-2007]
> ===============
> *-343-* FDNY
> Never Forgotten
> ===============
>
>
>
>
>
>
>
> MowGreen [MVP] wrote:
>
>> According to MS, it's only one .dll causing the issue:
>>
>> Updates are not installed successfully from Windows Update, from
>> Microsoft Update, or by using Automatic Updates after you repair a
>> Windows XP installation
>> http://support.microsoft.com/kb/943144
>>
>>> This problem occurs because of how the Windows XP repair operation
>>> replaces Windows system
>>> files. When you repair a Windows installation by using a Windows XP
>>> CD, the repair operation performs both of the following operations:
>>> • It replaces all the Windows system files with the corresponding
>>> files from the CD.
>>>
>>> Note This includes the Windows Update files.
>>> • It restores the Windows registry.
>>> The latest version of Windows Update includes a file that was not
>>> available in the release version of Windows XP. This file is named
>>> Wups2.dll. Therefore, after the repair operation is complete, the
>>> following situation exists:
>>> • The Wups2.dll file remains on the computer.
>>> • The registry entries that correspond to this file are missing.
>>> Because the registry files that correspond to the Wups2.dll file are
>>> missing, update installations are unsuccessful.
>>
>>
>> Blogged:
>> http://windowsvistablog.com/blogs/wi...rom-xp-cd.aspx
>> http://blogs.technet.com/mu/archive/...airing-xp.aspx
>> http://www.bleepingcomputer.com/blog...showentry=1170
>>
>> It would be NICE if MS updated the link to the WUA. Then folks
>> wouldn't have to needlessly install the PREVIOUS version and *hope*
>> that AU/WU/MU can install the latest V. <sigh>
>> That's where 3rd party 'software' comes in, Freudi.
>>
>> MowGreen [MVP 2003-2007]
>> ===============
>> *-343-* FDNY
>> Never Forgotten
>> ===============
>>
>>
>>
>>
>> Ottmar Freudenberger wrote:
>>
>>> "MowGreen [MVP]" <> schrieb:
>>>
>>>
>>>> The reason that the .dll files need to be reregistered is because
>>>> '3rd party software' is guarding/locking reg entries and system
>>>> files, thus preventing one or some of them, from registering when
>>>> they are installing.
>>>
>>>
>>>
>>> Ehm, not really. It's a DLL version conflict arousing with WUA 3.0
>>> (which version so ever) installed and executing a "Repair
>>> installation"
>>> of Windows XP SP2 afterwards. While I still find the following
>>> instal-
>>> lation of WUA 3.0 with paramenter /wuforce easier and more targeting
>>> (since every machine now needs to download and install WUA 3.0 to
>>> get
>>> Auto/Windows Update to work anyway), you can for sure try to
>>> reregister
>>> some DLLs and let WUA 3.0 redownload afterwards automatically.
>>>
>>> I'm pretty sure about that this problem doesn't target us any longer
>>> when SP3 for Windows XP will be released sometime next year.
>>>
>>> Bye,
>>> Freudi

"MowGreen [MVP]" <> schrieb:

> Freudi ... another MVP dug around in the wuredist.cab and came up with:
>
> x86-based versions of Windows [32 bit]
> http://download.windowsupdate.com/Wi...gent30-x86.exe
>
> x64-based versions of Windows [64 bit]
> http://download.windowsupdate.com/Wi...gent30-x64.exe
>
> Itanium-based versions of Windows
> http://download.windowsupdate.com/Wi...ent30-ia64.exe
>
> Feel free to spread the URLs around <w>

Thanks & done

Bye,
Freudi

Thanks, winston. WTG

MowGreen [MVP 2003-2007]
===============
*-343-* FDNY
Never Forgotten
===============


....winston wrote:

>
>
> ...winston
> MS-MVP Windows Live Mail
>
> "MowGreen [MVP]" <> wrote in message
> news:...
>
>> Freudi ... another MVP dug around in the wuredist.cab and came up with:
>>
>> x86-based versions of Windows [32 bit]
>> http://download.windowsupdate.com/Wi...gent30-x86.exe
>>
>>
>> x64-based versions of Windows [64 bit]
>> http://download.windowsupdate.com/Wi...gent30-x64.exe
>>
>>
>> Itanium-based versions of Windows
>> http://download.windowsupdate.com/Wi...ent30-ia64.exe
>>
>>
>> Feel free to spread the URLs around <w>
>>
>> MowGreen [MVP 2003-2007]
>> ===============
>> *-343-* FDNY
>> Never Forgotten
>> ===============
>>
>>
>>
>>
>>
>>
>>
>> MowGreen [MVP] wrote:
>>
>>> According to MS, it's only one .dll causing the issue:
>>>
>>> Updates are not installed successfully from Windows Update, from
>>> Microsoft Update, or by using Automatic Updates after you repair a
>>> Windows XP installation
>>> http://support.microsoft.com/kb/943144
>>>
>>>> This problem occurs because of how the Windows XP repair operation
>>>> replaces Windows system
>>>> files. When you repair a Windows installation by using a Windows XP
>>>> CD, the repair operation performs both of the following operations:
>>>> • It replaces all the Windows system files with the corresponding
>>>> files from the CD.
>>>>
>>>> Note This includes the Windows Update files.
>>>> • It restores the Windows registry.
>>>> The latest version of Windows Update includes a file that was not
>>>> available in the release version of Windows XP. This file is named
>>>> Wups2.dll. Therefore, after the repair operation is complete, the
>>>> following situation exists:
>>>> • The Wups2.dll file remains on the computer.
>>>> • The registry entries that correspond to this file are missing.
>>>> Because the registry files that correspond to the Wups2.dll file are
>>>> missing, update installations are unsuccessful.
>>>
>>>
>>>
>>> Blogged:
>>> http://windowsvistablog.com/blogs/wi...rom-xp-cd.aspx
>>> http://blogs.technet.com/mu/archive/...airing-xp.aspx
>>> http://www.bleepingcomputer.com/blog...showentry=1170
>>>
>>> It would be NICE if MS updated the link to the WUA. Then folks
>>> wouldn't have to needlessly install the PREVIOUS version and *hope*
>>> that AU/WU/MU can install the latest V. <sigh>
>>> That's where 3rd party 'software' comes in, Freudi.
>>>
>>> MowGreen [MVP 2003-2007]
>>> ===============
>>> *-343-* FDNY
>>> Never Forgotten
>>> ===============
>>>
>>>
>>>
>>>
>>> Ottmar Freudenberger wrote:
>>>
>>>> "MowGreen [MVP]" <> schrieb:
>>>>
>>>>
>>>>> The reason that the .dll files need to be reregistered is because
>>>>> '3rd party software' is guarding/locking reg entries and system
>>>>> files, thus preventing one or some of them, from registering when
>>>>> they are installing.
>>>>
>>>>
>>>>
>>>>
>>>> Ehm, not really. It's a DLL version conflict arousing with WUA 3.0
>>>> (which version so ever) installed and executing a "Repair installation"
>>>> of Windows XP SP2 afterwards. While I still find the following instal-
>>>> lation of WUA 3.0 with paramenter /wuforce easier and more targeting
>>>> (since every machine now needs to download and install WUA 3.0 to get
>>>> Auto/Windows Update to work anyway), you can for sure try to reregister
>>>> some DLLs and let WUA 3.0 redownload afterwards automatically.
>>>>
>>>> I'm pretty sure about that this problem doesn't target us any longer
>>>> when SP3 for Windows XP will be released sometime next year.
>>>>
>>>> Bye,
>>>> Freudi
>
>