Navigation section

Is Windows preventing 3 browsers from streaming msnbc I can view in apple device

F

frustratedtoujours

Extraordinary Member
Joined
Nov 27, 2013
Messages
17
My access to MSNBC is good and does work. I have 3 browsers, FF, Edge, & Chrome and all 3 fail to receive the stream, the circle keeps circling. I can get the stream on my iphone using my WIFI, so I'm ruling out my WIFI provider.
 

Solution
ChatGPT
Thanks — good clarification. You were trying the Test‑NetConnection text in the wrong place (that’s why it failed). Let’s do three simple, safe steps (exact keystrokes/commands) so we can tell for sure whether this is an IPv6 path problem — then we’ll try the Windows change that usually fixes the “IPv6 tried but failed” behavior.
I’ll keep commands copy/paste‑ready and explain what to paste back.
1) How to run the PowerShell reachability test (exact, step‑by‑step)
  • Why: Test‑NetConnection runs only in PowerShell (not in the old cmd.exe). It will tell us if your PC can open a TCP connection to the failing host (and whether Windows is trying IPv6 and failing). See Microsoft docs for this cmdlet.
Steps:
  1. Click Start → type...
Sort by date Sort by votes
Thanks — this is a good start (iPhone working on the same Wi‑Fi narrows the problem to the PC/browser side). Let’s go through a short, prioritized checklist and a couple of targeted diagnostics so we can pinpoint why Firefox / Edge / Chrome just show the spinning circle.
Short troubleshooting checklist (do these one at a time, testing the stream after each step)
  1. Try a private window
    • Chrome/Edge: Ctrl+Shift+N. Firefox: Ctrl+Shift+P.
    • Open the MSNBC live URL (MSNBC Live: Stream the latest TV shows or the exact page you use). If it works in private, a cookie/extension is the likely culprit.
  2. Disable all extensions (especially ad blockers, privacy/privacy‑badger, VPN/smart DNS, security extensions)
    • Disable them and retry. If it works, re‑enable extensions one‑by‑one to find the offender.
  3. Check DRM / content‑decryption modules
    • Chrome/Edge: go to chrome://components (or edge://components) and update “Widevine Content Decryption Module” (click Check for update).
    • Firefox: Settings → General → make sure “Play DRM‑controlled content” is checked. Firefox will download Widevine automatically when enabled.
      DRM missing or blocked is the most common cause of streams that never start.
  4. Clear site data for msnbc / nbc domains
    • Chrome/Edge: Settings → Privacy & security → Cookies and other site data → See all cookies and site data → search msnbc/nbc and remove.
    • Firefox: Settings → Privacy & Security → Cookies and Site Data → Manage Data → remove msnbc/nbc entries.
  5. Check autoplay/media permissions
    • Chrome/Edge: site settings (lock icon in address bar) → Permissions → make sure Autoplay and Sound are allowed and Nothing related to Protected Content is blocked.
    • Firefox: lock icon → Permissions; also ensure sites are allowed to play audio/video.
  6. Test with another network quickly
    • Temporarily hotspot your phone to the PC and try the stream. If it works on phone hotspot but not on your Wi‑Fi network even though phone on Wi‑Fi works, that points to a PC‑specific setting (proxy/hosts/antivirus).
  7. Check system proxy / hosts file / DNS
    • Proxy: Windows Settings → Network & internet → Proxy. Ensure “Use a proxy server” is Off (unless you intentionally use one).
    • Hosts: open Notepad as Administrator and open C:\Windows\System32\drivers\etc\hosts — verify there are no entries blocking msnbc/nbc or related CDN domains.
    • If you use custom DNS or a router SmartDNS/AdGuard Home, try switching to your ISP DNS temporarily.
  8. Temporarily disable antivirus/firewall (brief test)
    • Some security suites block streaming CDNs. Disable real‑time protection briefly and retry (be mindful of security; re‑enable after test).
If the above doesn’t fix it, collect this diagnostic info and post it here
  • Browser and exact versions for each (Chrome: Help → About Chrome; Edge: Help → About Microsoft Edge; Firefox: Help → About Firefox).
  • Are you logged into MSNBC (or required cable provider)? Do you see a login prompt or any error text?
  • Any extensions you always run (uBlock, Privacy Badger, DuckDuckGo extension, Avast/AVG browser plugin, VPN client)?
  • Does other DRM streaming (for example Netflix in the browser or Amazon Prime video) play or also fail?
  • The browser console output: open Developer Tools (F12) → Console and Network, then reload the live page and copy/paste the top errors. Typical useful errors are messages about “DRM”, “EME”, “Widevine”, 403/404/502/403 from CDN, or CORS errors.
Quick commands/links to run now
If you paste the Console error text (or a screenshot), I’ll interpret it and give the exact next step. If you prefer, tell me the browser you want to debug first and I’ll give a short step‑by‑step for that browser only.
 

Upvote 0 Downvote
I went through steps 1 - 8 with no change.
So jumping to "If the above doesn’t fix it, collect this diagnostic info and post it here"

item 1: Given historically withOUT exception I have always been able to achieve in either Chrome or Edge what was not achievable in Firefox, I fail to be convinced at all that fixing the 3 browsers would change the outcome. And, in fact, I only care about the outcome in FF and it is the browser I use by default.

item 2:I do not access MSNBC on my TV I only access it on my PC and iphone using my DISH loggon info, which work without issue.

item 3: Apparently I do not use any extensions except apparently Duckduckgo's whatever which I removed, which changed nothing.

item 4: other streaming services work just fine (Hulu and Paramount+)

item 5: "The browser console output: open Developer Tools (F12) ? Console and Network, then reload the live page and copy/paste the top errors."
I have absolutely NO CLUE WHAT this is, how to get it, do it, or huh? I need instructions to continue with this item.

FIREFOX is the only browser I wish to fix.
 

Upvote 0 Downvote
Good — thanks for the clear update. Since you only care about Firefox, let’s focus entirely on capturing the two diagnostic artifacts I need from Firefox: the Console log (for DRM/JS errors) and a Network HAR (full request/response waterfall). Those will show what the player is doing (license requests, 403s, blocked resources, CORS, EME/Widevine errors, etc.) so I can tell you the exact next step. This follows the checklist I suggested earlier. u
  • A copy of the Firefox Console output from the MSNBC live page (after a fresh reload).
  • A Network HAR file captured while reloading the same page (contains all requests the player makes).
  • Your Firefox version (Help → About Firefox).
Step‑by‑step: capture Console + Network HAR in Firefox
1) Open Firefox and the MSNBC live page you normally use (leave it on the spinning circle).
2) Open Developer Tools: press F12 (or Menu → More Tools → Web Developer Tools). You’ll see tabs like Inspector, Console, Network, etc.
3) Console log (quick, reliable method)
  • Click the Console tab.
  • Enable “Persist Logs” (click the small gear icon in DevTools and check Persist Logs) so messages survive the reload.
  • Right‑click inside the console output → Select All → Copy, then paste into Notepad and save as msnbc-firefox-console.txt.
    • (If you prefer, you can use the console’s export/save option if your Firefox shows one — but Select All / Copy works every time.)
      4) Network HAR (this is crucial)
  • Click the Network tab in DevTools.
  • Check “Disable cache” (so nothing is served from cache), and enable “Persist Logs” if available.
  • Reload the page (F5). Let it attempt to load until the spinner appears again and the page stops adding network activity.
  • Right‑click any row in the network list → “Save all as HAR” (or “Save HAR”) and save the file as msnbc-firefox-network.har.
  • If your Firefox version uses a slightly different label, look for any Export/Save/Save all as HAR option in the Network pane — the network tool supports exporting HARs.
    5) What to attach heles (msnbc-firefox-console.txt and msnbc-firefox-network.har) to your reply. If you can’t attach files, paste the first 50 lines of the console output into your reply and tell me whether any Network requests to license or drm endpoints show 403 / 401 / blocked / CORS in the HAR (I can read key lines there too).
    6) One more quick check (before upload)
  • Confirm Firefox DRM settings: open about:preferences#general and make sure “Play DRM‑controlled content” is checked. Also check about:addons → Plugins and look for “Widevine Content Decryption Module” — click the gear and choose “Check for Updates” if present. If either setting is off, enable it and try again, then capture logs fresh. (This was in the earlier checklist.)
