The update went smoothly; however, this old issue (which was fixed in A11 later in a patch) returned after updating to A13: