For better attention I have moved this from Home/SiteAdvisor to Business/SiteAdvisor Enterprise.
From my own experience with the home product I will offer a suggestion that makes most things work better with IE10, go into IE10/Tools/Compatibility View Settings and ensure that all sites are displayed in Compatibility View.
In case that doesn't help, hopefully someone from the Enterprise side of things will be able to do so.
Hi Marc, IE 10 in Windows 7 is currently not supported by SAE 3.5 only in Windows 8. But even in windows 8 we are facing issues with IE 10.
How could it be that a Major Product like the SiteAdvisor is not supported on the most used constalation world wide? Is that a Joke ? Hmm I dont think so..
It make me a bit angry that McAfee is so unprofessional that they are loosing the look for stability. Lets remember IE10 comes out with automatic Update from
Microsoft. That means over 70% of all users world wide that has Win7 has IE10 too.
..looks to me like mcafee Siteadvisor is at least more a nighmare then a soulution.
There is a fix for the Win 7 & IE10 script issue:
Simply install the hot fix HF788673 released Feb 2013. This hotfix was released to correct the problem with IE10. (Win7 & Win8)
We're running Win7, 64bit, Epo 4.6 and SAE 3.5 SP1. As soon as users upgraded to IE10 we got the pop-up script error. The hotfix corrected the problem.
As per KB51244 - Supported environments for SiteAdvisor Enterprise,
Internet Explorer 10 is currently only supported on Windows 8. McAfee aims to add support for Windows 7 in Q3 2013, after the release of SAE 3.5 Patch 2.
Also as per the HF788673 Release Notes, Hot fix for IE10 Script Error in Windows 8.
· Issue: Script errors pop up when McAfee SiteAdvisor Enterprise Menu items are accessed on
Microsoft Windows 8 with Internet Explorer 10, which may result in loss of functionality of SiteAdvisor
Resolution: After installing this hotfix, script errors do not appear and McAfee SiteAdvisor Enterprise
continues to function properly on Microsoft Windows 8 having Internet Explorer 10.
Reference ID: 788673
While McAfee doesn’t currently support IE10 & Win7, the hot fix HF788673 does correct the script issue.
Perhaps McAfee is unaware of how much of an issue this is causing end-users. Every time IE is opened, the user receives the script error. This also happens when opening a new tab in IE as well as when there is a pop-up from IE.
We’ve deployed the hotfix in our environment and it has corrected the problem and does not appear to have compromised SAE.
I had this problem with IE 10 on Windows 8 and was working directly with a developer at McAfee who gave me an unreleased beta hotfix until the official hotfix was released. Several weeks later Microsoft decided to add IE 10 as an important update for Windows 7. The next morning my phone was ringing off the hook from end users reporting the script error message. After speaking with McAfee they told me that IE10 in Windows 7 was not supported, but gave me a hotfix that at least got rid of the error message and made IE 10 usable. With the hotfix installed if you try to click on the About SAE link it will throw the script error message again.
My environment is as follows:
ePO v4.6.4 build 202 running on Windows Server 2008 32-bit.
McAfee Agent 220.127.116.1122
McAfee VirusScan Enterprise + AntiSpyware Enterprise 18.104.22.1688
SAE on Windows 7 + 8 shows up as 22.214.171.1244 hotfix 788673 in ePO but from the add-on drop down it is 126.96.36.1995.
It is now June 2013 and IE 10 for Windows 8 has been RTW since October 2012, and beta since long before that. I'm not sure when IE 10 first went beta for Windows 7 but I'm sure it was long before it went RTW. It is completely unacceptable that a security software company such as McAfee does not support RTW releases of software. Especially software that is used by so many people worldwide.
Personally, I hate McAfee, I spend a good portion of my time at work removing malware that their product is simply incapable of detecting. I once had a McAfee representative tell me this is because McAfee chooses to err on the side of caution when deciding what to let through and what to block, choosing to be less agressive than other AV companies such as Norton, Kaspersky, or Sophos. What good is their product then if it's not blocking the bad stuff, isn't that what their product is for? If it was up to me I'd drop McAfee altogether and go with Kaspersky of Sophos, but my boss tends to be retarded at times and thinks McAfee is the bees knees.
How can customers like me expect an AV company to stay on top of all the malicious software out in the wild when they can't even make their product compatible with publicly released software.
Also, that developer I was working with told me that SAE only works hlafway with IE 10 in Windows 8. SAE works with the desktop version of IE 10, but since Microsoft removed the ability for add-ons in the Windows 8 App version, SAE does not work in it. So if your end users are using Windows 8 and you haven't removed access to the Windows 8 App version of IE 10 they are working completely unprotected.
Like and spot on!
My frustration is this: McAfee is acting like IE 10 was some big surprise – that it had no idea that Windows 8 or IE10 was coming out; and it’s not just Site Advisor, it was HIPS and Virus Scan as well – how long did it take for HIPS 8.0 p3 to come out? I know I've been told many times that McAfee works with Microsoft, and I'm sure someone at McAfee read the news about Windows 8 and IE10. Did they not think anyone would want it? Or thtat it would be perfectly acceptable to wait so long to update their products.
It doesn’t matter what we say on here, McAfee isn’t listening anyway….