What I’ll look for when you attach the fies mentioning EME, Widevine, Encrypted Media, “DRM”, “EME”, or errors like “Failed to request license”, “Playback error”, or CORS/blocked-by-client.
  • Network HAR: license endpoints (often to domains containing license, drm, or widevine), HTTP status codes (403/401/500), or resources blocked by the client (mixed content / blocked by extension). These reveal whether the problem is a DRM/license rejection, CDN block, or local client blocking.
If you want to try one quick test before collecting logs
  • Open Firefox in Troubleshoot Mode (Help → Troubleshoot Mode…). That disables all extensions without changing your profile. Try the stream; if it works, we know an extension/interference is the cause. If it still fails, capture the HAR/Console as above and attach them.
Upload instructions
  • Use the forum’s attachment button when replying and attach the two saved files. If you prefer not to attach files, paste the console output (first ~50 lines) here and tell me the top few failing request URLs you see in the Network tab (or paste a short snippet of the HAR around license requests).
If you’re unsure while doing any of the above, tell me your Firefox version and I’ll send a tailored one‑page set of screenshots/keystrokes for that exact version. Once I have the console + HAR (or a pasted snippet), I’ll read them and give the exact fix (e.g., enable/update Widevine, remove a blocking preference or host entry, or reconfigure your security suite).
 

Upvote 0 Downvote
I'd attach the file but it won't.
I can't even type the lette that comes between q and s he*e
 

Upvote 0 Downvote
Thanks — that helps. Two quick points before we continue:
  • The steps I asked you to run for grabbing the Firefox Console + Network HAR are here if you want to re‑check them. oard letter is failing (the key between Q and S is W), that explains both the trouble typing and why the forum attach/save dialog “felt” like it wouldn’t accept your input — but it’s fixable. See the keyboard troubleshooting checklist below.
What you can do rig is easiest)
1) Paste the console output into the forum post (no attachments required)
  • Reproduce the failing page in Firefox so the spinner is visible.
  • Press F12 → Console tab → enable “Persist logs” → Reload the page.
  • Right‑click inside Console → Select All → Copy (Ctrl+C) → come back to this reply and Paste (Ctrl+V). If you can’t type the letter W anywhere, you can still paste — copying & pasting doesn’t require typing. (See the HAR option below if you can’t attach files.)
2) Use the On‑Screen Keyboard (fastest local fix for a dead letter)
  • Press Win+R, type osk, Enter → the On‑Screen Keyboard opens. Click the W key on it to type W where needed (for filenames, form fields, etc.). This avoids plugging in anything else.
3) Upload the HAR/console files from yourC typing problem)
  • Save the HAR and console .txt on the PC.
  • Transfer them to your iPhone quickly (AirDrop, iCloud Drive, OneDrive, or email).
  • Open the forum thread on your iPhone and use the Attach button to upload the two files. This avoids typing on the broken key entirely.
4) Alternate attach methods (no typing required)
  • Drag & drop files into the post reply box (your browser supports this).
  • Rename the file in File Explorer using Right‑click → Rename — if you can’t type W during rename, use the On‑Screen Keyboard (osk).
5) If none of the above work, tell me this and I’ll guide you s you can paste text into the reply box (yes/no).
  • If you can open the On‑Screen Keyboard (Win+R → osk worked / didn’t work).
  • Whether you prefer me to walk you through exporting the HAR and emailing it to yourself (so you can upload from phone).
Which would you like to try first? If you want to paste the console output here, paste the first ~50 lines and I’ll read them for the DRM / license / network errors (those are the most telling signs). If you prefer I walk you through using osk or transferring via iPhone, tell me which and I’ll post the exact keystrokes/screens to follow.
 

Upvote 0 Downvote
Ignoring unsupported entryTypes: longtask. _app-36f48cc0d58e6a73.js:5:132167
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://e12872de91aaca7a39095801bdf5f168d87912fa.ipv6.cws.conviva.com/0/wsg. (Reason: CORS request did not succeed). Status code: (null). 2
Cookie “_sp_root_domain_test_1755626012197” has been rejected for invalid domain. live
Cookie warnings 15
Partitioned cookie or storage access was provided to “<URL>” because it is loaded in the third-party context and dynamic state partitioning is enabled. 5
[AccessEnabler.js][info] Version: 4.7.1-5a99613 RELEASE AccessEnabler.js:1:130588
[AccessEnablerProxy.js][info] Version: 4.7.1-5a99613 RELEASE AccessEnablerProxy.js:1:5601
Partitioned cookie or storage access was provided to “AccessEnablerProxy 4.7.1-5a99613 because it is loaded in the third-party context and dynamic state partitioning is enabled. AccessEnablerProxy.js:1:5019
This page is in Almost Standards Mode. Page layout may be impacted. For Standards Mode use “<!DOCTYPE html>”. activityi;src=8168974;type=msnbc0;cat=msnbc0;ord=6277201461436;npa=0;auiddc=54426428.1755564967;pscdl=noapi;frm=0;_tu=IFA;gtm=45fe58i0v9190897070za200zd9190897070;gcd=13l3l3l3l1l1;dma=0;dc_fmt=2;tag_exp=101509157~103116026~103200004~103233427~104527907~104528501~104684208~104684211~104948813~105033766~105033768~105103161~105103163~105231383~105231385;epver=2;dc_random=IZImpJDniFdqDIYvb8pLd7BrCV8cUZZHbg;_dc_test=1;~oref=MSNBC Live: Stream the latest TV shows
Cookie “AWSALBCORS” rejected because it has the “SameSite=None” attribute but is missing the “secure” attribute. msnbc
Cookie “AWSALBCORS” rejected because it has the “SameSite=None” attribute but is missing the “secure” attribute. msnbc
Cookie “AWSALBCORS” rejected because it has the “SameSite=None” attribute but is missing the “secure” attribute. usermetadata
Cookie “AWSALBCORS” rejected because it has the “SameSite=None” attribute but is missing the “secure” attribute. usermetadata
Cookie “AWSALBCORS” rejected because it has the “SameSite=None” attribute but is missing the “secure” attribute. usermetadata
Cookie “AWSALBCORS” rejected because it has the “SameSite=None” attribute but is missing the “secure” attribute. usermetadata
Cookie “AWSALBCORS” rejected because it has the “SameSite=None” attribute but is missing the “secure” attribute. shortAuthorize
Cookie “AWSALBCORS” rejected because it has the “SameSite=None” attribute but is missing the “secure” attribute. shortAuthorize
Cookie warnings 2
This page is in Quirks Mode. Page layout may be impacted. For Standards Mode use “<!DOCTYPE html>”. cei
XML Parsing Error: no root element found
Location: https://sp.auth.adobe.com/adobe-services/shortAuthorize
Line Number 9, Column 121: shortAuthorize:9:121
[Omega]
Object { appVersion: "6.10.0", cvsdkVersion: "11.0.1" }
4856.d7d4c42502a0e69b.js:1:405674
### YALC TEST: Omega Player component successfully loaded! 4856.d7d4c42502a0e69b.js:1:679687
EmeEncryptionSchemePolyfill: Waiting to detect encryptionScheme support. 6d060570.567bee80c891fdf7.js:1:342176
McEncryptionSchemePolyfill: Waiting to detect encryptionScheme support. 6d060570.567bee80c891fdf7.js:1:343822
### YALC TEST: Omega Player component successfully loaded! 2 4856.d7d4c42502a0e69b.js:1:679687
McEncryptionSchemePolyfill: No native encryptionScheme support found. Patching encryptionScheme support. 6d060570.567bee80c891fdf7.js:1:344446
[mps:hb:config] window.screen.width = 1920 load-nbcnews-bento.js:3869:9
****** [mps] REDIRECTED: false → mps.nbcuni.com ****** live line 324 > injectedScript:2:28
The script from “https://usasync01.admantx.com/adman...":"URL","body":"https://www.msnbc.com/live"}” was loaded even though its MIME type (“text/plain”) is not a valid JavaScript MIME type. live
[mps:loadJS] async:true, service?request=%7B%22decorator%22%3A%22template.nbc_template%22%2C%22key%22%3A%2262263fff3cc1d07f85c7f8261a0c8f7dc096b35f59c82a713f20a9db8d562ff2%22%2C%22method%22%3A%22descriptor%22%2C%22filter%22%3A%22default%22%2C%22mode%22%3A%22async%22%2C%22type%22%3A%22URL%22%2C%22body%22%3A%22https%3A%2F%2Fwww.msnbc.com%2Flive%22%7D load-nbcnews-bento.js:735:19
[mps:PM3] JS LOADED: Admantx load-nbcnews-bento.js:735:19
[mps:loadJS] async:true, pub.js load-nbcnews-bento.js:735:19
The following functions are deprecated: googletag.pubads().setTagForChildDirectedTreatment(), googletag.pubads().clearTagForChildDirectedTreatment(), googletag.pubads().setRequestNonPersonalizedAds(), and googletag.pubads().setTagForUnderAgeOfConsent(). Please use googletag.pubads().setPrivacySettings() instead. pubads_impl.js:19:244210
Ignoring unsupported entryTypes: layout-shift. 24610.js:2:39415
[mps:loadJS] async:true, 24610.js load-nbcnews-bento.js:735:19
[mps:hb:dv] Call onDvtagReady load-nbcnews-bento.js:4054:51
Cookie “mptest” has been rejected for invalid domain. 7 live
For '$t sigma_cvsdk_playerInit', the corresponding attribute value of '$t mvpdId' must be a string, number, boolean, or null. mparticle.js:39:45549
Cookie “mptest” has been rejected for invalid domain. 2 live
[mps:patch] adloads empty refreshed live line 324 > injectedScript:5:30
InstallTrigger is deprecated and will be removed in the future. p.js:7:26510
[10:54:33 GMT-0700 (Pacific Daylight Time).865] [ERROR] [MediaHeartbeat] API call trackSessionEnd is unsupported in the current state. live line 2 > injectedScript:9:8583
Cookie “mptest” has been rejected for invalid domain. 3 live
Source map error: Error: request failed with status 404
Stack in the worker:networkRequest@resource://devtools/client/shared/source-map-loader/utils/network-request.js:43:9

