Windows 10: So your last update, done on 6/24/2023 @3:00 A.M. destroyed our computers. It made the hard...

The title says it all

:)

 

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

Ste84,

I'm with you. I have noted the same thing on my MDT setup with Creators Update and Fall Creators Update. Suddenly, late last week, this strange action started occurring. I allow the continuation on error for the updates, so it was not a show stopper, but with the default of 7 tries, that many reboots lengthened the time of deployment unacceptably for no decent reason.

Microsoft - Printer - 6/21/2006 12:00:00 AM - 10.0.15063.0
Error: 0x80240017

Things to note:

1. This is a NEW thing. Just started, late last week.
2. The update attempts do not appear in the update history.
3. Manually scanning for updates does not locate/attempt to install said update.
4. It affects, at least, Windows 10 Creators Update and Windows 10 Fall Creators Update (otherwise already fully patched.)

I have seen this on my virtual machine testing environment - I have NOT tested it on a physical machine yet (sounds like you are using physical machines.)

 

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

I deploy machines in bulk via MDT with a Windows Update step in the task sequence. This update appeared some time between Thursday evening and Friday morning here (UTC+8). It fails to install 8 times then craters the deployment. I had to disable the Windows Update task sequence step and run a manual update at the end of the deployments. Interestingly, this update doesn't appear when Windows Update is run manually.




These are brand new Surface Pros being imaged with a clean 1709 build, with no printers or other devices besides the type cover.

Pretty sure this update release is a cockup from Microsoft: 10.0.15063.0 is the build version of the March creators' update (1703), but we're deploying 1709 (10.0.16299.19). And why would XPS and print to PDF driver versions from 2006 be applicable to any version of Windows post-XP? Hopefully they'll realise and pull it sooner rather than later.

 

Problem with March 15, 2023 Update

Hey Greg,

I'm texting from my phone. And watching my Asus finish setting up. Okay . Here it is...

ASUS VivoBook Max

AMD A6-9225 Radeon R4 5 Compute Cores

2 Computing cores, 3 Graphical cores

4.00 GB RAM ( Expandable to 12 GB)

Windows 10 Home

22H2

Installed on 3/24/2023

OS Build. 19045.2328

Windows Feature Experience Pack 120.2212.4190.0

I was all ready to do the step by step Clean Install, yet after I found out by reading Ten Forums and methods six and seven, I decided to go with that. It actually took thirty repetitions of the method they suggested, not three or four, to get past the Automatic Repair option. I finally got to Reset or Wipe choices. I picked full reset ND wiped all my stuff out. It worked.

I am now doing Windows Update for March 2023. If, in a couple of weeks, there are issues with these patches, I'll let you know. Otherwise, thanks for keeping me honest and in earnest.

BK