Yet another reason why you should avoid Automatic Update – KB 4039396

Topic

New Reply

If you’re running Win10 Anniversary Update, Microsoft released a fix yesterday that’ll clean everything up — as long as you didn’t install the origin
[See the full post at: Yet another reason why you should avoid Automatic Update – KB 4039396]

Reply | Quote

Replies

Or to put it another way, it’s another reason not to upgrade to Windows 10 if you haven’t done so already (and possibly a reason to revert to your previous OS if you have already upgraded). I’ve lost track of the different versions of Windows 10 and precisely how they differ, and which upgrades apply to which versions, and with what varying degrees of success. Frankly the whole Windows 10 saga seems to be unraveling at the seams, or so it seems to me.  Less secure than its predecessors given the greater number of vulnerabilities reported by MS each month, and an updating system that appears to be wholly unfit for purpose.

3 users thanked author for this post.

FakeNinja, dononline, Cybertooth

Reply | Quote

@Seff, totally agree; W10 has been a mess for two years now and by my reckoning the situation is deteriorating rather than improving. I will never install W10 on any system upon which I rely for money making activities. I learned a long time ago that if you need to change the policy you need to change the people and there are several individuals at MS that have done incalculable damage to the Windows ecosystem IMO.

Reply | Quote

Lucky this is why I wait until it’s Level 3 to patch and what  one’s are safe. I’ll be sure to check windows 10 hide which helps me hide and see the updates that will be installed or waiting to be installed.

So it is safe to install
KB 4039396 as long as you didn’t install the one on August 8th.

Very simple to follow 🙂

1 user thanked author for this post.

dononline

Reply | Quote

I’d wait a few more days, to make sure nothing weird comes out of the woodwork.

Reply | Quote

That’s why I’m waiting until after Labor Day or Wednesday after the day after labor day 🙂 Or next Thursday I mean no rush. When Level 3 happens, those updates get installed the first week of September sometime

Reply | Quote

woody wrote:

Yet another reason why you should avoid Automatic Update –
If you’re running Win10 Anniversary Update,

But if you don’t avoid Automatic Update you won’t be running Win10 Anniversary Update. 😉

Windows 11 Pro version 22H2 build 22621.2361 + Microsoft 365 + Edge

Reply | Quote

???

My brain twisted around the double negative…

Reply | Quote

He probably means that auto update ON = auto upgrade to ver 1703

Reply | Quote

In my initial testing, it looks like KB4039396 causes Get-HotFix to return the wrong date.

Reply | Quote

Ugh. This is headache inducing. I decided ages ago to stick with Win7 on my desktops but allowed my stupid Win8.1 tablet to upgrade to stupid Win10 because I rarely use it and wanted to see what Win 10 was like for future reference. I use WUshowhide regularly on the tablet to keep tabs on the c***** updates MS is trying to foist on me and don’t install anything automatically. Still, I spend far more time researching stupid Win 10 updates and bugs than I actually spend using the stupid tablet.

My conclusion is Win 10 is stupid and I’ve had it up to here with it’s updating nonsense. I spent half an hour yesterday trying to find out what KB 4033637 was all about and like everyone else came up with nothing so I hid it. Combined with the one hour I spent on researching this topic’s update that’s 90 minutes. I haven’t used the darned tablet for anything else in months. I turn it on to check for updates, find out what they are and how they’re going to potentially s**** up my tablet, hide some, install some and then turn the stupid thing off.

In conclusion I’d like to say this stupid OS 10 (and my stupid tablet) are stupid.

Venting concluded.

EDIT html to text – contents may not appear as intended

Reply | Quote

Have to say my complaints about Windows 10 have been primarily about privacy regarding data collection and the forced upgrade path along with forced Windows updates. I believe if Microsoft had kept a more flexible Windows update system and significantly toned down  collection of data to just when a PC actually recorded a fault and ask the end user if it was OK to report that fault to Microsoft. We would see a much more accepting Windows user to Windows 10. We now are at a point where Microsoft is releasing patches to fix patches which for any of us ain’t good. The six month upgrade schedule seems way to frequent for Microsoft to get a handle on properly. This is going to go from bad to worse.

Reply | Quote

Okay.
I have 4034658 Cumulative Buggy? & 4035631 Servicing Stack & 4033637 caution unsure? = Hidden.
What happens to Hidden 4034658 & 4035631 & 4033637  when I install 4039396 stand-alone Cumulative Fix.
Should I install 4035631 Servicing Stack before or after 4039396.

I’m currently at 1607 (14393.1480)

Thanks

 

Reply | Quote

It’s still too early to install August patches.

Wait until the MS-DEFCON level goes down (up?) to 3. Should happen in the next few days.

1 user thanked author for this post.

bjm

Reply | Quote

Nobody should be running 1607 anymore. Creator’s update is finalized and everyone should have moved to it by now. There’s literally no reason left to wait. Especially since the Fall Creator’s update is right around the corner.

Reply | Quote

anonymous wrote:

Nobody should be running 1607 anymore. Creator’s update is finalized and everyone should have moved to it by now. There’s literally no reason left to wait. Especially since the Fall Creator’s update is right around the corner.

Hello anonymous,

If you’re talking to me.  I haven’t been offered CU as yet.  And what does CU get me.   CU discussion is probably off-topic.   Thanks

Reply | Quote

It isn’t that simple, for many reasons. Details coming when we move to MS-DEFCON 3.

1 user thanked author for this post.

bjm

Reply | Quote

woody wrote:

It’s still too early to install August patches. Wait until the MS-DEFCON level goes down (up?) to 3. Should happen in the next few days.

