Complete an in-place Windows upgrade without Dynamic Update

An in-place Windows 10 or Windows 11 feature upgrade can fail or remain indefinitely at Making sure you're ready to install while Setup searches for, downloads, or stages Dynamic Update content. Dynamic Update is the part of Windows Setup that can obtain Setup fixes, Safe OS updates, servicing-stack or cumulative-update content, and applicable drivers during the upgrade.

This procedure runs Setup from current Microsoft installation media while preventing Dynamic Update during that one upgrade attempt. It does not disable Windows Update permanently, bypass hardware eligibility, or prove that Dynamic Update caused every failure carrying the same code.

Searchable Windows error codes and exact messages

Use this procedure when:

• Windows 10 or Windows 11 still starts normally enough to run setup.exe from inside the installed Windows session;
• the requested operation is an in-place feature upgrade or repair upgrade, not a clean installation booted from USB;
• Setup displays 0x80888002, 0x80888002 - 0x40008, or remains at Making sure you're ready to install;
• the target edition, architecture, language, and supported upgrade path have been confirmed;
• no explicit compatibility, disk-space, licensing, storage, or hardware failure explains the stop; and
• the previous attempt used online update acquisition, or its logs show activity involving Dynamic Update, update download, or Safe OS update staging.

Do not use this procedure to bypass Windows 11 hardware requirements, Secure Boot/TPM eligibility, a Safeguard Hold, an incompatible application or driver named by Setup, insufficient space, an unsupported edition/language path, damaged storage, or an installation that cannot start.

It does not apply to a clean installation started by booting from USB. Microsoft's /DynamicUpdate upgrade control applies when Setup is started from a running Windows 10-or-later installation, not to the normal WinPE clean-install path.

Do not treat every Making sure you're ready to install screen as hung. Setup can legitimately take time while evaluating compatibility. Continue only after activity and logs establish that progress has stopped or repeatedly fails at the same point.

The particular Dynamic Update package, server-side condition, or transient network transaction that caused the original stop may remain unknown if the offline attempt completes.

The following may not remain unknown:

• source and target Windows versions;
• target edition, display language, and architecture;
• whether Keep personal files and apps is offered;
• the complete result and extend codes from the failed attempt;
• available system-volume space;
• whether Setup reported a compatibility block; and
• whether the media came from Microsoft and matches the intended release.

An exact installed build is not needed merely to choose Not right now. It is required when selecting media for a same-version repair upgrade or when the target release has a specific compatibility or servicing requirement.

• A verified backup of important files
• Stable AC power
• Administrative access to the running Windows installation
• Current Microsoft Windows 10 or Windows 11 ISO/media for the intended release, edition, language, and architecture
• At least the free space Windows Setup requires, plus working space for rollback files
• Copies of the previous Setup logs before another attempt overwrites or rotates them
• Recovery media or a known way to enter WinRE if Setup rolls back badly
• The Windows product/license state required for the intended upgrade

Do not delete Windows.old, $WINDOWS.~BT, or Panther logs before preserving the failed-attempt evidence.

Start in the Windows installation being upgraded. Sign in with an administrator account. Do not boot from the ISO or USB.

Disconnect nonessential external storage, docks, printers, capture devices, and specialty USB hardware. Keep the keyboard, mouse, display, network adapter until the offline step, and any device required to access the system disk. Do not change firmware mode or storage-controller mode.

Restart Windows once so no earlier Setup instance or pending restart remains. Confirm that ordinary Windows starts again before continuing.

1. Record the exact message and both code halves. Photograph the screen if possible. Distinguish 0x80888002 from 0x80888002 - 0x40008.

2. Record the installed version, edition, build, language, and architecture:

   winver
   dism /online /Get-CurrentEdition
   dism /online /Get-Intl
   echo %PROCESSOR_ARCHITECTURE%
   

