Build 1764 works as well, thanks.

Can you also confirm that build 1763 works ok for you?

Thanks.

-Rusty

Norton quarantined the winamp.exe from build 1762 at the time I wrote my last post.
But now I've installed it again and can confirm that Norton has updated the definitions in the meantime and 1762 works.

It seems that Norton just update the signature, so build 1762 might work for you.

Regardless, we've also created a new build that uses the Winamp.exe file from MMW build 1751. Can you confirm that it solves the problem for you?
http://www.mediamonkey.com/sw/MediaMonk ... 9.1762.exe

Thanks.

-Rusty

Thanks for feedback, re-opened:
http://www.ventismedia.com/mantis/view. ... 797#c42075

Was the WinAmp.exe from 4.1.8.1751 ok? I used that one as permanent for the fix to apply.

I recommend to release the new version only if Symantec updates the definitions. They haven't done so yet.
Alternatively the old Winamp.exe could be used for the release.

Usually there is no feedback they just update definitions for false positives.

Alternatively you could give full permissions to users for the MM program folder (e.g. "c:\Program Files (x86)\MediaMonkey").
I prefer this, because I don't like a separate root folder.
For a more or less clean install, you would have to first rename the existing folder, create the program folder manually, set the permissions and then install MM portable there.
Of course it's easier and a little bit cleaner, if you let MM install the portable version to e.g. C:\MediaMonkey.

BTW, any feedback from Symantec yet?

PDoyle wrote:Don't think I should use 1758 Portable, as in the past installing portable in same folder as a regular install caused problems. Correct?

Yes, Portable uses install folder to save settings and files so installing in regular folder will 100% make permission problems. Install portable always to Separate non protected folder like c:\MMWPortable

Also if portable works than problem is in system settings and permissions.

HINT: When You install MMW as Portable you can always copy regular MM.DB to portable folder and avoid creatin of library from Scratch

Thanks, replied via the ticked with other instructions.

1759 crashes as soon as it opens, when installed regular on Windows 8.1. I have allowed winamp.exe in Norton after it had been quarantined. I have tried installing and starting up with Norton disabled. I can send in the .elf file if that would help.

While regular installation of 1759 RC fails to open on Windows 7; PORTABLE installation has been successful. Which is what I found with 1758.

just submitted support ticket with debug log attached...
- 1758 Portable install seems to be working fine, whether NOrton 360 is enabled or disabled.
- Tried to install 1758 regular; Norton removed what it called the Suspicious.Cloud file
- INstalled 1758 regular with NOrton disabled. It still wouldn't open; asked me to create a new database, but never opened.
- 1757 regular install now will not open. 1757 was opening fine last week. This week, it won't open.

Don't think I should use 1758 Portable, as in the past installing portable in same folder as a regular install caused problems. Correct?

thanks

BTW MMW Winamp.exe was called number of things over the years https://www.google.com/search?q=Mediamo ... 8&oe=utf-8# in all cases it was proven FALSE positive. Actualy I often use that file as Antivirus App Quality Test for in order to ractify payed premium Deep Guessing scan feature.

Any update on this? I see here http://www.mediamonkey.com/forum/viewto ... 24#p413990 that 1757 also does not work, so it looks unrelated to the build 1758 but rather to a Norton security update ? If you disable Norton, does it work then?

Could you open eSupport ticked and attach debug log? Item 4B here: http://www.mediamonkey.com/forum/viewto ... ?f=6&t=341

Thanks!