I find vegas190.chm here C:\Program Files (x86)\Sony\Shared Plug-Ins\Help Files (or C:\Program Files (x86)\Vegas\Shared Plug-Ins\Help Files). For some it may be in C:\Program Files (x86)\Vegas\Shared Plug-Ins\Help Files
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Sony Creative Software\VEGAS Pro - MAGIX (This may only exist for version VP14)
6. You could also consider deleting some of the other folders in the following locations, but only if you are 100% sure they are only related to VEGAS Pro and not other VEGAS or Sony Creative software:
@EricLNZ as you know the Sony vs. Vegas folder case was discussed earlier here. Maybe this is still the reason. Has not been an issue for me, personally.
I only commented as we jump on users who through habit still think their software is Sony Vegas...
@EricLNZ ... IMO, your comment was a valid comment. Years ago when I first read the clean uninstall procedure, I thought that this can't be right - surely Sony registry entries refers back to pre-MAGIX days. But on checking the registry, it was true for VP in MAGIX days.
I think that the difference is that VP users - particularly new VP users on the forum - referring to Sony Vegas Pro some 8 years after Sony's last version release - 13 - is often a cause for concern. I'm not sure that a VP "pirate" is basing their naming convention of Sony Vegas Pro on file names deep in the bowels of Windows Program Files or the registry.
I just thought it quite hilarious that deep inside VP it was still using "Sony". Apart from "through habit" users and pirates isn't there a legal issue here with the continuing use of "Sony"?
Maybe it's been overlooked.
Former user
wrote on 2/22/2022, 5:07 PM
@EricLNZ Maybe it's some kind of ghost or left over because mine's C:\Program Files (x86)\VEGAS\Shared Plug-Ins\Help Files, I've never had a Sony version on this pc,
Just did a search on my pc & 45 items are related to Sony & Vegas, so4compound, upscale, ,, there's a few like that that still have Sony in the details,
Maybe it's some kind of ghost or left over .......
This "some kinde of ghost" will not disappear until all the code is rewritten.
We users already had to do our homework by adjusting our scripts according to the following instruction: The scripting namespace for VEGAS Pro 14 changes from “Sony” to “ScriptPortal”. In your scripts, any occurrence of items like “Sony.Vegas” or “Sony.MediaSoftware” must be changed to “ScriptPortal.Vegas” and “ScriptPortal.MediaSoftware”. We chose this namespace (“ScriptPortal”) in order to remove any company branding and thus avoid this problem in the future.
With all the Vegas Pro code, it certainly won't be that easy - but at some point, this work has to happen too.
Maybe this thread is a good impetus to put more energy into it again👍
All my Vegas160.chm through Vegas190.chm files are in the VEGAS folder. All of the other help files in that folder are for newer fx and also have chm file types. My Sony folder has help files for older fx and most of them are in the much older hlp format.
Btw, the older hlp format is no longer supported by Win10 unless you get the the old winhlp32.exe from win7 or win8 and install it correctly. This link outlines how to get it from Microsoft and do it. This github link already has the pieces extracted and includes the script I use. The process works for both Win10 and Win11. Keep in mind its not needed for recent Vegas chm help but if you use older versions of Vegas, fx, or maybe Sound Forge 7 and/or its vintage noise reduction and restoration pack, you'll definitely want it.