I had the same issue. I had not played D2 since before the update applied. I noticed it did actually connect to the Bungie servers (if you watch closely it errors after the connection stage when it tries to 'sign in'). Just as a precaution i rebooted my router (this reassigned a new public ip address by my isp). Once this was done i opened battle.net clicked on Destiny 2 and on the options selected scan and repair. The scan immediately ran through my game files and at the end said i needed to update (again!). I had previously updated and the version had even showed 2.2.2 but after the actions above and rescan it reset itself back to 'Update'. After reapplying the update it now works. The takeaway here is that the original application of the update failed for whatever reason yet produced a 'play' option along with a build update which clearly didnt work.