While upgrading a Windows 7 machine to Windows 10, the following error appeared:
Windows 10 Setup error
We couldn't install Windows 10
We've set your PC back to the way it was right before you started installing Windows 10.
0xC1900101 - 0x30018 The installation failed in the FIRST_BOOT phase with an error during SYSPREP_SPECIALIZE operation
To diagnose these cryptic, unhelpful errors, run the SetupDiag tool. It will place a log file in the same directory where you run the tool. In my case, there was this error:
Error: Found AdvancedInstaller failure.
Last Phase: Pre SysPrep
Last Operation: Upgrade security
Executable: SMConfigInstaller.exe
Exit Code: 3222072836
Phase: 38
Mode: Install (first install)
Component: WCF-GenericCommands, Culture=neutral, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64SMConfigInstaller.exe is a part of the .NET Framework. After searching for Error: Found AdvancedInstaller failure., I came across this thread: https://answers.microsoft.com/en-us/windows/forum/all/upgrading-from-win-10-1909-to-2004/5aae9ea6-8d09-456c-b9bd-d336d8d16477?page=3
One post suggested removing the .NET Framework 3.5 feature (in Windows 7, click Start and type “Turn Windows features on or off”). In my case, that failed; through the GUI, the error was An error has occurred. Not all of the features were successfully changed, and running the command DISM.exe /online /disable-feature /FeatureName:NetFx3 resulted in an error 1603. It suggested to look in the DISM log (C:\windows\logs\dism\dism.log), which showed numerous errors, but didn’t point me in the right direction.
Next step was to restore the .NET config files to their defaults. On a 64-bit version of Windows, I did this twice, once for the Framework folder and a second time in Framework64 (the blog post linked below only lists the process for Framework).
https://dllpurgatory.blogspot.com/2011/04/unable-to-turn-on-net-framework-351.html
cd %SystemRoot%\Microsoft.NET\Framework\v2.0.50727\CONFIG
copy machine.config.default machine.config
copy web.config.default web.config
copy web_hightrust.config.default web_hightrust.config
copy web_lowtrust.config.default web_lowtrust.config
copy web_mediumtrust.config.default web_mediumtrust.config
copy web_minimaltrust.config.default web_minimaltrust.config
cd %SystemRoot%\Microsoft.NET\Framework64\v2.0.50727\CONFIG
copy machine.config.default machine.config
copy web.config.default web.config
copy web_hightrust.config.default web_hightrust.config
copy web_lowtrust.config.default web_lowtrust.config
copy web_mediumtrust.config.default web_mediumtrust.config
copy web_minimaltrust.config.default web_minimaltrust.configI still got the same error when removing the feature, but after rebooting and going back into the “Turn Windows features on and off” utility, the .NET Framework 3.5 box was unchecked. Now, after running the OS upgrade again, it worked.
Below are the things I tried which did NOT help.
I had previously run sfc /scannow. I then ran dism /online /cleanup-image /scanhealth which asked me to check the log at C:\windows\logs\cbs\checksur.log. It repaired some issues:
=================================
Checking System Update Readiness.
Binary Version 6.1.7601.23471
2022-06-28 14:14
Checking Windows Servicing Packages
Checking Package Manifests and Catalogs
Checking Package Watchlist
Checking Component Watchlist
Checking Packages
Checking Component Store
(f) CSI Missing Winning Component Key 0x00000000 x86_policy.14.0.avg.vc140.crt_f92d94485545da78_14.0.28127.0_none_dd53aa65eb668795
(fix) CSI Missing Winning Component Key CSI Registry Item Repaired Deleted winners map value 14.0.28127.0
(f) CSI Missing Winning Component Key 0x00000000 amd64_policy.14.0.avg.vc140.crt_f92d94485545da78_14.0.28127.0_none_95a6738ed6ea5e8f
(fix) CSI Missing Winning Component Key CSI Registry Item Repaired Deleted winners map value 14.0.28127.0
(f) CSI Missing Winning Component Key 0x00000000 amd64_policy.14.0.avg.vc140.mfc_f92d94485545da78_14.0.28127.0_none_8e278dc4dbb8db72
(fix) CSI Missing Winning Component Key CSI Registry Item Repaired Deleted winners map value 14.0.28127.0
(f) CSI Missing Winning Component Key 0x00000000 x86_avg.vc140.crt_f92d94485545da78_14.0.28127.0_none_b9658084e274aae7
(fix) CSI Missing Winning Component Key CSI Registry Item Repaired Deleted winners map value 14.0.28127.0
(f) CSI Missing Winning Component Key 0x00000000 amd64_avg.vc140.crt_f92d94485545da78_14.0.28127.0_none_71b849adcdf881e1
(fix) CSI Missing Winning Component Key CSI Registry Item Repaired Deleted winners map value 14.0.28127.0
(f) CSI Missing Winning Component Key 0x00000000 x86_avg.vc140.mfc_f92d94485545da78_14.0.28127.0_none_b1e69abae74327ca
(fix) CSI Missing Winning Component Key CSI Registry Item Repaired Deleted winners map value 14.0.28127.0
(f) CSI Missing Winning Component Key 0x00000000 amd64_avg.vc140.mfc_f92d94485545da78_14.0.28127.0_none_6a3963e3d2c6fec4
(fix) CSI Missing Winning Component Key CSI Registry Item Repaired Deleted winners map value 14.0.28127.0
(f) CSI Missing Winning Component Key 0x00000000 x86_policy.14.0.avg.vc140.mfc_f92d94485545da78_14.0.28127.0_none_d5d4c49bf0350478
(fix) CSI Missing Winning Component Key CSI Registry Item Repaired Deleted winners map value 14.0.28127.0
Summary:
Seconds executed: 425
Found 8 errors
Fixed 8 errors
CSI Missing Winning Component Key Total count: 8
Fixed: CSI Missing Winning Component Key. Total count: 8Unfortunately, this did not resolve the problem; I still couldn’t remove .NET and the Windows upgrade still failed.
Chris Tech Blog 