Resource URL: https://sp.auth.adobe.com/entitlement/v4/AccessEnablerProxy.js
Source Map URL: AccessEnablerProxy.js.map
Source map error: Error: request failed with status 404
Stack in the worker:networkRequest@resource://devtools/client/shared/source-map-loader/utils/network-request.js:43:9

Resource URL: https://entitlement.auth.adobe.com/entitlement/v4/AccessEnabler.js
Source Map URL: AccessEnabler.js.map
Navigated to MSNBC Live: Stream the latest TV shows
Ignoring unsupported entryTypes: longtask. _app-36f48cc0d58e6a73.js:5:132167
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://e12872de91aaca7a39095801bdf5f168d87912fa.ipv6.cws.conviva.com/0/wsg. (Reason: CORS request did not succeed). Status code: (null). 2
Cookie “_sp_root_domain_test_1755628130343” has been rejected for invalid domain. live
[AccessEnabler.js][info] Version: 4.7.1-5a99613 RELEASE AccessEnabler.js:1:130588
Cookie warnings 21
Cookie “AWSALBCORS” rejected because it has the “SameSite=None” attribute but is missing the “secure” attribute. AccessEnablerProxy.html
Source map error: Error: request failed with status 404
Stack in the worker:networkRequest@resource://devtools/client/shared/source-map-loader/utils/network-request.js:43:9

Resource URL: https://entitlement.auth.adobe.com/entitlement/v4/AccessEnabler.js
Source Map URL: AccessEnabler.js.map
Partitioned cookie or storage access was provided to “<URL>” because it is loaded in the third-party context and dynamic state partitioning is enabled. 6
This page is in Almost Standards Mode. Page layout may be impacted. For Standards Mode use “<!DOCTYPE html>”. activityi;src=8168974;type=msnbc0;cat=msnbc0;ord=4303028491272;npa=0;auiddc=54426428.1755564967;pscdl=noapi;frm=0;_tu=IFA;gtm=45fe58i0v9190897070za200zd9190897070;gcd=13l3l3l3l1l1;dma=0;dc_fmt=2;tag_exp=101509157~103116026~103200004~103233427~104527906~104528500~104684208~104684211~104948813~105033763~105033765~105102051~105103161~105103163~105231383~105231385;epver=2;dc_random=eJl2rGcLRAla7b-Trmj3WtK6mN1FPJiwEQ;_dc_test=1;~oref=MSNBC Live: Stream the latest TV shows
Cookie warnings 2
Cookie “AWSALBCORS” rejected because it has the “SameSite=None” attribute but is missing the “secure” attribute. AccessEnablerProxy.js
Cookie “AWSALBCORS” rejected because it has the “SameSite=None” attribute but is missing the “secure” attribute. AccessEnablerProxy.js
[AccessEnablerProxy.js][info] Version: 4.7.1-5a99613 RELEASE AccessEnablerProxy.js:1:5601
Partitioned cookie or storage access was provided to “AccessEnablerProxy 4.7.1-5a99613 because it is loaded in the third-party context and dynamic state partitioning is enabled. AccessEnablerProxy.js:1:5019
Source map error: Error: request failed with status 404
Stack in the worker:networkRequest@resource://devtools/client/shared/source-map-loader/utils/network-request.js:43:9

Resource URL: https://sp.auth.adobe.com/entitlement/v4/AccessEnablerProxy.js
Source Map URL: AccessEnablerProxy.js.map
Cookie warnings 2
This page is in Quirks Mode. Page layout may be impacted. For Standards Mode use “<!DOCTYPE html>”. cei
Cookie “AWSALBCORS” rejected because it has the “SameSite=None” attribute but is missing the “secure” attribute. msnbc
Cookie “AWSALBCORS” rejected because it has the “SameSite=None” attribute but is missing the “secure” attribute. msnbc
[mps:hb:config] window.screen.width = 1920 load-nbcnews-bento.js:3869:9
Cookie “AWSALBCORS” rejected because it has the “SameSite=None” attribute but is missing the “secure” attribute. usermetadata
Cookie “AWSALBCORS” rejected because it has the “SameSite=None” attribute but is missing the “secure” attribute. usermetadata
Cookie “AWSALBCORS” rejected because it has the “SameSite=None” attribute but is missing the “secure” attribute. shortAuthorize
Cookie “AWSALBCORS” rejected because it has the “SameSite=None” attribute but is missing the “secure” attribute. shortAuthorize
Cookie “AWSALBCORS” rejected because it has the “SameSite=None” attribute but is missing the “secure” attribute. usermetadata
Cookie “AWSALBCORS” rejected because it has the “SameSite=None” attribute but is missing the “secure” attribute. usermetadata
XML Parsing Error: no root element found
Location: https://sp.auth.adobe.com/adobe-services/shortAuthorize
Line Number 9, Column 121: shortAuthorize:9:121
****** [mps] REDIRECTED: false → mps.nbcuni.com ****** live line 324 > injectedScript:2:28
[Omega]
Object { appVersion: "6.10.0", cvsdkVersion: "11.0.1" }
6997.e5668ec24aaf4679.js:1:18498
### YALC TEST: Omega Player component successfully loaded! 4856.d7d4c42502a0e69b.js:1:679687
### YALC TEST: Omega Player component successfully loaded! 4856.d7d4c42502a0e69b.js:1:679687
The script from “https://usasync01.admantx.com/adman...":"URL","body":"https://www.msnbc.com/live"}” was loaded even though its MIME type (“text/plain”) is not a valid JavaScript MIME type. live
[mps:loadJS] async:true, service?request=%7B%22decorator%22%3A%22template.nbc_template%22%2C%22key%22%3A%2262263fff3cc1d07f85c7f8261a0c8f7dc096b35f59c82a713f20a9db8d562ff2%22%2C%22method%22%3A%22descriptor%22%2C%22filter%22%3A%22default%22%2C%22mode%22%3A%22async%22%2C%22type%22%3A%22URL%22%2C%22body%22%3A%22https%3A%2F%2Fwww.msnbc.com%2Flive%22%7D load-nbcnews-bento.js:735:19
[mps:PM3] JS LOADED: Admantx load-nbcnews-bento.js:735:19
EmeEncryptionSchemePolyfill: Waiting to detect encryptionScheme support. 6d060570.567bee80c891fdf7.js:1:342176
McEncryptionSchemePolyfill: Waiting to detect encryptionScheme support. 6d060570.567bee80c891fdf7.js:1:343822
### YALC TEST: Omega Player component successfully loaded! 2 4856.d7d4c42502a0e69b.js:1:679687
[mps:loadJS] async:true, pub.js load-nbcnews-bento.js:735:19
The following functions are deprecated: googletag.pubads().setTagForChildDirectedTreatment(), googletag.pubads().clearTagForChildDirectedTreatment(), googletag.pubads().setRequestNonPersonalizedAds(), and googletag.pubads().setTagForUnderAgeOfConsent(). Please use googletag.pubads().setPrivacySettings() instead. pubads_impl.js:19:244210
Cookie “mptest” has been rejected for invalid domain. 3 live
[mps:hb:dv] Call onDvtagReady load-nbcnews-bento.js:4054:51
Ignoring unsupported entryTypes: layout-shift. 24610.js:2:39415
[mps:loadJS] async:true, 24610.js load-nbcnews-bento.js:735:19
McEncryptionSchemePolyfill: No native encryptionScheme support found. Patching encryptionScheme support. 6d060570.567bee80c891fdf7.js:1:344446
Cookie “mptest” has been rejected for invalid domain. 7 live
For '$t sigma_cvsdk_playerInit', the corresponding attribute value of '$t mvpdId' must be a string, number, boolean, or null. mparticle.js:39:45549
Cookie “mptest” has been rejected for invalid domain. 2 live
[mps:patch] adloads empty refreshed live line 324 > injectedScript:5:30
 

