Why "StartDocPrinter was not called"?

Question

Windows

Comrades, I'm confused, help me figure it out. I don’t understand the essence of what happened ...
1) There is an image of windows 10 1803 (taken from a LC with Microsoft)
2) Installed on a PC
3) Upgraded to windows 10 1909 through WSUS
4) Installed "office" software (office, acrobat, 7zip ) + symantec antivirus.
5) sysprep
6) Removing the image with an acronis.
7) We roll out the image on exactly the same PC
8) We enter the PC into the domain, connect the network printer
and ..... when we try to print, we get an error: "StartDocPrinter was not called"
How!????? System "zero" flies did not fuck ......
In the Internet there are similar cases, but already on PCs that have been working for a long time. But then ...... At what stage? Why? It seems that everything was taken into account when forming the "golden" image. I did not do any tuning, did not delete or disable anything ....

Answer 1

Naturally, I installed firewood, both fresh and those that already work on other 10s