Is anyone missing the sounds for alerts running MSC in Win 7 (64)?
I noticed when running MSC that the "chime" sound for alerts/notifications are not playing when they should on my new computer running Win 7 Ultimate (64-bit).
I have checked the configuration and the box is checked to play the sounds.
However, the only time it works (as far as I can tell) is when I am notified that updates are available (I have the updater set only to notify me, but not to download or install); I get both the pop-up and the chime.
It does NOT play when an update has finished (at the time of the installation is complete), or at the end of a scheduled, clean scan, or when I do a manual update check. I get the pop-ups, but no sound.
On my other system (Vista Ult SP2 (32)), it plays for all of these.
Audio is otherwise fine on the system (Windows sounds, other applications, video and mp3 playback, streaming audio, WMP, etc), and the Win 7 audio troubleshooter found no problems.
Audio drivers are current.
Were it not for the fact that I have McAfee configured on this system IDENTICALLY to the configuration on my other desktop running the exact same software versions in a Vista Ultimate SP2 (32-bit) environment, I probably would not have noticed.
I DO know from talking to tech guys that 64-bit Win 7 *does* have "issues" playing "older" wav files.
In fact, when selecting my email notification and a few other sounds from my saved wav files on this new system, I did have to find "current" wav files that will play in the Windows OS.
It's a weird glitchy thing with 64-bit Windows 7 (Dell and MS have info/alerts about this), but none of the troubleshooting they suggest (driver updates, windows patches, etc) resolved the issue.
But, since the McAfee sound DOES play SOME of the time it's supposed to (but not ALL of the time), and since sound is otherwise totally fine on the system, it must be something in the sound files coded into McAfee Security Center that is "buggy" in 64-bit Win 7.
This is more of a peculiarity than a serious functional issue, and perhaps it has been resolved in the 2010 versions (haven't received them yet).