Upvote 0 Downvote
Good paste — that console output is very useful. Two high‑probability culprits jump out from what you pasted and we’ll try them in this order.
Short summary of what the log shows
  • Repeated CORS/network failures to a Conviva analytics host (hostname contains “ipv6…conviva.com”) — “CORS request did not succeed. Status code: (null)”. That usually means the request never completed (network/IPv6 routing or firewall), not a normal HTTP 403 from the server.
  • Several messages about partitioned/third‑party cookie storage and cookie rejections (AWSALBCORS rejected for SameSite=None without Secure; “Partitioned cookie or storage access … dynamic state partitioning is enabled”). That points at Firefox’s cross‑site cookie partitioning / Enhanced Tracking Protection interfering with the entitle/license flow (Adobe AccessEnabler + sp.auth.adobe.com).
  • EME/encryption polyfills are being applied (player checking for encryptionScheme support), which means the player is trying to use DRM — if the Adobe/entitlement flow fails because third‑party cookies or requests are blocked, playback will hang.
Those three facts together strongly suggest either (A) Firefox is blocking/partitioning the cross‑site/auth requests the player needs, or (B) your PC is failing to reach an IPv6 CDN endpoint the player tries to contact. Both can stop the player from ever obtaining a license.
What to try — do these in order and test the MSNBC Live page after each step
1) Temporarily disable Enhanced Tracking Protection for msnbc.com (fast, non‑destructive)
  • Open MSNBC Live: Stream the latest TV shows in Firefox.
  • Click the shield icon at left of the address bar.
  • Click “Turn off Enhanced Tracking Protection for this site” (or open Page Settings and allow cookies).
  • Reload the page.
    Why: your console shows “Partitioned cookie or storage access … dynamic state partitioning” and rejected cookies — the entitlement flow (sp.auth.adobe.com / AccessEnabler) often fails when third‑party cookies/storage are blocked or partitioned. If this fixes it, the cause is Firefox’s cross‑site protections.
2) If that didn’t work: allow third‑party cookies for the auth domains
  • Firefox menu → Settings → Privacy & Security → Cookies and Site Data → Manage Exceptions.
  • Add and Allow: [.msnbc.com], [.auth.adobe.com], [.conviva.com], [.nbcuni.com] (you can remove after testing).
  • Clear site data for msnbc and auth.adobe: Cookies and Site Data → Manage Data → search msnbc / adobe → Remove Selected. Then reload the page.
    Why: the console shows AWSALBCORS and other cookie rejections — allowing the cookie flow removes that variable.
3) Test with DRM enabled and Widevine present
  • Type about:preferences#general in the address bar → under “Digital Rights Management (DRM) Content” make sure “Play DRM‑controlled content” is checked.
  • Restart Firefox.
  • Check Widevine: Menu → Add‑ons and Themes → Plugins (or type about:addons) — look for “Widevine Content Decryption Module” and ensure it’s enabled/updated. If it’s not present, enabling DRM will cause Firefox to download it when you next attempt playback.
    Why: the player requires EME/Widevine for license decryption; missing DRM will block playback.
4) Quick IPv6 test (very important because the failed Conviva URL contains ipv6)
  • Temporarily disable IPv6 on your PC:
    • Open Control Panel → Network and Internet → Network Connections (or right‑click the network icon → Open Network & Internet settings → Change adapter options).
    • Right‑click your active adapter → Properties → uncheck “Internet Protocol Version 6 (TCP/IPv6)” → OK.
    • Restart the browser and test the stream.
  • If disabling IPv6 fixes playback, re‑enable IPv6 and we’ll investigate your IPv6 route/ISP/router configuration; many sites try IPv6 first and if your PC’s IPv6 path is broken the requests fail without a clean fallback.
    Why: the console line showed an ipv6.conviva host failing with status null — that’s classic for an IPv6 connectivity problem.
5) Try Firefox Troubleshoot Mode (disables extensions but keeps profile)
  • Menu → Help → Troubleshoot Mode… → Restart. Try the stream.
    Why: just in case an extension or profile setting is still interfering even though you removed DuckDuckGo.
6) If it still fails: create a fresh Firefox profile (fast check)
  • Type about:profiles → Create a New Profile → Launch profile in new browser. Open the MSNBC live page and test.
    Why: rules out corrupted profile/state.
7) System clock sanity check
  • Make sure Windows date/time are correct (Settings → Time & language → Date & time → Set time automatically). DRM license checks fail with an incorrect system clock.
What to report back
  • Which step (1, 2, 3, 4, 5 or 6) changed anything — especially whether disabling Enhanced Tracking Protection or disabling IPv6 fixed it.
  • If you try step 4 (disable IPv6) and it fixes playback, say so — that will point to an IPv6 routing issue and I’ll give precise router/Windows fixes.
  • If nothing changes, paste the first 20 lines of the Console again after you’ve tried step 1 and step 4 (they change the most useful bits); the new errors will tell us whether the entitlement/license calls succeeded or are still blocked.
Extra notes from your log (why they matter)
  • “CORS request did not succeed. Status code: (null)” = the network request didn’t complete (not an HTTP 403). This often means the request was blocked locally or never reached the server (IPv6 routing, firewall, or extension).
  • “Partitioned cookie or storage access” = Firefox is actively isolating third‑party storage (good for privacy but bad for cross‑site entitlement flows). Turning off ETP for the site or allowing the auth domains temporarily usually fixes it.
  • AWSALBCORS cookie rejections are minor but relevant: the entitlement/auth flow uses cookies and cookies rejected for being insecure/invalid can stop auth.
Reference: the steps I asked you to capture earlier and the DevTools guidance (in case you want to re-export a HAR later) are in the previous diagnostics post I wrote. ive step‑by‑step screenshots for any of the above actions (turning off ETP, disabling IPv6, checking Widevine, or creating a new profile). Which step do you want to try first?
 

Upvote 0 Downvote
BTW, my key that isn't wo king he e wo ks fine eve ywhe e else on my PC. Just not on this fo um.
 

Upvote 0 Downvote
Thanks — that narrows it: if the W key works everywhere except the forum reply box, the problem is almost certainly the forum editor or a browser extension (or an editor shortcut) interfering — not your physical keyboard.
Do these quick checks in this order (fastest → most diagnostic)
1) Quick private‑window test (one minute)
  • Open Firefox private window: Ctrl+Shift+P.
  • Open this thread, click into the reply box and type the letter w a few times.
    If it works in Private mode, an extension is the culprit. If it still fails, continue.
2) Disable extensions (only in your normal profile)
  • Firefox menu → Add‑ons and Themes → Extensions.
  • Toggle off all extensions (especially typing/grammar helpers, password managers, privacy blockers, ad/tracking blockers).
  • Reload the thread and try typing w.
    If it works after disabling, re‑enable extensions one at a time until the problem returns so you identify the offender.
3) Switch the forum editor to plain/BBCode or use quick reply
  • Some XenForo editors have a Rich Text / BBCode toggle or a “Switch editor” / “Source” (<> icon) option — switch to the plain editor and try typing w.
  • If there’s a “Quick Reply” box at the bottom of the page, try typing there instead of the full editor.
4) Clear site data for the forum (clears cached editor state)
  • Firefox → Settings → Privacy & Security → Cookies and Site Data → Manage Data → search windowsforum.com → Remove Selected.
  • Reload the thread and try again.
5) Use the On‑Screen Keyboard or paste (workarounds)
  • Open On‑Screen Keyboard: Win+R → type osk → Enter. Click the W key on it to insert W where needed.
  • Or type your text in Notepad and paste into the reply box (paste works even if typing W is blocked). These tricks were suggested earlier for uploading/logging when a key misbehaves. browser briefly
  • Open Chrome or Edge and log into the forum, then try posting. If W works there, it’s a Firefox‑specific interaction.
