Streamfab 6.2.1.9 Win10, all Peacock videos showing "Can't play Right now" page

TANGd878

I have Streamfab 6.2.19, and a Peacock Premium Plan. Been trying to get series called "JAIL" (3 seasons). Every time I try this series (or any Peacock series or movie), I'm getting this same "We Can't Play This Right Now" (meaning built in browser not working with Peacock). Longest I've left the page sitting analyzing is about 15 minutes, then I gave up. If I go to my regular Firefox, and try watching any videos from there, all Peacock videos play fine. I did try clearning out all Streamfab temp files, everything in APPDATA, and tried again. Same result. Anyone else have this issue?

Cats4U

I had absolutely no problem getting a sample episode from each 3 seasons. Do a clean install and try again. If it doesn't fix things, attach your StreamFab.log.

Cats4U

I forgot to include the instructions on how to do a clean install. https://forum.dvdfab.cn/forum/streamfab-support/streamfab/451029-how-to-do-a-clean-install-of-streamfab-windows Follow the instructions exactly.

I did try clearning out all Streamfab temp files, everything in APPDATA, and tried again. Same result.

That is not enough to fix your problem.

TANGd878

Thanks for the advice. My only two cents on all of this. Considering these guys push out a new Streamfab almost weekly, to do this kind of deep and complete FULL uninstall and then reinstall, and then have to reset all one's custom settings... again and again week after week... is like a ful time job. Which I already have at a real job. It really shouldn't have to be this difficult. Actually, I actually have been doing 'upgrade' installs for the past year. And for that year, I have had zero issues with any STreamfab functionality or performance. Until this issue. I have my Windows 10 computer sort of locked down --- in the sense that I don't keep any installer-services enabled on my system. So, it makes it less ideal to have to do full uninstalls and then re-installs. Otherwise, I've loved Streamfab, but the process to keep it updated and functional, is way too much. Sigh.....

Cats4U

Oh, stop being so dramatic. It takes an extra 5 minutes. Do you know how I know? Because I do a clean install with every update. Wouldn't you rather do a clean install in an extra 5 minutes and have it work immediately, or do you prefer to sit there and watch "the page sitting analyzing" for "about 15 minutes, then I gave up"? But you don't give up. You next have to get on the forum and explain your problem and hope someone comes along to tell you how to fix your problem. That takes additional time that you could avoid if you just did a clean install.
For me, a clean install is not just an SF thing. I do a clean install with almost all my program updates.

TANGd878

Followed the clean install steps to the letter (Wise uninstaller). Completely wiped (which I confirmed with Regalyzer). Then did fresh install of 6.2.1.9. Once all installed, went to Peacock, logged in, went to JAIL page, and when Streamfab tried to analze... the exact same issue. No difference. Logs attached.

TANGd878

