Problem: My Vegas 17 has suddenly stopped working. (I’ve used Vegas for years with no problem.) I’ve searched all the forums, and have researched the error code that appears. I contacted Magix support two weeks ago, but no help yet

About 3 seconds after clicking the Vegas icon to open an existing project, the “Vegas Pro has stopped working” box appears), and the project does not open. This is true of all existing projects.

Also: If I open a new (empty) project, an empty Vegas project screen does appear. However, it will not accept any project media, neither whether dragged into the project media box, or onto the timeline (the "cannot place" icon appears).

I have completely uninstalled the program, removed all Vegas-related files from my PC, and reinstalled – it still doesn’t work.

I’ve uninstalled Boris FX to be sure there’s no conflict there – But I still can’t open Vegas.

Following is the problem description that appears when I try to use Pro 17:

Application Name: VEGAS Pro
Application Version: Version 17.0 (Build 452)
Problem: Unmanaged Exception (0xe06d7363)
Fault Module: C:\WINDOWS\System32\KERNELBASE.dll
Fault Address: 0x00007FFCCDC54B59
Fault Offset: 0x0000000000034B59
Fault Process Details
Process Path: C:\Program Files\VEGAS\VEGAS Pro 17.0\vegas170.exe
Process Version: Version 17.0 (Build 452)
Process Description: VEGAS Pro
Process Image Date: 2020-05-08 (Fri May 08) 17:08:36

Thank you in advance for any ideas!

Intel i7-7700K CPU @ 4.20 GHz
Operating system: - Windows 10
Memory: - 32 GB
Graphics Card: - NVIDIA GeForce GTX 1060 6GB
Vegas program is loaded on internal SSD

Move to a newer build?

Update graphics drivers?

Just throwing ideas out there.

Before starting Vegas 17 Hold down both the CTRL and SHIFT keys. Now double-click on your Vegas 17 icon to start Vegas. You should get the following image pop up. Tick the "Delete all cached application data." check box. Select YES to totally reinitialize Vegas. Hopefully, this will fix the problem.

"WARNING" Take note! This will reset everything back to the initial Vegas install parameters. If you have created render presets etc along with saved GUI layouts all those will be lost. You will have to recreate them. You have nothing to lose really so it may be a way to fix the problem. Good luck.

Chris Young

Could it be related to this? Need to remove Microsoft patch KB5001330 and KB5000842, this temporary solution allows VP18 to unload m2ts files with 5.1 audio channel.

And additional information: This is bigger than Vegas. Not only M2TS and MTS, but VOB and MPG, even MP4 stopped working in Windows yesterday -- won't play, can't open, rename, delete, or move. Windows HARD LOCKS and must use POWER BUTTON RESTART!

So I went back to Control Panel, and the damned update had been installed--again! Everything went back to normal after second uninstall.

This is a Microsoft problem. Vegas is just our local poster child.
Paused updates for a month. Microsoft owes us a fix; we owe them nothing for this abomination.
Leave the files on my computer alone! If there's a problem with malformed downoads, fix that!
If I wasn't too old to learn a new OS, I would be dumping Windows today. Just damn them.
But with billions of all-important gamers screaming at Microsoft as well, I think the bottom line is going to force a fix soon.

That's bad news, really bad news! I now see these issues date back to at least April 20th. In the past, I've been caught out with certain MS updates. One affected JPGs some time back. I'm running the "Win Update Stop" app that stops updates if you have selected stop updates. Been running it for a couple of years now. Run it in conjunction with a system backup before updating then if anything goes astray you can get out of jail fairly easily.

Chris Young

https://www.winupdatestop.com/

Did you ever get this resolved? I am having the EXACT same problem. I've had it for a while but hadn't been using Vegas but now I have a project to work on and need it desperately.

Problem: My Vegas 17 has suddenly stopped working. (I’ve used Vegas for years with no problem.) I’ve searched all the forums, and have researched the error code that appears. I contacted Magix support two weeks ago, but no help yet

