New
#1
There's a workaround in the article below
http://www.winhelponline.com/blog/we...yuys-standard/
On August 2nd, Microsoft released the Anniversary Update for Windows 10 and when the bits arrived on computers around the globe, it brought with it new features and also broke webcams for millions of consumers. If your webcam has stopped functioning since the release of the Anniversary update, you are not alone but the good news is a fix is coming, hopefully in September.
Microsoft made a significant change with the release of Windows 10 and support for webcams that is causing serious problems for not only consumers but also the enterprise. The problem is that after installing the update, Windows no longer allows USB webcams to use MJPEG or H264 encoded streams and is only allowing YUY2 encoding.
Why did the company remove these options? The short answer is that with the Anniversary update there are new scenarios for applications to be able to access the webcam and the MJPEG or H264 encoding processes could have resulted in duplication of encoding the stream (poor performance) so the company limited the input methods to stop this from happening.
Because of this change, which Microsoft tried to defend but then realized the scale of the impact this change has caused, means that when a webcam tries to use MJPEG or H264, the device will freeze. If you use Skype and your webcam freezes after about a minute, this is the reason...
Read more: Microsoft Has Broken Millions Of Webcams With Windows 10 Anniversary Update - Thurrott.com
See also: MJPG encoded media type is not available for USB/UVC web-cameras after Windows 10 version 1607 (OS Build 14393.10 anniversary)) update
Workaround:
Tweet
— Twitter API (@user) View on Twitter
There's a workaround in the article below
http://www.winhelponline.com/blog/we...yuys-standard/
Perhaps MS is proving their commitment to user privacy?
MS' first response is always to blame someone else for the changes they have introduced.Because of this change, which Microsoft tried to defend but then realized the scale of the impact this change has caused, ...
They used the same tactic with the W8 series.
This sort of thing is one of the reasons why people hate replacing/updating their working systems.
I didn't think 10 was ready for Public release a year ago, and I think it still isn't. Kind of reminds me of the old adage ''if it ain't broke, don't fix it''.
When people are upgrading, as the name says, they are expecting "more", not "less".
They are removing things, for example, they limited also the Colors available for the Desktop.
I have been thinking about this and the freezing problem with the AU. With all the testing from MS and the Insiders, I wonder if MS made some last minute changes that we didn't get a chance to test before the official release. Releasing a buggy OS is not the best way for MS to convince the public that Windows 10 is the greatest OS they ever released. Just my thought on the subject. :)