And.... Streamfab working for me everywhere else. pluto, tubi, roku, discovery, hbo, amazon (to name the big ones) all working perfectly (that's before and after the full uninstall).

Cats4U

Other than the fact that you are using 21H2 (depreciated) of Windows 10 rather than 22H2 (current and maintained), nothing really strikes me. I'm not as good at reading the logs as others here, so I'd like to ask @Germania or any of the other trusted members to take a look at your log.

I just did another series of Jail downloads and, again, they downloaded perfectly. Since no one has posted any problems with Peacock since before 6.2.1.3, it looks like it is something on your end (but I don't know what).

TANGd878

Well, I do appreciate your reply. Yeah, I have some work-related SQL db programs that essentially break when I move up to 22H2 (ongoing issue with the DMS company). So, I've been cruising with 21H2 for last few years (if you can believe it). I don't think it's that, though... since I was doing fine with Streamfab & peacock when I was at 6.2.1.7/6.2.1.8 and earlier. It's only on this latest version where I'm getting this isolated Peacock hiccup. Related question, sort of. When I queue up a ROKU video in SF, I'll often see (and it's no more than maybe 1.5 seconds), a similar "Browser not compatible" message, which then redirects back to the Roku landing page. But, no issue there, because concurrently as that happens, SF's analysis always completes and pops up the selection menu ---> and from there, I'm good to go. Just wonder if anyone else ever sees the same thing? I've just always assumed it was part of the function of SF's internal browser (which is there primarily to faciliate the stream grabs). Speaking of which, just curious... is there a .ini or other config file that stores the settings for SF"s internal browser? I ask because I wonder if, like I do in Firefox, could I fake a different useragent string with an override? Something that might trick Peacock into believing the version is fine? I'm in particular ESR fork of Firefox, and I frequently have to fake the useragent to get certain websites to play nice. I'll keep digging. thanks again.

Germania

so I'd like to ask @Germania or any of the other trusted members to take a look at your log.
Cats4U

I've never an Peacock account so i can't test anything or compare log ..
.. and I can't see any critical in the log - so I don't know the problem

However, I cannot understand why Windows 10 does not have at least 22H2 !

Win 10 21H2 (19044) has not received any updates for ages - info
I wouldn't go online with several hundred open security gaps.

TANGd878

Well, this is pretty crazy, thought I'd share. I spent the afternoon doing full uninstalls of 6.2.1.9 and then fresh installs starting at version 6.2.1.4, on up through 6.2.1.8, to see if any version would display Peacock for me (instead of that Widevine/DRM "Can't play right now" page). All those versions gave me bupkis. Same exact result. Same "can't play" page. Then, in opposition to what everyone has been saying on here, I did a fresh clean install of 6.2.2.0. And.... well... yup. 6.2.2.0 solved the Peacock issue. This latest version is letting me analyze and grab the Peacock videos without any issues. I guess I'll just steer clear of Amazon.com!

TANGd878

continued... just FYI...
Here's what I actually had to do to get Peacock working for me. And yeah.... this is beyond odd. So, even with 6.2.2.0, when I first opened SF, and called for "Peacock" from the VIP menu, any attempts to get to content gave me that cute kitty "we can't play this right now" redirect. When I see that, I know SF wont' complete Analysis. Tried it multiple times. Then I exited, cleared all cache, temps, appdata, logs. Then, went back in, but instead of clicking on Peacock from the VIP menu, I typed in peacock.com in SF's url bar. That brought up same, correct Peacock, but... SF doesn't recognize site as official Peacock that way. So, I get no analysis. Best I get is a lower right "MPD" clickable icon (though technically, clicking on MPD icon doesn't actually work).
Here's what I discovered, however. This SF manual Peacock page loads and plays videos 100% fine. Let's me play any videos... and never see "can't play right now" redirect in this instance.
But wait! Gets even weirder. While leaving that manual SF Peacock window open, If I then open Peacock from the SF VIP link. that instance will then work (no redirect). So yes, at that point, 2 Peacock tabs need to be open... the manual which I can't actually download from, and.... the suddenly functional working VIP Peacock --- which works fine and I can dl from --- as long as I keep that manual instance open.
To me, it hints at some kind of sporadic, oddball hiccup in the SF code. I'll send them a support ticket and at least make them aware. Maybe I'll get lucky with 6.2.2.1 (which has to be coming fairly soon...)

Chameleon

Peacock works fine on my Windows 10 machine

Cats4U

Hey, Chameleon, haven't seen you in a while.
There seems to be only one person having a problem with Peacock, and I don't know why other than he is using a depreciated version of Win10. What worries me is that if he sends in a ticket, the developer might try to fix something in Peacock and screw it all up for the rest of us that aren't having any problem.

Wilson.Wang

peacock.com will be also added to the support list in next version.

Wilson

Cats4U

peacock.com will be also added to the support list in next version.

Great! /s
That means that Peacock will be out of action for the next few updates. Typical, one step forward, two steps back. Why fix something that nobody (except one New Member with a depreciated Windows version) is having a problem with? Peacock has been downloading perfectly since 6.2.1.3.

MrGrackle

Did we go into our peacock account via a web browser and log out of all devices? Is that a thing any more?
@Wilson.Wang does that mean we may get h265 in the next version? That would be nice!

chris01

Did we go into our peacock account via a web browser and log out of all devices? Is that a thing any more?
@Wilson.Wang does that mean we may get h265 in the next version? That would be nice!
MrGrackle

h265 will require L1 so you can forget about this being supported.

TANGd878

While some are gung ho about my deprecated version of 10 (21H2) being a factor, it's not. I use Firefox 128.7.0esr and stream Peacock on this very same PC daily, all the time. Streaming a show as I type in fact. And everything plays in FF perfectly... with 21H2. Amazing, right? I have never seen that "Can't play right now" message in FF on this PC. Also, double checked, and pretty sure actual build info not part of browser's useragent info sent reported to sites. It's just O/S, browser brand, version, o/s architecture, etc. That... "Can't play message"... is something I'm getting pretty much randomly, only through SF's internal "chrome" browser (yet another reinforcer as to why I sort of loathe chrome). Anywhooo... I've been using SF for 2 years now ("new user"). All on this PC. And this is first time I've had this hiccup redirect issue with Peacock. Based on their track record, I'd bet dollars to donuts, it's something within the SF code. All in the name of progress....

Wilson.Wang

peacock.com is also redirected to the peacocktv.com, normally to say, it should be supported as the VIP services.

Coding glitch :(

Wilson