My Versions are below - they match those in your inquiry...
Release Name: 14.0.R11
Last Update: 1/8/2017
McAfee QuickClean and Shredder
Last update: 12/26/2016
Thank you also for your invaluable input. It helps immensely in Isolating the issue. Especially since now it seems that it is presenting itself in both the Most (Current) Version/Build...regardless if it is provided from a 'Third Party'/or McAfee itself.
Please know that I will inform/update everyone on what the Senior Level Engineers have to say, following our Conference Call on Monday 1/9/2017.
Again thanks to everyone for your input,
One last question...It may be that a Technician/Engineer may be required to 'Remote In' and compile some logs in a effort to help resolve this issue. Would all that is effected by this, be willing to allow such. No personal information will be gathered, as I can sincerely attest to.
Unfortunately there's so much going on at the moment I doubt I'd be able to find time for remote access. Hopefully things might settle down but I can't be sure. Also wanted to add my AffId is 105 and my Build Versions are identical to the ones included in your previous post.
Yes It is directly from McAfee
Last Update: 1/6/2017
My system is setup to not allow "Remote In" for security reasons. I would rather not go un-doing everything. In there any reason I could not download the app so I could gather the logs.
Understandably most people are cautious of 'Remote In' connections, even from know sources, its what the we're told to control by the likes of McAfee all of the time.
Although there are perhaps only a handful of people within this forum mentioning the issue, there will undoubtedly be 1000's more out there with the issue, even if they don't look in Process Explorer so won't know it ... or perhaps they reboot their machine everyday etc ... so surely McAfee labs must have a least 1 machine with this same leak ??
Why does it need a Forum Moderator such as catdaddy (your work and connections within McAfee are invaluable, mind), to have to escalate the problem, why hasn't McAfee informed users of the issue and affected a fix yet themselves ?
There's just no way that Mondays conference call aught to be the first they know of the issue, this has been happening since the last update around 16th December (for me anyhow)
Ok, evening rant over ... I'll be interested in their response and speed to fix the issue after the call
Ummmm, something's strange here ...
I've go Access Protection 'ON' ... but had the QcShm.exe file changed to old, and that's been like that for a few days now, and no additional entries have been generated in Process Explorer,
yet just checking now, and there were 11 entries of QcShm.exe in Process Explorer ??
When I check in folder, C:\Program Files\McAfee\MQS my QcShm.exe.old is still there, but today it has created a fresh new file of QcShm.exe in addition !!
Clearly, either McAfee software is trying to protect itself (or rebuild itself automatically) or McAfee have sent an update to ensure the file is always true ???
Ummmm, suspicious activity me thinks
Actually if you look at the beginning of this thread, you will see that Selvan, who works for Mcafee, has seen this issue on his lab machine. Thus McaFee hopefully knows the root cause by now.
New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.
Thousands of customers use the McAfee Community for peer-to-peer and expert product support. Enjoy these benefits with a free membership: