During our recent Windows 10 feature update deployment from 1809 to 20H2, we ran in to an issue on some clients where they reported back error 0XC190012E to ConfigMgr.
The error code its self is just a generic code and I couldn’t find it in either
Windows update error code list
Windows Update error code list by component – Windows Deployment | Microsoft Docs
or the Windows 10 upgrade errors doc
Get help with Windows 10 upgrade and installation errors (microsoft.com)
We first checked the temporary location that feature update deploys to c:\$Windows.~BT, to check if there was any issue in the compatibility xml file or in the setup logs under sources\panther, but there was no folders other than sources.
Since there was no files I though this might be a space issue so ran some remote WMI commands to check the disk space available. I used the below PowerShell using Get-WMIObject.
Get-WmiObject Win32_logicaldisk -ComputerName RemoteComputerName | Select-Object @{Name="Drive";E={$_.DeviceID}},
@{Name="Size(GB)";E={[math]::Round($_.size/1gb)}},
@{Name="Free Space(GB)";E={[math]::Round($_.freespace/1gb)}},
@{Name="%Free Space";E={"{0:N2}" -f (($_.freespace/$_.size)*100)}}
In this case it wasn’t disk space a there was over 100GB free.
There wasn’t much online about the error other than the usually run scf /scannow, diskcheck and run the update troubleshooter but none of these worked.
Then found this post on the Microsoft forms that pointed to an issue with the setupconfig.ini
Generic 0xc190012e trying to upgrade Windows 10 1909 to 20H2 – Microsoft Community
C:\Users\Default\AppData\Local\Microsoft\Windows\WSUS
We aren’t using any custom setting in the setupconfig.ini so there was no issue for me to remove this.
Once I removed the file and kicked off the feature update again it now completes without issue.
I don’t know how the setupconfig.ini file was created on only a few devices but it was a quick fix once we found the issue was the config file.
Select Windows Desktops and Servers (custom)
Select Windows 10 as the version of Windows that will be assessed. 
Add a new settings item. 
Give the item a name
Put in the script above.
Next add in a compliance rule.
Once all the settings and compliance rules are configure following the wizard to complete 
Next we need to create the configuration baseline
Give the compliance baseline a name
Add the configuration item created earlier. 
Click ok to complete the baseline 
Once the baseline is configured, deploy the baseline to the required device collection 
You can either wait for the next time the client does a machine policy retrieval or run the action manually from the client. Once the client get the updated policy the baseline should show under configurations.
By default USMT will use the MigApp.xml and MigDocs.xml to set what will be copied.
We will be using the default xml but you can create custom xml’s to customize what files and setting need to be copied and restored.
Once the TS is setup we just need to deploy to a collection so that devices can be added and pick up the wipe and reload TS. 
Once deployed either wait for the TS to be picked up or run the client action machine policy and app deployment evaluation. 
We can check the smsts.log file to view what is happening we can see below that the files are being downloaded for the USMT package. 
Once the scanstate kicks off you can see the xml files that are used in the log. 
We can check the USMT folder on the state migration point to see if data is being copied. 
Once the image is applied, we can check the restore state task in the smsts log. The command will call the loadstate and cause use the default or custom xml files. 
When the TS has fully finished we can logon to Windows we should see that the devices is running Windows 10 and also has the file and settings migrated.
Give the applications a name and sign in to Azure using a account with the required permission 
I just left user discovery enabled. 
Click next to finish configuring the Azure services. 
Once finished the Azure service should now be showing 
The Azure AD tenant should also show with both application we just created. 
I left the alerting as default 
Just follow the wizard to complete. 
To allow the software update point to communicate with the CMG, tick the allow configuration manager cloud management gateway traffic. 
After this has been configured the clients should now pick up a the CMG as a internet based management point in the network tab of client agent properties. 
To confirm the query is working we can create a search filter for all software updates to make sure they match.
Last step was to create a weekly email report using SQL Server Reporting Services (SSRS).
I created a custom Reports folder to keep any report I created.
Follow the report wizard to finish the report creation. 
Once the report wizard completed the report builder should load. 
First create a new dataset. Right click on Datasets > Add Datasets
Once that click ok and the dataset should show under datasets. 
Select the dataset we create.
I just wanted to use all values so drag all row to the value box.
Next just go through the rest of the wizard. Once completed you should see something similar to the below. I added a text box at the top for a tile and added in some grey filling on the table. 
Now save the report and we can run from the MECM console to see what the report will look like. 
Last step is to create subscription to send a the weekly report 
Select report delivered by Email and put in the required detail and report to be included.(Email settings need to be configured in SSRS before you can select email as a deliver option)
Set the schedule that is required and complete the wizard. 
The report should now be sent out weekly as a csv file.
We currently install MBAM successfully on Windows 1809 so it didn’t look like a MBAM server issue or connection issue. I checked and there was a newer servicing release from May 2019
Now I can image the surface pro 6 1TB model successfully.
Select deployment tools. 
Once the install has finished, go to the start menu and down to Windows Kits and open Windows System Image Manager .
Below is the extracted ISO.
Go to Sources > install.wim.
Select the version.
Next create a new answer file.
Go to Windows Image
Edit “amd64_Microsoft-Windows-Shell-Setup__neutral” to add in Register Owner and any other details as required.
Next edit the required OOBE settings.
Once all the settings have been added save the answer file.
Last step is to create a package for the answer file and apply the answer file in the SCCM task sequence.
TheSleepyAdmins 