SOLVED - Error 0x80131700. Failed to Bind to MS Common Language Runtime Scripting Host failed to start up.

bengalstripes wrote on 10/7/2016, 10:16 PM

After updating to the latest Windows 10 (I think it was 1607), opening Sound Forge Pro 11 produced the following error:

Error 0x80131700. Failed to Bind to MS Common Language Runtime Scripting Host failed to start up.

Looking on the Internet, I stumbled across a couple of posts, discovered this forum but no solutions.

Well, I had a gut feeling that I knew what this was about and I was right. Basically, the last Windows 10 update seems to have disabled some .Net framework components. That's the bad news.

The good news is that it's really quite easy to restart them...

1. Go to the search point next to the Start menu and type 'Windows Features'.

2. 'Turn Windows Features on or off' will appear.

3. Click on this. You may be asked for your Administrator password, so enter it.

4. At the top of the list, you will see '.NET framework 3.5 (includes .Net 2.0 and 3.0)'. Expand this item and check the check boxes next to the two items that drop down and ensure that the main item is also checked. Press OK.

5. You will be asked to confirm the download of some additional components. Do so and let the system do its stuff.

6. You'll be prompted when the process has completed.

7. Close the panel. You do not have to restart your computer. Fire up Sound Forge and it should open without the annoying error.

On a side note, I have Sound Forge Pro 11 installed on a couple of machines in my studio and this error has only appeared on two of them. All computers have been updated to Windows 10 release 1607. Weird or what?!?!?!

I hope this helps some people.

Comments

Cielspacing wrote on 10/19/2016, 9:54 PM

Thank you bengalstripes your post is one of the best examples of a good "users for users" forum post.
I have a long story of dealing with Windows configuration but is my first time that I see you may actually tinker with the .NET Framework; well done.
///I am saving this in my Soundforge Installation folder for future reference, and will also remember it for similar cases with other software.

fprstudio wrote on 1/3/2017, 6:49 PM

Thanks a million!!! bengalstripes

It works and by doing this I also could install DVD Architect Pro 6 😁

bengalstripes wrote on 1/5/2017, 5:21 PM

Thank you for the kind comments, guys.

So many people put up good stuff that really helps others and on this occasion... well, it was my turn for a change. Glad I could put in a little.🙂

kenneth-berrier wrote on 1/29/2017, 12:38 AM

Worked like a charm! Thanks!

bengalstripes wrote on 1/31/2017, 10:39 AM

Happy to have helped, Kenneth.

My SoundForge is still working just fine, nine months later.

I actually have SoundForge installed on two machines. Both machines are identical in terms of hardware and software. In fact other than the obvious licenses, the boot drives are clones of each other.

This problem only happened on one machine. Why? I never bothered to get to the bottom of it. Just so glad that the .net hack worked.

mp4music wrote on 9/10/2017, 12:49 PM

Just what the doctor ordered; Thanks Bengalstripes; You de man; The Disco Daddies!! :D

Studiochap wrote on 9/12/2017, 5:58 AM

Thanks Bengalstripes! I had this on one machine a couple of weeks ago...didn't chase it then. Had it agin installing on a second machine now., googled, and 2 minutes later problem solved - thanks to your post!

rachelsound wrote on 10/2/2017, 5:32 AM

Thanks a million for this! Not only did it fix the error but it also fixed my problem with the Batch Converter. If anyone else finds their batch converter is greyed out they should give this fix a try. Thanks again :)

bill-byers wrote on 3/12/2018, 11:31 PM

Thank you this answered my question.

Khaled-Selim wrote on 8/18/2018, 2:29 PM

Thank you for saving me from hours of frustration!

depascla wrote on 10/16/2018, 6:06 PM

Grazie Mille, ho risolto il problema dell'errore, ora suono forgiamo perfettamente senza quel fastidioso meggio all'apertura del programma, era molto frustrante. Grazie ancora

igniz-krizalid wrote on 3/11/2019, 10:21 PM

Thank you!

eduardo-nolazco wrote on 5/2/2020, 8:34 PM

Thanks a lot! I have Windows 10 Pro. Version: 10.0.18363 (Build 18363).

This message appeared with Sound Forge Pro 11. I did what you shared and it works! No more annoying messages

sentier34 wrote on 8/12/2020, 3:21 PM