7) If nothing fixes it: test for JavaScript errors while typing
  • Open DevTools (F12) → Console, then focus the reply box and press W. See if any console error appears. If you can copy the first few console lines here I’ll read them.
One‑line troubleshooting priority for you to try now
  • Open a Private window (Ctrl+Shift+P) and type w in the reply box. Tell me whether it works there.
If that fixes it, say “Private mode fixed it” and I’ll give the fastest steps to find and disable the specific extension causing the issue. If it still fails in Private, tell me:
  • Firefox version (Help → About Firefox).
  • Whether W fails only in this thread or across the whole forum.
Once you try the Private‑window test, post the result and I’ll walk you through the next precise step.
 

Upvote 0 Downvote
I can type W and w in p ivate o in this window, still can't type r but I can paste it as I just did. Those a e pastes not typed.
None of the steps changed anything. "All the while trying your steps I've opened my laptop, opened MSEdge and have been waiting for msnbc.com/live to open. Same problem, no different. This type between quotes I have created in Notepad to copy and paste into my reply on the forum." end of paste...
FF is up to date V142.0(64bit) It is obviously not just a FF fault.


Ignoring unsupported entryTypes: longtask. _app-36f48cc0d58e6a73.js:5:132167
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://e12872de91aaca7a39095801bdf5f168d87912fa.ipv6.cws.conviva.com/0/wsg. (Reason: CORS request did not succeed). Status code: (null). 2
[AccessEnabler.js][info] Version: 4.7.1-5a99613 RELEASE AccessEnabler.js:1:130588
Cookie “_sp_root_domain_test_1755630900412” has been rejected for invalid domain. live
[AccessEnablerProxy.js][info] Version: 4.7.1-5a99613 RELEASE AccessEnablerProxy.js:1:5601
This page is in Almost Standards Mode. Page layout may be impacted. For Standards Mode use “<!DOCTYPE html>”. activityi;src=8168974;type=msnbc0;cat=msnbc0;ord=6355785833216;npa=0;auiddc=759171591.1755629399;pscdl=noapi;frm=0;_tu=IFA;gtm=45fe58i1h2v9190897070za200zd9190897070;gcd=13l3l3l3l1l1;dma=0;dc_fmt=2;tag_exp=101509157~103116026~103200004~103233427~104527906~104528501~104684208~104684211~104948813~105033766~105033768~105103161~105103163~105231383~105231385;epver=2;dc_random=ek4AuW_JaEs6Tepl3U35RO65miv78cAjvQ;_dc_test=1;~oref=MSNBC Live: Stream the latest TV shows
This page is in Quirks Mode. Page layout may be impacted. For Standards Mode use “<!DOCTYPE html>”. cei
Cookie “AWSALBCORS” rejected because it has the “SameSite=None” attribute but is missing the “secure” attribute. 2 usermetadata
Cookie “AWSALBCORS” rejected because it has the “SameSite=None” attribute but is missing the “secure” attribute. 2 shortAuthorize
XML Parsing Error: no root element found
Location: https://sp.auth.adobe.com/adobe-services/shortAuthorize
Line Number 9, Column 121: shortAuthorize:9:121
Cookie “AWSALBCORS” rejected because it has the “SameSite=None” attribute but is missing the “secure” attribute. 2 usermetadata
[Omega]
Object { appVersion: "6.10.0", cvsdkVersion: "11.0.1" }
4856.d7d4c42502a0e69b.js:1:405674
### YALC TEST: Omega Player component successfully loaded! 2 4856.d7d4c42502a0e69b.js:1:679687
[mps:hb:config] window.screen.width = 1920 load-nbcnews-bento.js:3869:9
****** [mps] REDIRECTED: false → mps.nbcuni.com ****** live:2:28
EmeEncryptionSchemePolyfill: Waiting to detect encryptionScheme support. 6d060570.567bee80c891fdf7.js:1:342176
McEncryptionSchemePolyfill: Waiting to detect encryptionScheme support. 6d060570.567bee80c891fdf7.js:1:343822
### YALC TEST: Omega Player component successfully loaded! 2 4856.d7d4c42502a0e69b.js:1:679687
The script from “https://usasync01.admantx.com/adman...com/live?utm_source=email&utm_medium=email"}” was loaded even though its MIME type (“text/plain”) is not a valid JavaScript MIME type. live
[mps:loadJS] async:true, service?request=%7B%22decorator%22%3A%22template.nbc_template%22%2C%22key%22%3A%2262263fff3cc1d07f85c7f8261a0c8f7dc096b35f59c82a713f20a9db8d562ff2%22%2C%22method%22%3A%22descriptor%22%2C%22filter%22%3A%22default%22%2C%22mode%22%3A%22async%22%2C%22type%22%3A%22URL%22%2C%22body%22%3A%22https%3A%2F%2Fwww.msnbc.com%2Flive%3Futm_source%3Demail%26utm_medium%3Demail%22%7D load-nbcnews-bento.js:735:19
[mps:PM3] JS LOADED: Admantx load-nbcnews-bento.js:735:19
[mps:loadJS] async:true, pub.js load-nbcnews-bento.js:735:19
The following functions are deprecated: googletag.pubads().setTagForChildDirectedTreatment(), googletag.pubads().clearTagForChildDirectedTreatment(), googletag.pubads().setRequestNonPersonalizedAds(), and googletag.pubads().setTagForUnderAgeOfConsent(). Please use googletag.pubads().setPrivacySettings() instead. pubads_impl.js:19:244210
Cookie “mptest” has been rejected for invalid domain. 7 live
For '$t sigma_cvsdk_playerInit', the corresponding attribute value of '$t mvpdId' must be a string, number, boolean, or null. mparticle.js:39:45549
Cookie “mptest” has been rejected for invalid domain. live
Ignoring unsupported entryTypes: layout-shift. 24610.js:2:39415
[mps:loadJS] async:true, 24610.js load-nbcnews-bento.js:735:19
Cookie “mptest” has been rejected for invalid domain. live
[mps:hb:dv] Call onDvtagReady load-nbcnews-bento.js:4054:51
McEncryptionSchemePolyfill: No native encryptionScheme support found. Patching encryptionScheme support. 6d060570.567bee80c891fdf7.js:1:344446
Content-Security-Policy warnings 4
A resource is blocked by OpaqueResponseBlocking, please check browser console for details. sodar
A resource is blocked by OpaqueResponseBlocking, please check browser console for details. sodar
For '$t uni_cvsdk_error', the corresponding attribute value of '$t cause' must be a string, number, boolean, or null. mparticle.js:39:45549
For '$t uni_cvsdk_error', the corresponding attribute value of '$t reason' must be a string, number, boolean, or null. mparticle.js:39:45549
For '$t uni_cvsdk_error', the corresponding attribute value of '$t originalSeverity' must be a string, number, boolean, or null. mparticle.js:39:45549
Cookie “mptest” has been rejected for invalid domain. live
### YALC TEST: Omega Player component successfully loaded! 4856.d7d4c42502a0e69b.js:1:679687
[12:16:03 GMT-0700 (Pacific Daylight Time).193] [ERROR] [MediaHeartbeat] API call trackSessionEnd is unsupported in the current state. live:9:8583
Cookie “mptest” has been rejected for invalid domain. live
### YALC TEST: Omega Player component successfully loaded! 4856.d7d4c42502a0e69b.js:1:679687
Source map error: Error: request failed with status 404
Stack in the worker:networkRequest@resource://devtools/client/shared/source-map-loader/utils/network-request.js:43:9

Resource URL: https://sp.auth.adobe.com/entitlement/v4/AccessEnablerProxy.js
Source Map URL: AccessEnablerProxy.js.map
Source map error: Error: request failed with status 404
Stack in the worker:networkRequest@resource://devtools/client/shared/source-map-loader/utils/network-request.js:43:9

Resource URL: https://entitlement.auth.adobe.com/entitlement/v4/AccessEnabler.js
Source Map URL: AccessEnabler.js.map
Navigated to MSNBC Live: Stream the latest TV shows
Ignoring unsupported entryTypes: longtask. _app-36f48cc0d58e6a73.js:5:132167
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://e12872de91aaca7a39095801bdf5f168d87912fa.ipv6.cws.conviva.com/0/wsg. (Reason: CORS request did not succeed). Status code: (null).
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://e12872de91aaca7a39095801bdf5f168d87912fa.ipv6.cws.conviva.com/0/wsg. (Reason: CORS request did not succeed). Status code: (null).
[AccessEnabler.js][info] Version: 4.7.1-5a99613 RELEASE AccessEnabler.js:1:130588
Source map error: Error: request failed with status 404
Stack in the worker:networkRequest@resource://devtools/client/shared/source-map-loader/utils/network-request.js:43:9

