Thank you so much for your reply. Unfortunately, checking the update and even resetting the update had already been completed prior to posting this message. Again, this is something that has just recently appeared - I have not had this issue before.