Thank you Joe,
I do hope my post did not come across as rude or disrespectful, as that was NOT my intention. I did hope we could all do exactly as you have done; provide specific details to help Verizon Messages developer/QA staff identify what is causing this failure. Though now retired, I've had many years at most phases of software design, development, QA, maintenance, troubleshooting, etc. I am acquainted with how complex identifying a "bug" can be, long before the scope of a "fix" can be assessed.
My first suspicion is that a Microsoft update has "tightened" a loophole Verizon Messages can no longer jump through.
Both my Windows 10 desktop(Professional) and laptop(Home) are current at:
- Windows 10 64-bit
- Version 1903 (OS Build 18362.239)
My Windows 7 desktop is current at:
- Windows 7 Professional SP-1 64-bit (6.1.7601)
- latest update 7/21/2019 (KB4507437)
Norton Security Deluxe Version 18.104.22.168 (all 3 of my Windows machines)
My theory only fits the details if Microsoft made some similar change to both Windows 10 Home and Pro, as well as Windows 7, on about the same date (approx 19 July 2019)