- SONY SOUND FORGE PROBLEMS DRIVERS
- SONY SOUND FORGE PROBLEMS UPDATE
- SONY SOUND FORGE PROBLEMS SOFTWARE
- SONY SOUND FORGE PROBLEMS TRIAL
- SONY SOUND FORGE PROBLEMS PLUS
Thanks Jeff, that did play a part in solving this! Before trying that I actually managed to finally delete the registry entry. Uninstall Sound Forge and clean out any installation files left behind, they may be in several locations eg Program Files (x86), Program Data, the All user and Public folders, and your own account Appdata folder, then re-install.
If after the third run you still get an error message make a note of the files that are damaged or cannot be repaired. Repeat once more if you again get error message
SONY SOUND FORGE PROBLEMS DRIVERS
If you get any error message about fles cannot be repaired or are damaged, restart the computer - not a shutdown and power up - you want Windows to reload all drivers etc, and run the sfc scan again.
SONY SOUND FORGE PROBLEMS UPDATE
That would suggest that the update has affected your account permissions in the same way that the Anniversary update change account permissions for some users, me included.Ĭheck the Windows update has installed correctly by right clicking the Windows Start button and select Command prompt(Admin) in the command dialog type sfc /scannow and press the enter key. the only change I can think of since I last performed this operation is that I've gotten the Creators Update to Win 10. Sorry for venting a bit, I'm just so sick of this (I previously spent many useless hours with the Sony support trying to get this solved, before the registry tweak was announced as a solution).
SONY SOUND FORGE PROBLEMS SOFTWARE
have Magix fixed the root cause of this, or will they? Right now I (again) have an expensive software (I've bought it as a private user) that I can't use due to a faulty registration/validation mechanism. I'm going to open a ticket in the Magix support and ask the initial question in this thread, i.e. Of course, none of us should need to bother with this at all, the software should have a stable registration/validation mechanism. And now that fix is not working (for me) anymore so I'm back to square one. I was so fed up with Sony, who spent years without coming up with any working fix or solution so I was VERY happy when the registry tweak was confirmed to be working, although it did not fix the root cause.
SONY SOUND FORGE PROBLEMS TRIAL
Thanks but I've had to do that so many times over the years to try to get rid of this problem (after having paid hundreds of $ for the software) so I'm not willing to start that trial and error phaze all over again since I know that even if it would solve the problem temporarily, which is far from certain, the problem is likely to come back within a few weeks again.
You can't just tell Windows "use this SID" you have to authenticate to the account associated with the ID to be in that user's security context. N.b.: I've obfuscated my SID above but there's nothing you could do with my SID even if you had it.
SONY SOUND FORGE PROBLEMS PLUS
But a) if for some reason you want to put it back, you can, just name it back and b) next time the problem happens, if you've forgotten this fix, a registry search on "Sound Forge" plus a bit of checking will remind you what to do. SF never looks for that key so as far as SF is concerned the key is not there it works just as well as deleting. I rename mine from "11.0" to "11.0_delete_the_other_one_to_fix_reg_problem". One other point: If it makes you nervous to delete the registry key you can just rename it to something else.
Given the above SID, the registry key I want would be HKEY_USERS \ S-1-5-21-184784223-2718281828-3141592653-1001_Classes > VirtualStore > MACHINE > SOFTWARE > Wow6432Node > Sony Creative Software > Sound Forge > The four-digit number at the end will be "1000" for the local Administrator account if you enable it, "1001" for the first user account created on the machine, etc. (Or, if you're in a domain, they're common to the domain, and instead of "yourcomputername" you'll see your domain name.) The three ten-digit numbers in the SID are unique to each machine, but common to all accounts on the same machine (the "machine ID"). One way to find it is to go to a command prompt (Windows-R cmd) and use the whoami command: C:\Users\yourusername> whoami /user If you have more than one user account then you need to pick your own for this fix to be effective. If you only have one user account on your machine there will only be one of these keys in the registry, so it is easy. A couple of notes on the _Classes part of the registry key string:
0 kommentar(er)
