This has kind of a nasty install for such a small, simple app, & it requires .NET 4. As monitored in a V/Box win7 32 bit VM:
The installation performed the following activity:
150 files added
64 files deleted
45 files updated
3875 registry entries added
1480 registry entries deleted
76 registry entries updatedInstalled 5/4/2014 10:44:47 AM
If anyone wants the install logs I'd be happy to post them -- they might help with finding & removing stuff like the 15 MB ,msi setup file stuck in the Windows folder. Most of the new registry entries are divided up into 3 categories -- .msi install records, .NET, & the many Direct Show [DS] files or filters added in the Common Files\ HDX4 folder. Uninstall *seems* pretty complete -- I monitored uninstall but the registry portion was unusable, so I just spot checked several CLSID keys the software added, & they were gone. [When you monitor a win7 install or uninstall, somewhat often you'll record a hundred thousand + new entries -- sometimes several hundreds of thousands -- & when that happens those records are for many (most?) practical purposes useless. And that's why BTW I prefer to monitor this stuff 1st in XP, but this was .NET 4, & that does not work well in my VM so it's not installed.]
If you have any problems with other software that you think might be attributed to MovieSaver 4, assuming you don't want to just uninstall MovieSaver 4 to see what happens, rename or move or delete [to the Recycle Bin] that HDX4 folder, or the individual files in it if you're trying to narrow it down to a single file. DO remember though that Windows may just use the new folder name or location if one of the files is in use when you rename or move it.
Briefly, when a DS file's registered with Windows, added registry entries tell Windows what that file's capable of. That information is not always accurate. When software goes to use DS to render something, relevant DS files are loaded, & it tries to assemble a sort of chain of DS files that can work together, e.g. this one to decode the video file, this one to split the audio & video, & so on. If one file doesn't work the app will try to use another combination, though the one that's just been discarded may stay loaded. If one [or more] loaded files is incompatible with one or more other loaded files, or if any of them are incompatible with the app, or if a file got loaded but the registry info on it's capabilities is a lie, software can break.