Prev: Is there a PSR (Problem Steps Recorder) for Windows XP?
Next: Scanning website files on the fly
From: PA Bear [MS MVP] on 1 Mar 2010 12:59
Resolutions for both SP3 issues were available within a few weeks of the
release of SP3 and well before SP3 was released to Automatic Updates.

Furthermore, MS was offering no-charge support for SP3 installation and
post-installation issues from 14 April 2008 thru May 2009.

PS: The "cutoff date" for WinXP SP2 is 10 Jul-10. 13 Apr-10 is the "cutoff
date" for Vista Gold/RTM. <wink>


powerwalk wrote:
<snip>
> Pa Bear--early in the release of this Service Pack there were a few
> glitches--one of my computers had the AMD chip that was problematic, two
> of
> the computers had Realtek audio drivers for which there was no update and
> SP3 caused loss of sound for many, and some lost their networking.
>
> So, in answer to your question: "Why did I wait two years?" I subscribe to
> the adage, if it ain't broke, don't fix it. The April cutoff date for
> additional critical updates from Microsoft forced me to attempt the
> installation.
>
> "powerwalk" wrote:
>> After installing SP3 on my three computers, two desktops, 2002 XP Home
>> and
>> 2007 XP Pro, and a 2008 laptop XP Pro, I notice the Event Viewers show
>> under the heading Application, the Warnings I've listed below. After
>> checking the Event ID site, I found there is no Event 5603. Are these
>> items a potential problem.
>>
>> Also, a month ago after an critical update, I've been getting a Service
>> Control Manager Error, Event 7000, The adfs service failed to start due
>> to
>> the following error:
>> The system cannot find the file specified. This under the heading
>> System, and on all three computers.
>>
>> Other than the above no other problem has surfaced after this update. Any
>> input would be appreciated.
>>
>> Event 5603
>> Source WinMgmt
>>
>> A provider, Rsop Planning Mode Provider, has been registered in the WMI
>> namespace, root\RSOP, but did not specify the HostingModel property.
>> This
>> provider will be run using the LocalSystem account. This account is
>> privileged and the provider may cause a security violation if it does not
>> correctly impersonate user requests. Ensure that provider has been
>> reviewed for security behavior and update the HostingModel property of
>> the
>> provider registration to an account with the least privileges possible
>> for
>> the required functionality.
>>
>>
>> Event 63
>> Source WinMgmt
>>
>> A provider, HiPerfCooker_v1, has been registered in the WMI namespace,
>> Root\WMI, to use the LocalSystem account. This account is privileged and
>> the provider may cause a security violation if it does not correctly
>> impersonate user requests.

First  |  Prev  | 
Pages: 1 2
Prev: Is there a PSR (Problem Steps Recorder) for Windows XP?
Next: Scanning website files on the fly