Fix Windows Update Error 0xc19001e2

Issue type: Windows feature update preinstall script failure | Applies to: Windows 10, Windows 11

0xc19001e2 windows update error usually means Windows Setup failed during a preinstall script step before the feature update could continue. Microsoft identifies 0xC19001E2 as MOSETUP_E_PREINSTALL_SCRIPT_FAILED, which means a preinstall script failed to execute or returned an error. The strongest fix is to read the setup logs, remove software that injects setup scripts, clean the upgrade cache, repair Windows Update, and retry with the Windows Installation Assistant or ISO setup.

This is not the same as 0xC1900101. Error 0xC1900101 usually points to drivers. Error 0xC19001E2 points more directly to a setup script failure before the upgrade can continue.

The most useful evidence is in the Windows Setup logs. Do not guess first. Check the logs, then remove the blocker that setup identifies.

What to Do First: Fix 0xc19001e2 Windows Update Error

1. Restart the PC and make sure no update restart is pending.
2. Open C:\$WINDOWS.~BT\Sources\Panther\setuperr.log if the folder exists.
3. Search the log for 0xc19001e2, preinstall.cmd, script, and MOSETUP_E_PREINSTALL_SCRIPT_FAILED.
4. Uninstall or disable the software named near the failure, especially encryption, endpoint security, VPN, device management, or OEM utilities.
5. Clear the Windows Update and setup cache so Windows downloads a fresh upgrade package.
6. Retry the upgrade using the Windows Installation Assistant or mounted ISO if Windows Update fails again.

Fix 2: Read setuperr.log and setupact.log First

Feature update errors are easier to fix when you read the logs. The message beside 0xc19001e2 often identifies the failed script, folder, or product that blocked setup.

Check these paths:

C:\$WINDOWS.~BT\Sources\Panther\setuperr.log
C:\$WINDOWS.~BT\Sources\Panther\setupact.log
C:\Windows\Panther\setuperr.log
C:\Windows\Panther\setupact.log

Open the logs in Notepad and search for:

0xc19001e2
preinstall.cmd
MOSETUP_E_PREINSTALL_SCRIPT_FAILED
script failed
return code
rollback

The line before the error is often more important than the error line itself. It may show the script path or application component that failed.

Fix 3: Remove Security, Encryption, VPN, and Management Tools Temporarily

Preinstall script failures are often caused by software that hooks into setup or controls the system before upgrade. This includes endpoint protection, encryption, VPN, device management clients, OEM update utilities, and old cleanup tools.

1. Temporarily uninstall third-party antivirus or endpoint protection.
2. Temporarily uninstall VPN clients.
3. Temporarily uninstall disk encryption or device control tools if they are not required by your organization.
4. Temporarily uninstall OEM update utilities that manage drivers or BIOS updates.
5. Restart the PC before retrying the feature update.

If the PC belongs to a company or school, do not remove managed security or encryption tools without IT approval.

Fix 4: Run the Windows Update Troubleshooter

If the error appears while upgrading through Windows Update, run the troubleshooter before clearing files manually. It can repair update scan, download, and service states that prevent setup from starting cleanly.

1. Open Settings → System → Troubleshoot → Other troubleshooters.
2. Run Windows Update.
3. Apply suggested fixes.
4. Restart the PC.
5. Try the feature update again.

If Windows Update never starts downloading the upgrade, use Windows Update not downloading to check service and download causes.

Fix 5: Clear the Windows Update Upgrade Cache

A damaged feature update payload can trigger setup failures before installation begins. Clearing the update folders forces Windows to download a fresh upgrade package.

net stop wuauserv
net stop bits
net stop cryptSvc
net stop msiserver
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 catroot2.old
net start msiserver
net start cryptSvc
net start bits
net start wuauserv

Restart and run Windows Update again. If the upgrade is stuck at the beginning of download or preparation, check Windows Update stuck at 0 percent.

Fix 6: Remove Leftover Windows Setup Folders

Windows Setup can reuse old setup data after a failed feature update. Remove old setup folders only when no update is currently running.

Important: Do not delete these folders while Windows Update is actively downloading, installing, or showing “working on updates.” Close Windows Update first and restart the PC before cleanup.

