My 1702 upgrade seems to be stuck. What do?

[Admiral Awesome]

Hi,

I had to update my SCCM environment to 1702 due to the Office 365 update bug. The upgrade went okay until the install procedure copied the new x86 and x64 boot images. Now the installation seems to be stuck for around an hour (nothing happens in cmupdate.log)

These are the last messages my SCCM delivered:

INFO: Default SMS_BootPackageImage instance for x64 already exists. Updating the instance now.    CONFIGURATION_MANAGER_UPDATE    28.04.2017 14:45:55    11116 (0x2B6C)
INFO: The source path for the old boot image package is \\blanked out\SMS_PS1\osd\boot\x64\boot.PS100005.wim    CONFIGURATION_MANAGER_UPDATE    28.04.2017 14:45:55    11116 (0x2B6C)
INFO: Successfully copied the new source WIM file from \blanked out\SMS_PS1\osd\boot\x64\boot.wim to \\blanked out\SMS_PS1\osd\boot\x64\boot.PS100005.wim    CONFIGURATION_MANAGER_UPDATE    28.04.2017 14:45:56    11116 (0x2B6C)

Should I just roll back to my previously made snapshot or wait further until something happens? There are no errors in the log that I could think of being the reason of this?
 

[anyweb]

i'd wait, did you ?

[Admiral Awesome]

I restarted the server and after ~15 minutes SCCM retried the last couple of steps and then finished the update after ~4 hours. But now everything seems to work just fine!