Thank you for your answer. I have read in the help file. But that does not solve the problem now. When the proxy file is complete, this message will appear: "An error occured while creating a proxy file for at stream. The file is most likely corrupted or of an unknown format".

By the way, I have read that Magix should be aware of the error, and therefore I ask if anyone knows if an update is forthcoming.

Best regards

Hans-Jørgen Sindholt

Denmark

I haven't seen any reports like yours, at least not in the past year or so.

Since this seems to be an individual issue, it will help others trying to assist you by posting the MediaInfo and Vegas file properties for your source as described here:

https://www.vegascreativesoftware.info/us/forum/faq-how-to-post-mediainfo-and-vegas-pro-file-properties--104561/

Thank you for your answer. I have read in the help file. But that does not solve the problem now. When the proxy file is complete, this message will appear: "An error occured while creating a proxy file for at stream. The file is most likely corrupted or of an unknown format".

By the way, I have read that Magix should be aware of the error, and therefore I ask if anyone knows if an update is forthcoming.

Best regards

Hans-Jørgen Sindholt

Denmark

@Hans-Jorgen-Sindholt
A lot of people found it already since the latest build 221.
It is a common fault , the developpers are aware of it but still there is no new update to repair this bug.
It was apearing suddenly on the latest build that had only the intention to undo the Windows update, that disturbed the more than 2 channel AAC files.
At the moment the developpers are not in the hurry-up to repair this VMS Pl build.

I would say that we are not in a hurry to fix this issue, it is a matter of resources to actually put an update out. We have no resources to do this at the moment.

@Hans-Jorgen-Sindholt The strange thing is it doesn't affect everyone.

Where on your system are your source files stored?

Could you upload a short file to cloud storage so others can download and try on their installations?

I am also having this problem, error occurs at the 99% mark. Was not an issue with the previous build, is there any way to install the previous version?

@Oli-15 see if the Direct links here in section 6 or here still work. If a browser does not download without the workaround (copy/paste the url text to your browser), you could try another.

I am also having this problem, error occurs at the 99% mark. Was not an issue with the previous build, is there any way to install the previous version?

@Oli-15
There's a link at the bottom of this post https://www.vegascreativesoftware.info/us/forum/vegas-movie-studio-17-update-2-builds-159-204--124910/ But get in quick as it may not be there for long. It currently works at 8.35 a.m GMT12 June 2021.

Uninstall your current version then install the previous one.

Hi vkmast, we've just crossed. As per my comments above your second link is still working at present.

@EricLNZ thanks for confirming. (Not too bad flooding compared to what's going on thereabouts?)

Thank you @vkmast and @EricLNZ, downloading it now

I would say that we are not in a hurry to fix this issue, it is a matter of resources to actually put an update out. We have no resources to do this at the moment.

This is happening to me also since "upgrading" to 221. MV17 is now unusable. Magix had resources enough to break it. Where did they all go?

I have now today reinstalled Vegas movie studio platinum 17 (build 221) under a "clean" Windows 10 (version 21H1). The error creating a proxy file still occurs.
On the other hand, the program has not gone down since - yet.
The program is otherwise a great program to work with - and it will be great if the many crashes do not occur in the future.

I am an indomitable optimist.
After installing Vegas Movie Studio Platinum 17 (Suite) on a completely clean Windows 20 (version 21H1). It seems that VMS runs fine without crashes. On the other hand, the proxy still does not work, which other users in this forum have noted.
Sincerely
Hans-Jørgen

We do have a fix for this proxy issue and are work working to get an update out as quickly as possible.

Thank you.