Okay, I did some more testing with this and it seems this type of notebook is causing more issues this way. I'll describe them one by one:
1) Because of the first error, the client task doesn't get properly removed from CD. It's stuck in the queue at 99% or 100%. This causes the queue to get full sooner or later and you need to manually cancel these tasks or no new tasks will be able to start eventually.
2) Before restoring partition 1, there is also some error with restoring the GPT table. The error scrolls by really fast, still trying to capture it. It says something about 'this may not be a problem' or something. I'll try recording it.
3) Because of either error 1) or error 2), it is not possible to restore any other image to these notebooks. What I mean is this: I usually have a VM in which I build a clean image with all required software. I can restore this image to other hardware using CD just fine. I also built an EFI image which restores just fine to a VM at least. I can also restore this image to this HP Notebook, but it won't boot. I just get a Windows Blue Screen with boot errors and startup recovery, but it never fixes itself. I suppose this is because of error 1), CD can't write the proper boot file location to the EFI? If I create the base image on another HP Notebook 460, the deployment goes just fine since the partition layout is the same.