This problem has occurred three time in Feb 2013. I had it starting Feb7. It fixed itself for a while. It then started again on Feb 15. It was fixed this morning (Feb 22) when I started. I was researching at 8:30PM EST (Feb 22) when the ancestry.com web site quit responding. When the web site returned so did this problem. Apparently ancestry.com updated and reintroduced this problem. I have had this problem in WinXP, Win7, Win8, IE8(?), and IE9(?). As somebody stated, Ancestry.com hard codes the IE being used and we have no choice. I am not sure what version is being used by ancestry.com and FTM. I am using FTM 2011.