Scheduled Shows are not being updated when Guide updates

When my DVR has exhibited this behavior, I have soft rebooted it and it has corrected the issue.  I used to do so about every two weeks just to make sure, but I quit doing that and my wife hasn't complained lately... she may just be manually recording the episodes that get dropped.

@JefferMC , I can do a soft reboot, but having to remember to do that every two weeks seems like a cheesy work around. I can also "fix" it by just making a change in any of the Series-that seems to make it synch with the Guide.  Seems like AT&T should be able to fix the bug?

I do not think there is a development team working on improvements for the TV receiver software at this time.  They may have somebody who can do urgent security fixes.  Microsoft sold the Mediaroom platform (on which U-verse TV is based) to Ericsson.  Ericsson spun it off.  AT&T hasn't purchased a new TV device since the Ericsson sale, and is still running on the original software platform.

This problem has existed for at least a decade and I expect will continue until U-verse TV, as it currently exists, is shut down.

It does seem odd that this issue has only started in the last month or so. Before that it’s been working fine for many years.

@JefferMC When you say you soft rebooted dvr and it fixed the issue which type of reboot are you referring to?  Are you talking about when you use the 1)remote control to go to menu and restart receiver?  2) when you hold down power button on receiver for 10 seconds? 3) unplugging dvr and plugging back in? 4) the "non-destructive" one that I always have trouble getting to work, is that the unplug and plug in 3 times one? 5) a destructive reboot?

Does that actually solve the problem the of series not automatically scheduling at all?  @marchem 's issue seems to be almost identical to the one affecting miami, the only difference being when he does the work around it fixes all his 8 series, when the rest of us do the settings change workaround it only fixes that 1 series and we have to do it for all series individually.

While the software is ridiculously ancient, there's no reason it shouldn't be stable at this point.  To have a bug pop up years later to customers who've never had it before is a absurd.  

Even crazier is that mediaroom runs on windows CE 5.0.1400, a mobile operating system that was never really intended to be used as dvr software (other than that it had low hardware requirements so att could buy cheap low spec equipment).  It was released in 2004 and Mainstream Support Ended October 13, 2009 and Extended Support Ended October 14, 2014.  Meaning it's been over 8 years since it last received any security updates, it's amazing all of this equipment hasn't been hacked and turned into a botnet at this point lol.

hmm after some quick googling, it does seem Mediaroom still exists and is now part of an Erickson company/division spun off as  "MediaKind" they apparently offer way more modern software including newer versions of Mediaroom that are android based but at&t apparently never bothered to upgrade.  

When you say this issue as existed for a decade I only found the posts from the midwest and california from 3-4 years ago? are there other older posts we should be looking at?  Has anyone ever identified a root cause? a reason for the regionality?  a solution of any kind?  Does a dvr swap or erasing dvr ever actually solve it?  Does a "line issue" ever cause this problem(thats what one department is convinced the problem is ).  

I mean #2, Soft reset by holding the power button in for 10 seconds, which should be identical to #1.

I'm not going to second guess design decisions made by Microsoft 20 years ago as to whether Windows CE was a viable choice.  If the tool you have is a hammer, then all problems look like a nail.  The U-verse TV product has been a Phase 4 business for over 5 years.  Expecting any improvement at all is not rational.

I did a reboot this morning (press power button for 10 seconds) and that did update the Scheduled list, which had gotten out of date again.

I did go through the troubleshooting with the remote and menu. Got to the point of it wanting to do a reboot. I said yes, and it sat there for 10 minutes with the little white wheel spinning (and live TV playing behind it) until I got tired of waiting and cancelled it. So much for the built in troubleshooting.

@JefferMC I haven't expected any improvements or new features in years, I just want it to continue functioning the same way it has for over a decade ago and 3 weeks ago still was working. 

hmm I've only tried 1) and 3).  I guess I'll give #2 a try on the off chance it manages it fix something.  Having to go through all series by series every 10 days and change a setting is not really a viable long term solution.  

update: gave a #2) reset on dvr+all stbs a shot.  Did not accomplish anything.  

Also do you know what the IP-ARC team is? that's newest team they claim they are working with.  

Just sent @ATTHelp a Twitter DM describing my issue. I'll let you all know what happens.

I'm having the same problem in Nashville. It started in middle of November. Since it started, they have sent me a new DVR box and the series record issue is still there. Rebooting doesn't change anything for me. The only way I found is having to change record settings to record all, then back to record only new. This only works for whatever shows are in my program list. Any new shows that come up the next day I have to repeat this same prosses.

@pyates34 it's ridiculous that this keeps happening to different regions.  You arent going to like my answer.  1st thing decide how much time and energy you are willing to spend solving this vs. Leaving uverrse tv (which you can never return to as it's no longer offered).

See my giant post off all the steps we took when it hit south Florida 

https://forums.att.com/conversations/watching-uverse-tv/uverse-dvr-series-scheduled-recordings-are-not-functioning/625ce61d453e2f45c8bcf945

In the end the only thing that solved it was contacting corporate making friends with a guy at corporate customer support.  Gathering account #s to prove multiple customers in region were affected thus it being a server side issue and not an issue affecting a single customers equipment.  

Eventually corporate guy was able to find a friend who was a VP in uverse division(which barely exists still) who was able to quickly solve it as it's some sort of minor software glitch.  

To make it worse att claims everything is proprietary and confidential so they refuse to say what the issue is or how they solved it each time.  So every time it happens customers have to start all over and fight to have it fixed in their region.  

Good luck! But prepare yourself for battle.  

@pyates34 , good luck. I’ve got no idea how my issue got resolved, but it finally did and now it all works fine.  

My finally started working correctly for 3 days in a row. I hope it continues.