Movie Studio Platinum Ver 13 (Build 967) 64 bit.
Sony Vaio Desktop, Win 10 Intel i7 64 bit, 16 Gb ram, 960 Gb SSD, Capture device is Canopus ADVC100.
It worked fine yesterday and now won't start. It freezes at "Initializing External Monitoring..."
A large Microsoft update happened today.
Have you tried uninstalling/reinstalling since the Windows update?
Nothing worked. This is seriously impacting my work. Where is support?
I contacted sales by phone trying to reach tech support, result, refund in process... I'm sticking with my SONY Vagas Pro V10. It's solid and works great for me.
Same problem with Movie Studio 12 (32bits), Movie Studio 12 (64bits) Movie Studio 10 (32bits) after last W10 update. They were all working fine 3 days ago before I processed the big W10 update
I found in one forum that it can work if you start windows in Safe Mode! I tried it and it's true, it works in safe mode.
This being said it is not an acceptable solution
I have tried uninstalling/re-installing: no effect.
May be (probably) the standard uninstalling feature does not cleanup correctly the registry and the files, but then
defining what has to be cleaned up manualy is not part of my competencies.
Last News
I just got a new windows update (important one if I relate to the wait time and percent achievement progress)...
Just for fun, I restarted Windows, tried again starting Movie Studio and beleive it or not:
IT WORKS !
my 3 releases of Movie Studio are back.working.
Cannot understand why MS is so stressed to release stuff and then pushed to repare damages in a hurry...they really need to step back and think.
Last News
I just got a new windows update (important one if I relate to the wait time and percent achievement progress)...
Just for fun, I restarted Windows, tried again starting Movie Studio and beleive it or not:
IT WORKS !
my 3 releases of Movie Studio are back.working.
Cannot understand why MS is so stressed to release stuff and then pushed to repare damages in a hurry...they really need to step back and think.
I just went to windows update as alain-e mentioned and it found a cumulative update. Installed it and the program works fine now.
The problem is this is still a downgrade as it is not able to open Vegas Pro files. Why would anyone want to downgrade? I am a Vegas Pro user so why send me this offer.
The problem is this is still a downgrade as it is not able to open Vegas Pro files. Why would anyone want to downgrade? I am a Vegas Pro user so why send me this offer.
MIschele, you need to read this
http://www.focusonvegas.com/movie-studio-vegas-pro-version-faker/
Start from the top there. It explains what has been possible with the SCS versions.
I have not tried that version faker. And as said there "The current version ‘ll (probably) not work with projectfiles of the new Magix versions of Vegas Pro and Movie Studio. Use at your own risk."
Also this https://www.vegascreativesoftware.info/us/forum/can-t-open-vegas-pro-11-files--103817/
As for sending offer emails, much of it remains a mystery to many, even at the company.
Happy birthday 😩
Almost one year later same story:
an important Windows 10 update leading to the same bug:
Thanks MS,
I followed this morning your advice to update my Windows 10 and I am now facing the exact same issue as 1 year ago: none of my 3 Vegas Movie Studio can now start anymore.
...and by the way as it was happening last year if I start the program in safe mode, everything works fine...but who can use this kind of software in safe mode?
Which Win 10 version/build are you now on?
Hi Eric
I moved my Vaio laptop from W7 to W10 one year and a half ago
I was on W10 Home (updated) version 1607 / 14393.1715 when I got 2 days ago a Windows message inviting to install a very big update...this is what I did yesterday
This update installation time took over one hour but before launching this update (I do not have anymore a lot of confidence into MS...sorry!) I made a backup (using Acronis) of the complete system softwares and files (a full disk image).
When I discovered the issue regarding Vegas Movie Studio, I tried to do some tests (So I discovered like a year ago, the program does not freeze in safe mode) and then I re-installed my backup...I must say at that time I didn't note the specific information regarding the Windows version/release after update, but there is not (to my knowledge) a lot of W10 updates of this size currently pending.
You probably noticed I am not an English speaking Citizen so my 3 Vegas Movie Studio are in french.
The freeze is identical to the one of last year: When starting Vegas Movie Studio there is a process with few phases of installing some pieces of sotware the last one being "installation de la surveillance externe" which I am not sure how to translate this one in English...something like "installing external oversight" word for word?
You may watch the startup screen to read the English message titles ...It is the last one of this installation phases on which my VMS freeze.
I am currently trying to understand what to do before going back to re-install this update.
Looks like your big update was the Creators update which takes you from Version 1607 to 1703. I have 1703 and have not had any problems. But my pc is only 18 months old and came with Win10 installed. It seems that most problems occur when Win 7 is updated to Win 10. One recommendation I've seen is to do a clean install of Win 10. But that's drastic and might not be possible.
"installation de la surveillance externe" is probably "Installing External Monitoring". I'm not sure what that does. I do have a second monitor. Perhaps it's a clue to your problem if someone more knowledgeable pops by.
I've just noticed that in the first post Mischele was freezing at the same point.
Thanks Eric for your attention
My Sony Vaio came with a lot of Sony stuffs. Not sure I can rebuild them after a clean W10 install. My only hope is as it happened last year an additional update from MS could come (within a few days last year) to correct the bug.
Nevertheless I doubt the last year additionnal update was done for this specific issue (MS re-acting in a few days !!!! hard to believe), I feel it may have been a side-effect from something else...pure hazard... so I am not very optimistic.
May be if many people are experiencing similar issue it may push MS to do something
If I can understand what means "external monitoring" this could help.
I have read in a french forum someone experiencing a freeze issue due to one of his 2 graphical cards delivering GPU support so he fixed the problem turning off the card driver until VMS is started and then turning on the driver. We may not have only W10 and VMS in the loop.
Eric, using your translation for "installation de la surveillance externe", I just found this : 
, so I am going to re-install the W10 update and try it.
I will be back here with the result
Back again
1) I have followed the above Youtube process after re-updating W10 (1703 confirmed) but no effect.
2) During my many tests I discovered the following:
It is like if some tasks are not loaded in the proper order, and when killing VMS one task remains active (in memory ?) and the next time(s) I start one of my VMS, the loading is correct and everything goes fine...
3) I checked several time: killing the VMS task through the task manager does not kill one of the back-ground VMS process and the only way to kill this process is to restart Windows. This "never-ending" piece of VMS may keep active a necessary process in a good place for the next call (we need to dream sometime)
Not sure the above is clarifying the issue but I will keep W10 (1703) and survive with an un-elegant double-startup VMS process until (may be) a miraculous new Windows update.
Try running the program as "Administrator".
If that doesn't work try the 32 bit version of Movie Studio.
Corel had the same problem, the 64 bit hangs but the 32 bit doesn't, it's random some machines run the 64 and some don't. It's a bad instruction in some 64 bit versions of the Intel CPU... IMHO
Try running the program as "Administrator".
If that doesn't work try the 32 bit version of Movie Studio.
Corel had the same problem, the 64 bit hangs but the 32 bit doesn't, it's random some machines run the 64 and some don't. It's a bad instruction in some 64 bit versions of the Intel CPU... IMHO
I tried both 32 and 64 versions as admin with no success
I am currently trying to compare the "services" before launching VMS (leading to a freeze)and after doing the successful launch (as described before).
May be there is a problem triggering the services in the right order...what difference do we have in the services status when the starup freeze versus when the starup is successfull?
It will take some time, but if I find something I will come back
Try disconnecting all USB and fire-wire devices, restart the computer and then try launching Movie Studio with nothing plugged in. Also, went to the .exe and set "Run as an administrator" in compatibility mode so it stays that way.
Try disconnecting all USB and fire-wire devices, restart the computer and then try launching Movie Studio with nothing plugged in. Also, went to the .exe and set "Run as an administrator" in compatibility mode so it stays that way.
My Vaio labtop has no device attached (USB or FireWire).
I tried running as admin and in admin/compatibility mode but no success
I just finishedcomparing 269 services status when VMS freezes versus when VMS launch successfully.
3 of them were in a different status, but puting them all in the status of the successfull launch before any launch does not change anything. So it seems the services status are not in the loop of the problem.
Probably not it, but curious, how are your keyboard and mouse connected?
Alain - When VMS freezes have you tried opening a second instance of VMS without killing the first with Task Manager.
Also check in your graphic properties that only one monitor is being used.
Probably not it, but curious, how are your keyboard and mouse connected?
My computer is a labtop: Sony Vaio VPCF13 with a touchpad into the integrated keyboard.
SSD 500Gb, Core I7 Q740 1.73GHz, 8Gb Ram
Alain - When VMS freezes have you tried opening a second instance of VMS without killing the first with Task Manager.
Also check in your graphic properties that only one monitor is being used.
Following your remark, I just made a serie of tests with not killing the frozen one:
I have 3 releases of VMS (VMS10, VMS12_32bits, VMS12_64bits)
1) starting anyone of these releases leads to a freeze
2) when I start first VMS10 (always ending in a freeze),
3) when I start first one of the VMS12 (always ending in a freeze),
I seems that a pending frozen release (10 or 12) disable the start of another instance of this release but enable the successfull start of the other one.
Not sure where we can go with that 😩
alain_e wrote on 10/21/2017, 3:52 PM
I think I have finally identified the origin of the problem.
I noticed when I started Skype or the Camera App (which are both activating my integrated webcam), then I also could start VMS without any issue and so I concluded it may be the driver of the integrated webcam causing issue when VMS tried to link to it.
This driver is named "Sony Visual Communication Camera" and was created, provided, and numerically signed by Microsoft accordind to the properties informations.
De-activating this driver allows the startup of any of my VMS but without the function of connecting to the webcam for video recording.
Once VMS is up and running then if I activate the driver the function of webcam recording in VMS becomes available.
Mischele was on this track in one of his post.
I also noticed in the properties of this driver an information telling (in french) something like "the installation of this device must be continued". not sure of what that means and what to do...I will try re-installing the driver (up-to-date according to MS).