Ray, I've looked through your install logs and it looks like it's pitching a 1603 exception code. You might search the forums for solutions related to this error code. From the context, it appears to have something to do with the VSTA debugger-which may have been damaged by your recovery attempts or by the malware you extricated.
If worst comes to worst, you might have to do an OS reload.
Incidentally, was there a precipitous event for SolidWorks running slow, or has it always done that on your nieces machine?
I've spent days on this problem, it gets even worse. Apparently her machine has been getting slower over time. Her system is an old one (XP) about 10 years old. Theres too many issues with this thing, so I'm just going to give her some money to upgrade to a new one. I'm throwing in the towel on this one John, too many other things to do. Thank you very much for responding I truly appreciate it.
Good choice..... I suspect it wasn't a high powered machine even back in the day.
A 10 year old XP machine is like a dinosaur. Computers years are like dog years.
My niece is very happy shes getting a new computer. I'm sure you know how it is with starving students.