Resource URL: https://entitlement.auth.adobe.com/entitlement/v4/AccessEnabler.js
Source Map URL: AccessEnabler.js.map
[AccessEnablerProxy.js][info] Version: 4.7.1-5a99613 RELEASE AccessEnablerProxy.js:1:5601
Cookie “_sp_root_domain_test_1755631045750” has been rejected for invalid domain. live
This page is in Almost Standards Mode. Page layout may be impacted. For Standards Mode use “<!DOCTYPE html>”. activityi;src=8168974;type=msnbc0;cat=msnbc0;ord=7890043582920;npa=0;auiddc=759171591.1755629399;pscdl=noapi;frm=0;_tu=IFA;gtm=45fe58i1h2v9190897070za200zd9190897070;gcd=13l3l3l3l1l1;dma=0;dc_fmt=2;tag_exp=101509157~103116026~103200004~103233427~104527907~104528501~104684208~104684211~104948813~105033766~105033768~105103161~105103163~105231383~105231385;epver=2;dc_random=rzf-D4OZS93ZDNKBdBpr0XBnaRLbwotfLQ;_dc_test=1;~oref=MSNBC Live: Stream the latest TV shows
Source map error: Error: request failed with status 404
Stack in the worker:networkRequest@resource://devtools/client/shared/source-map-loader/utils/network-request.js:43:9

Resource URL: https://sp.auth.adobe.com/entitlement/v4/AccessEnablerProxy.js
Source Map URL: AccessEnablerProxy.js.map
Cookie “AWSALBCORS” rejected because it has the “SameSite=None” attribute but is missing the “secure” attribute. 2 msnbc
This page is in Quirks Mode. Page layout may be impacted. For Standards Mode use “<!DOCTYPE html>”. cei
Cookie “AWSALBCORS” rejected because it has the “SameSite=None” attribute but is missing the “secure” attribute. 4 usermetadata
Cookie “AWSALBCORS” rejected because it has the “SameSite=None” attribute but is missing the “secure” attribute. 2 shortAuthorize
XML Parsing Error: no root element found
Location: https://sp.auth.adobe.com/adobe-services/shortAuthorize
Line Number 9, Column 121: shortAuthorize:9:121
[Omega]
Object { appVersion: "6.10.0", cvsdkVersion: "11.0.1" }
6997.e5668ec24aaf4679.js:1:18498
wW

### YALC TEST: Omega Player component successfully loaded! 4856.d7d4c42502a0e69b.js:1:679687
[mps:hb:config] window.screen.width = 1920 load-nbcnews-bento.js:3869:9
EmeEncryptionSchemePolyfill: Waiting to detect encryptionScheme support. 6d060570.567bee80c891fdf7.js:1:342176
McEncryptionSchemePolyfill: Waiting to detect encryptionScheme support. 6d060570.567bee80c891fdf7.js:1:343822
### YALC TEST: Omega Player component successfully loaded! 2 4856.d7d4c42502a0e69b.js:1:679687
****** [mps] REDIRECTED: false → mps.nbcuni.com ****** live:2:28
The script from “https://usasync01.admantx.com/adman...com/live?utm_source=email&utm_medium=email"}” was loaded even though its MIME type (“text/plain”) is not a valid JavaScript MIME type. live
[mps:loadJS] async:true, service?request=%7B%22decorator%22%3A%22template.nbc_template%22%2C%22key%22%3A%2262263fff3cc1d07f85c7f8261a0c8f7dc096b35f59c82a713f20a9db8d562ff2%22%2C%22method%22%3A%22descriptor%22%2C%22filter%22%3A%22default%22%2C%22mode%22%3A%22async%22%2C%22type%22%3A%22URL%22%2C%22body%22%3A%22https%3A%2F%2Fwww.msnbc.com%2Flive%3Futm_source%3Demail%26utm_medium%3Demail%22%7D load-nbcnews-bento.js:735:19
[mps:PM3] JS LOADED: Admantx load-nbcnews-bento.js:735:19
[mps:loadJS] async:true, pub.js load-nbcnews-bento.js:735:19
McEncryptionSchemePolyfill: No native encryptionScheme support found. Patching encryptionScheme support. 6d060570.567bee80c891fdf7.js:1:344446
The following functions are deprecated: googletag.pubads().setTagForChildDirectedTreatment(), googletag.pubads().clearTagForChildDirectedTreatment(), googletag.pubads().setRequestNonPersonalizedAds(), and googletag.pubads().setTagForUnderAgeOfConsent(). Please use googletag.pubads().setPrivacySettings() instead. pubads_impl.js:19:244210
Ignoring unsupported entryTypes: layout-shift. 24610.js:2:39415
[mps:loadJS] async:true, 24610.js load-nbcnews-bento.js:735:19
Cookie “mptest” has been rejected for invalid domain. 7 live
For '$t sigma_cvsdk_playerInit', the corresponding attribute value of '$t mvpdId' must be a string, number, boolean, or null. mparticle.js:39:45549
Cookie “mptest” has been rejected for invalid domain. 2 live
[mps:hb:dv] Call onDvtagReady load-nbcnews-bento.js:4054:51
[mps:patch] adloads empty refreshed live:5:30
 

Upvote 0 Downvote
Thanks — the new console lines confirm two likely causes and give a clear testing path.
Why I’m betting on two things
  • The Conviva host failing over IPv6 (“ipv6.cws.conviva.com … CORS request did not succeed. Status code: (null)”) strongly suggests your PC is trying IPv6 first but the IPv6 path fails, so the player never completes its analytics/auth/license handshakes.
  • The Adobe entitlement / cookie warnings and “partitioned cookie or storage access” messages show the auth/license flow is sensitive to third‑party cookies/partitioning; if those requests are blocked or their cookies rejected, playback will hang.
Those two findings (IPv6 connectivity problems + third‑party cookie/entitlement failures) match your symptom set and match the earlier diagnosis steps I suggested. See the original thread context for that checklist. ed, quick, and reversible
1) Quick test — disable IPv6 temporarily (very often fixes “status: (null)” IPv6 failures)
  • Windows (GUI):
    • Open Control Panel → Network and Internet → Network Connections (or Settings → Network & internet → Advanced network settings → More adapter options).
    • Right‑click your active adapter (Wi‑Fi or Ethernet) → Properties.
    • Uncheck “Internet Protocol Version 6 (TCP/IPv6)”, click OK.
    • Close browser, reopen and test MSNBC Live: Stream the latest TV shows.
  • If that fixes the stream, re‑enable IPv6 later and we’ll troubleshoot the router/ISP IPv6 route. WindowsForum threads show IPv6 often causes similar site failures and a temporary disable is a standard diagnostic.
2) If IPv6 disable immediately (site privacy/auth)
  • On the MSNBC page in Firefox: click the shield icon (left of address bar) → “Turn off Enhanced Tracking Protection for this site” → Reload. If that fixes it, the problem was cross‑site cookie partitioning/blocking.
  • Alternatively (fine‑grained): Firefox → Settings → Privacy & Security → Cookies and Site Data → Manage Exceptions → Add and Allow:
    • [*.msnbc.com]
    • [.auth.adobe.com] and [.entitlement.auth.adobe.com]
    • [.conviva.com] and [.nbcuni.com]
    • Then clear site data for msnbc and re‑load.
3) Ensure DRM/Widevine is enabled (player needs EME)
  • about:preferences#general → make sure “Play DRM‑controlled content” is checked.
  • about:addons → Plugins: ensure “Widevine Content Decryption Module” is present/enabled (Firefox will download it when DRM is enabled). Restart Firefox and test.
4) Flush DNS + restart browser (cheap, useful)
  • Open Command Prompt (Admin) and run: ipconfig /flushdns
  • Close browser, reopen and test.
5) Test network route to the failing host (if you’re comfortable running these)
  • Open PowerShell and run (will test reachability over IPv6):
    • Test-NetConnection -ComputerName e12872de91aaca7a39095801bdf5f168d87912fa.ipv6.cws.conviva.com -Port 443 -InformationLevel Detailed
  • If that returns no route/failed, that confirms broken IPv6 path and the disable IPv6 test is the right fix.
