j-v wrote on 11/20/2019, 9:13 AM

Better to update to the last one:

Maybe also good to look into your taskmanager if somewhere an instance of the program is running, in the taskmanager or the background processes .

met vriendelijke groet

Camera : Pan X900, GoPro Hero7 Hero Black, DJI Osmo Pocket, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W11 home version 22H2, i7 9700 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti with driver
537.42 Studiodriver and Intel HD graphics 630 with driver
Laptop  :Asus ROG Str G712L, W11 home version 22H2, CPU i7-10875H, 16 GB RAM, NVIDIA GeForce RTX 2070 with Studiodriver 537.42 and Intel UHD Graphics 630 with driver
Vegas software: VP 10 to 21 and VMS(pl) 10,12 to 17.
TV      :LG 4K 55EG960V

My slogan is: BE OR BECOME A STEM CELL DONOR!!! (because it saved my life in 2016)

RgVideo wrote on 11/20/2019, 7:38 PM

Got same error msg when trying to update newly purchased MSP16 (Build 142) to Build 167, using the update window that showed on MSP startup. Not resolved yet.

EricLNZ wrote on 11/20/2019, 9:26 PM

@RgVideo Download the file as j-v suggests in his post above. Then with VMS closed run the file. Then if you get the running message check in Windows Task Manager as per j-v's post.

RgVideo wrote on 11/20/2019, 9:53 PM

Tried to install again from within MSP.  Got same error msg.  Didn't see any MSP in Apps part of Task Mgr, but about 8 lines of it in the Processes part.  I've had multiple hangs at the "Creating Windows" point before and maybe this where they came from.  After killing MSP processes tried update from within MSP16.  Clicked on "Install Immediately" and get same "unable to update" msg.  Still have MSP process. Looks like to me that Installer kills MSP app, but not process.

So, downloaded Build 167 from Magix.  When I ran it I get msg that says "earlier version has been detected and do I want to update?"  Well, I have MSP13 installed and don't want that deleted so I said NO.  Do you think it's safe to say YES here?

EricLNZ wrote on 11/21/2019, 1:00 AM

Yes, should be safe. It's referring to an earlier build of MSP16 and will uninstall that build.

vkmast wrote on 11/21/2019, 5:11 AM

Indeed. This version vs. build terminology should be consistent. Why not "earlier build of this version has been detected"?

RgVideo wrote on 11/21/2019, 10:27 AM

Thanks for the input. Very good way to reword the msg. I wouldn't have been reluctant that way. :)

RgVideo wrote on 11/21/2019, 12:12 PM

Yay, did the update and all OK now! Thanks for the assistance.