Tried to re scan once the settlement was made and waited a few hours but now none of the channels are giving me the Cable provider authentication failed message on all YTTV channels
Also lost the local ABC station after I re scanned everything.Everything is back except for that one
I found this tidbit interesting. I knew about the channels being pulled during “the breakup” but I didn’t realize that would also apply to previous recordings in the cloud, too.
Yet another reason I'm grateful for Channels DVR and the local recordings that we, the people, are able to control 
This is causing the entire process of adding YouTube TV to fail!
For one thing - your chrome is too old.
Thank you for the info. It looks like they are using a poor method for VPN detection.
I don't use a VPN but do have multi-provider, multi-homed internet connections. This is configured for load balancing and automatic failover. Also of note is that one provider uses DHCP for dynamic address assignment.
Correcting the problem required "authorizing" both networks ... :
I'm sure I will run into this issue again, but for now it seems to be working well.
This is a bit of an edge case and is an issue with the providers not the Channels DVR service.
Though it could be easier to solve if the "Add Source" process and/or rescanning would allow more interactivity for individual channel authorizations, similar to the Hulu processing. Maybe you could add this to the schedule? 
Thank you for the help and for doing a great job with the Channels DVR product!
I am seeing the same screen after YT TV restored the Disney channels. I believe this is not an 2FA error message because previously the message of this type was a verify your identity message. This looks like a simple login error. I am guessing that YT TV is generating this message. I am using a member login without 2FA, logged into NBC live, not double homed to the internet). I am using Chromium on a lap top to connect to channels DVR running on a Synology NAS. One issue I have is I can't seem to find the correct log file that has this error in it or perhaps I don't have the correct logging set. The path I follow under the Channels directory is the most recent directory under Logs/recording. The other question I have is where do I need to be logged into NBC live, my laptop or the NAS?
The DVR log is available on the web UI, under Support > Logs
Your laptop.
Here is my log file relative to You Tube TV Provider. I have stopped using firefox on Linux and this log is from an attempt on a Windows 11 laptop. I am not sure caused the reference to Chrome (on the 5th line) as Chrome is not on this laptop.
2021/12/29 17:44:37.335112 [TVE] Auth starting for YouTubeTV as XXXX@gmail.com
2021/12/29 17:44:37.335164 [TVE] action=auth mvpd=YouTubeTV requestor=nbcentertainment
2021/12/29 17:44:37.443840 [TVE] action=error_response type=Other error=net::ERR_UNKNOWN_URL_SCHEME url=
2021/12/29 17:44:37.444975 [TVE] action=version product=Chrome/76.0.3805.2 jsVersion=7.6.274 protocol=1.3 revision=@b96ff990aaa019fca0942aadc19c721d20cfa213
2021/12/29 17:44:37.457122 [TVE] action=mock
2021/12/29 17:44:37.469939 [TVE] action=navigate url=https://sp.auth.adobe.com/adobe-services/authenticate/saml?noflash=true&mso_id=YouTubeTV&requestor_id=nbcentertainment&no_iframe=true&domain_name=adobe.com&redirect_url=https%3A%2F%2Fsp.auth.adobe.com%2Fadobe-services%2FcompletePassiveAuthentication
2021/12/29 17:44:37.470924 [TVE] action=request type=Document method=GET url=https://sp.auth.adobe.com/adobe-services/authenticate/saml
2021/12/29 17:44:37.670316 [TVE] action=wait_for_page
2021/12/29 17:44:37.721995 [TVE] action=request type=Document method=POST url=https://youtube.auth-gateway.net/saml/saml2/idp/SSOService.php
2021/12/29 17:44:37.722026 [TVE] action=auth_domain domain=youtube.auth-gateway.net
2021/12/29 17:44:37.866938 [TVE] action=request type=Document method=GET url=https://youtube.auth-gateway.net/saml/module.php/authbypass/firstbookend.php
2021/12/29 17:44:37.955728 [TVE] action=request type=Document method=GET url=https://youtube.auth-gateway.net/saml/module.php/authbypass/firstbookend.php
2021/12/29 17:44:38.017366 [TVE] action=request type=Document method=GET url=https://accounts.google.com/o/oauth2/auth
2021/12/29 17:44:44.272898 [TVE] action=page_ready
2021/12/29 17:44:44.272943 [TVE] action=wait_for_page done=true reason=page_ready
2021/12/29 17:44:44.272961 [TVE] action=fill_form u=lXX@gmail.com
2021/12/29 17:44:44.276016 [TVE] action=tvejs msg="googleLogin"
2021/12/29 17:44:44.299992 [TVE] action=wait_for_auth
2021/12/29 17:44:46.797958 [TVE] action=tvejs msg="googleLoginPassword found a CAPTCHA"
2021/12/29 17:45:08.300364 [TVE] action=auth_timed_out
2021/12/29 17:45:08.300429 [TVE] action=screenshot
2021/12/29 17:45:08.386175 [TVE] action=screenshot size=51691
2021/12/29 17:45:08.414895 [TVE] action=capture_html
2021/12/29 17:45:08.595649 [TVE] action=capture_html size=1845051
2021/12/29 17:45:08.614035 [TVE] Auth failed for YouTubeTV: Cable provider authentication failed
Probably need to update chrome via the Support > Troubleshooting page
It doesn't matter what browser you use yourself. The DVR runs a headless chrome on your NAS that it uses to connect to TVE streams.
This was extremely helpful. I was able to update Chrome on the troubleshooting page and it got me past the CAPTCHA issue I have been facing for over a week. I was not aware that this troubleshooting feature existed. Still not sure why Chrome did not update automatically with a DVR update on Synology NAS. I had been chasing this as a forced 2FA issue with YTTV.
Thanks for that, I had no idea the DVR was running a headless version of Chrome! Upgraded Chrome and it allowed me to login using my normal Google password.
Where is the troubleshooting page? I have a Synology with the same issues. Appreciate any assistance!
I am attempting to add YouTube TV as a Channels source for the first time and am getting the image error below. I am using a secondary account without 2-factor authentication and have successfully logged in to nbc.com/live in Chrome. Are there any ways around this verification screen?
Have you also ensured your non-2FA Google account is not recoverable (i.e., no phone number or email address for recovery?). Here's my non-2FA non-recoverable account info; note no phone number or recovery email.