6) If disabling IPv6 fixed playback
  • Re‑enable IPv6 (undo GUI step) and then:
    • Reboot router and PC.
    • If problem returns, contact your ISP (show them the Conviva ipv6 host was unreachable from your PC) or we can walk through router settings to fix IPv6 RA/DHCPv6 issues. WindowsForum threads show real‑world examples where IPv6-only routing breaks sites; a temporary IPv6 disable is a safe troubleshooting step.
7) If nothing fixes it after the above
  • our phone’s hotspot (not the phone on Wi‑Fi — literally create a hotspot and connect the PC). If hotspot works while your home network doesn’t, the router/ISP is almost certainly the problem.
  • Create a fresh Firefox profile (about:profiles → Create a New Profile) and test — this rules out profile corruption.
Keyboard/forum editor note (brief)
  • You said the W key works everywhere else except the forum reply box and it works in a Private window — that points to a site/editor interaction (or an extension) rather than hardware. Try: Private window (you already did), disable extensions globally, or use the forum’s quick‑reply / plain BBCode editor. Clearing site data for windowsforum.com can also resolve editor oddities. The steps I recommended earlier still apply.
What I need you to report back (one reply)
  • Result of step 1 (NBC live start? (Yes / No)
  • If you ran the PowerShell Test‑NetConnection, paste the short result (pass/fail lines).
  • Did turning off Enhanced Tracking Protection for msnbc.com change anything?
  • If disabling IPv6 fixed it, say so and I’ll supply exact router/Windows fixes to restore IPv6 safely.
  • If none of the above fixes it, I’ll ask you for a fresh console output after you’ve tried steps 1 and 2 and we’ll look at license requests in the HAR.
If you want, I’ll give exact one‑click GUI screenshots/keystrokes for the IPv6 disable and the Firefox ETP toggle for your Firefox 142 build — tell me which (IPv6 GUI or the Firefox toggle) and I’ll post the step‑by‑step with the smallest number of clicks.
 

Upvote 0 Downvote
ChatGPT said:
Thanks — that narrows it: if the W key works everywhere except the forum reply box, the problem is almost certainly the forum editor or a browser extension (or an editor shortcut) interfering — not your physical keyboard.
Do these quick checks in this order (fastest → most diagnostic)
1) Quick private‑window test (one minute)
  • Open Firefox private window: Ctrl+Shift+P.
  • Open this thread, click into the reply box and type the letter w a few times.
    If it works in Private mode, an extension is the culprit. If it still fails, continue.
2) Disable extensions (only in your normal profile)
  • Firefox menu → Add‑ons and Themes → Extensions.
  • Toggle off all extensions (especially typing/grammar helpers, password managers, privacy blockers, ad/tracking blockers).
  • Reload the thread and try typing w.
    If it works after disabling, re‑enable extensions one at a time until the problem returns so you identify the offender.
3) Switch the forum editor to plain/BBCode or use quick reply
  • Some XenForo editors have a Rich Text / BBCode toggle or a “Switch editor” / “Source” (<> icon) option — switch to the plain editor and try typing w.
  • If there’s a “Quick Reply” box at the bottom of the page, try typing there instead of the full editor.
4) Clear site data for the forum (clears cached editor state)
  • Firefox → Settings → Privacy & Security → Cookies and Site Data → Manage Data → search windowsforum.com → Remove Selected.
  • Reload the thread and try again.
5) Use the On‑Screen Keyboard or paste (workarounds)
  • Open On‑Screen Keyboard: Win+R → type osk → Enter. Click the W key on it to insert W where needed.
  • Or type your text in Notepad and paste into the reply box (paste works even if typing W is blocked). These tricks were suggested earlier for uploading/logging when a key misbehaves. browser briefly
  • Open Chrome or Edge and log into the forum, then try posting. If W works there, it’s a Firefox‑specific interaction.
7) If nothing fixes it: test for JavaScript errors while typing
  • Open DevTools (F12) → Console, then focus the reply box and press W. See if any console error appears. If you can copy the first few console lines here I’ll read them.
One‑line troubleshooting priority for you to try now
  • Open a Private window (Ctrl+Shift+P) and type w in the reply box. Tell me whether it works there.
If that fixes it, say “Private mode fixed it” and I’ll give the fastest steps to find and disable the specific extension causing the issue. If it still fails in Private, tell me:
  • Firefox version (Help → About Firefox).
  • Whether W fails only in this thread or across the whole forum.
Once you try the Private‑window test, post the result and I’ll walk you through the next precise step.
Click to expand...
 

Upvote 0 Downvote
Thanks — good info and helpful console paste. Short version: the logs still point at two likely causes (broken IPv6 reachability to Conviva + cross‑site cookie/entitlement traffic being blocked), so the next, targeted tests are the IPv6/network checks and one more cookie/DRM toggle. I’ll give exactly three things to run now (fast → slightly more intrusive). After you do them paste the short outputs (or say what happened) and I’ll tell you the exact fix.
Why I’m asking these (one line)
  • Your console shows failed requests to an ipv6.conviva host (CORS request “status: (null)”) and repeated cookie/AccessEnabler messages — that usually means the browser tries IPv6 but the IPv6 path fails, and/or the entitlement (Adobe/DRM) flow is being blocked by cross‑site cookie protections. knetwork reachability test (PowerShell) — tells us if the IPv6 path to the failing host works
  • Open PowerShell (type PowerShell in Start and run). Paste and run exactly:
    Test-NetConnection -ComputerName e12872de91aaca7a39095801bdf5f168d87912fa.ipv6.cws.conviva.com -Port 443 -InformationLevel Detailed
  • Copy the short result lines (TcpTestSucceeded: True/False, PingSucceeded, RemoteAddress) and paste them here.
    Why: if TcpTestSucceeded is False (or no route) it confirms an IPv6 connectivity problem and explains the “status: (null)” CORS failures.
2) Temporary IPv6 disable (quick, reversiostic
  • Windows GUI:
    • Settings → Network & internet → Advanced network settings → More adapter options.
    • Right‑click your active adapter → Properties → uncheck Internet Protocol Version 6 (TCP/IPv6) → OK.
    • Close browser, reopen Firefox (or Edge) and try MSNBC Live: Stream the latest TV shows.
  • Tell me whether the stream now starts (Yes / No).
    Why: many sites try IPv6 first; if your router/ISP/PC IPv6 path is broken the site’s analytics/auth calls can hang and block playback. If disabling IPv6 fixes it, we’ll fix IPv6 routing properly.
3) Quick entitlement/cookie/DRM checks in Firefox (non‑destructge in Firefox: click the shield icon (left of address bar) → “Turn off Enhanced Tracking Protection for this site” → reload the page and test.
  • Also check DRM: type about:preferences#general → make sure “Play DRM‑controlled content” is checked, then restart Firefox. Check about:addons → Plugins for “Widevine Content Decryption Module” (it downloads automatically when DRM is enabled). Reload page.
  • Report whether either action changes anything (Playback started / Still spins).
    Why: your console shows AccessEnabler and cookie rejections (SameSite/AWSALBCORS) and Firefox’s ETP/partitioning can break the entitlement flow unless allowed.
If those do nothing, do this extra quick isolate test
  • Create a phone hotspot and cue and enable Personal Hotspot), then open the MSNBC live page on the PC. If the stream works on the hotspot but not on the home Wi‑Fi, the router/ISP path (likely IPv6) is the culprit.
Also — a couple of short checks/questions
  • Are you using any VPN / SmartDNS / DNS‑level ad blocking (on the router)? If yes, temporarily disable it while testing.
  • Did you try Troubleshoot Mode in Firefox (Help → Troubleshoot Mode) — you said private window worked for the typing test, but the stream problem affects all browsers so it’s likely network/auth related rather than an extension.
What to paste back here (one short reply)
  • Result of the PowerShell Test‑NetConnection (the TcpTestSucceeded/Ping/RemoteAddressbling IPv6 make the stream work? (Yes / No).
  • Did turning off Enhanced Tracking Protection for msnbc.com or enabling DRM/Widevine make any difference? (Yes / No).
  • If you tried the phone hotspot, did it work there? (Yes / No).
  • Are you using a VPN / SmartDNS / router adblocker? (Yes / No).
If disabling IPv6 fixes it
  • I’ll give exact steps to re‑enable IPv6 and then fix the router/Windows configuration so you don’t lose IPv6 permanently.
If none of these help
  • I’ll ask you to capture a short HAR around the license/entitlement calls (I showed how earlier) and we’ll read the license request/response codes. That’ll nail whether it’s a license HTTP 4xx/5xx or a network drop.
Pick one (do the PowerShell test first) — paste the output and I’ll interpret it and give the next exact command/setting to change.
 

Upvote 0 Downvote
Re your:
5) Test network route to the failing host (if you’re comfortable running these)

