Very interesting - thank you for sharing, good sir!
And yes - this is certainly a good place for it .
A couple of additional points:
Assuming you're upgrading / provisioning OS'es via WIM's, you CAN patch the WIM itself. If you google for "WIM offline patching" you'll get a bunch of hits and "pick your favourite" to go with.
Gotchas to look out for there (I've done a bit of research for a Provisioning Webinar I've hosted recently):
- Not *ALL* patches can be installed offline (example being - .NET 4.0 on Windows 7).
- SOME updates can bork your OS install itself as well (see here - http://iboyd.net/index.php/2013/01/04/applying-kb2506143-to-an-offline-windows-7-sp1-wim-windows-setup-fail/ - for an example).
The above examples may be specific to Windows 7, but "sooner or later" the odds are you'll run into this sort of issue with Windows 10 as well.
But this is indeed a very interesting gotcha!
Thanks for the references. We are not doing any offline patching nor do we use the WIM method. I'm still seeing this come up again in my processes. I am slowly moving other patches out. 3081449 & 316017 I've now tried pulling out.
Consistently if we force the reboot (power off and power on) it will proceed with no further issues.)
I'll keep this updated if I can get to a singular root cause.
Happy to help along a little bit.
You can always just include that oldest of Windows "fixes" (that infamous "Have you tried turning it off & on again" ) routinely in there. Because Microsoft ... or weird install shenanigans.
Possible that you've got one of those "lovely" situations where your install routine is having a weird hiccup unique to your environment / combination - in which case the above links should give you an idea as to the generally likely nature of things, but it'll be a lot of research / effort to chase down. It may be overall easier just accepting an additional reboot in there for the sake of your sanity / getting on with things.
Some IT gremlins seem to still demand that reboot even though one would think that some 30+ years on, we'd figure that one out a bit better. Ah well ... drivers (usually, I find).