3. Confirm free space on the Windows volume in File Explorer or with:

   fsutil volume diskfree %SystemDrive%
   

   Stop if Setup already displayed 0xC190020E or the volume lacks the required working space.

4. Preserve the previous attempt's logs in an elevated Command Prompt:

   md C:\SetupEvidence\FIX-064
   robocopy C:\$WINDOWS.~BT\Sources\Panther C:\SetupEvidence\FIX-064\Panther /E /COPY:DAT /R:1 /W:1
   robocopy C:\$WINDOWS.~BT\Sources\Rollback C:\SetupEvidence\FIX-064\Rollback /E /COPY:DAT /R:1 /W:1
   copy C:\Windows\Logs\MoSetup\BlueBox.log C:\SetupEvidence\FIX-064\BlueBox.log
   

   A path can be absent depending on where Setup stopped. Record a missing path instead of claiming it was copied.

5. Run the SetupDiag included with the failed Setup files when available, or the current Microsoft SetupDiag, and save its output outside $WINDOWS.~BT. Do not assume the last visible screen identifies the root cause. If SetupDiag names a driver, optional component, application, disk-space problem, or compatibility block, route to that finding first.

6. Search the preserved setupact.log, setuperr.log, and BlueBox.log for the exact result code, DynamicUpdate, DU, Download, SafeOS, abort, and the timestamp of the stop. Use the last fatal occurrence, not the first warning in the file.

7. Confirm that the ISO is suitable before mounting it:

   • It came from Microsoft.
   • Its architecture matches the installed Windows architecture.
   • Its base display language supports keeping apps and files.
   • Its edition has a supported path from the installed edition.
   • Its build is not older than the installed build for a repair upgrade.

8. Mount the ISO, note its drive letter, and run setup.exe only far enough to inspect the choices. Stop if Keep personal files and apps is unavailable when retaining the installation is required. Do not continue by silently accepting Nothing.

The diagnosis is sufficiently bounded when online Setup repeatedly stops at the same acquisition/readiness point, no explicit hard block is present, appropriate media is available, and offline Setup presents the expected retain-apps-and-files choice.

Branch A — Interactive Setup, preferred

1. Cancel any open Setup window and restart Windows.

2. Mount the verified ISO. In File Explorer, right-click the ISO and select Mount. Note the mounted drive letter.

3. Disconnect the computer from the Internet for this attempt:

   • unplug Ethernet; and
   • turn off Wi-Fi from Quick Settings.

   Do not disable or uninstall the network adapter.

4. Open the mounted ISO and run setup.exe as administrator.

5. On the page that asks how Setup should download updates, select Change how Windows Setup downloads updates or the equivalent link presented by that build.

6. Select Not right now, then continue. This choice applies to this Setup run; it does not permanently disable Windows Update.

7. Review the final summary. Require all of the following before selecting Install:

   • the intended Windows edition;
   • Keep personal files and apps, if preservation is required; and
   • no unresolved compatibility warning.

8. Select Install. Keep stable power. Do not reconnect networking, remove the system disk, force a shutdown, or boot from the mounted media during the offline phases.

9. Allow Setup to restart as required. If a one-time boot menu appears, choose the normal Windows Boot Manager for the installed system, not the installation USB.

10. After the desktop appears and section 12 baseline checks pass, reconnect networking and run Windows Update normally.

Branch B — Documented command-line control for an interactive upgrade

Use this branch only when the graphical link is absent but the correct ISO is mounted and Setup is being started from the running Windows installation.

1. Open an elevated Command Prompt.

2. Replace <ISO-letter> with the mounted ISO drive letter and run:

   <ISO-letter>:\setup.exe /auto upgrade /dynamicupdate disable
   

3. Continue interactively if Setup presents its normal pages. Verify the edition and final retention summary when those pages are shown. The /auto upgrade switch selects the upgrade path, so it does not guarantee a separate retention-choice dialog.

