" . "
Couldn't agree more! :)
----------
"Now check this one out.. I'm sure you'll love this one...
Key Name:
HKEY_USERS\Sandbox_NoNet\machine\software\Classes\AppID\{2580FD71-40E2-4319-8768-49EF61C0452B}
Class Name: <NO CLASS>
Last Write Time: 5/23/2013 - 4:10 AM
Value 0
Name: <NO NAME>
Type: REG_SZ
Data: SubsHelperBHO
When you search the AppID first thing that shows up in google is a virus report."
FWIW... Not doubting your results, I don't show that key(s) for the trial or GOTD versions, recording install, registration &/or activation, & 1st run of Sounfrost in a very minimal XP Mode VM. I do show:
[HKEY_CLASSES_ROOT\AppID\SubsHelperBHO.DLL]
"AppID"="{2580FD71-40E2-4319-8768-49EF61C0452B}"
[HKEY_CLASSES_ROOT\AppID\{2580FD71-40E2-4319-8768-49EF61C0452B}]
As far as "2580FD71-40E2-4319-8768-49EF61C0452B" [w/out quotes], Google comes up with 3 hits for me, ALL McAfee. If a few more brands came up I'd be concerned, or if one of the market leaders in AV software came up likewise I'd be more worried. *Just* on the basis of the McAfee reports [& the fact there were no others] I'd personally treat it as a 25 or 30% shot it's mal-ware related, & then it could be mal-ware using a legitimate ID. The fact that Mcafee scans everything clean, as does the SE beta reduces those odds, that that AppID = malware, to very close to zero IMHO.
"I suggest for anyone who plans on properly removing this off your pc to get a reg file done on a similar os as yours to manualy clean the keys out I can give a list but my os is Windows XP SP3 English."
Again purely FWIW, Vista/7/8 tend to add more irrelevant keys, & the 64 bit versions also add a couple of 32 bit registry sections, but the registry entries an app adds & uses are for the most part [overwhelmingly actually] identical to what's added/used in XP -- IMO that's why XP's favored as a test/monitoring environ when you're say, monitoring an app to make it portable. OTOH there's a couple of weaknesses with taking a sandbox approach, & why I prefer not to use them for monitoring purposes -- ANY running software makes changes to Windows registry & to the hard drive, including whatever sandbox app, & the sandbox app itself can change things, e.g. the perhaps altered key you recorded.
As far as the actual keys added, search individually in regedit for: [note that this is a combo of trial & GOTD entries so there will be some you don't find unless you installed both]
Soundfrost, d997c836-ff82-4519-b459-1482ba942a4f, 2580FD71-40E2-4319-8768-49EF61C0452B, A1D74F49-2C1A-400B-A3BA-22147E24B208, 7ACA7342-3323-4B4A-A4E2-1D1F140A71DE, IgnoreFrameApprovalCheck, MyPrintScreen, 081524f7-7ed8-43ff-b01e-915c410a9cbe
As noted McAfee blocked the connection to 217.23.8.104 -- I was simply too lazy to restore my VM, turn on Timefreeze, un-block the site, fire up the VM, & then start over just to see what happened when it connected... at the time I wasn't expecting any issues & was just recording info for my own interest/use. With the group policy changes I'd think it entirely possible something could be downloaded added without notice. Because I'd already nixed the app for my own use -- ONLY because I don't like audio processing with ffmpeg -- I didn't try monitoring changes to the VM while actually using Soundfrost to find & get whatever audio files, so I can't say more about if the browser helpers include naughty code or not.