I didn't think I was fully removing IE. When I've done this in the past with windows XP I used nLite. That program was able to remove IE browser, but leave the underpinnings intact. From what was said above this is the way it is supposed to work here too. Evidently not. I usually leave IE out and so I was following what I have done before. There was never a problem until now. I've built three systems including my own that I'm using to type this message and only one has an issue. Yeah, a couple of days is due to my not driving and my friend having to pick me up and have the time to get together. It's also about scheduling her's and mine. I'm also busy so we try to schedule things so it's when she is going to be busy and not need the computer. My friend is almost 80, but she is very busy just the same and I am too several days per week. The other thing that takes time is backing up the data. She has 35GB of pictures alone that I backed up to DVDs. The write time after several failures was 30 minutes per disc. Since some of these are very important to her I've taken time to be redundant. I backed up to DVDs AND cloned the old XP install to a second HDD so I could copy the files from that. I was lucky I did. IMGBurn skipped dozens of 'hidden' files from Picasa. I had thought they were just duplicated temp files so I let it do so to save space, but found out later they are not. If I had not backed up to both DVD and HDD as well about 200 pictures would have been wiped out. On that note. I'm going to start over with her computer this weekend. She is going to be busy with family and will not have time to mess with her computer. I'll backup anything that has changed in her FTM files and pictures to a flash drive and start from scratch. The Family Tree Maker 2006 is also not working right since we did some updates on it. There were two patches and the second one had almost the exact same symptom as the FTM2014 where it didn't log in correctly though the FTM program to Ancestry.com. This is either a further symptom of the IE issue I'm suspecting or FTM2014 imports more than just the data files of FTM2006 and therefore caused the issue to parallel to both versions. I suspect that in spite of the Ancestry.com tech's assurances to the contrary FTM2014 uses common DLLs libraries with FTM2006 that have become mixed up or otherwise corrupted in the original update of FTM2006 then new installation of FTM2014. Removing all and re-installing is going to be the only way to be sure this is sorted out right. She has decided to return for refund FTM2014 since she is unsatisfied with the changed interface. There are evidently a lot of such customers since they actually have a process to get a refund by signing a form promising to destroy all copies of FTM2014 under penalty of perjury.