Video Studio Won't Open -- After Windows Update?

[RobertOZ]

User guide for VSX9 available here

http://help.corel.com/videostudio/v19/m ... index.html

[arobertson1]

I can confirm that uninstalling KB 3126587 and KB3126593 resolved the issue.

Microsoft is aware of this but is adopting the approach that it is Corel's problem:

https://support.microsoft.com/en-us/kb/3126587
https://support.microsoft.com/en-us/kb/3126593

"Known issue # 1
After you install this security update, the behavior of searching for DLLs to load in certain scenarios (specifically, when loading implicit dependencies of COM server DLLs) will be changed from the previous behavior in the following way: Unless a prefix of the current directory’s full path is in the Safe Load List, the current directory will be skipped during the search (notice that previously, the current directory was used to search for the DLL). This new behavior may affect some legacy application behavior, and when the DLL loader notices this possible change in behavior, a warning or error message that resembles one of the following may be displayed in the Application log that is available in Event Viewer:

The following warning message indicates the dependency file was not loaded from the current working directory (CWD) because of it not being trusted, but was found in another location:
Loading dependency %2 from the current directory was not allowed when attempted by %1. Another DLL was found: %3.

The following error message indicates the DLL was not loaded from the current working directory (CWD) because of it not being trusted, and was not found at all.
Loading dependency %2 from the current directory was not allowed when attempted by %1. No other DLL was found and the dependency resolution failed.

In both cases, %1 is the full path to the application process’s executable (.exe) file, and %2 is the full path if the DLL is found in the CWD.

If the application requires the old dependency loading behavior for its correct operation for a specific directory, you can achieve this scenario by adding this directory or its trusted ancestor to the Safe Load List. To do this, follow these steps:

Make sure that your trusted location, together with all its descendant tree, is protected properly from unauthorized modifications by NTFS permissions.
Add a string value to the following subkey in the registry in which the data is the full path to that trusted location:
HKLM\System\CurrentControlSet\Control\Session Manager\Safe Load Prefixes

After you make these changes, as long as the CWD is under that location, the DLLs in that CWD will be trusted and loaded as before.

Known issue # 2
Customers using Corel VideoStudio X8 or Corel VideoStudio X9 on Windows 7 may experience a crash while launching or using that product. Customers should install the latest updates from Corel to prevent this issue, or contact Corel for more information and help.

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products. "

******************************************************************************************
Could anybody from Corel please confirm their position on this? This seems like forced obsolescence - are you going to patch older versions or not? You are only talking a couple of years with your software and it does appear to be the way in which you wrote the software that is causing the problem.
******************************************************************************************

[jdowney]

Hi,

Ran the hot fix listed on the previous page. Worked fine, and now my VS8 is working fine; however, my VS7, VS6 and VS5 are still not working since the Windows upgrade...

Jeff

[Ilene]

And they wont.... The hot fix is just for X8. For X7 and lower you need to remove the windows updates mentioned in previous posts -- which will only be a temp solution unless you turn off automatic windows updates and monitor the files that are downloaded fr microsoft. Hard choice. Corel really needs to come up w a fix for older versions. Its not fair.

[BrianCee]

It appears that there are two ways to get them back Jeff

one is to uninstall two of the windows updates namely Kb3126587 and kb3126593 and not let them install again

and the solution from Corel is to take the free upgrade to Windows 10



....

[Ilene]

Well thats interesting. Not sure why that would make a difference?? Doesnt windows 10 have those same updates embedded which would still effect VS7 --not sure I understand. Dont know muchabout windows 10. Do we like it?!

[plasmavideo]

Microsoft in their release notes regarding Kb3126587 and kb3126593 confirms the issue with VSP 8 and 8.5. No mention of earlier versions.

[Ken Berry]

Doesnt windows 10 have those same updates embedded which would still effect VS7 --not sure I understand. Dont know muchabout windows 10. Do we like it?!

FWIW, I have Windows 10 on all my computers that will support it (some older ones won't). And I find it works very well indeed, as did Win 8.1 before it. Moreover, I have VS X7, X8.5 and now X9 on this computer and all work well under Win 10. I got an update for Win 10 at the same time as others got the problematic updates for Win 7 -- I think Microsoft has set times for their rollout of updates. But in my case -- and that of other Win 10 users -- all my programs continue to work, including all the VS versions, after that update.

Now I can't guarantee that everything will be sweetness and light, as it was for me, in following what is obviously Microsoft's preferred upgrade path. All I can do is recount my own experience, and it has been positive.

[lata]

Hi

I have X4 through to X8 and all versions were affected

[david1939]

What a treasure to have this forum! Like everyone else I found X6, X5 and X4 would not run this morning; suspected Windows updates, but first tried soft restart, hard restart and re-install all to no avail. Then checked the forum, et voila! Felt good that I was not alone. Removed the three updates (I'm running Vista) and we are back in business. Thanks to all. How did you find that those updates were the culprits? Incidentally, MotionStudio was not affected.

I guess it's time to upgrade to X8. (not X9 - don't like to be on the bleeding edge )

[Ilene]

Corel support team was extremely helpful and were able to identify the culprits. Thank you Auz!!

[MikeA]

Thank goodness for this forum. Wish I had seen it earlier. I had the error, uninstalled VS8, re-installed it, and still the problem. But the hot fix fixed it. BUT - just got a new error - please see the attached clip. It happened when I tried to copy a video file to the time line. It is a C++ error and says Assertion Failed. I never had this before.

[tletter]

The KB articles on two recent security updates for Windows Vista, 7 and 8.1 identify a problem specific to Corel VideoStudio X8 and VideoStudio X9 on Windows 7.

KB3126587 (https://support.microsoft.com/en-us/kb/3126587) states the following:

Known issue #1: Customers using Corel VideoStudio X8 or Corel VideoStudio X9 on Windows 7 may experience a crash while launching or using that product. Customers should install the latest updates from Corel to prevent this issue, or contact Corel for more information and help.

KB3126593 (https://support.microsoft.com/en-us/kb/3126593) states the following:

Known issue #2: Customers using Corel VideoStudio X8 or Corel VideoStudio X9 on Windows 7 may experience a crash while launching or using that product. Customers should install the latest updates from Corel to prevent this issue, or contact Corel for more information and help.

This is the first time in four years of using VideoStudio that I've experienced a Windows update breaking the application. Corel must have coded something unusual in VideoStudio.

[Ken Berry]

BUT - just got a new error - please see the attached clip. It happened when I tried to copy a video file to the time line.

Mike -- can we assume that the video clip you were trying to insert was a .mov file? If not, what was it. (For Properties, right click the clip in the library if it is there. If not tell us where it came from and what extension it uses.)

I ask since that error message, while referring to C++, seems to be pointing more directly to Quicktime, which of course controls .mov files. So do you have Quicktime installed? If so, what version? If not the latest version, have you tried updating?

Also, have you rebooted the computer and still get the error?

[dickshonary_55]

Thanks a lot for the tips. I had reinstalled 3 times and I suspected that Windows update. I've never had a single glitch with all my Videostudios before.
I've had 100% trust in this product since the beginning. Now, I must confess that this trust relationship has changed a little. I've disabled Windows update and as far as I'm concerned, Microsoft's suspicious ¨free upgrade¨ will wait for a long long long time. On the other hand, that event has made me discover this great board and I'll be back often.

Thanks again.