If windows security or any other virus/malware programs do not see it as a threat, chances are that it is part of windows task manager.
Why in the world would "buwish" write such a nonsensical response. Self Gratification? Ego Issue?.. It annoyed me so much I thought I'd look at what that script does.
Basically it's a task that checks if McAfee OEM version is running at 50 mins past midnight on the first of the month.
If it finds the McOEMmgr.exe process, it deletes the task that calls the script and also another similar task.
If it doesn't find the McOEMmgr.exe process it only deletes the task that calls this script.
Mine has never run (a/ the task still exists and b/ scheduler says so) but the other task is not present. Probably becase I uninstall all the OEM "features" as the first step of turning each new computer on.
I imagine all this just causes a reminder to register or an initial engine update on new computers where the OEM version is in use and the user may not be be savvy enough to have already sorted this.
: run tasklist.exe (a windows os component) and dump the output.
: read the output, skipping the first three lines)
: if it DOES find mcoemmgr.exe as a running process go to "BYPASS"
: which will delete the task the calls this file
: if it DOESN'T find mcoemmgr.exe as a running process
: it will delete the task McQcTask,
: it will delete the task that calls this batch file.
My suggestion, delete the cmd file, and in fact the directory it's in, and also delete one or more tasks from scheduler starting with McQcTask<anything> unless of course you are running the OEM McAfee that some "helpful" vendor has pre-installed for you.