- Joined
- Oct 17, 2012
- Messages
- 9,781 (2.32/day)
- Location
- Massachusetts
| System Name | Americas cure is the death of Social Justice & Political Correctness |
|---|---|
| Processor | i7-11700K |
| Motherboard | Asrock Z590 Extreme wifi 6E |
| Cooling | Noctua NH-U12A |
| Memory | 32GB Corsair RGB fancy boi 5000 |
| Video Card(s) | RTX 3090 Reference |
| Storage | Samsung 970 Evo 1Tb + Samsung 970 Evo 500Gb |
| Display(s) | Dell - 27" LED QHD G-SYNC x2 |
| Case | Fractal Design Meshify-C |
| Audio Device(s) | on board |
| Power Supply | Seasonic Focus+ Gold 1000 Watt |
| Mouse | Logitech G502 spectrum |
| Keyboard | AZIO MGK-1 RGB (Kaith Blue) |
| Software | Win 10 Professional 64 bit |
| Benchmark Scores | the MLGeesiest |
Hello TPU I know this isnt new, but if it helps someone , im glad i posted it, so no need to post it can be found by googling., if any others are having this issue, i thought this info might help them as it did me.Photo is still Borked for ME tho, but video works in all aspects.
Once i upgraded to the new anniversary update on Win 10, My C920Pro shit the bed, and wouldn't work.*M$ apparently removed support, or something pertaining to the H264 codec* There IS a minor half solution that gives back SOME functionality by choosing to "update driver" in Dev manager, and selecting "choose my own media", and opting out of the Actual device, and instead choosing a "usb video device" as is shown Here.....
but that solution is crap, so there is another way with some simple regediting, that fixes it good as new, as far as i can tell. the solution was posted by Rafael Rivera (WithinRafael), and i have since applied it , and tested it, and it works perfectly. So here is that better option solution.
1-open regedit, navigate to the following location...
2-HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows Media Foundation\Platform
3-Once you've reached the "platform" folder, right click it, and choose "new".
4-under "new" create a "Dword" entry,
5-when prompted to name it, give it the name "EnableFrameServerMode" *case sensitive*value is 0 (zero)
6-You can now back out, and Your H264 based cam SHOULD work fine.no restart was required for me.
Once i upgraded to the new anniversary update on Win 10, My C920Pro shit the bed, and wouldn't work.*M$ apparently removed support, or something pertaining to the H264 codec* There IS a minor half solution that gives back SOME functionality by choosing to "update driver" in Dev manager, and selecting "choose my own media", and opting out of the Actual device, and instead choosing a "usb video device" as is shown Here.....
but that solution is crap, so there is another way with some simple regediting, that fixes it good as new, as far as i can tell. the solution was posted by Rafael Rivera (WithinRafael), and i have since applied it , and tested it, and it works perfectly. So here is that better option solution.
1-open regedit, navigate to the following location...
2-HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows Media Foundation\Platform
3-Once you've reached the "platform" folder, right click it, and choose "new".
4-under "new" create a "Dword" entry,
5-when prompted to name it, give it the name "EnableFrameServerMode" *case sensitive*value is 0 (zero)
6-You can now back out, and Your H264 based cam SHOULD work fine.no restart was required for me.
Last edited:
