Don't give up Murff, maybe the friendly expert vegas enthusiasts here could help you where other forums and vegas staff couldn't. You should be more detailed about what's going wrong with your installation.

The OP has reported getting error -2147163964. Lots of discussion on this error code here. You might read this FAQ, sections 4, 6, and 7, but you've probably tried them already.

Well, Adobe is gonna increase its fees even more soon!

http://www.studiodaily.com/2018/03/adobe-creative-cloud-get-expensive/

Magix is not a rip off... I understand your frustration, but its simply a matter of you not being able

to install your Vegas version no matter what you do/try..... So what specifically is causing you this

installation problem? Is it failing at some point during the installation, What?

An expensive working Adobe is better than a Movie Studio Platinum that I can't install. I've tried everything suggested by tech support and online forums. Nothing. I tried to respond to the last tech support email at the end of January and found that my case had been closed and was instructed to open a new case. I copied and pasted all correspondence into a new case request. No response. I posted on the Magix Facebook page including my case number. I was told that someone would contact me. No one contacted me. I don't know what else to do. Magix obviously knows there's a problem with Movie Studio Platinum 14 and Windows 10. Can you understand how I feel like I've been ripped off? Six months and I'm still unable to install my upgrade.

The OP has reported getting error -2147163964. Lots of discussion on this error code here. You might read this FAQ, sections 4, 6, and 7, but you've probably tried them already.

I've tried everything.

But you did not tell us anything here that would allow us to think about it really- what are the technical specs of your machine, what components are used?

But you did not tell us anything here that would allow us to think about it really- what are the technical specs of your machine, what components are used?

A couple of situations the I personally know of that can cause an error like this...

The most common is if the user manually deletes files a VEGAS or Movie Studio install without using the proper uninstall method, and then tries to reinstall the product. I personally do not have the information on how to correct that issue, but usually you have to manually unregister some of the components and delete some entries in the registry.

The second situation is that the installer if failing to recognize that your machine is missing a specific C++ runtime redistributable package. Normally the installer will detect the runtime libraries are missing and install them, but sometimes is does not work. If that is the case, you can go to https://www.microsoft.com/en-us/download/details.aspx?id=30679 and https://www.microsoft.com/en-us/download/details.aspx?id=40784 and install both the x86 and x64 resistributable packages for each C++ version.

The OP has reported getting error -2147163964. Lots of discussion on this error code here. You might read this FAQ, sections 4, 6, and 7, but you've probably tried them already.

I've tried everything.

Maybe check section 7 (C++) again?

A couple of situations the I personally know of that can cause an error like this...

The most common is if the user manually deletes files a VEGAS or Movie Studio install without using the proper uninstall method, and then tries to reinstall the product. I personally do not have the information on how to correct that issue, but usually you have to manually unregister some of the components and delete some entries in the registry.

The second situation is that the installer if failing to recognize that your machine is missing a specific C++ runtime redistributable package. Normally the installer will detect the runtime libraries are missing and install them, but sometimes is does not work. If that is the case, you can go to https://www.microsoft.com/en-us/download/details.aspx?id=30679 and https://www.microsoft.com/en-us/download/details.aspx?id=40784 and install both the x86 and x64 resistributable packages for each C++ version.

Still the same. I love Movie Studio. I just hate that I can't get it to install.

But you did not tell us anything here that would allow us to think about it really- what are the technical specs of your machine, what components are used?

This is a Windows error, not an application error. The installer attempts to register a library (sfvstproxystubx86.dll) and Windows report that it can't - via a non-successful HRESULT which forces the installer to stop and report. The fact that it can't depends on the state of your system and your user, not on the calling application.

You could try to extract the dll from the installer and run manually from a cmd (as administrator) regsvr32.exe sfvstproxystubx86.dll and most likely you'll see the same error. You could even try to de-register it (using regsvr32.exe /u sfvstproxystubx86.dll) and see what happens.

Assuming you've tried all the usual paths (like made sure al the C++ runtimes neede are available, for example) unfortunately there's a gazillion of Windows corruption modes that can create that kind of situation. The best would be to reinstall Windows. Btw, when you intalled W10, was a fresh installation or did you upgrade?

If you can't reinstall... well, it's tough: you obviously wouldn't be able to register the dll if it's already there and something's loaded and locking it, so you could try utilities like Technet's Process Explorer and systematically search for that dll name in any loaded process.

A failure mode I've seen often is a corrupted registry - entries which are there and shouldn't or keys which are missing etc, sometimes as result of previous, unrelated failures (like resetting the system in the middle of an installation/deinstallation).

Another peculiar one which I once encountered is that the account I was logged on with had, for some reason, lost security permissions to access the registry on more than half of the key trees - which resulted in all sorts of odd behavior from installers and applications (and due to the rareness of the situation, none of that was handled very well by the standard installer software that everyone uses to make application installers.

By any chance - is the user you're logged in when installing an Administrator? If you look at the event viewer, do you get any security or system error? Do you find anything at all?

You could give it a try to create another administrator user, log in as that one and try to install MS. Also you could go into the registry, and simply try to edit some keys to see if for some reason the account you're using can't write into the registry.

But you did not tell us anything here that would allow us to think about it really- what are the technical specs of your machine, what components are used?

This is a Windows error, not an application error. The installer attempts to register a library (sfvstproxystubx86.dll) and Windows report that it can't - via a non-successful HRESULT which forces the installer to stop and report. The fact that it can't depends on the state of your system and your user, not on the calling application.

You could try to extract the dll from the installer and run manually from a cmd (as administrator) regsvr32.exe sfvstproxystubx86.dll and most likely you'll see the same error. You could even try to de-register it (using regsvr32.exe /u sfvstproxystubx86.dll) and see what happens.

Assuming you've tried all the usual paths (like made sure al the C++ runtimes neede are available, for example) unfortunately there's a gazillion of Windows corruption modes that can create that kind of situation. The best would be to reinstall Windows. Btw, when you intalled W10, was a fresh installation or did you upgrade?

If you can't reinstall... well, it's tough: you obviously wouldn't be able to register the dll if it's already there and something's loaded and locking it, so you could try utilities like Technet's Process Explorer and systematically search for that dll name in any loaded process.

A failure mode I've seen often is a corrupted registry - entries which are there and shouldn't or keys which are missing etc, sometimes as result of previous, unrelated failures (like resetting the system in the middle of an installation/deinstallation).

Another peculiar one which I once encountered is that the account I was logged on with had, for some reason, lost security permissions to access the registry on more than half of the key trees - which resulted in all sorts of odd behavior from installers and applications (and due to the rareness of the situation, none of that was handled very well by the standard installer software that everyone uses to make application installers.

By any chance - is the user you're logged in when installing an Administrator? If you look at the event viewer, do you get any security or system error? Do you find anything at all?

You could give it a try to create another administrator user, log in as that one and try to install MS. Also you could go into the registry, and simply try to edit some keys to see if for some reason the account you're using can't write into the registry.

My computer was purchased new in September of 2017, I purchased the Movie Studio Platinum update the first week of November 2017. The computer came with Windows 10. I've had no trouble installing any other software.

I see. Nevertheless, something must have got corrupted in the meantime - the error message is quite clear. For some reason a DLL that should be registered cannot be. Something must be preventing it do so. Have you tried to manually register/deregister the DLL by using regsvr32?

Also not sure if the DLL is 32 or 64bit, so you may want to use %windir%\SysWoW64\regsvr32.exe in the former case, and %windir%\System32\regsvr32.exe in the latter.

It would be interesting to see if it still fails to register when you try manually.