VPX 10 no longer works

gmlotkow wrote on 2/4/2019, 7:25 PM

Took at Win10 update recently, now VPX no longer works. The program opens, when I try and import a file, a crash develops. Like this. I only import .mts files/

VPX can no longer start an existing, or new project. Program takes a dump I tried restoring my PC to an earlier date, but that only goes back a few days.

The moment I try and drag and drop a clip into the timeline, there is no indication it would add it, and if I do drop it, the program take a immediate crash. I can drop a .jpg, but once I try a .mp4, or mts: program exits.

I did a restore program to defaults, did not work. Reinstall the program, did nothing.

Any existing projects creates the same fault, makes you close the program.

Dead in the water.

Comments

RogerGunkel wrote on 2/5/2019, 5:03 AM

Can't offer any advice to help, but I recently had an auto update with Win 10 and since then VPX10 has been regularly locking up on 4k footage which never happened previously. I also notice that when scrolling the timeline, there is a lot more cpu loading and most lockups occur whilst scrolling.

I also updated to the latest version of VPX a few weeks ago and noticed a slow down in performance compared to before the update. Maybe the Win and VPX updates make the software less compatible than previously.

Roger

johnebaker wrote on 2/5/2019, 5:07 AM

Hi Greg

. . . . Took at Win10 update recently, now VPX no longer works . . . . I tried restoring my PC to an earlier date, but that only goes back a few days. . . .

The lack of Restore points would suggest the update was a major upgrade - did you update to Windows 10 1809?

I am still on 1803, had a small update a few days ago, and VPX works fine.

If the update was to 1809 there is a known issue where built in Administrator account may be disabled - this would affect the program if you were running it in Administrator mode.

John EB

gmlotkow wrote on 2/5/2019, 4:11 PM

Yes, it had updated to 1809. Win10 now has a different method to restore, it asks you if you want to go back to a prior build, I did that, and found it reverted back to 1803. Same problem.

I went back even further, to 1803 installed on 5/11/2018

Same problem. Now the PC is completely useless in running VPX.

VPX will start, even load a prior project for just a few seconds, then I get the error screen, like this:

Then shut down.

What do I do now? Will it be format my C: drive from scratch, and load everything over again?

johnebaker wrote on 2/6/2019, 3:22 AM

@gmlotkow

Hi Greg

. . . . it had updated to 1809 . . . .

If you have not already done so, try running the VPX installer again and doing a Repair on the installation.

HTH

John EB

shgrude wrote on 2/6/2019, 4:23 AM

@gmlotkow

I have a working VPX (Latest version 16.0.2.306) running on Windows 10 1809. I am not sure if I have tried with .mts files, but if you have a sample file in the format that crashes for you, I can try using it for verification of this being a serious bug or just a problem on your machine/installation.

gmlotkow wrote on 2/6/2019, 9:07 AM

Thanks shgrude, I sent you a message.

gmlotkow wrote on 2/6/2019, 9:56 AM

I did start a ticket with Magix support, Ticket#2019020617000188, we'll see what happens...

I did a complete uninstall of Magix, used Avast to clean up my registry, took the Win10 update to get me to the latest 1809, ran Avast again, downloaded and installed VPX to the latest .306, and whoa-la, same problem.

Does not work.

Liviu-Tatan wrote on 2/6/2019, 10:12 AM

This is the las version Video_Pro_X10_DLV_en-US_181120_10-08_16_0_1_242 , 306 is very buggy

Liviu-Tatan wrote on 2/6/2019, 10:14 AM

The link http://dl03.magix.net/videoprox10_dlm.exe

gmlotkow wrote on 2/6/2019, 10:15 AM

Yes indeed a bit buggy, but when it stops working all together, it take it to another level. Many of us have learned to work around the bugs.

johnebaker wrote on 2/6/2019, 11:52 AM

@gmlotkow

. . . . 1809 . . . . reverted back to 1803. Same problem. . . . .

As you were working before on 1803 this suggests that the 1809 update also installed something that has not reverted back, a possibility is the Intel CPU/GPU drivers were updated as well and have not been rolled back.

Check the driver versions and if they are the latest then they cannot be rolled back as this causes issues, you have to download the previous version, uninstall the latest driver then re-install the older version.

HTH

John EB

gmlotkow wrote on 2/6/2019, 11:57 AM

Decided to do a system reset.

After a clean disc, new Win10, I may update my bios.

shgrude wrote on 2/6/2019, 1:08 PM

@gmlotkow

I have successfully created a New Project (checking your file with MediaInfo) and just tested exporting it as MPEG-4 No Crashes. I can provide you with exported result if you like. Provided details of VPX and Windows version also. (NB! Windows is Norwegian)

gmlotkow wrote on 2/6/2019, 1:19 PM

I fixed it. Cleaned off my c: drive, new Win10 at 1809, VPX started with .204, now going to .268, .306, and still works.

All’s installed, I shut down, restart to a blue screen:(, stopcode error, internal_power_error, it self reboots fine, and everything works.

Must have had a corrupt driver or something. Still have not updated bios.

Scenestealer wrote on 2/7/2019, 4:40 PM

Hi All

I came across a comment elsewhere recently where someone suggested that a major Windows update had reset the Windows Power options and checked mine to find they were on "Balanced". This allows the CPU clock to throttle back depending on load requirements so I set it to High Performance eg. CPU Min state 100% and since have felt VPX is a little more snappy.

@johnebaker

There has been some discussion on the German forum about a possible problem that MS knows about, to do with previous restore points not being available after a recent update. I, like you immediately thought about the Intel driver rollback problem and wondered if the change in driver model might be causing an issue there.

Peter