Most Recent Win 10 Patches Have Killed My Clients

[jusjoken]

Originally Posted by Telecore

Just wanted to confirm - I upgraded from 9.0.11.483 to 9.0.13.536 - both server and PC client. I already had kb4013429 installed prior to updating and the PC client crashed after updating. Uninstalling kb4013429 fixed the problem- however the previous SageTV client version was working with kb4013249.

What was the timing of these changes? I understand the kb was released March 14. From my understanding the kb breaks some mpeg decoders that use a specific dll that Microsoft changed. I cannot see anything between 9.0.11 installer and 9.0.13 that would affect this.

k

[Telecore]

Actually now that you mention it, I am not 100% sure that I ran the client after 3/14 - it's possible that it was broken and I didn't use it. I'll try running the client from my work PC tomorrow (our Sage server at work is still at 9.0.11.483) and see if it works with the kb.

UPDATE: Sage Client at work (9.0.11.483) crashes - I think the update occurred after the last time I used the client, sorry for the confusion.

[BobbyDing]

Looks like Microsoft may have fixed this problem in a new update KB4015438 (released on March 20th).

http://www.catalog.update.microsoft....px?q=KB4015438
.

My win 10 had the issue. Now Sage works again.
.

[korben_dallas]

yay, my bitstreaming is back

[GKenny]

Is anyone else still having issues? My SageTV service has been crashing quite regularly for the last week. I first attempted to do a system restore... no restore points. I next uninstalled the windows updates as recommended... No joy. I then installed the windows update that was supposed to fix the problems... still no joy. Next, I upgraded to the Windows Creators Update... This seemed to help a little bit, but crashes came back. Out of frustration, I restored Windows 10 to a fresh install, reinstalled Sage and the problem remains. I have done a memory and disk check - all OK. I installed SageTVSetup_9.0.14.568_R1.012.exe and let it set up Java 7 update 79 and the Microsoft Visual C++ 2010 & 2015. Not sure what else to try now. I can get the logs if that may help.

[EnterNoEscape]

Originally Posted by GKenny

Is anyone else still having issues? My SageTV service has been crashing quite regularly for the last week. I first attempted to do a system restore... no restore points. I next uninstalled the windows updates as recommended... No joy. I then installed the windows update that was supposed to fix the problems... still no joy. Next, I upgraded to the Windows Creators Update... This seemed to help a little bit, but crashes came back. Out of frustration, I restored Windows 10 to a fresh install, reinstalled Sage and the problem remains. I have done a memory and disk check - all OK. I installed SageTVSetup_9.0.14.568_R1.012.exe and let it set up Java 7 update 79 and the Microsoft Visual C++ 2010 & 2015. Not sure what else to try now. I can get the logs if that may help.

I am not, but it might be prudent to roll back to 9.0.13 and verify if there is still a problem on that version.

[GKenny]

I tried downgrading to a couple versions... still no luck. It seems like there is a conflict with the Hauppague tuners that I'm using. I can watch previously recorded video on clients or server without problem. Once it starts recording, the server will crash between 30 seconds to 5 minutes. I'm wondering if we can kill a flock of birds with one stone. How easy would it be to update OpenDCT to support all video sources? Could this open up the possibility of using all the tuners on the Hauppauge capture cards and other cards that are limited by the old BDA architecture?

[EnterNoEscape]

It's a significant effort. Honestly, while I was thinking that I was going to add support to OpenDCT for these things, I think it would be better for someone to re-write the BDA support for SageTV. I am adding some capabilities to SageTV that would make that the easier approach.

[Tiki]

Originally Posted by GKenny

I tried downgrading to a couple versions... still no luck. It seems like there is a conflict with the Hauppague tuners that I'm using. I can watch previously recorded video on clients or server without problem. Once it starts recording, the server will crash between 30 seconds to 5 minutes. I'm wondering if we can kill a flock of birds with one stone. How easy would it be to update OpenDCT to support all video sources? Could this open up the possibility of using all the tuners on the Hauppauge capture cards and other cards that are limited by the old BDA architecture?

So, have you reviewed your logs (or posted them for someone else to review), to try to figure out what's causing the crash? Have you noticed any pattern to when the crashes occur?

[GKenny]

I was planning to write my own network encoder module to handle Hauppague tuners (and I still may). Hauppague sent me their SDK and when I installed that, my Sage crash problem went away.

Now, the only benefit of creating the network encoder is to bypass SageTV's lack of support for the multi-tuner cards like the WinTV-quadHD tuner.

[SHS]

Originally Posted by GKenny

I was planning to write my own network encoder module to handle Hauppague tuners (and I still may). Hauppague sent me their SDK and when I installed that, my Sage crash problem went away.

Now, the only benefit of creating the network encoder is to bypass SageTV's lack of support for the multi-tuner cards like the WinTV-quadHD tuner.

I think the issues is more along the line with sagetv exe are so out date that need be update or even rewritten.
I wish the best of lucky I and min people would love see this happing but you do know that both WinTV-dual/quadHD tuner should be supported under Ubuntu 17.04 on up.