topic Re: No Playback From Library On Home Computer in Arlo Pro 2

No Playback From Library On Home Computer

Skillywee — Mon, 27 Aug 2018 21:34:51 GMT

Just started happening, system and cameras work fine. However, when I attempt to playback a recording from the library, all I get is a dark screen and the word "loading", but nothing happens. This is only on my home computer, the app on my IPad and 2 android phone all work fine and will playback from library.

If I download a recording on my computer, it will play properly.

Basestation is a VMB4000.

Need some help to resolve this. Thanks

It use to work.

Re: No Playback From Library On Home Computer

jguerdat — Mon, 27 Aug 2018 21:35:08 GMT

Have you read any of the multipe threads about this same issue? MS updated things recently which caused IE and Edge to not play the videos from thelibrary. Chrome and Firefox still work fine.

Re: No playback from library on home computer.

michaelkenward — Mon, 27 Aug 2018 09:10:49 GMT

Indeed, my solution is to hit the Download link and Play rather than save.

Re: No Playback From Library On Home Computer

jguerdat — Mon, 27 Aug 2018 21:35:22 GMT

MS had a patch yesterday that fixed the problem. MS' fault, regardless of how much you want to blame Arlo.

Re: No Playback From Library On Home Computer

michaelkenward — Mon, 27 Aug 2018 21:35:36 GMT

@jguerdat wrote:

MS had a patch yesterday that fixed the problem. MS' fault, regardless of how much you want to blame Arlo.

Indeed. Had Arlo tried fixing Microsoft's problem, the knock-on effects could have been serious.

We saw that when many hardware makers rushed to fix Google's Chromecast bug and came up with solutions that broke other functions.

Re: No Playback From Library On Home Computer

jguerdat — Mon, 27 Aug 2018 21:35:51 GMT

Dang - shot myself in the foot. Tested the wrong browser - the patch didn't fix anything. DOH!

Re: No Playback From Library On Home Computer

Paul_FCCL — Fri, 31 Aug 2018 04:08:29 GMT

@jguerdat wrote:

Dang - shot myself in the foot. Tested the wrong browser - the patch didn't fix anything. DOH!

MS will likely (hopefully) fix this with its next KB####, as long as there is enough users feedback. It would help our case if we all could report the problem.