I like All Media Grabber -- I keep a copy installed in my XP Mode VM -- but installation is a small bit of a PITA, which is why I keep it there & not here in win7 64.
"mscomctl.ocx" is the name of the file that causes a small problem, more an inconvenience really, in this old fashioned VB app -- that Visual Basic part is why it's banished to the XP VM. Developers -- If you must use mscomctl.ocx stick it in Windows' system folder & register it there [System32 in 32 bit Windows, SysWOW64 in 64 bit], NOT in the app's program folder, where if you ever remove, or move All Media Grabber you'll just broken every other VB app that uses the file, & a good many do use that particular file. Reversing that change means dragging or copying the file from the "AllMedia Grabber" folder to the system folder & (re)registering it with Windows -- currently it seems to be the latest version, but Windows will warn you if there's already an existing copy so you can check which is newer. Registering 32 bit files isn't *too* bad -- there's all sorts of info, tips & tools on-line... I use Regdrop.exe, an older app, that only works with 32 bit files BTW, that I have on the desktop where I can just drag files from Windows' Explorer on top of it. There are several places to download a copy if you use Google.
Now to the reason I tend to banish VB apps in the 1st place... As I said I already have an older copy of All Media Grabber in my XP Mode VM, which meant I'd have to monitor the install in a win7 32 VM if I was going to monitor it. Win7 can sometimes have a small fit behind the scenes when you add a VB app like this, & in this case it showed up as roughly 150,000 registry entries recorded as being deleted. It's not as drastic as it sounds -- schema related keys can sometimes be created &/or deleted in huge numbers, but after a restart they will not show up in regedit, leading me to believe they're temporary. Regardless, I like to avoid the wear & tear on the registry if/when I can. I also suspect at least some of the effects linger in .NET, where Microsoft tries to handle VB nowadays, but realistically I've never examined each one of those 150k or so registry entries to make sure -- it's more than enough of a burden just trying to read text files that large, particularly in a VM, where that kind of volume regularly crashes my monitoring apps.
I tried BTW to see if there was an easier way of fixing the mscomctl.ocx thing, but it's not included in the VB runtime from microsoft.com, where a search on mscomctl.ocx comes up with a hotfix that doesn't include the latest version, & it doesn't work to change anything anyway in that win7 32 VM where All Media Grabber was installed.