this is still an issue despite the update. The only way I can get the weather to update in a timely manner (we're talking 2+ hours) is to completely reboot the machine...

I saw in the last post from admin - the update was to make sure the weather will update in 1-2 hours? Is there no way to get it to update faster than that? I don't expect it to be live, but 30-45 minutes seems much more reasonable than 1-2 hours.

We really don't have a lot going on in the weather scene (although - isn't this system designed to handle multiple animations? The preview campaigns are all super busy, showing the capability of the software..)

There's only one animation for the current weather conditions, otherwise there are static weather icons, temperatures and a background image. That's it. I deleted & re-uploaded the background image in case that caused it, but that didn't help.

I don't have time to go through and remote in and delete all the cache folders right now, I tried one... we'll see if that works.

We have 30 units, about half of them are totally freezing on one of our weather screens. When I remote into them, I see the "SignagePlayer.exe has stopped working..." message, and the only way to fix is to totally reboot. It happens every couple days, and only on half the units.

This makes no sense whatsoever... I don't know why it wouldn't be happening on all of them, and why it wouldn't be happening every time that weather scene plays. Feels like there's gotta be a glitch somewhere. Is anyone else having issues with anything similar?

I'm also receiving this error ("Download failed There was an error downloading the update. Error# 16824") while trying to update from Version 5.0.80 on a Mac -- so I can't use the uninstaller listed above, as it's a Windows-only program. What do you suggest I do?

We're server customers, we updated our players to the 5.0 version and were happy to see the weather component working again. However, I've noticed the 'current conditions' haven't updated since this morning on any of our machines.

Whats up with that? Is this a weather.gov issue, or are there still issues with this component?