Can't resume synchronization after patch failed on secondary node of Availability Group
When you restored the VM, its LSN was no longer in sync with the primary and thus it can't be resumed. The primary is too far ahead to resume. 

You'll need to drop the secondary and add it to the Availability Group again in order to resume synchronizing. You can do this with an existing FULL backup plus the LOG chain.