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?

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.

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.

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.....

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.

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.

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).

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).

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.

so I'd like to ask @Germania or any of the other trusted members to take a look at your log.Cats4UI'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 problemHowever, I cannot understand why Windows 10 does not have at least 22H2 !Win 10 21H2 (19044) has not received any updates for ages - infoI wouldn't go online with several hundred open security gaps.

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!

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

Cats4U

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.

You'd better triple check. How do you think I knew you were using a depreciated Windows version? Your StreamFab.log. See last line.

2025:02:07-07:38:38 0x0000076c [Info]: Root Domain: "dvdfab"
2025:02:07-07:38:38 0x0000076c [Info]: Platform: winx64
2025:02:07-07:38:38 0x0000076c [Info]: app: system_type= Windows [Windows|macOS]
2025:02:07-07:38:38 0x0000076c [Info]: app: system_architecture= x86_64 [x86_64|i386|arm64|arm]
2025:02:07-07:38:38 0x0000076c [Info]: app: system_version= Windows 10 (10.0)
2025:02:07-07:38:38 0x0000076c [Info]: app: machine_id= 00-50-b6-61-f9-2b:68-f7-28-f2-93-e8
2025:02:07-07:38:38 0x0000076c [Info]: app: app_platform= x64
2025:02:07-07:38:38 0x0000076c [Info]: app: app_client_id= cry_s//YRgquLx+/SsnosHdLcQ==_cry
2025:02:07-07:38:38 0x0000076c [Info]: app: app_version= 6.2.1.9
2025:02:07-07:38:38 0x0000076c [Info]: app: app_launch_id= "b1ac55a4-0774-43b1-9c14-e0a24c912540"
2025:02:07-07:38:38 0x0000076c [Info]: app: applicationFilePath= "C:/Program Files/DVDFab/StreamFab/StreamFab64.exe"
2025:02:07-07:38:38 0x0000076c [Info]: app: app_args= ("C:\\Program Files\\DVDFab\\StreamFab\\StreamFab64.exe")
2025:02:07-07:38:38 0x0000076c [Info]: app: cmd_line: "C:\Program Files\DVDFab\StreamFab\StreamFab64.exe"
2025:02:07-07:38:38 0x0000076c [Info]: app: QLocale::system QLocale(English, Default, United States)
2025:02:07-07:38:38 0x0000076c [Info]: app: QLocale::c QLocale(C, Default, Default)
2025:02:07-07:38:38 0x0000076c [Info]: app: fabApplication compiled time Jan 29 2025 22:55:38

2025:02:07-07:38:38 0x0000076c [Info]: System: 64bit System Windows 10 Build 19044

Depreciated almost 2 years ago.

Besides, not all streamers use user-agent anymore. They can learn a lot more about you using Client Hints. Look it up.

Cats4U

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

Please don't screw it up if you are going to do it, otherwise I'll sic my wife on you. She'll rip you apart if she doesn't see her daily soap opera episode downloaded from Peacock. :eek:

Cats4U

Good job, @Wilson.Wang! My wife is happy that she can still get her soap opera. It took me a while to figure out what you wanted to fix. You could have left it alone. It was not a biggie. There are still plenty of real issues that have been ignored for years.

Cats4U

@Wilson.Wang - I was wrong in thinking about what you were fixing on Peacock in 6.2.2.1. I thought you were going to fix the blank, white screen that appears the first time you click on the Peacock icon.

The problem was previously written about in the topic - https://forum.dvdfab.cn/forum/streamfab-support/streamfab/457959-built-in-browser-not-loading-pages. You always have to close the display and then have to click on the icon again to be able to load up Peacock. From the other topic, it might be happening with other modules as well. For right now, I am only running Peacock, and so I don't know what is going on with the other modules. Could you please have the Developer look into this? Thank you.

TANGd878

@Wilson.Wang - I was wrong in thinking about what you were fixing on Peacock in 6.2.2.1. I thought you were going to fix the blank, white screen that appears the first time you click on the Peacock icon.

The problem was previously written about in the topic - https://forum.dvdfab.cn/forum/streamfab-support/streamfab/457959-built-in-browser-not-loading-pages. You always have to close the display and then have to click on the icon again to be able to load up Peacock. From the other topic, it might be happening with other modules as well. For right now, I am only running Peacock, and so I don't know what is going on with the other modules. Could you please have the Developer look into this? Thank you.
Cats4U

For me when this happens, if I just do a single left click in the url bar --- (anywhere in there, making it active), that somehow pushes the page load along so it loads 100%. Then I don't have to close it and open it a 2nd time. Might work for others too until fixed.

« Previous Page