G
Guest
A client's PC had a problem with Windows Installer, which mangled Norton AV
and other programs, so I reformatted and re-installed Windows XP Pro.
I re-installed the applications, such as Office 2003 and McAfee AV (instead
of Norton).
Now, a week later, the Windows Installer problem appears again. I performed
a system restore to the last point in time when I know it was working, but
this did not resolve the issue.
The error is similar to the KB 315346, except I don't get the numeric code
that the KB article references. I have tried the steps in this article
(although it is difficult, because the 'start-search' function is not
working---this happened previous to the reinstall also).
This computer is joined to a Windows 2003 domain, and the user is a member
of local admins. The problem occurs when logged in as administrator also.
I do not want to tell the client that I need to re-install again. I need to
determine the root cause regardless, as it will likely re-appear.
I'm wondering if it could be a domain policy issue......? I tried running
RSoP snap-in in logging mode on the server, but it gave an error connecting
to the PC in question.
What is my next move?
and other programs, so I reformatted and re-installed Windows XP Pro.
I re-installed the applications, such as Office 2003 and McAfee AV (instead
of Norton).
Now, a week later, the Windows Installer problem appears again. I performed
a system restore to the last point in time when I know it was working, but
this did not resolve the issue.
The error is similar to the KB 315346, except I don't get the numeric code
that the KB article references. I have tried the steps in this article
(although it is difficult, because the 'start-search' function is not
working---this happened previous to the reinstall also).
This computer is joined to a Windows 2003 domain, and the user is a member
of local admins. The problem occurs when logged in as administrator also.
I do not want to tell the client that I need to re-install again. I need to
determine the root cause regardless, as it will likely re-appear.
I'm wondering if it could be a domain policy issue......? I tried running
RSoP snap-in in logging mode on the server, but it gave an error connecting
to the PC in question.
What is my next move?