backup .cmd file blocked????

[Kernel Krumpet]

Hi - again.

I'm the person that suffered - a lot of - mediocre embarrassment at my Microsoft Windows 7 seminars and community talks whereby it was not possible to demonstrate the Windows 7 Backup process due to Malwarebytes Software. 'Nuff said!

And now, I have a two line backup file - named c:\bpbak.cmd - that contains these simple lines in below:

xcopy c:\users\joe\documents\*.* i:\test\docs\*.* /c /d /e /y /h

xcopy e:\*.* i:\test\e_drive\*.* /c /d /e /y /h

In other words - back up all my stuff to a USB drive folder named i:\test - a no-brainer!

and, now, months later here we go again:

I'm not caring that it gives me the option to Yes/No/Maybe - bogus! What happens to an 11:00pm automated batch file after the polyester suits and ties go home at 4:59:59 ???

This little conundrum I hope is not the reason I've now spent 5 hours and additional hardware purchases wasting my time tracking down the reason for the - best backup script in the world for small businesses and home users - failing on a clients PC!

I'm gonna rename it to bpbak.bat now and see what happens. (would you like to know the result? or do you already?)

If I was a typical American I would - very quickly - sacrifice integrity and ethics (not taught or comprehended in USA) for easy money and use another antimalware program. I am proud not to be American, I live in America and gosh darn it I want this program to get out of "bogus" status and work. Why? because it is the best out there. Period! but regrettably, costs me embarrassment and irrecoverable billable time.. not to mention the affiliate and lack-of-a-contact-to-buy-from disaster.

Get on it, buck up and make the millions you deserve.

I'm not sure if I have a question here but I sure have an attitude about it - apparently - after 25 years in the tech. support business!

You're welcome for the precise documented objective analysis & feedback.

[AdvancedSetup]

There are a couple issues. With 25 years in the business then if you go back to the old days one will remember that you kept all OS files and your own files apart from each other as best you could. ie. you didn't drop your own files into C:\DOS you created your own folder and added it's location to the path, you didn't put your utils or batch files in the root. We sort of take the same stance here in that you cannot easily determine if a batch or cmd file is being used for good or bad purposes as the root of any volume is not a typical storage location for executable files but is a heavily used practice by malware programs. I would recommend creating a folder for such utility operations even with XP/Vista/Win7 and adding to the path if needed which will prevent this type of detection.

The ways and means by which malware attempts to bypass and trick security programs is never ending and most security programs have become more and more strict on how programs operate and get flagged for certain behavior. Currently if the protection module flagged it you can temporarily ignore it but to ignore it all the time without moving the file as recommended then you'll need to either do a Quick Scan or Full Scan to detect it and then add it to the ignore list and we'll no longer detect it. In a future version we will add a permanent ignore feature to the protection module as well but currently it's not available.

You can report false positives here: http://forums.malwarebytes.org/index.php?showtopic=3228

Thank you

[Kernel Krumpet]

We sort of take the same stance here in that you cannot easily determine if a batch or cmd file is being used for good or bad purposes as the root of any volume is not a typical storage location for executable files but is a heavily used practice by malware programs. I would recommend creating a folder for such utility operations even with XP/Vista/Win7 and adding to the path if needed which will prevent this type of detection.

Thank you

Thank you, as always, for your timely and accurate response. An increasingly rare quality these days in the technical support business.

I will then, following your recommendations, create various batch and cmd files in various system and user created folders and re-test... I will skip the "False Positive" link tho'. My programming skills hardly warrant such status!

Also, I personally find the AppData folder to be the most heavily used..... I yaint never found nuthin in the root... Thanks for the head's up.

Thank you as well for your - unlike my own - balanced response...

[Kernel Krumpet]

... a two line backup file - named c:\bpbak.cmd - that contains the below:...

xcopy c:\users\joe\documents\*.* i:\test\docs\*.* /c /d /e /y /h

xcopy e:\*.* i:\test\e_drive\*.* /c /d /e /y /h

[Kernel Krumpet]

I would recommend creating a folder for such utility operations even with XP/Vista/Win7 and adding to the path if needed which will prevent this type of detection.

Thanks for the recommendation AdvancedSetup and, in the process, for making me a better tech. support person and for increasing my value to the computer community at large.

Appreciated muchly..