Thank you for reaching out to Microsoft Q&A Platform .
The suspected root cause is either of the following :
1) Either you are hitting a known bug which was fixed recently , Which had exactly the same symptoms .
or
2) The other disk which you are talking about is not created from the current VM backups .
The only workaround in your situation is as follows:
1) Take a snapshot of the current OS Disk again .
2) Create a new Disk out of the snapshot in the same region/zone where the current VM is running .
3) Use this newly created disk to swap the OS .
4) And you can delete the previous backup disk that you are talking about .
Hope this helps in use case .
Thanks & Regards,
Pradeep
Pease don't forget to accept the answer if this was helpful .