Theo
Mon Jun 11 08:23:40 CDT 2007
And another thought: Try logging as Administrator and apply
SP2 from there.
Theo wrote:
> Another thought. Slipstream the SP2 into Win x64 and then do a Repair
> install, probably best booting from CD. This would put your system up
> to the SP2 level of about December 2006.
>
>
> Theo wrote:
>> Did you call the Microsoft Support about this?
>>
>> Since you're trying to install SP2, do a Repair install of Win x64 and
>> then try applying SP2. The Repair install can be initiated while in
>> Win x64, or it can be done from the setup. If you boot and go into
>> the setup, the Repair you want is after you press F8 to accept the
>> EULA, not the first one that comes up shortly after setup starts.
>>
>> Do a Repair install will put your system back to the original
>> configuration without any updates, but SP2 will bring your system
>> up-to-date most of the way.
>>
>>
>> Chris B wrote:
>>> Thanks for the advice, but apparently, buying OEM software is easier
>>> than getting support for it - they won't help me.
>>>
>>> If anyone else has any ideas, they would be greatly appreciated.
>>> perhaps you could think of something I might be doing wrong.
>>>
>>> Thanks
>>>
>>> Chris B
>>>
>>> "Charlie Russel - MVP" wrote:
>>>
>>>> Service Packs are considered security updates and are a free support
>>>> call. I'd suggest that might be your best avenue of resolution.
>>>>
>>>> --
>>>> Charlie.
>>>>
http://msmvps.com/xperts64
>>>>
http://mvp.support.microsoft.com/profile/charlie.russel
>>>>
>>>>
>>>> "Chris B" <Chris B@discussions.microsoft.com> wrote in message
>>>> news:95018B85-9290-4926-809D-516F66F3F095@microsoft.com...
>>>>> Whenever I try to install the x64 pro SP2 update, I receive an
>>>>> "Access is
>>>>> denied" message, and everything has to be uninstalled. The problem
>>>>> I am
>>>>> having is described in this article:
>>>>>
http://support.microsoft.com/kb/873148
>>>>> However I am having problems with the verbose logging of the setup,
>>>>> described here:
>>>>>
http://support.microsoft.com/kb/906485
>>>>> Whenever I set the LogLevel entry to 0000ffff as instructed, and I
>>>>> have
>>>>> tried this on several occassions, it resets itsself during the SP2
>>>>> setup and
>>>>> I am none the wiser as to which registry entry is causing the problem.
>>>>> Also the setupapi.log file doesn't increase in size at all after
>>>>> applying
>>>>> the registry change, and no further information is displayed to when
>>>>> LogLevels was set to 0.
>>>>> I'm really struggling with this one, and I've follwed the
>>>>> instructions fully.
>>>>> Any help or suggestions would be much appreciated,
>>>>> Thanks
>>>>> Chris B
>>>>