About 3 seconds after clicking the Vegas icon to open an existing project, the “Vegas Pro has stopped working” box appears), and the project does not open. This is true of all existing projects.

Also: If I open a new (empty) project, an empty Vegas project screen does appear. However, it will not accept any project media, neither whether dragged into the project media box, or onto the timeline (the "cannot place" icon appears).

I have completely uninstalled the program, removed all Vegas-related files from my PC, and reinstalled – it still doesn’t work.

I’ve uninstalled Boris FX to be sure there’s no conflict there – But I still can’t open Vegas.

Following is the problem description that appears when I try to use Pro 17:

Application Name: VEGAS Pro
Application Version: Version 17.0 (Build 452)
Problem: Unmanaged Exception (0xe06d7363)
Fault Module: C:\WINDOWS\System32\KERNELBASE.dll
Fault Address: 0x00007FFCCDC54B59
Fault Offset: 0x0000000000034B59
Fault Process Details
Process Path: C:\Program Files\VEGAS\VEGAS Pro 17.0\vegas170.exe
Process Version: Version 17.0 (Build 452)
Process Description: VEGAS Pro
Process Image Date: 2020-05-08 (Fri May 08) 17:08:36

Thank you in advance for any ideas!

Intel i7-7700K CPU @ 4.20 GHz
Operating system: - Windows 10
Memory: - 32 GB
Graphics Card: - NVIDIA GeForce GTX 1060 6GB
Vegas program is loaded on internal SSD

Brad, did you try the steps listed above?

Update video drivers
Reset Vegas Pro back to defaults


What is your "fault module"? We need to see your "details".

Just received the following v17 upgrade to build 455. It states it fixes a conflict with recent Windows 10 updates. Let's see if it solves the problem!

Chris Young

Actually I asked re this back in March...

I attempted to update...(Build 482)

However, on hitting Update Immediately, I downloaded the update, then got a message saying I had to reboot because another update had not been installed...or something like that.

So I rebooted and the same thing occurred with the update being downloaded and the same message coming up.

Thus I haven't been able to update.

This has been fixed in the current installer of Vegas Pro 18. Plus you can log into your account at Magix and download the installer from there and install it directly without needing to have VEGAS open.

Thus I haven't been able to update.

Check mail!

Chris Young

Thanks guys...

It is version 18 that I can't update, so is it really fixed for this version?

I'll have a go the way Edward suggests...

Renton

Yes, they really fixed the issue in the last Vegas Pro 18 update. Of course, that only fixed it AFTER it is updated so going to your account and downloading it from there or going to "News" forum post telling about this update in at vegascreativesoftware will get you the new download link.

BTW, here's the latest version:
Vegas Pro 18: https://rdir.magix.net/?page=RGT36MUZFBY8
Vegas Post Suite: https://rdir.magix.net/?page=EK1JU261HFUM

And here's the changes in the latest version:

New Features:

BETA: VEGAS Hub access for VEGAS 365 users
HEVC 10-bit 4:2:2 decoding with supported hardware
Disk usage field in the Render Progress dialog

Bug Fixes:

Scale & Location tracking mode no longer missing from Bezier Mask tracking
YouTube and Vimeo uploads now work
Bezier masks with 32 or more curve points will no longer crash when rotating the mask
Now will disable the "Hardware Decoder to use" field in preferences if no hardware decoder can be used
Resetting color grading after a Camera LUT has been apply no longer crashes.
Fixed crashes that could occur when adjusting the HLS and Input/Output slider in the Color Grading panel
Issues with recent Windows Update and AC3 decoding have been resolved
Minimizing VEGAS while doing a batch render will properly keep the Render Progress dialog minimized as well
Driver update utility now sees Xe Max GPUs
Video Stabilization no longer crashes after applying a preset
Fixed scenario where Render As dialog is not visible when launched