I loved Susan Bradley's article about MSIE 10 cautions because I had a disaster I think was related to MS pushing its pre-release to the final:
I had the former on since December, and it worked great (nevertheless, I continue to prefer Firefox). However, MS seemed to have pushed the final onto my Win7SP1, causing some bad effects: The Control Panel | Programs and features | Turn Windows features on or off DB started coming up blank. The system store was apparently corrupted. After fruitlessly trying to hack and patch my way back (because a healthy system restore point from before MSIE 10 pre-release install had been pushed off the stack), I did an in-place reinstall using Langa's procedure to bring the O/S back, without MSIE 10 (9, instead)
But, after four hours of installation, Windows Update wouldn't work, and I had to turn auto-Update and the two buttons below it off, forcibly scan for updates, which worked (found 68), then set it back to notify/confirm mode. After another two and a half hours of patching the in-place install, everything was back to normal, and the System Health Report, which had NEVER worked, also did. I didn't lose ANY settings or customizations. Seems MS' push hot-patching the pre-release of MSIE10 to the release seems to have been a problem — word of caution to pre-release adopters!
Yesterday I reasoned that MSIE 10 itself or its install wasn't the problem, but the pushed install, so since I had new SR points from the in-place pseudo-upgrade and patches as backstops, I decided to reinstall MSIE 10, which hadn't been available at microsoft.com til yesterday, did, and the store continues to work.
Though polls seem to show Chrome is now dominating the browser wars, I don't trust Google's respect for security. MSIE 10 will compete well. Opera is also a fine browser. Take your pick.
BTW: I still LOVE Corel WP Office in preference to MS Office.