Replies

The late timing of this E(?) week update makes it pretty much useless, might as well wait few days for patch Tuesday. I wonder if this is record for Microsoft to cut it this close?

Also, this update mysteriously appeared and then disappeared from my Windows Update, after I selected it to be installed. So I guess I’ll just ignore this update anyway.

I’m guessing it will appear to Windows Update today.

And since in about week and half it’s patch tuesday again, installing this optional update is kinda pointless for most. Would it kill MS to release these D week updates on C week like the rest of them?

1 user thanked author for this post.

woody

I wonder why the newest Windows 10 versions always are always week or more behind of the older ones to get these optional updates.

It kinda diminishes the benefits of the whole optional update round because often next official patch Tuesday looms only week or so ahead. So why bother releasing these D week updates at all to public?

It’s also one more thing discouraging to be on latest Win10 version – you’ll be ‘rewarded’ by getting fixes later than others.

Didn’t this patch sit like over a week at release preview ring? So much use for that.

Might have probably just send it straight to public with the 1809, 1803 and 1709 patches. Then MS could have had time to get this fixed in third patch round by the end of this month. Now it’s likely to be fixed late next month as regular patch Tuesday is less than 10 days ahead, no way MS is going to bother hurry to fix for this by then.

1 user thanked author for this post.

woody

KB4512941 for 1903 just dropped.

Once again,  Microsoft’s “latest and greatest” Windows 10 gets to be the last one. And since we’re in for next month’s updates in just ten days, I gotta wonder, is there a point for this kind release cycle? Most users who are on 1903 and just go with default automatic update settings have been scratching their heads over two weeks, wondering why their VB apps stopped working.

Microsoft seriously works hard to make being on their latest Windows 10 unrewarding for users.

3 users thanked author for this post.

Charlie, lanceboil, woody

1709?

Microsoft’s release order logic for these patches-of-patches is baffling to say the least. It often seem to be ‘last comes first’, though not always.

Anyway, I’m betting that we who are brave enough to use 1903 will have to wait again until the last week of the month. Just another ‘reward’ for using ‘latest and greatest’.

Thanks again, Microsoft.

I wouldn’t have minded if MS had released fixes for 1903 too. I guess us suckers who foolhardily installed Microsoft’s ‘latest and greatest’ can wait ’till end of month (or even next month), as it was before with 1809. Can’t really figure the release timing logic of these ‘patches for patches’. Though I don’t know if there is any.

Does anyone have a clue, why MS is now delaying these third Tuesday patches for 1903 ?

Before 1903 was released, 1809 got similar delay treatment for monthly second round patches, but I was under impression this was because of 1809’s LTSB status and MS wanted to be just a little more cautious with it.

In my opinion, this kind of late month release schedule is rather frustrating, because it leaves little time between next month’s patch Tuesday and lots of time to enjoy things which were broken in current month’s patch Tuesday patches.

Like in this month: Event viewer.

There sure isn’t any reward to follow ‘latest and greatest’ version of Windows, except maybe that you don’t have to stay vigilant to fight unexpected feature updates.

 

It sure did get installed on all my machines.

Microsoft – one step forward, two steps backward, again.

Tested this on two of my laptops.

Win10 Pro + SAC + Feature update deferral(365 days) + Check WU -> No KB4458469 from WU

Win10 Pro + SAC(T) + Feature update deferral(365 days) + Check WU -> No KB4458469 from WU

Win10 Pro + SAC(T) + Check WU -> KB4458469 installs

Win10 Pro + SAC + Check WU -> KB4458469 installs

It would seem that this CU depends on whether you have Feature update deferral enabled. That’s weird.

 
Edit: nope, scratch that. The CUs that were installed on my laptops, were the older KB4464218. I can’t get the KB4458469 from WU with any of the above combinations.

2 users thanked author for this post.

Elly, woody

Ah, the new release seems to be off with a start as good as you could expect from the history of Windows 10. Can’t wait to see what other surprising bugs have slipped from Microsoft’s “Users as QA” process.

Original reporter @juzuo here again,

I copied the O&O Shutup10 tool’s configuration from my force-upgraded laptop to a virtual machine running 1703, but so far I can’t get it to upgrade as physical machine did.

Maybe there are some additional requirements that trigger the force-upgrade.

This is a bit puzzling.

2 users thanked author for this post.

Elly, woody

Original reporter here.

I just tried to do a test install of 1703 to a virtual machine, to see if it would force-upgrade itself as my laptops did, but after installing and giving it few reboots and update rounds, it doesn’t seem to be upgrading to 1709.

The Microsoft’s info page about this does say:

This update is also offered directly to Windows Update Client for some devices that have not installed the most recent updates.

I guess ‘some devices’ is a limited selection. Maybe this applies only to physical machines?

Both my laptops that were forcibly upgraded from 1703 to 1709 had Feature Updates deferred for 365 days and they both had been clean-installed just month ago (so deferring period wasn’t run out).

Quality updates weren’t deferred nor were the updates paused. Don’t know if they might have prevented this from happening.

In any case, this was a nasty surprise. Windows didn’t even care that laptop was running on battery. Would have been even nastier, had I been on the road and the upgrade procedure had failed, leaving me with unbootable Windows. Luckily I was at home and the upgrade seemed to go through ok.

1 user thanked author for this post.

woody