Open PowerShell and run (will test reachability over IPv6):
Test-NetConnection -ComputerName e12872de91aaca7a39095801bdf5f168d87912fa.ipv6.cws.conviva.com -Port 443 -InformationLevel Detailed
If that returns no route/failed, that confirms broken IPv6 path and the disable IPv6 test is the right fix.

My reply:
The above instruction is unclear. I copied and pasted from "Test-" through the word "Detailed" at the cmd for admins and it failed to understand the command. So do I fail to understand what you want me to do here.

Disabling the IPv6 didn't change or improve anything.

I'm having trouble keeping up with your instructions as,
1) they are not time stamped,
2) they arrive in emails long before they show up on screen,
3) you jump from fixing my msnbc access to fixing a key, which is the r key not the w key. But I don't care if the r doesn't work on this forum because it does work everywhere else. I simply have to write in Notepad and copy/paste to this forum.

I do not know how to connect to my ISP Comcast's hotspot and I do not care to learn, my brain space is already stressed out.

You suggested I contact my ISP and shoe them something. Until I've checked all on my end, they are usually useless. so...

You wrote "or we can walk through router settings to fix IPv6 RA/DHCPv6 issues." Let's try the router fix.

ETP, GUI, you are assuming I understand all this stuff.
 

Upvote 0 Downvote
Thanks — good clarification. You were trying the Test‑NetConnection text in the wrong place (that’s why it failed). Let’s do three simple, safe steps (exact keystrokes/commands) so we can tell for sure whether this is an IPv6 path problem — then we’ll try the Windows change that usually fixes the “IPv6 tried but failed” behavior.
I’ll keep commands copy/paste‑ready and explain what to paste back.
1) How to run the PowerShell reachability test (exact, step‑by‑step)
  • Why: Test‑NetConnection runs only in PowerShell (not in the old cmd.exe). It will tell us if your PC can open a TCP connection to the failing host (and whether Windows is trying IPv6 and failing). See Microsoft docs for this cmdlet.
Steps:
  1. Click Start → type PowerShell.
  2. Right‑click “Windows PowerShell” (or “Windows PowerShell (x86)” if you only see that) → Run as administrator. (Or press Windows+X → choose “Windows PowerShell (Admin)”).
  3. In the elevated PowerShell window paste this single line (exact):
    Test-NetConnection -ComputerName e12872de91aaca7a39095801bdf5f168d87912fa.ipv6.cws.conviva.com -Port 443 -InformationLevel Detailed
  4. Press Enter and wait for the output. Important fields to copy/paste back here are:
    • RemoteAddress
    • TcpTestSucceeded (True / False)
    • NetRoute (NextHop) or PingSucceeded (if present)
If you get an error “The term 'Test‑NetConnection' is not recognized”, tell me that exact message — it means you’re running PowerShell Core where that cmdlet may be missing. If that happens, tell me and I’ll give a fallback command you can run.
(If you want an easier-to-read example of the output, Microsoft shows sample output lines for TcpTestSucceeded and RemoteAddress here.)
2) You already tried disabling IPv6 in the adapter GUI — good test. Since that didn’t help, the next recommended and safe step is to make Windows prefer IPv4 over IPv6 (this is reversible and recommended over permanently disabling IPv6). Microsoft documents the registry setting for this (DisabledComponents = 0x20 = prefer IPv4 over IPv6).
If the PowerShell test above shows IPv6 route failures, run this (exact, admin required):
  • Open an elevated Command Prompt or PowerShell (Run as Administrator) and paste:
    reg add "HKLM\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters" /v DisabledComponents /t REG_DWORD /d 0x20 /f
  • Then reboot the PC. After reboot, open Firefox/Edge/Chrome and test MSNBC Live: Stream the latest TV shows again.
Notes about that registry change
  • This tells Windows to prefer IPv4 when both are available (it’s safer than fully disabling IPv6). Microsoft documents this method and warns a restart is required. If you want to undo it later, run the same command with /d 0x0 and reboot.
3) Quick non‑technical toggle to try (Firefox: one click)
Because your console showed AccessEnabler / cookie partitioning warnings, it’s worth turning tracking protection off for msnbc.com for the test (this is temporary and reversible):
  • Open MSNBC Live: Stream the latest TV shows in Firefox.
  • Click the shield icon at the left of the address bar → click “Turn off Enhanced Tracking Protection for this site” → reload the page and test.
    If that gets the stream going, we know the entitlement/cookie flow was being blocked.
If any of these steps feel risky, do the PowerShell Test‑NetConnection first and paste the 3 lines I asked for — I’ll interpret them and tell you exactly which of the steps above to run next.
If you’d like me to walk you through the registry command or reboot step by step while you do it, say “Yes — walk me through it” and I’ll post the precise keystrokes/screens you’ll need.
A couple of quick reassurances and housekeeping
  • The Test‑NetConnection failure you saw earlier happened because you likely pasted into the old cmd.exe or a non‑elevated shell — that’s why Windows “didn’t understand” the Test‑ command. Use an elevated PowerShell window (Win+X → Windows PowerShell (Admin)).
  • Disabling IPv6 on the adapter (what you already tried) is a valid test; preferring IPv4 via the registry is usually the better, reversible fix if IPv6 routing is flaky.
  • You don’t need to contact Comcast yet — let’s confirm the Test‑NetConnection and (if needed) try the prefer‑IPv4 registry change first. If those don’t help, we’ll look at router/ISP steps (and I’ll walk you through router steps only after you tell me the router model).
Which one do you want to do right now?
  • A. Run the Test‑NetConnection and paste the TcpTestSucceeded / RemoteAddress lines here.
  • B. I’ll walk you through applying the registry change (prefer IPv4) and rebooting.
Say A or B and I’ll give the next exact step (and I’ll stay with you through each paste/confirmation).
 

Upvote 0 Downvote
Solution
Suddenly I now have access on both this PC and my laptop to msnbc. So, I'm signing off and going to have a drink. The r still doesn't work here, I am pasting it in.
 

Upvote 0 Downvote
Great news — glad the stream started working on both machines. Enjoy your drink!
A couple of brief notes and a tiny checklist if it comes back (keeps the next steps short so you don’t have to hunt through the thread later):
Why it probably fixed itself
  • Most likely a transient network/edge problem (CDN/IPv6 routing or server-side retry) or the remote auth/DRM service recovered. Those things can temporarily cause the “spinner forever” behaviour and then clear up without any local change.
If it returns, the fastest useful checks
1) Quick test (no heavy tech): open the MSNBC page in a Private/Incognito window — if it works there it’s likely a browser profile/extension/site‑data issue.
2) One‑click browser test (Firefox): click the shield at left of the address bar → Turn off Enhanced Tracking Protection for this site → reload. If that fixes playback, we know the entitlement/cookie flow was being blocked.
3) PowerShell connectivity check (only if it fails again and you want to test network): run PowerShell as Administrator and paste this one line, then tell me TcpTestSucceeded result:
Test-NetConnection -ComputerName e12872de91aaca7a39095801bdf5f168d87912fa.ipv6.cws.conviva.com -Port 443 -InformationLevel Detailed
4) If PowerShell shows an IPv6 failure and the stream fails repeatedly, the reversible Windows tweak I recommend is to prefer IPv4 (I can walk you through the two commands and a reboot).
About the “r” key in the forum editor
  • Since the key works everywhere else, it’s almost certainly the forum editor or an extension interacting with the editor. Quick, non‑annoying workarounds:
    • Type in Notepad and paste (what you’re already doing).
    • Use the On‑Screen Keyboard (Win+R → osk → click the r).
    • If you ever want to chase it down: try Private mode (Ctrl+Shift+P) in Firefox, or disable extensions temporarily, or clear site data for windowsforum.com — those usually find the culprit.
If you want me to walk you through the PowerShell test or the “prefer IPv4” registry change later, say the word and I’ll give the exact one‑click/paste steps and stay with you while you do them.
Have a good evening — cheers, and let me know if it reappears tomorrow and we’ll finish it off.
 

Upvote 0 Downvote
You must log in or register to reply here.
Back
Top