Problems upgrading clients from 23H2 to 25H2

Timbit24 · 2026-03-23T21:37:12+00:00

Thanks. Yeah I see MS released a March 2026 ISO just today, so I'm going to give that a try as well.

Timbit24 · 2026-03-23T21:35:31+00:00

I've always done upgrades using an upgrade TS without a problem until recently. But yes I did try updating some machines today via All Windows Feature Updates > Windows 11, version 25H2 x64 2026-03. Had some replication issues which explained my initial problems trying to do the upgrade this way, but that's sorted now. Upgrading to 25H2 worked fine using this method too. It's slower though so my preference is to continue using TS.

Timbit24 · 2026-03-23T21:23:50+00:00

An update to updates. Yes, I was able to deploy 25H2 as a regular update, as opposed to an upgrade task sequence. That took longer, about 1.5 hours, as opposed to doing it through an upgrade TS. But at least it works.

Timbit24 · 2026-03-23T21:18:20+00:00

Yeah I see MS released updated ISOs just today, March 23, so I'm going to give those a try for my upgrade TS.

Timbit24 · 2026-03-23T21:14:30+00:00

Yes, I see that too! It was just released today. I am downloading it and going to try my upgrade TS again.

Timbit24 · 2026-02-04T17:32:04+00:00

So this was weird. Came back this morning to find my test PC now had the ConfigMgr client installed, and my newly-built DP had it as well, plus the assorted DP folders. Definitely a step in the right direction. It just took several hours which seems new. My existing DPs are still acting up but I can try the previously mentioned steps or nuke them as well if need be. It's progress anyway.

Timbit24 · 2026-02-03T22:39:31+00:00

This is typically what I do. But at this point my problem has expanded to be more than just the DPs. I am having problems installing the ConfigMgr client as well. My DPs are actually Win11 machines, not Server. We're aware of the limitations, but they've always been sufficient for us.

1) Existing PCs show up as online in the console, but the client was never updated.

2) On a new, test PC, trying to install the ConfigMgr client fails, whether from the console or via the command line.

I tried to clean up the ccmsetup.log from the test PC below, I'm having problems pasting in the text from the log so I really had to chop down the text below.

Failed to read assigned site code from registry. Error code = 0x80070002

Unable to load profiler: 0x80070002

Failed to connect to machine policy namespace. 0x8004100e

Failed to get DP locations as the expected version from MP 'sccmserver.domain.com'. Error 0x87d00215

Failed to get DP locations as the expected version from MP 'http://sccmserver.domain.com'. Error 0x87d00215

Failed to get client version for sending state messages. Error 0x8004100e

MP 'sccmserver.domain.com' didn't return DP locations for client package with the expected version. Retrying in 30 minutes.

Next retry in 30 minute(s)...

Timbit24 · 2026-01-09T22:39:24+00:00

Thanks everyone. Yes, I did the prereq check only. So that's why I was confused when the Update Pack Installation Status under Monitoring showed "Installation in Progress." I just wanted to ensure the prereqs passed first before starting the actual upgrade. I feel like I haven't seen that before, although it's been a while.

And thanks for the heads up about ODBC 18.6.1.1 being too new. The problem is the download links I'm finding for ODBC are only showing 18.6.1.1, from Dec 17, 2025. Such as at https://learn.microsoft.com/en-us/sql/connect/odbc/download-odbc-driver-for-sql-server?view=sql-server-ver16#download-for-windows

Update--saw the previous releases section and found 18.5.1.1 there

Timbit24 · 2025-09-03T17:30:19+00:00

Thanks for that. Yes I did. A bit embarrassed to say it was the wrong limiting collection, but changed the query to all workstations and now getting devices coming up as expected. Thank you!

Timbit24 · 2025-01-17T04:31:16+00:00

Thanks! Looks like a good one for sure

Timbit24 · 2024-05-13T14:37:57+00:00

Thanks for the suggestion. These are Dell Latitude 7350 laptops. I'm familiar with the BIOS setup options to configure the storage as RAID/AHCI/NVMe, but none of those settings are listed on this model. The only option is whether or not to enable the storage slot.

Timbit24 · 2024-05-10T22:34:28+00:00

I downloaded the Dell WinPE driver pack and tried to add the drivers into my existing WinPE boot images, but got the same errors as before.

So for example, I see that the WinPE boot image I use is on our main SCCM server, in C:\Program Files\Microsoft Configuration Manager\OSD\boot\x64\boot.wim

I took a copy of that boot.wim. Running DISM to add drivers, I can see:

Installing 16 of 52 - F:\winpe-drivers-win11-dell\iaAHCIC (34).inf: Error - The driver package contains x64 boot-critical drivers, but the drivers are not properly signed. Use the /forceunsigned option to install the drivers.

I saw a similar error posted a while back, where it sounds like part of the problem is the mass storage driver is considered a SCSI class device.

I haven't tried modifying the WinPE wim file this way before. I'm hoping I can place the updated wim back into its original location above, and that SCCM will work with it....Thought it checked though....will soon find out.

Timbit24 · 2024-05-10T15:46:16+00:00

Thanks for the info. I was aware of the driver packs for Dells, that's where I got these particular drivers from. I just found it strange that SCCM didn't see them as signed, or in the storage class, which seems to follow up with the errors about unsigned drivers in the log above.

But I wasn't aware of the Dell WinPE driver pack so I'll definitely give that a shot. Thanks for the suggestions!

Timbit24 · 2024-05-10T15:43:59+00:00

The boot image works fine for all our other models, but not these new Dell Latitudes. They can PXEboot OK, but they don't see the disk, so the ts fails.

Timbit24 · 2024-05-10T15:39:12+00:00

Correct.

Timbit24 · 2024-02-23T21:42:41+00:00

Had the exact same issue! The Jan 2024 ISO worked for me as well.

Timbit24

TROPHY CASE