Might be how you uninstalled it try reinstalling and note post 24 for what to do.
Coldfusion will pass this on seems now to have fixed nearly 10 users so far.Message was edited by: Peacekeeper on 30/01/12 6:43:32 AM
Can you please let me know if you have a software that says – Alcohol 120% installed on your PC ? If not, please let know your concurrence on a remote session so that we could collect logs
I uninstalled latest version of alcohol and no more errors here too. mchost and sync errors are all gone.
When I reinstalled alcohol 120 I get the mchost error again. Confirmed that alcohol is colliding with the latest mcafee update since december 2011. Have been using this alcohol version for more than 8 months without problem until dec 2011 mcafee update.
All in McAfee, not wishing to spoil your party here, but after an update from your program i would need to uninstall another program in order to have your program (for which i pay yearly) work correctly. Not want to nit pick, but, should McAfee not try to fix the problem. Ie before your update it was no problem having Alcohol 120% installed, after your update it was, generally sounds like a problem with your program.
Now i agree as a quick solution to get the annoying pop up messages to disappear uninstall the other program but being fair, it should be McAfee that finds a work around, not by removing a third party software.
Can you imagine if it was Windows version xxxx that was the cause of the error, would you have suggested the same, remove it to make your program work.
Disappointing to say the least and maybe McAfee will realise this when us users no longer buy your software.
Also considiring that Alcohol 120% is not an illegal program, does any of their developers consider taking action against your product as advising customers not to use it or remove it can not be quite legal?
The alcohol 120% issue is now fixed by a simple renaming of its start menu folder and shortcuts.
2 minute job to fix it. No need to remove itMessage was edited by: Peacekeeper on 29/02/12 6:33:09 AM
I am amazed by the time it took for McAfee to post a response to this that actually fixes this. Can i ask why no one else at McAfee could have taken the time to respond with the solution even tho it was reported as soon as the new year started. The solution, just in case anyone missed it is as follows:
I guess it works but like many would have done before, most of us have removed Alcohol 120%
Now to go a little more indepth, if indeed this is the problem, special character in program structure that causes failures with mchost and mcsync, does this mean that anyone could mess around with any other persons machine by creating a simple batch file (.bat) extension, that runs on startup of the machine renaming program folders by adding '%' or a whole other host of characters, to create this problem with McAfee related programs.
Surely this can not be right, put simple it would mean that McAfee can only be used by English speaking machines and any other languages like German, French, Spanish, etc... would have an issue as the use of special characters is quite common in those languages. Also if this is not the case, should McAfee not advise which other special characters should be excluded, so us meaningless coding monkeys, could avoid spamming your message boards trying to get a fix for something that was rather simple to solve and avoid.
Also why did it only become a problem after an update from McAfee and could a simple message to the user after the update not have prevented the miscommunication, afterall McAfee does scan the users machine on a regular basis?
Honestly i came to that logic when the problem initially started, but, as i thought something this simple could not be the issue, i completely disregarded it.
Having some input from McAfee on this issue would be nice, as i can see a whole lot of issues if a malicious person released the aforementioned batch process in the wild.
Maybe some of the people on this board should be offered a job at McAfee... (hint, hint)
Actually I reported it as soon as I realised the issue was an issue. A developer sorted it out but the solution needed external testing before they could release the fix. The testing was done and a FAQ TS101320 prepared and approved . It was out a week or so before I linked to it but I did say that there was a fix (more info following) 10 days ago but missed adding that comment to this thread.
I have tested making shortcuts with % signs in them and no problems. It must be a unique combination with alcohol 120% I will ask.
I am here again. No real solution yet, but the error seems to be rarer then previously.
I have many files with the % character. If this is the real problem, I will not have any long term solution than change McAfee program to an other software... Some file and link can be renamed, its OK. But eg. some more difficult program with % files and folders:
-Skype makes file with % in the Temporary Internet Files folder. It can appear any time (or at least I use Skype). Impossible to look and delete it after all conversation. By the way Internet Explorer saves every special character (or space etc.) with % in file names (%20, %7E, %2F...). So if you save a web page (.htm, .html, .mht etc.) or in the Temporary Internet Files it could be very common.
-an older Adobe Photoshop plugin also uses files with names containing % character,
-or the most diffucult: the Borland Developer Studio also uses it frequently. I do not prefer to rename dozens of files of third party product. I think it will not work correctly.
Previously it caused no problems. I used McAfee and the same programs together for years without problems. I think you should check the development log of the two files (mchost.exe and mcsync) about the time the error occured and carefully look after each modification step by step, line by line, to find which cause the problem with this special character (or other issue).
Have a nice day.