Get-WindowsUpdateLog is of no help since I guess it needs some symbols to make the data readable. Also adding KB3176929 made no difference (both of these are referenced by multiple threads) I've tried setting the GPO option here to bypass with the intent of making sure the box gets updates straight from WSUS and not from other clients.Īdding KB3176495 as a preinstall package for one of my deployments via MDT seemed to help but it isn't working now. It likes to get stuck downloading updates and never go anywhere. Someone more knowledgeable is welcome to correct me on any of this, or offer a better option.If you google the issue, it appears that Windows 1607 doesn't play nice with WSUS. I mean, there is this, but this is all quite honestly a bit over my head. I'm not sure that it's possible to implement a fix for this in OBS Studio. Toggle a registry value to restore the functionality from before the Anniversary Update (also mentioned here).Uninstall the Win10 Anniversary Update.Wait until Microsoft releases patches to workaround the issues between Win10 and the drivers.
Wait until companies with products/drivers that don't work with the new Win10 update release fixed drivers.Unfortunately, the options at the moment are: This has been discussed quite a bit since the Anniversary Update was released in early August. The Anniversary Update introduced a breaking change to this process, and device drivers for most devices have not been updated to work with the new way Microsoft wants everyone to do it now. The change that's causing issues has to do with how Windows allows applications/processes to access data from video capture devices. The Windows 10 Anniversary Update isn't causing issues with OBS Studio, it's causing issues with any kind of video capture device (webcams, game capture boxes, etc.).
0 kommentar(er)
