MS13-057 patch causing video heartburn

[Davidk]

I came across this article on The Register site relating to a critical change published in the Microsoft July patch tuesday batch, which is causing video editors heartburn:
http://www.theregister.co.uk/2013/07/15 ... deo_codec/

The article includes an image of what is happening to some editors using the modified MS .wmv file libraries.

You will note the recommendation in the article. To be safe, I rolled back that patch, expecting that sooner or later MS would announce an update or revision to it as a response to the screams from the more demanding portion (video + gamer users) of their user population. But thus far (2+ weeks later), nada. And of course the article is still posted, unamended or updated. And thus the queries below.

The 1st question: is there any indication at all that this is happening to or affecting VS users??
the 2nd question: if VS is affected, what is Corel doing (or going to do) about it?

Davidk

[Ken Berry]

No one seems to have reported it as affecting VS as yet. I am also away from home and won't be back in NZ till Sunday, so can't access my video computer till then.

Of course, it appears, from that article, that the flaw only appears when trying to produce some types of .wmv format. I don't normally do so. So I guess we will need to wait for someone who does to see if things are affected...

But thanks for bringing it to our attention.

[lata]

Hi David / Ken

Reading further to the comments seem to suggest it is a Windows 8 issue, guess that’s another reason why we have had no reports.

The only problem I have in creating a new WMV template is saving it, the windows operating system does not allow changes, until you reset the “read only” tag associated with the Wmv file?
Don’t think that is associated with this latest issue which is easy to ID as half the screen is black.

[Davidk]

Re the comment about windows 8 - interesting. The patch detail in windows update lists this as kb2803821. Clicking on the more information link on the detail page connects to here:
https://technet.microsoft.com/en-us/sec ... n/ms13-057
The MS13-057 article itself basically only talks about opening wmv media files in media player - which on the face of it, should have a limited impact. Nevertheless, that register article makes it pretty clear that they see a broader, unintended effect. And in that ms13-057 article there is an extensive, detailed tabular list of all OS that are affected - and just about every MS OS (including variants like x32 and x64) since XP is listed there as a 'critical' impact.

The tenor of the reg article is that a bad result occurs but the sub-text is that some editors are reacting differently, and that might also include an OS component for the platform the editor is running on. But clearly its not just windows 8.

Davidk
Postscript.
FYI, I read an early (Gartner) pre-beta review of win8 (the one that got pulled from the gartner site after MS corporate pressure) and concluded that Vista mk2 was in the offing, stay away. That impression has been reinforced by various user comments and specific applications usage since then, most recently yesterday when I was helping a student get over problems using X6 on her new win8 laptop. Most of the issues were win8, not VS, and the rest were just good practice. But the horrible impact that new windows 8 UI is having on general users is really turning them off. And me, even more off. There's a way to get a start panel displayed on the desktop using boot-time command string (DOS still lives!!) and apparently win8 SP1 when released will have an option to do the windows 7 desktop and start panels - in a more accessible and seamless manner - but it's not here yet. In the meantime the computer store techs are doing a land office business.

[Davidk]

One of the links in the register article gets you here, which has a better description/list of the programs that this is affecting:
http://www.infoworld.com/t/microsoft-wi ... 904-222636

Davidk

[skier-hughes]

Each update has a related KB article
KB2803821
https://support.microsoft.com/kb/2803821

KB2834904
https://support.microsoft.com/kb/2834904

Other reference info for MS13-057 (with public references/details about ‘Known Issues’ for/with updates 2803821 and 2834904)
https://support.microsoft.com/kb/2847883

Apparently MSFT is aware of it and has made the following information public

<qp>

• Known issues in security update 2803821:
If you use some of the following software, you may experience issues after installing 2803821. In some cases, WMV video files may fail to successfully encode or decode. Upon completion of the investigation, Microsoft will take appropriate action to help protect our customers. This may include providing mitigations and workarounds or re-releasing this security update.
• Camtasia Studio
• Adobe Premiere Pro
• Serif MoviePlus
• YouTube Movie Maker

• Known issues in security update 2834904:
If you use some of the following software, you may experience issues after installing 2834904. In some cases, WMV video files may fail to successfully encode or decode. Upon completion of the investigation, Microsoft will take appropriate action to help protect our customers. This may include providing mitigations and workarounds or re-releasing this security update.
• Camtasia Studio
• Adobe Premiere Pro
• Serif MoviePlus
• YouTube Movie Maker
</qp>

Latest revision dates for all above referenced articles range from Jul 17-18th, 2013.