Error installing .NET 3.5 sp1 on WinXP

Following error installing .NET 3.5 sp1 on WinXP sp3, not in a domain:    I have administrator privileges.

EventType : visualstudio8setup     P1 : 35101    
P2 : 3.5.30729.01_orcas_x86_net     P3 : pr     P4 : inst     P5 : f    
P6 : gencomp211     P7 : baseret_failure     P8 : -     P9 : 1603     P10 : -

Error log:
[04/07/11,14:19:21] XPSEPSC Installer: [2] Setup Failed on component XPSEPSC Installer
[04/07/11,14:19:22] WapUI: [2] DepCheck indicates XPSEPSC Installer is not installed.

Have repeatedly cleaned up with Stebner's cleanup tool and reinstalled 1.0, 1.1, 2.0 and 3.0 which all go in OK, plus patches.

Thank you for any suggestions. - easyb
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

easybAuthor Commented:
Thanks.  Cleaned, re-downloaded .Net Framework 3.5 sp1 and installed yet again with the
same results.  
could it be that your installer is corrupted?
10 Tips to Protect Your Business from Ransomware

Did you know that ransomware is the most widespread, destructive malware in the world today? It accounts for 39% of all security breaches, with ransomware gangsters projected to make $11.5B in profits from online extortion by 2019.

easybAuthor Commented:
Yes.  But reinstalling XPSEPSC did no good.  My solution was to replace
the boot drive with a stable clone from a similar installation.  You can only whip
a tired horse so long.   Had to reconfigure or course but back in production now.
The question may come up again as XP is still very much out there but I must
leave it to someone else to cope with.  The question is withdrawn.

Thanks for looking into it for me. - easyb

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
easybAuthor Commented:
Please withdraw the question.  Thanks - easyb
why not pass on some points for the effort. I know its not the answers you wanted but it would be kind to do.
easybAuthor Commented:
The solution was to rebuild the system, working from a clone in
good condition which was easier than a naked reinstall.

Thanks for the effort.  
sorry for your troubles, but system rebuilds are sometimes the best and only options.
easybAuthor Commented:
Rebuilding a system is never easy.   The trick is to recognize when to proceed with the "nuclear" option before you reach the point of diminishing returns looking for a fix.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Legacy OS

From novice to tech pro — start learning today.