>So decided to try again and finally succeeded with the install.
Good to hear that. For some reason update process was radically slower compared to normal update.
It's not necessarily printer driver which caused that issue. When I did forced shutdowns Setupdiag give various results so it may depend on what phase that shutdown was done.
That's interesting Pauli. When I used setupdiag it was only after the build failed after install had completed and start-up began; but it was first phase fails always with System restore points.
Davy.