Can't get rid of Printer-6/21/2006 12:00:00 AM 10.0.15063.0 update

I set the update step to continue on error originally but it looked like it was still failing the deployment, but I had another post applications Windows Update step at the end I forgot about - d'oh. I disabled one and set the other to continue on error and it does now complete with the same warning you show.

To speed up the 8 reboots thing, edit this file: %DeployRoot%\Scripts\ZTIWindowsUpdate.wsf

On line 30 change:

Const MSIT_WU_REBOOT_MAX = 7

to a lower value. I used 2, maybe even 1 would be fine (max 2 passes).

Yep - I changed that to two (see the image), but I don't like that low of a number in particular.

I have also have changed my task sequences as the other answer given here earlier (missing now) suggested -- where the XPS service and Print to PDF role/feature is removed early in the task sequence and put back late in the task sequence - just to see if that would 'work around' the issue - but I have not actually tried it.

About to. Will update.

Very interested to see what your results are. Just started seeing this driver fail all our deployments and thought I was going crazy. Glad I'm not the only one. This has happened for me with both 1703 and 1709 deployments.

Putting in the uninstall of the XPS Service and Print to PDF at the beginning of the task sequence and re-installing them at the end got rid of the error/extra time - so worth it that way - not worth it from a 'what the heck is Microsoft doing' aspect. ;-)

shenans said:

Putting in the uninstall of the XPS Service and Print to PDF at the beginning of the task sequence and re-installing them at the end got rid of the error/extra time - so worth it that way - not worth it from a 'what the heck is Microsoft doing' aspect. ;-)

Do you mind sharing how you added the uninstall/install? Please excuse my ignorance, I've only been working with MDT for a few months now. :)

No problem.

Someone else posted this earlier in this conversation (pontuswendt), but they took it down (or someone did) - so let's see if it sticks if I link it again (hope they do not mind it):
ZTIWindowsupdate has run And Failed too Many Times. Microsoft Client Management

It's a decent post / description of what you would need to do.

shenans said:

No problem.

Someone else posted this earlier in this conversation (pontuswendt), but they took it down (or someone did) - so let's see if it sticks if I link it again (hope they do not mind it):
ZTIWindowsupdate has run And Failed too Many Times. Microsoft Client Management

It's a decent post / description of what you would need to do.

Excellent! Thank you very much! Now I just need to get my custom Start menu layout working and I'll be all set.

Issue bled over into my Insider Preview build 17040 this morning.

I resolved this in my MDT share by setting my CustomSettings.ini (<MDT Share>\Control\CustomSettings.ini) to ignore the updates.

;Exclude Microsoft - Printer - 6/21/2006 12:00:00 AM - 10.0.15063.0
WUMU_ExcludeID2=0fbb4325-056c-4fcb-8f13-36a5b19020fd
WUMU_ExcludeID3=b57027c8-2e8f-4196-ac30-d4698939f668

bensmitty said:

I resolved this in my MDT share by setting my CustomSettings.ini (<MDT Share>\Control\CustomSettings.ini) to ignore the updates.

;Exclude Microsoft - Printer - 6/21/2006 12:00:00 AM - 10.0.15063.0
WUMU_ExcludeID2=0fbb4325-056c-4fcb-8f13-36a5b19020fd
WUMU_ExcludeID3=b57027c8-2e8f-4196-ac30-d4698939f668

I am having exactly the same issue. I tried to do as you suggest with no joy. This is what I added:


Do you know the KB by chance that are related to these drivers? Maybe we can use the KB##### format to exclude the updates on the deployment.