WSUS XP SP3 Client Installation Failure

We've recently pushed out XP SP3 to our clients. We have about 20% of systems
reporting that it has not installed.

Computers are Dell-Intels with XP Pro, SP2.

Information from the local svcpack.log file is as follows:
233.734: [dumpDownloadTask] We have all necessary files for the package to
install. Return STATUS_READY_TO_INSTALL
233.734: dumpDownloadTask returned 0xf201 (ready to install)
235.469: UnRegisterSpuninstForRecovery, failed to delete SpRecoverCmdLine
value, error 0x2
235.469: DoInstallation: Failed to unregistering spuninst.exe for recovery.
235.484: Service Pack 3 installation did not complete.
235.484: Update.exe extended error code = 0xf201

Clients are presented with the "updates are ready to install" shield in the
task bar. The updates fail to install when the client attempts to run it due
to lack of privledges (clients should not have permissions.) The shield
reappears the next day. The above error message appears in the svcpack.log
file on every system attempt to install the SP. Registry permission issue?

WSUS reports the machines as needing the updates, but not failing.

- Google has turned up similar issues, but nothing that fits our svcpack.log
error messages.
- Restarted services.
- Deleted the SoftwareDistribution folder and ran a /detectnow. That did
not work.

Further information is available upon request.

Thank you for your time.

Additional Troubleshooting steps performed:

- BITS restarted.
- All steps detailed here: http://support.microsoft.com/kb/950718
- All steps detailed here: http://support.microsoft.com/kb/949384
- Verified Admin and System permissions on HKLM, HKCU, HKCR, %windir%, and
%systemdrive%.

Other error log entries (Duplicates removed
82.406: SetupOpenInfFile in IsThirdPartyInf Failed with error 0x5
193.828: Service Pack 3 Setup encountered an error: The update.ver file is
not correct.
195.719: Failed to open c:\windows\$hf_mig$\KB912812\update\updatebr.inf

Is the update.ver file the main issue? A permissions issue?

Additional Troubleshooting step performed:

- All steps detailed here: http://support.microsoft.com/kb/949377

"Cleffer" <> wrote in message
news:FC939A05-5304-4FA9-A8A1-...

> Clients are presented with the "updates are ready to install" shield in
> the
> task bar.

Your users should IGNORE that notification, and let the AGENT install the
update at the SCHEDULED installation time.

>The updates fail to install when the client attempts to run it due
> to lack of privledges (clients should not have permissions.)

The AGENT has sufficient privileges to install the service pack.


--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)

MS WSUS Website: http://www.microsoft.com/wsus
My Websites: http://www.onsitechsolutions.com;
http://wsusinfo.onsitechsolutions.com
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin

"Cleffer" <> wrote in message
news:6A0DBE74-3322-43AF-8B45-...

> 193.828: Service Pack 3 Setup encountered an error: The update.ver file
> is
> not correct.
> 195.719: Failed to open c:\windows\$hf_mig$\KB912812\update\updatebr.inf
>
> Is the update.ver file the main issue?

Could be. Have you ever performed a repair installation on this machine?
If so, after performing the repair installation, did you verify that all
previously existing updates were reinstalled?

The likely cause here (and it has been reported in on other, as yet
unresolved, instance)...

is that the system thinks KB912812 has been installed... but it can't find
the INF file in the $hf_mig$ folder.

> A permissions issue?

Not likely.. unless you're trying to install the service pack with a user
who does not have full Admin permissions on the machine.



--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)

MS WSUS Website: http://www.microsoft.com/wsus
My Websites: http://www.onsitechsolutions.com;
http://wsusinfo.onsitechsolutions.com
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin

Cleffer wrote:

> We've recently pushed out XP SP3 to our clients. We have about 20% of systems
> reporting that it has not installed.

> 235.469: UnRegisterSpuninstForRecovery, failed to delete SpRecoverCmdLine
> value, error 0x2

Wild guess: check that the registry key HKEY_LOCAL_MACHINE\SYSTEM\Setup exists.

You could also try using Process Monitor to see if you can identify the exact
operation that is failing here.

http://technet.microsoft.com/en-us/s.../bb896645.aspx

<http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx>

> Clients are presented with the "updates are ready to install" shield in the
> task bar. The updates fail to install when the client attempts to run it due
> to lack of privledges (clients should not have permissions.)

It shouldn't make any difference; the install should run in the update agent
context anyway. Have you tried logging in as an administrator to do this? Have
you tried installing the service pack on an affected machine using the
administrative download rather than via WSUS?

Harry.

Found one of our policies forcing User and System account deny permissions on
a .sys file in the %windir%\system32 directory causing the fail. Have
successfully tested on two machines thus far.

We have yet to discover why this did not fail on all machines since it is
mandatory policy.

I'll post another update if and when more information becomes available.

Thank you for your assistance.

"Cleffer" <> wrote in message
newsC0D79D0-9B56-42DC-9F84-...
> Found one of our policies forcing User and System account deny permissions
> on
> a .sys file in the %windir%\system32 directory

OUCH!

> causing the fail.

No doubt!


--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)

MS WSUS Website: http://www.microsoft.com/wsus
My Websites: http://www.onsitechsolutions.com;
http://wsusinfo.onsitechsolutions.com
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin

Just wanted to let you guys know what the issue was.

During the backup portion of the install, SP3 was running into a sys file in
the %windir%\system32 folder that was set to explict deny permissions for the
User and System accounts. This was obviously causing the backup (and SP) to
fail. The file was set deny to comply with mandatory policy.

We're currently in Beta to install the SP with the no backup switch. It's
our only plausible work-around after many tried-and-failed ideas.

Thank you for your assistance in the matter. It is greatly appreciated.