Microsoft Has Broken Millions Of Webcams With Windows 10 Anniversary Update (thurrott.com)
The Anniversary Update which Microsoft rolled out to Windows 10 users earlier this month has broken millions of webcams, the company said on Friday. The problem is that after installing the update, the company added, Windows no longer allows USB webcams to use MJPEG or H264 encoding processes, and only supports YUY2 encoding. Microsoft says it introduced the changes to prevent an issue that was resulting in duplication of encoding the stream (poor performance). If you're facing the issue, there's a workaround (via Thurrott.com): Rafael has figured out a workaround that should hopefully stop the freezing issue; if you are comfortable tweaking the registry, make this change. HKLM\SOFTWARE\WOW6432Node\Microsoft\Windows Media Foundation\Platform, add DWORD "EnableFrameServerMode" and set to 0
Headaches.
"Microsoft Has Broken Millions of Computers With Windows 10 Anniversary Update"...
H.264? There are evil patents associated with that right?
This just sounds like Microsoft is trying to act like a positive in the freedom dimension Linux distro by refusing to support that evil patenty thing and by refusing to support webcams, which we all know could be used as NSA backdoors and are therefore evil.
AntiFA: An abbreviation for Anti First Amendment.
Fun for everyone!!! Well, except you.
The real reason, it was interfering with the NSA backdoor that watches you sleep.
"Grab them by the pussy" -- President of the United States of America
Install Linux, no drivers needed to be installed
Because the USB device didn't even get recognized at all? ;)
At least Windows 10 doesn't have systemd yet.
(It's probably coming).
Older versions of Windows have a "Favorites" sub-menu on the left side of File Explorer. When I had to convert to Windows 10 at work, the "Favorites" links were automatically migrated into something called the "Quick Access" (QA) menu. So far so good: it converted old stuff into its new convention.
However, "Favorites" used alias names, similar to naming a Windows Shortcut. But QA doesn't (at least not by default). Instead, QA uses the last actual folder name in the path as the displayed title.
I thought QA simply rudely renamed my Favorites titles, so I right-clicked on them to "fix" the titles. Turns out I wasn't looking at an alias, but the live folder name.
The result is I inadvertently renamed network folders used by hundreds of employees! Of course trouble-tickets started popping up like pop-corn. I put two and two together, and quickly renamed them back, and then went for a walk to dry off the sweat.
Table-ized A.I.