Yes, I always wait until DEFCON 3 or greater.

Thanks!

Reply | Quote

woody wrote:

It isn’t that simple, for many reasons. Details coming when we move to MS-DEFCON 3.

Thanks!  ~ will watch for Details.

Regards w Respect

Reply | Quote

bjm wrote:

woody wrote:

It isn’t that simple, for many reasons. Details coming when we move to MS-DEFCON 3.

Thanks! ~ will watch for Details. Regards w Respect

Okay.  I’ve reviewed Details.
https://www.computerworld.com/article/3221371/microsoft-windows/its-time-to-install-august-windows-and-office-patches-carefully.html
“If you decide to stick with 1607, do yourself a favor and manually install KB 4039396 before you run Windows Update. Running KB 4039396 will preserve your Update history, keep your hidden patches hidden, and add a couple dozen bug fixes in the mix.”

1) Wondering, I have 4034658 Cumulative Buggy? & 4035631 Servicing Stack & 4033637 caution unsure? = Hidden.  What happens to Hidden 4034658 & 4035631 & 4033637  when I install 4039396 stand-alone Cumulative Fix.  Will Hidden 4034658 update be at risk for me to accidentally install.  Should I install 4035631 Servicing Stack before or after 4039396.

Since, @woody “now recommends that 1607 users upgrade to version 1703, the Creators Update, using the Windows Update mechanism, if it’ll work.”

2) What happens to Hidden 4034658 & 4035631 & 4033637  if I install version 1703, the Creators Update, using the Windows Update mechanism, if it’ll work.”

Will wushowhide tool hidden updates do housekeeping.   Or, will wushowhide tool keep accumulating hidden never to be used updates.  And I’ll have to remember which updates are hidden never to be used updates vs hidden may be used updates.

Thanks

 

Reply | Quote

Manually install KB 4039396
Then Unhide the Servicing Stack KB4035631 – you need to install it.
You also need to install the IE Flash Player update.

1 user thanked author for this post.

bjm

Reply | Quote

@bjm: wushowhide probably doesn’t show updates that have been superseded by other updates. If you want a more complete view of what updates have been hidden, you can use Windows Update MiniTool with checkbox “Include superseded” ticked. Even then, you probably won’t see hidden updates that have been expired by Microsoft.

1 user thanked author for this post.

bjm

Reply | Quote

PKCano wrote:

Manually install KB 4039396 Then Unhide the Servicing Stack KB4035631 – you need to install it. You also need to install the IE Flash Player update.

Hi PKCano,
Okay.  4039396 stand-alone installed okay. Update history and hidden updates okay.
wushowhide did housekeeping because 4034658 is no longer listed with hidden.
4035631 Servicing Stack & 4033637 caution (path to 1703) are still hidden.
Flash Player update was installed some time back.

Okay, I’ll do 4035631 now.

I’m currently at 1607 (14393.1670)

Thanks

Edit: paste from https://answers.microsoft.com/en-us/windows/forum/windows_10-update-winpc/windows-10-update-kb4033637/2feb85a7-84b5-47aa-95aa-9c60ef8cd821

“I to am having problems with this update 1607 KB4033637. That update installed correctly, then automatic updates tried to update 1703 creator update. that was on 8-28-17.PC stuck in update in progress ever since ????????????????”

Reply | Quote

MrBrian wrote:

@bjm: wushowhide probably doesn’t show updates that have been superseded by other updates. If you want a more complete view of what updates have been hidden, you can use Windows Update MiniTool with checkbox “Include superseded” ticked. Even then, you probably won’t see hidden updates that have been expired by Microsoft.

Yes, I was unsure what wushowhide would do with 4034658.
I’m satisfied that wushowhide did housekeeping re 4034658 … no longer listed with hidden.
I’ll look into MiniTool.   I’ve been satisfied managing W10 updates thru wushowhide, tools.
Interesting aside: Belarc report still thinks I need 4034658.  😉

Thanks

Reply | Quote

If you didn’t unhide KB4034658 with wushowhide, then it’s probably still hidden but not listed as hidden anymore because you installed update KB4039396, which supersedes KB4034658. If you use Windows Update MiniTool in the manner I previously described, you’ll probably see that KB4034658 is still hidden.

1 user thanked author for this post.

bjm

Reply | Quote

MrBrian wrote:

If you didn’t unhide KB4034658 with wushowhide, then it’s probably still hidden but not listed as hidden anymore because you installed update KB4039396, which supersedes KB4034658. If you use Windows Update MiniTool in the manner I previously described, you’ll probably see that KB4034658 is still hidden.

No, I didn’t as far as I know unhide 4034658.  So, it’s probably still hidden but not listed as hidden.  Works for me.
Okay.  So, I’d use Windows Update MiniTool is place of Microsoft’s Wushowhide tool & Noel Carboni’s ConfigureAutomaticUpdates tool.

Thanks

1 user thanked author for this post.

HiFlyer

Reply | Quote

Wushowhide is probably fine for your update hiding needs. I suggested Windows Update MiniTool for a more complete view of those hidden updates that are superseded, but it’s not something most people should probably care about.

1 user thanked author for this post.

bjm

Reply | Quote

I’m somewhat put off by I don’t have Windows 10 Home with this, but it looks like WUMT should allow all the same controls, despite the lack of the Local Group Policy Editor.  & Caution: I looked at WUMT several month ago, and decided not to recommend it.

https://www.askwoody.com/2017/in-praise-of-windows-update-minitool/

W10 Home

Reply | Quote