1. Open File Explorer.
2. Enable hidden items.
3. Check the C: drive for $WINDOWS.~BT and $WINDOWS.~WS.
4. Use Disk Cleanup or Storage Sense to remove old Windows setup files when available.
5. If manual deletion is blocked, skip it and use Disk Cleanup instead.

Fix 7: Run DISM and SFC Before Retrying Setup

If setup scripts fail because system components are damaged, repair Windows before the next upgrade attempt.

DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

Restart after both commands complete. Then retry the feature update before reinstalling third-party security tools.

Fix 8: Perform a Clean Boot for the Upgrade

A clean boot reduces background services that can interfere with Windows Setup. This is useful when logs do not clearly name the blocker.

1. Press Win + R, type msconfig, and press Enter.
2. Open the Services tab.
3. Check Hide all Microsoft services.
4. Click Disable all for remaining non-Microsoft services.
5. Open Task Manager and disable nonessential startup apps.
6. Restart and retry the upgrade.

After the upgrade, return to msconfig and re-enable services gradually.

Fix 9: Use the Windows Installation Assistant or ISO Setup

If Windows Update keeps failing with 0xc19001e2, use Microsoft’s Installation Assistant or run setup from an ISO. This can bypass a broken Windows Update delivery path while still preserving files and apps.

1. Download the Windows Installation Assistant or Windows ISO from Microsoft.
2. Run the tool as Administrator.
3. Choose to keep personal files and apps.
4. Disconnect nonessential external devices before starting.
5. Let setup complete without interrupting the PC.

If ISO setup fails too, collect the Panther logs again. The failure will usually name a more specific blocker.

Fix 10: Check Free Space, External Devices, and Update Readiness

Even when the script failure is the main error, poor upgrade readiness can make setup unstable. Clean the basics before another attempt.

1. Keep at least 30 GB free on C: before starting the feature update.
2. Unplug external drives, USB hubs, docks, printers, and capture devices.
3. Update chipset, storage, network, and display drivers from the manufacturer.
4. Pause overclocking or aggressive tuning utilities during the upgrade.
5. Restart before running setup.

Fix 11: Managed PCs Need an IT Policy Check

On work or school devices, a preinstall script may be part of management software, encryption policy, endpoint security, or deployment tooling. In that case, local repair commands may not be enough.

Ask IT to check upgrade readiness policies, endpoint security logs, encryption status, device management scripts, and software deployment tools. A policy script that fails before setup can trigger 0xc19001e2 repeatedly.

Common Mistake

The common mistake is treating 0xc19001e2 like a normal Windows Update download error. It is usually a setup preinstall script failure. Resetting the cache can help, but the permanent fix is to read setup logs and remove the script, software, or policy component that blocks setup.

Best Next Step

If the error continues, use Microsoft’s feature update troubleshooting process and focus on the Panther setup logs. Microsoft documents 0xC19001E2 as MOSETUP_E_PREINSTALL_SCRIPT_FAILED, meaning a preinstall script failed to run or returned an error: Windows upgrade resolution procedures — Microsoft Learn.

Frequently Asked Questions

What does 0xc19001e2 Windows Update error mean?

It usually means a Windows Setup preinstall script failed before the feature update could continue. Microsoft identifies it as MOSETUP_E_PREINSTALL_SCRIPT_FAILED.

Is 0xc19001e2 the same as 0xc1900101?

No. 0xc1900101 usually points to driver rollback problems. 0xc19001e2 points to a failed preinstall script during Windows Setup.

Where do I find logs for 0xc19001e2?

Check C:\$WINDOWS.~BT\Sources\Panther\setuperr.log and setupact.log. Search for the error code, preinstall.cmd, and script failure entries.

Can antivirus cause 0xc19001e2?

Yes. Endpoint security, antivirus, VPN, encryption, and management tools can interfere with setup scripts or preinstall checks during a feature update.

Should I reinstall Windows to fix 0xc19001e2?

Not first. Remove the blocker from the logs, clean the setup cache, repair Windows, use clean boot, and try the Installation Assistant or ISO setup before considering a clean install.