windows update error C1900101-30018 - Windows 10 upgrade

Initial problem with upgrade to Windows 10 was windows update error 0x8024402C - Windows 10 upgrade

Windows 10 upgrade keeps failing. After searching I uninstalled Norton Internet Security and all Norton products. Got BITS working again. Still fails with above error. Run Microsoft troubleshooting tools and all problems fixed apart from this one. Searching led me to https://support.microsoft.com/en-us/kb/2509997 which warns don't try this at home!!!

Any ideas?

UPDATE

System info:

Latest, after more than 10 attempts (I have lost count!) is that I get C1900101-30018 (see http://answers.microsoft.com/en-us/windows/forum/windows_10-windows_install/windows-10-install-error-c1900101-30018/4715b825-ef7c-42ec-87a3-5e8fb56bd812?auth=1).

When I run the windows update troubleshooter, I get the error 0x80070005. I ran the fix (see http://answers.microsoft.com/en-us/windows/forum/all/windows-update-error-0x80070005-need-a-fix-click/e4cb8700-f215-4f1a-8bd4-6457ac619c19?auth=1) -the file  Accesschk.txt was empty, but checking the registry, the trustedinstaller had full permissions.

After lots of reboots, I tried again (with the error  0x80070005 still present, but it still fails at the same stage (30% complete)

After timing the update process and checking the resulting error log setuperr.log, the point of failure (after copying all files at 30% of update, reboot at the installing features and drivers stage) at 19:58:46, the end of the log file (which has loads of errors PRIOR to me starting the upgrade process), is as follows:-

2015-08-20 19:35:39, Error                 MOUPG  MoSetupPlatform: SetupPlatform::SetSqmEndTime returned: [0x80004005]
2015-08-20 19:35:47, Error                 MOUPG  CSetupHost::ReportEventW(1650): Result = 0x8007045B[gle=0x000003f0]
2015-08-20 19:35:47, Error                 MOUPG  SetupHost: Reporting pending reboot event failed: hr = [0x8007045B]
2015-08-20 19:35:47, Error                 MOUPG  CDlpManager::AsyncSerializeDisable(471): Result = 0x80070216
2015-08-20 19:36:31, Error                        CDiagnosticsHelper::SetDeferredSQMStartTime: Attempting to set a deferred SQM datapoint start time in an invalid SQM session[gle=0x000000b7]
2015-08-20 19:47:12, Error                        CDiagnosticsHelper::SetDeferredSQMEndTime: Attempting to set a deferred SQM datapoint end time in an invalid SQM session
2015-08-20 19:55:08, Error                        [SetupPlatform.exe] ReAgentXMLParser::ParseConfigFile (xml file: D:\Recovery\ReAgentOld.xml) returning 0X3.

HELP!

Update 21/8/15

Windows update troubleshooter reports error 0x80070057

Searching this error led me to run DISM.exe /Online /Cleanup-image /Scanhealth

Log file as follows:-

=================================
Checking System Update Readiness.
Binary Version 6.1.7601.18741
2015-08-21 22:09

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs
(f) CBS MUM Corrupt 0x00000000 servicing\Packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.mum  Expected file name Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~neutral~~10.2.9200.16437.mum does not match the actual file name
(f) CBS MUM Corrupt 0x00000000 servicing\Packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.mum  Expected file name Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~neutral~~10.2.9200.16437.mum does not match the actual file name
(f) CBS MUM Corrupt 0x00000000 servicing\Packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~11.2.9412.0.mum  Expected file name Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~neutral~~11.2.9412.0.mum does not match the actual file name

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store

Summary:
Seconds executed: 1463
 Found 3 errors
  CBS MUM Corrupt Total count: 3

Unavailable repair files:
 servicing\packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.mum
 servicing\packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.mum
 servicing\packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~11.2.9412.0.mum
 servicing\packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.cat
 servicing\packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.cat
 servicing\packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~11.2.9412.0.cat


=================================
Checking System Update Readiness.
Binary Version 6.1.7601.18741
2015-08-11 17:50

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs
(f) CBS MUM Corrupt 0x00000000 servicing\Packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.mum  Expected file name Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~neutral~~10.2.9200.16437.mum does not match the actual file name
(f) CBS MUM Corrupt 0x00000000 servicing\Packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.mum  Expected file name Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~neutral~~10.2.9200.16437.mum does not match the actual file name
(f) CBS MUM Corrupt 0x00000000 servicing\Packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~11.2.9412.0.mum  Expected file name Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~neutral~~11.2.9412.0.mum does not match the actual file name

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store

Summary:
Seconds executed: 1404
 Found 3 errors
  CBS MUM Corrupt Total count: 3

Unavailable repair files:
 servicing\packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.mum
 servicing\packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.mum
 servicing\packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~11.2.9412.0.mum
 servicing\packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.cat
 servicing\packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.cat
 servicing\packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~11.2.9412.0.cat

=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2015-08-12 18:26

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store

Summary:
Seconds executed: 2309
 No errors detected


=================================
Checking System Update Readiness.
Binary Version 6.1.7601.18741
2015-08-21 22:09

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs
(f) CBS MUM Corrupt 0x00000000 servicing\Packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.mum  Expected file name Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~neutral~~10.2.9200.16437.mum does not match the actual file name
(f) CBS MUM Corrupt 0x00000000 servicing\Packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.mum  Expected file name Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~neutral~~10.2.9200.16437.mum does not match the actual file name
(f) CBS MUM Corrupt 0x00000000 servicing\Packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~11.2.9412.0.mum  Expected file name Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~neutral~~11.2.9412.0.mum does not match the actual file name

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store

Summary:
Seconds executed: 1463
 Found 3 errors
  CBS MUM Corrupt Total count: 3

Unavailable repair files:
 servicing\packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.mum
 servicing\packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.mum
 servicing\packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~11.2.9412.0.mum
 servicing\packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.cat
 servicing\packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.cat
 servicing\packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~11.2.9412.0.cat

Running DISM.exe /Online /Cleanup-image /Restorehealth  reports the following:-

Update 25/8/15

Tried fixes suggested at http://answers.microsoft.com/en-us/windows/forum/all/command-prompt-sfc-scannow-corrupt-files-found/809cd697-54d6-4240-9811-b6760cd821ba?auth=1 - sfc issue still not resolved.

Tried running the update tool (https://www.microsoft.com/en-us/software-download/windows10) in safe mode with graphics driver (and other non-essential ones) disabled. Still failed at same stage (30% - starting drivers and features part), but got the message "0xC1900101-0x30018 The installation failed in the FIRST_BOOT phase with an error during SYSPREP operation.

In summary:-

1. Windows 10 upgrade fails with error C1900101-30018 at 30% stage

2. Windows update troubleshooter reports 0x80070005 not fixed

3. Sfc reports problems with tcpmon.ini that it can't repair

All drivers reported up-to-date and all other updates applied. Run full Dell diagnostics - no issues. System working well in all other respects - only win 10 upgrade failing.

Slowly going mad - escalated to level 2 with Microsoft, awaiting response...

Update 27/8/15

SUCCESS!!!

I uninstalled AVG Tune up (see

http://answers.microsoft.com/en-us/windows/forum/windows_10-windows_install/windows-10-install-error-c1900101-30018/4715b825-ef7c-42ec-87a3-5e8fb56bd812?auth=1). I was about to try again and just them Microsoft Lv2 contacted me. Did an ISO install from DVD and it has worked! Don't know if it would have worked with AVG uninstalled, but all seems working at last!

 

Question Info


Last updated July 2, 2019 Views 1,126 Applies to:

Finally, I have succeeded in installing Windows 10 Home from Windows 7 on a 2009 machine.

Processor            Intel(R) Core(TM)2 Quad CPU    Q8300  @ 2.50GHz, 2500 Mhz, 4 Core(s), 4 Logical Processor(s)

Installed Physical Memory (RAM)             8.00 GB

Total Physical Memory  8.00 GB

Available Physical Memory          5.14 GB

Total Virtual Memory     16.0 GB

Before I started I backed up my main drive using Acronis. This creates an image. Then  I stripped out or disconnected all extra internal drives. optical drives, all extension cards for video, USB,  sound and their drivers; uninstalled F-secure, Spyhunter, Disk Keeper, tuneuputilities and Acronis 2015. Just before installation I applied a clean boot.

I rebooted using a USB stick as the installation media source, opting to keep my files and apps.

As usual the process wouldn't accept my product number and asked me to continue installing from within Windows, but this time I got messages that Windows was finding updates to make my installation smoother. At the critical 30% point the system rebooted as usual, but instead of failing it continued to install drivers and features. After so much frustration I didn't relax until the system rebooted into Windows 10 and I had reinstated all hardware and drivers successfully.

Windows 10 appears to have made my system crisper than it was.  At this point I backed up my new system again with Acronis. I removed all the installation files and Windows .old, ran CCleaner and Tuneup. It runs nicely with no hiccups.

Windows .old takes up a lot of disk space, 26Gb in my case, but should only be removed when you are sure you have a stable system. It is best removed by using Windows Disk Cleaner in accessories. You have to opt to clean system files.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.