VP17 - Weird URL and folder access

turboBB73 wrote on 8/1/2020, 10:52 PM

From VP15 when I click on: Help > Vegas Pro Home Page, it first goes to this URL which has a long string of Chinese characters in it:

(it does ultimately resolve to: https://www.vegascreativesoftware.com/us/vegas-pro/ as the final link)

I managed to copy the URL here (scanned with VirusTotal but yielded no hits):

https://mediasoftwareapps.magix.com/v2/productinfo.asp?product=vegas&place=Home&version=15.0%E3%A8%80%E7%90%A0%E6%A5%A8%E2%81%B3%E6%89%AF%E6%95%AA%E7%91%A3%E6%90%A0%E6%95%AF%E6%B9%B3%E7%90%A7%E7%8C%A0%E7%81%B5%E6%BD%B0%E7%91%B2%E7%88%A0%E7%8D%A5%E6%B9%B9%E6%A1%A3%E6%BD%B2%E6%A5%AE%E6%85%BA%E6%A5%B4%E6%B9%AF%E5%8C%80%E7%89%B4%E6%85%A5%E5%91%AD%E6%85%B2%E7%8D%AE%E6%BD%A6%E6%B5%B2%E7%91%A1%E6%BD%A9%E3%A9%AE%E7%90%A0%E6%A5%A8%E2%81%B3%E6%89%AF%E6%95%AA%E7%91%A3%E6%90%A0%E6%95%AF%E6%B9%B3%E7%90%A7%E7%8C%A0%E7%81%B5%E6%BD%B0%E7%91%B2%E7%88%A0%E6%B9%A1%E6%BD%A4%E2%81%AD%E6%8D%A1%E6%95%A3%E7%8D%B3%E4%8C%80%E7%A5%B2%E7%91%B0%E4%B5%AF%E7%91%A1%E7%89%A5%E6%85%A9%E3%A9%AC%E7%90%A0%E6%A5%A8%E2%81%B3%E6%89%AF%E6%95%AA%E7%91%A3%E6%8C%A0%E6%B9%AF%E6%85%B4%E6%B9%A9%E2%81%B3%E6%B9%A9%E6%85%B6%E6%A5%AC%E2%81%A4%E6%85%B6%E7%95%AC%E7%8D%A5&build=416&lang=ENU

Also, I just upgraded to Vegas 17 and right after installation, I got a pop up form my Anti-Virus as per attached screenshot. Why does Vegas need access to this particular folder?

C:\Users\<username>\AppData\Roaming\Microsoft\Crypto\RSA

(I've blocked it for now)

Has anyone else experienced either of these?

EDIT: The only thing related I could google was this thread (but not resolved):

https://www.reddit.com/r/VegasPro/comments/hs04vn/vegas_is_trying_to_alter_a_file_in_the_microsoft/

Given Avast owns AVG - wondering if it's a false positive but would still like to understand the reason for Vegas utilizing that particular folder.

Thx!

Comments

turboBB73 wrote on 8/22/2020, 12:30 PM

As a followup I just tried the VP18 Edit Trial version and my AV kicked in warning that mxdonwloadmanager.exe was again trying to update files in that protected folder. Does anyone have any thoughts on this?

EDIT: I didn't get screenshot of the 1st message but here's a second after installation completed: