Comments

vkmast wrote on 4/4/2025, 9:40 AM

Would this help?

https://www.vegascreativesoftware.info/us/forum/vegas-pro-22-build-122-general-discussion--147185/?page=5#ca926662

@DANI-FELLA

LdM_Edit wrote on 4/5/2025, 4:18 AM

@DANI-FELLA ¿Es la beta Build 243 la que tienes instalada?

DANI-FELLA wrote on 4/5/2025, 4:24 AM

Si, tenia la anterior y ahora tengo la 243 tambien @LdM_Edit

@vkmast

DANI-FELLA wrote on 4/5/2025, 4:24 AM

@LdM_Edit Si, tenia la anterior y ahora tengo la 243 Tambien

DANI-FELLA wrote on 4/5/2025, 4:25 AM

No funciona, el programa abre en español, pero una vez vuelvo ha abrirlo ya está en ingles @vkmast

vkmast wrote on 4/5/2025, 4:48 AM

Did the current VP 22 public build work for you? If so, go back to that one and wait until the new public build.is released..The 243 is "an experimental open beta".

@DANI-FELLA

LdM_Edit wrote on 4/5/2025, 5:40 AM

@DANI-FELLA Alguien ha reportado el mismo problema con la beta en el hilo oficial, es mejor que la desinstales y reinstales la versión 239. Yo aún no he instalado la 243 así que no puedo confirmar si efectivamente es un problema con la beta.

Maybe someone from VEGAS could take a look at this issue.

Nano wrote on 4/6/2025, 4:47 AM

Hi, I'm having the same problem. I installed the program in Spanish, but when I open it, the interface is in English. I have version 22 (Build 239). I've tried looking for solutions, such as going into the registry and entering key 40a, but that's the one that appears.

DANI-FELLA wrote on 4/6/2025, 4:56 AM

@Nano Estoy totalmente enojado y lo peor de todo es que el soporte no responde. que fiasco

RogerS wrote on 4/6/2025, 9:11 AM

Did you both write to VEGAS support (not the community forum?) They might have a solution.

DANI-FELLA wrote on 4/6/2025, 5:35 PM

@RogerS muchas veces y ni contestan

VEGASDerek wrote on 4/7/2025, 3:28 PM

I have raised this problem with management. There should not be any reason that the Spanish version is being prevented from being used for any license.

VEGASDerek wrote on 4/8/2025, 11:18 AM

We have discovered the problem and are working hard to try to have this resolved for our upcoming update. We apologize for the inconvenience.