4. If Setup exits without presenting a window, record the command's exit code and preserve the newest Panther/SetupDiag evidence. Treat that as a failed diagnostic attempt; do not infer that the retention choice was accepted and do not add /quiet or compatibility-bypass switches.

5. If Setup rejects the command line, close it and use Branch A. Do not invent alternate switches.

• If Setup passes Making sure you're ready to install and completes, Dynamic Update avoidance was an effective workaround for that attempt. It does not prove which downloaded package or transaction was defective.
• If Setup now reports a named application, driver, feature, disk-space, or eligibility block, stop and resolve that specific finding.
• If the same result and extend code return offline, disabling Dynamic Update did not isolate the cause. Preserve the new logs and compare the final fatal entries with the prior attempt.
• If Setup rolls back, let rollback complete. Do not repeatedly restart Setup before preserving the Rollback and Panther logs.
• If Keep personal files and apps disappears, cancel. Wrong media language, edition, architecture, or an unsupported upgrade path must be corrected before retrying.
• If Windows no longer starts after rollback, use WinRE and the code/file path now displayed; do not repeat this article from recovery media.

• Do not use offline Setup to bypass a Safeguard Hold or Windows 11 eligibility block.
• Do not choose Keep nothing as a substitute for a failed in-place upgrade unless data destruction is the explicit, backed-up intent.
• Do not download modified ISOs or hardware-bypass scripts.
• Do not add /compat ignorewarning to hide an unidentified compatibility problem.
• Do not delete Setup logs, $WINDOWS.~BT, or Windows.old before the result is verified.
• Do not disable all services, delete Windows Update databases, or remove drivers without a named cause.
• Do not change UEFI/legacy mode, Secure Boot, TPM, storage-controller mode, or partition layout for this symptom.
• Do not assume 0x80888002 always means Dynamic Update; the evidence supports a bounded workaround, not a universal diagnosis.

Before selecting Install, close Setup to abandon the attempt; no boot-stage rollback is required.

If Setup fails after installation begins, allow Windows Setup to perform its automatic rollback. Do not power-cycle during rollback unless the machine has shown no storage activity and no progress for an independently justified hardware-recovery interval.

If the upgrade completes but must be reversed and Windows offers the supported rollback option:

1. Keep Windows.old intact.
2. Open Settings > System > Recovery in Windows 11, or Settings > Update & Security > Recovery in Windows 10.
3. Select Go back only if the option is available and the required files remain.
4. Preserve new Setup logs before starting the reversal.

If Go back is unavailable, do not fabricate it with BCD or folder renames. Restore the verified system backup or use the appropriate supported reinstall/recovery plan.

1. Sign in and run winver. Confirm the intended target version/build.
2. Confirm the expected edition with dism /online /Get-CurrentEdition.
3. Confirm personal files, installed applications, user profiles, activation, networking, audio, display, and storage devices.
4. Restart twice and perform one full shutdown/cold start.
5. Review Device Manager for newly failed devices; do not treat hidden historical devices as new failures.
6. Reconnect networking and run Settings > Windows Update > Check for updates. Dynamic Update was skipped only during Setup; ordinary servicing must work afterward.
7. Confirm that no new rollback directory or Setup failure result exists.
8. Retain the before/after Setup logs until the system has remained stable through normal use and a new backup has been made.

Confidence is 80% for cases that match this evidence boundary: Windows starts, an in-place upgrade using online acquisition repeatedly stops at 0x80888002, 0x80888002 - 0x40008, or the final readiness stage, no explicit hard block exists, and the same supported upgrade completes from verified media with Dynamic Update disabled. This is not an 80% claim for every occurrence of those identifiers.

Stop and escalate to log-directed diagnosis when SetupDiag names another cause, the media cannot retain apps and files, storage is unstable, a compatibility/Safeguard block exists, the same failure repeats offline, rollback cannot complete, or the machine no longer starts. No independent TechXplored reproduction has been performed for this article.