You might be thinking that you are alone in having trouble with your webcam, but it isn’t the case, like you, many others are also faced with the same problem. The reason is that Microsoft’s big Anniversary Update for the operating system has caused different webcams defunct. The arrival of a fix is expected to come in September as indicated by Microsoft representatives. So, Windows users who are clever don’t intend to wait for Microsoft’s update and already trying to get rid of the issue.
A Microsoft’s statement to Gizmodo reads, “Windows 10 continues to have the highest customer satisfaction of any version of Windows. We have seen a small number of reports of unexpected behaviors following the Windows 10 Anniversary Update. Engineering and customer support are investigating these on a case by case basis and offering troubleshooting tips as necessary. If a customer has any issues, we offer customer support at www.microsoft.com/support”.
The problem arose due to Microsoft’s decision for preventing webcams from using MJPEG- and H264-encoded streams with Microsoft’s new Windows Camera Frame Server. Multiple apps could access the camera stream via the server, camera stream is a change in the Windows 10 Anniversary Update, however, as per Microsoft decision, the Frame Server should only receive an uncompressed YUY2 stream from your webcam.
So, it would result in the hanging, freezing of any webcam which attempts to use those two prohibited codes. Microsoft aimed at finding the best solution that could keep your webcam’s availability to apps like Windows Hello and Cortana without having multiple applications decoding the same webcam stream simultaneously.
A post in Microsoft’s Support Forums from Windows Camera Team member Mike M states, “MJPEG and H.264 being decoded / filtered out is the result of a set of features we needed to implement, and this behavior was planned, designed, tested, and flighted out to our partners and Windows Insiders around the end of January of this year. We worked with partners to make sure their applications continued to function throughout this change, but we have done a poor job communicating this change out to you guys. We dropped the ball on that front, so I’d like to offer my apologies to you all. We’re working on getting better documentation out, to help answer any questions you may have”.
Microsoft is decided to first fix the issue for the MJPEG codec, though some extra time might be needed in trying out a fix for H.264 with its various Windows Insider testers.
Mike M’s post further reads, “Since it will take some extra time for the H.264 work to go through this additional layer of testing, and we would prefer not to delay the MJPEG changes, we will ship these two separately. You can expect the MJPEG media type work to reach you first”.