Many thanks. Works OK

houston-texas wrote on 1/17/2021, 2:02 PM

Thank you so much! I have Sound Forge Pro 11 and I started getting that message years ago but it only started bugging me a lot recently. This post made it so easy to fix!

Gustavo-Miranda wrote on 3/19/2021, 11:14 AM

Thank you so very much Bengalstripes! I recently had a flurry of issues with my machines and moving into a new home studio. Your single post helped me with three distinct problems. Again, many, many thanks!!!

Timbre4 wrote on 5/30/2021, 10:23 AM

2021 - This is still helping! Thanks

Sandyman wrote on 7/17/2022, 8:30 PM

This was an error I also got when trying to install and open my Movie Studio 8 on a Windows 10 install. Your post was the beginning of the fix but hit a wall when the .NET update failed with error 0x800736b3. I followed the steps at this link https://answers.microsoft.com/en-us/windows/forum/all/error-update-0x800736b3/85a56759-67a7-4fe5-bb66-47fe9d03924c then performed the steps you outlined again and it worked.

EDIT: The above steps got the load error to go away but the program still doesn't function. The error still occurs when I try to open a video for editing. :(

bengalstripes wrote on 7/18/2022, 6:35 AM

Thanks for your comments, Sandyman. I think we all need to appreciate that my original post and hence, the fix, is six years old. That's several lifetimes in terms of software. It might be time to give in and move on!

Sandyman wrote on 7/18/2022, 12:06 PM

Thanks for your comments, Sandyman. I think we all need to appreciate that my original post and hence, the fix, is six years old. That's several lifetimes in terms of software. It might be time to give in and move on!

Thanks for your contribution.

NEVER MOVE ON! LOL! TOO CHEAP!

EDIT 2: My remaining conflict in Movie Studio was not having Quicktime installed. I put that in and it seems it breathed new life into my antiquated software.

johnebaker wrote on 7/18/2022, 3:11 PM

@Sandyman

Hi and welcome to the forum

. . . . NEVER MOVE ON . . . .

I am afraid you may be going to, well at least regarding Movie Studio 8, though do stay for Sound Forge.😂

You may already know this, however, just in case not - Vegas products, with the exception of Magix Movie Studio 18 and later versions, have their own forum see the Important Posts here.

John EB
Forum Moderator

Sandyman wrote on 7/18/2022, 3:30 PM

@Sandyman

Hi and welcome to the forum

. . . . NEVER MOVE ON . . . .

I am afraid you may be going to, well at least regarding Movie Studio 8, though do stay for Sound Forge.😂

You may already know this, however, just in case not - Vegas products, with the exception of Magix Movie Studio 18 and later versions, have their own forum see the Important Posts here.

John EB
Forum Moderator

I found this forum while searching for the Error 0x80131700. I was getting this same error trying to open Movie Studio so it wasn't exactly related to either software but a program error using either program in Windows 10. I don't see any mention or solutions of this issue in the video forum.

The OP in this thread ultimately led me to the fix for Error 0x80131700. The only reason I joined to contribute was to pass along the problem I encountered trying to apply the .NET fix and what I found to fix THAT problem.

At the end of the day applying both solutions and installing the old version of Quicktime got my old program running. Regardless of forum location it might continue to help others looking for a fix to these same errors. That is the ultimate goal and purpose for posting problems and solutions in online forums.

Thanks!

johnebaker wrote on 7/19/2022, 7:52 AM

@Sandyman

. . . . The only reason I joined to contribute was to pass along the problem I encountered trying to apply the .NET fix and what I found to fix THAT problem. . . .

Your contribution is most welcome.

I mentioned that Vegas products have their own forum, for no other reason, intended or implied, then passing on useful information if you have issues with Movie Studio 8.

. . . . I don't see any mention or solutions of this issue in the video forum. . . .

You wouldn't - this is a 'new' old issue (again) caused by a recent Windows 10 update that is affecting some users - fortunately a very small number (so far).

It was only when checking the update for potential issues, before installing it on my laptop, two days ago, that I found it had raised it's ugly head again.

This is a known issue by Microsoft and if you look at the history of Windows 10 appears to be a frequent occurrence of Microsoft breaking the .net Framework 3.5 installation - you would have thought they had learned by now from over 6 years of this happening !

John EB