Text to Speech issues and workaround

VEGASDerek wrote on 10/19/2022, 4:04 PM

As many have reported, currently the Text to Speech feature, which is available to users who have a VEGAS 365 subscription, is not working for many people.

This problem occurs on Windows 10 (latest) and Windows 11 (21H2) machines. The issue has to do with a specific windows update which has rolled out recently. The cognitive services used for the Text to Speech feature is also from Microsoft, like Windows, and the update specifically broke this feature. Other developers who use this service also are experiencing this problem.

Microsoft was informed of this problem and has been working on a solution to the problem. The problem was introduced by patch KB5018418 for Windows 11, and KB5018410 on Windows 10. We have instructed people to temporarily uninstall these patches to remedy the problem. Microsoft has also released fixes for this as well which can be accessed here: https://www.catalog.update.microsoft.com.

The chart below shows what patches can be installed to remedy the problem. These patches will be distributed in a future Windows update.

Windows 10   20H1 thru 21H2           KB5020435
Windows 10   1909                     KB5020437
Windows 10   1809                     KB5020438
Windows 11   21H2                     KB5020387

Comments

bitman wrote on 10/20/2022, 3:18 AM

@VEGASDerek

The link to the windows catalog is without "." at the end ...
The solutions in the catalog do not include windows 11 - 22H2 yet, I do not have KB5018418 installed for Windows 11
Downloading windows 11 (21H2) KB5020387 has windows 10 in the installer filename and refuses to install on my system (as my system has windows 11 and 22H2)
Currently the only thing that works for me is to disable TLS 1.3

1) open the run window (press windows key + R)

2) Type inetcpl.cpl in Run and press ENTER

3) Internet properties panel pops up, select the advanced tab, scroll down all the way and uncheck TLS 1.3

4) Restart your PC

NOTE: as soon as Microsoft has a fix (they already have for some OS versions) enable TLS 1.3 again and (restart); or enable again if you do not use text to speech anymore.

bitman wrote on 10/25/2022, 5:05 AM

Update 25/10: For those on win 11 22H2, offending Microsoft patch is KB5018427, according to Microsoft: "We are working on a resolution and estimate a solution will be available in late October"

You may try to uninstall KB5018427 (I did not want to try that) but disabling TLS 1.3 as described in the post above definitely works.

bitman wrote on 10/26/2022, 2:33 AM

Update 26/10: For those on win 11 - 22H2 - it is fixed with the new KB5018341 and KB5018496 that came in today with the windows updates (looking at the contends I presume it is KB5018496 that fixed it).

ShD wrote on 10/27/2022, 1:35 PM

@bitman I tried your suggestion about TLS 1.3, and it's working!

Thank you!

Kong-KaiChi wrote on 10/30/2022, 9:57 PM

Update 25/10: For those on win 11 22H2, offending Microsoft patch is KB5018427, according to Microsoft: "We are working on a resolution and estimate a solution will be available in late October"

You may try to uninstall KB5018427 (I did not want to try that) but disabling TLS 1.3 as described in the post above definitely works.

The only way works for me is to uninstall KB5018427.

bitman wrote on 10/31/2022, 3:51 AM

@Kong-KaiChi Make sure you restart (not just power off/on) your PC after disabling TLS 1.3, or it will not work. Anyway, try to force a Microsoft update KB5018496 if possible, this will fix it (also do not forget to reactivate TLS 1.3 if you would have deactivated it, as it is a security improvement).

Jessariah67 wrote on 11/7/2022, 1:23 PM

Any idea what the KB number is for Win 10 21H2? I'm having the same issues. Thanks!

bitman wrote on 11/9/2022, 2:38 AM

@Jessariah67 According to @VEGASDerek for Windows 10 20H1 thru 21H2: KB5020435 should fix the issue, if you have not received the KB yet via the "normal" windows update (automatically as in periodically, or requested/refreshed by the user), there is the third option, which is a bit more work, that is to navigate to the Microsoft catalog (see link at the beginning of this post), and search for KB5020435, and download and install it for your specific system & OS variant manually.

Jessariah67 wrote on 11/9/2022, 3:54 AM

Ironically, "Bill" forced an update on me yesterday afternoon and it's all working again. Thanks!

AllanDest7 wrote on 1/10/2023, 12:26 AM

I'm fine too and everything works. thank you!

Simplest2remember wrote on 1/29/2023, 7:45 AM

@Jessariah67 According to @VEGASDerek for Windows 10 20H1 thru 21H2: KB5020435 should fix the issue, if you have not received the KB yet via the "normal" windows update (automatically as in periodically, or requested/refreshed by the user), there is the third option, which is a bit more work, that is to navigate to the Microsoft catalog (see link at the beginning of this post), and search for KB5020435, and download and install it for your specific system & OS variant manually.

I'm stuck with this, although the TTS tool worked a few times initially, then a restart fixed it for a couple more jobs, then another one, but now it's refusing to budge, restart or no restart. For me, TLS 1.3 was already disabled (no idea why), so I restarted and a switched it ON - didn't work - restarted again - switched it OFF (as suggested above), but still get the same error. I tried downloading two of the KB patches - this one

windows10.0-kb5020435-x64_c80ba81c2e9c810fed28af5ca133d92a6b52f1dd.msu

and this one

windows10.0-kb5020438-x64_56438b53dbad8a919ebe3b9ba8b793fafde11729.msu

because they both seemed designed for my H2 Intel64 (but different upload dates) - but both say they are incompatible / can't be installed. I have a 2 year old Thinkpad X13, Windows 10, 16GB, and all the latest patches (although annoyingly I can't seem to install the important KB5020435 as mentioned above). Help!! Has anyone else still got this issue? I only bought Vegas Pro 20 (365) 4 days ago.

Simplest2remember wrote on 1/30/2023, 9:02 AM

This is just a copy of the message I posted to the other thread on this, for those who don't know there is _another thread_

-----------------------

Right chaps, this took me a LONG time to fix, so I want to maximise all the karma coming my way...

My laptop was W10 21H2

I upgraded it to W10 22H2

Job done (I thought everything was automatically kept current in windows 10. Not so. Run Winver and find out)

KayG wrote on 11/28/2023, 1:07 PM

None of these fixes have worked for me, and I still can't access text to speech. I have a support ticket out there, but it's been 2 weeks almost with little response.