Thank-you sir...
Meaning of start type:
Start REG_DWORD Start constant
Specifies the starting values for the service as follows:
START TYPE LOADER MEANING
0x0 Kernel Represents a part of the
(Boot) driver stack for the boot
(startup) volume and must
therefore be loaded by the
Boot Loader.
0x1 I/O Represents a driver to be loaded
(System) subsystem at Kernel initialization.
0x2 Service To be loaded or started
(Auto load) Control automatically for all startups,
Manager regardless of service type.
0x3 Service Available, regardless of type,
(Load on Control but will not be started until
demand) Manager the user starts it (for example,
by using the Devices icon in
Control Panel).
0x4 Service NOT TO BE STARTED UNDER ANY
(disabled) Control CONDITIONS.
Manager
Thus by changing the setting from 2 to 3, the startup of the service will change from "Auto Load" to "Demand".
Okay, thanks truffle...
I just now changed that start type value from 2 to 3 (as you described above) and, bang, the issue is not displayed in the Event Viewer any longer.
Thanks much...
Message was edited by: inirons on 2/28/14 9:06:45 AM PSTI'm new here but for a few weeks now I've noted the problem in my event viewer late January 2014 and wanted to overlook but other things seem to be going on. So I'm back here
Like janvaneerden I ran virtual and it reported no problems BUT
My tune up utility has pointed out
"Windows reports that the "McAfee Inc. mfeapfk" device is not working properly"
According to what I've read in this post so far - and as polian pointed out - is the fix just disabling it or is this a real fix.
Basically, how do I really fix this or are well all on hold waiting on McAfee to do an update?
tks
p.s. I should note Windows Tune Up states these could be the results of the issue. Since I'm experiencing #3 and #4 now - I came back to "mfeapfk" issue instead of ignoring it
What are the effects of this problem?This can have the following consequences:
Don't want to appear negative but I'm almost ready to agree with wfmc.
Really thinking about what to install when all of my TP licenses expire in a few months. I guess if McAfee can't get this resolved by then I'll at least have to look around.
Oh, and the reason I'm back here is...
All four of my Win 7 PCs are now doing this again, both Home Premium and Pro. Went into one EV on one PC, and that led to another...
I checked the registry and the path is still what we changed it to "C:/..." but they must of changed the Start value to its previous setting as it's back to "2". Don't know when.
I queried Task Manager and there is no mfeapfk anywhere in the Services tab. Not sure if it should be listed there or not but it seems like it should since it's a service that's supposed to be starting?
Anyways, still not fixed and they actually broke my temp reg fix.
As to some comments about "if it seems to be working then don't worry about it"... How do you know if it's broken or working? Seems to me if you have an error then that's a pretty good indicator that something is up. Who knows what is unprotected if that service doesn't start or run. Anyone know?
Just my 3.5 cents. Inflation.
P.S. Just modded the reg again back to the "3" Start setting and the error is gone in EV. However, I also checked Task Manager Services and I still don't see it in there. SO... only McAfee knows how this thing works. I'm back to if an error is generated then I will investigate until they tell me why it doesn't matter that this error is being displayed in EV.
Cheers
Message was edited by: no_1_is_secure on 2/27/14 11:43:33 PM CSTThe problem seems to be back.
Today I received an update. McAfee Total Protection Security Center is now (in germany) 12.8, build 934.
The installation turns the key back from 3 to 2...
Well maybe rechange it seems the fix not there yet.
"Really thinking about what to install when all of my TP licenses expire in a few months".
So do I.
Few weeks ago I reported this problem at the Dutch help desk of McAfee. They tried to investigate by Remote Desktop this item.
First they installed a lot of stuff (.NET updates and so on) I never use.
But no result.
Finally I received a message "You have a structural Windows problem".
Since a lot of you reported the same "service failed" I do not believe the "research" of the Dutch technician.
I wish you all a nice Spring with flowers en greetings from Holland,
Jan van Eerden.
Message was edited by: janvaneerden on 3/1/14 5:26:51 AM CSTHi janvaneerden,
Investigation is going on for this issue and a bug has been filed with McAfee. Meanwhile try the temporary fix of changing the registry value back again. Highly Appreciate your Patience..!
Regards
Hi Selvan,
I have been following the threads on this issue. I haven,t been too concerned as all seems to function just fine. Having said that...I just went to "Device Manager" and checked all of my McAfee Drivers. When "Right-Clicking" on (McAfee Inc. Mfeapfk) Properties, General details....
I recieved the following info: (This device is not present, is not working properly, or does not have all it,s drivers installed Code 24?) If I am not mistaken, this is associated with McShield.exe and the Active Protection Filters?
Should I be concerned? There is a Microsoft " Fix it " for the Code (24). Should I attempt to run it, or leave well enough alone? And wait for the McAfee fix? MVT reports no problems ?
I might add that on all the other McAfee drivers I clicked on, stated: This device is working properly.
Thank you in advance,
CatDaddy (CD)
Message was edited by: catdaddy on 3/1/14 9:07:25 AM CSTNew 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: