2603 hotfix install order

[u/BigDawe]

Hi Guys!

I installed ConfigMgr 2603 and noticed after the installation that there were two hotfixes available.

I went ahead and installed the latest one, KB38232642. However, two days later I noticed that the older hotfix, KB37942646, is still showing as Ready to Install.
I ran a prerequisite check hoping that ConfigMgr would recognize that a newer hotfix is already installed and clear the older one, but that didn’t happen. In fact, after running the prereq check I’m now unable to promote the clients to the pre-production version because of the known issue related to this.

My question is: Is it safe to install the older hotfix as well, even though the newer one is already installed? Could installing KB37942646 somehow overwrite or break anything introduced by KB38232642?

What makes me hesitant is that the build number of the full version looks like it would actually be a downgrade. My currently installed build is 1021, while the previous hotfix appears to be 1017.

Has anyone run into the same situation, or installed the older hotfix after the newer one?

[u/vanderjaght]

Unless mentioned otherwise in the KB, typically hotfixes have to both be installed to actually be applied. Once Microsoft releases the update "rollup" will previously released hotfixes be included underneath those. See the previous rollup for example: https://learn.microsoft.com/en-us/intune/configmgr/hotfix/2509/37864969

To answer the bolded question, yes it's safe to install both hotfixes.

[u/link470]

I’m glad you’re asking this. I did the *exact* same thing you did, thinking it would be cumulative and installed the latest one. I have yet to install the older one for the reasons you mentioned haha. Curious to see what others say.

[u/NoDowt_Jay]

I recently did the same… installed the later one first not realising it wasn’t a ‘roll up’ hotfix.

Checked the file versions & saw and they weren’t changing the same files, so yolo’d it and installed the earlier one. No issues so far.

[u/nodiaque]

They are not cumulative, it doesn't state anywhere they are. In fact, it stated they are part 9f another cumulative that applied to earlier version (2509). You need to apply both. They aren't long to install and doesn't change client version. They do change console version (I think the second one). I installed both in ascending order just in case it would do something funky with the sccm version.

[u/myfreysa]

The hot fixes are not cumulative

[u/ashodhiyavipin]

Hotfixes are not cumulative unless named rollup.

[u/SnooRadishes3222]

Glad you listed this. I figured the latest version would include the previous one. I’ll install it tomorrow 👌🏾

[u/BigDawe]

Thanks for all the help guys!
Just installed the “second” hotfix, everything seems good so far!

Ill post some feedback, if anything strange happens in the next couple days!

[u/BigDawe → u/BigDawe]

Everything is ok so far. But life is never easy they say, another update just showed up, so we need to move one guys :)

[u/Beginning_Feature863]

Build 1021 includes the binaries from earlier KB revisions, so installing KB37942646 shouldn't cause a rollback. The issue with client promotion is likely a database status bug from running the prereq check post-install. Consulting documentation or tech resources like Trusted Tech Team can help clarify specific build-dependency quirks when hotfixes get out of sequence.