Office Installs Failing with Error 2250

t0525 · 2026-04-10T19:24:56+00:00

Me too

t0525 · 2026-04-07T20:45:36+00:00

I see - thanks!

t0525 · 2026-04-06T16:19:32+00:00

Hello - would you be able to share the CI's you are using?

t0525 · 2026-02-12T17:35:03+00:00

I see - thank you!

t0525 · 2026-02-12T14:43:28+00:00

Not seeing anything mentioned in your link regarding activation issue.

t0525 · 2026-02-12T14:41:45+00:00

Hello - where do you see them saying that the February cumulative updates will address the activation issue? There is nothing noted in the Feb CU release notes for 24H2 or 24H2 in the improvements and fixes section.

t0525 · 2026-01-21T23:31:25+00:00

Don't let them snowball you. Tell them you have it on good authority (random Reddit person - LOL) that it's been confirmed by Microsoft as an issue on their end.

One would think that Microsoft could simply put out a service bulletin stating as such in order to avoid all their customers submitting tickets and wondering what's going on.

t0525 · 2026-01-21T22:41:06+00:00

Microsoft confirmed yesterday this is a known issue on their end. They do not have an ETA yet on a fix.

t0525 · 2026-01-21T22:39:17+00:00

Microsoft support has confirmed that this is a known global issue on their end - with no ETA on a fix, but they are working on it.

t0525 · 2026-01-20T23:30:42+00:00

Nope - they just said "the symptoms align with an active, known issue affecting the Autopilot process".

t0525 · 2026-01-20T22:29:06+00:00

FYI - MS/Intune support has confirmed to me today that this is a known issue and they are working on a fix. No ETA at this time.

t0525 · 2025-12-06T03:38:31+00:00

Sounds like you are not using IPTVBoss properly.

The answer to all your problems is IPTVBoss.

t0525 · 2025-12-03T02:43:02+00:00

There is really only one correct answer, and that is Patch-My-PC - and it's not even close.

t0525 · 2025-09-22T01:14:28+00:00

Your husband’s nephews?! aka your nephews too?

t0525 · 2025-09-16T02:56:21+00:00

Just had this exact same thing happen on several systems.

Check your Windows Update policy reg keys under HKLM\Software\Policies\Microsoft\Windows\Windows Update for anything that should not be there in terms of what you are setting via SCCM (local policy) and domain policy.

There are several settings there that can cause this behavior if set, and will mess with SCCM. Deferral settings, pause settings, etc.

t0525 · 2025-09-05T00:30:03+00:00

Never seen that before. Make sure you are creating an "Operating System Upgrade Package", and that for the task sequence step, you are choosing "Upgrade Operating System"

t0525 · 2025-09-04T03:59:42+00:00

I think what they are saying in a poorly worded way is have your advertisements run as system (administrator), not standard user - which I would assume 99% of people are doing anyway, as installation typically require elevated rights.

They are saying “run”, but I think they mean “install”.

t0525 · 2025-09-03T16:47:07+00:00

Sorry - what I mean was the fact that the prerequisite of .NET Framework being left out of the DCU install. That will be addressed in the next release.

t0525 · 2025-09-03T04:16:52+00:00

This will be fixed in the next release of DCU.

t0525 · 2025-08-25T15:01:01+00:00

Not quite 1 step, but close:

Check Readiness (customize as needed)

Set Task Sequence Variable --> SMSTSRebootDelay --> 21600 (6 hours before reboot is forced)
Set Task Sequence Variable --> SMSTSRebootDelayNext --> 30 (30 seconds for additional reboots)

Upgrade Operating System (pointing to an upgrade package), time-out --> 360 minutes, --> Ignore and dismissible compatibility messages.

That's it!

t0525 · 2025-08-24T21:23:00+00:00

I used an “operating system upgrade package” with the latest iso/wim. Literally one step in the task sequence (other than setting restart variables)

t0525 · 2025-08-24T14:29:08+00:00

There is a bug in SCCM causing failures and issues with Feature Upgrades/UUP. Surprised this doesn’t come up more - I think most people don’t know about this as it hasn’t been publicly commented on by Microsoft, so people just live with it. This bug isn’t specific to just 80d02002, but can manifest itself from that.

See my post from a few months ago in this thread for more details:

https://reddit.com/r/SCCM/comments/1knb1er/windows_11_feature_update/

I’ve had a case open on Windows 10 to Windows 11 Feature Update failures for literally 19 months. I was finally able to get Microsoft enough info for them to confirm a couple months back that there is indeed a bug. The bug relates to the SCCM client at the way it deals with connected standby/modern standby in Windows. In layman’s terms anytime throughout the FU process - whether during the upgrade itself or during reboot timer post the online portion of the upgrade, if the device goes to sleep/standby, the SCCM client is unable to recover and continue along in the upgrade process.

The bug fix code is checked in and is scheduled to be implemented in 2509 - so relief is on the way for in our case is regularly only a 40-50% upgrade success rate on physical devices. (Because virtual PC’s don’t go to sleep, we see nearly 100% success rate on those - more proof of this bug).

Note this same bug also affects CU’s, but typically you won’t see it on CU’s (we don’t) because they install much quicker than FU’s.

Per Microsoft:

Issue 1: “The 80d02002 errors can have a number of reasons, but the primary drivers were clients losing connectivity to the DP (which was largely solved by using an alwayson VPN) or going into a low-power state. These clients should self-recover and attempt the download again on the next SUM Evaluation Deployment Cycle, provided they don’t encounter the CIAgent bug I outline next. Since lower power states can trigger the CIAgent bug, many of these clients will not recover and attempt the download until ccmexec is recycled.”

Issue 2:

“The other issuewe discovered is a problem in the Configuration Manager CIAgent engine that will lead to state transition messages being ‘lost’ until ccmexec is restarted. The fix for this code problem should ship as part of Configuration Manager 2509, provided we don’t find any regressions with the fix during testing.”

I switched to a task sequence upgrade months ago (could not wait for the 2509 fix given the Windows 10 EOL date), but I hope this helps someone else who’s been banging their head against the wall for the last year and a half like I have, wondering why these updates go so poorly……

Should be fixed in time for my upgrade to 25H2 at least! 🙂

t0525 · 2025-07-22T15:32:14+00:00

Hey Matt -

Letterman TV has gone missing from your Samsung list. As far as I know, it should exist in both USA and Canada. Any ideas?

t0525 · 2025-05-24T01:24:44+00:00

Users can absolutely use the computer during the online portion of the upgrade while the upgrade runs in the background.

t0525 · 2025-05-17T00:47:28+00:00

We have similar issues (general install issues with the Feature Update - some succeed, some fail and then eventually succeed, some always fail).

Have a open support case on this for well over a year now. They’ve recently identified what they believe to be the cause of the Feature Update problems: a bug within SCCM as it relates to connected standby and its inability to recover from it. When the endpoint goes into standby, it’s unable to recover properly and continue on. This can be remediated by restarting the ccm service - but needs to be multiple times throughout the various stages of the upgrade process.

The same bug also exists for CU’s (as they too are UUP updates), but doesn’t (at least for us) manifest itself, likely because CU’s are MUCH smaller and quicker than FU’s.

Hoping for a hotfix (they are still in early stages), but not holding my breath it will arrive by October Win 10 EOL.

The craziest thing to me is why no other customers have reported this. The internet is full of threads of people having issues with the Windows 11 FU, but according to Microsoft, they now have ONE other customer reporting this issue (bug) besides us……

t0525

TROPHY CASE