Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Monday, April 9, 2018 9:47 AM
Before rolling out Windows 10 upgrade Task sequence, I am running a compatibility scan on the machines to check for any issues.
The command used is "setup.exe /Auto Upgrade /Quiet /NoReboot /Compat ScanOnly" from Windows 10 1709 source.
The setuperr.log gives the following error.
===============================
2018-04-09 11:54:40, Error CallPidGenX: PidGenX function failed on this product key. (hr = 0x8a010001) 2018-04-09 11:54:40, Error MOUPG CDlpActionProductKeyValidate::ReportDownlevelInstallChannel(2975): Result = 0x8A010001 2018-04-09 11:54:40, Error MOUPG ProductKey: Failed to report Host OS channel to telemetry. 2018-04-09 11:54:41, Error CallPidGenX: PidGenX function failed on this product key. (hr = 0x8a010001) 2018-04-09 11:54:41, Error CallPidGenX: PidGenX function failed on this product key. (hr = 0x8a010001) 2018-04-09 11:54:41, Error MOUPG CDlpActionProductKeyValidate::SelectImageIndex(1636): Result = 0xC1900215 2018-04-09 11:54:41, Error MOUPG CDlpActionProductKeyValidate::ExecuteRoutinePkeyValidate(435): Result = 0xC1900215 2018-04-09 11:54:41, Error MOUPG CDlpActionProductKeyValidate::ExecuteRoutine(376): Result = 0xC1900215 2018-04-09 11:54:41, Error MOUPG CDlpActionImpl<class CDlpErrorImpl<class CDlpObjectInternalImpl<class CUnknownImpl<class IProductKeyAction> > > >::Execute(441): Result = 0xC1900215 2018-04-09 11:54:41, Error MOUPG CDlpTask::ExecuteAction(3243): Result = 0xC1900215 2018-04-09 11:54:41, Error MOUPG CDlpTask::ExecuteActions(3397): Result = 0xC1900215 2018-04-09 11:54:41, Error MOUPG CDlpTask::Execute(1631): Result = 0xC1900215 2018-04-09 11:54:41, Error MOUPG CSetupManager::ExecuteTask(2169): Result = 0xC1900215 2018-04-09 11:54:41, Error MOUPG CSetupManager::ExecuteTask(2132): Result = 0xC1900215 2018-04-09 11:54:41, Error MOUPG CSetupManager::ExecuteInstallMode(714): Result = 0xC1900215 2018-04-09 11:54:41, Error MOUPG CSetupManager::ExecuteDownlevelMode(346): Result = 0xC1900215 2018-04-09 11:54:43, Error MOUPG CSetupManager::Execute(236): Result = 0xC1900215 2018-04-09 11:54:43, Error MOUPG CSetupHost::Execute(375): Result = 0xC1900215
The return code from the Setup.exe is -1047526891
I am using SCCM to deploy the above command on the machines and collecting the .log and .xml files to a shared location.
I am unable to make sense from the xml files nor was able to find much details on error 0xC1900215.
Has anyone else faces similar issue with Windows 10 compatibility scan.
Deepak Sidhpura
All replies (6)
Monday, April 9, 2018 11:09 AM
Return codes need to be interpreted in a specific way.
For upgrade errors you need to divide your error in 2, first part suggests what type of error it is, while the second part show the error number.
Result codes can be matched to the type of error encountered. To match a result code to an error:
- Identify the error code type as either Win32 or NTSTATUS using the first hexadecimal digit:
8 = Win32 error code (ex: 0x80070070)
C = NTSTATUS value (ex: 0xC1900107) - Write down the last 4 digits of the error code (ex: 0x80070070 = 0070). These digits are the actual error code type as defined in the HRESULT or the NTSTATUS structure. Other digits in the code identify things such as the device type that produced the error.
- Based on the type of error code determined in the first step (Win32 or NTSTATUS), match the 4 digits derived from the second step to either a Win32 error code or NTSTATUS value
In this case it's an NTSTATUS error:
0xC0000215
STATUS_TRANSACTION_INVALID_TYPE
The transport does not recognize the specified transaction request type.
I suggest running SFC /Scannow or Dism /online /cleanup-image /restorehealth in an elevated prompt and retry.
Regards,
Thomas
Please remember to mark the post(s), which answered your question.
Tuesday, April 10, 2018 3:50 AM
Hi,
Did the error returns on each machine?
Since the info is limited, you can upload the setuperr.log and setupact.log to a network drive and share the link here. Thanks for your cooperation.
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
Wednesday, April 11, 2018 5:21 AM
Thank you for the response. I have copied the setuperr.log and setupact.log from couple of machines to the link below.
https://1drv.ms/f/s!AvwFkzFqlEY0gfgWSqwMgunxqi1Qfg
@Momominta: The same setup runs fine against other machines. There are around 20% machines failing with the above error. Reset are able to complete the scan. With this information, I would imagine the key is correct, yes?
Deepak Sidhpura
Wednesday, April 11, 2018 11:09 AM
Hi,
Thank you for going through the logs, I have added the requested files to the same location. I am not sure why is asking for a password. I have not set any password requirements.
Deepak Sidhpura
Thursday, April 12, 2018 3:30 AM
Have read the link momominta provided?
https://www.dropbox.com/s/lfty4woo6x421iv/apps1.rar?dl=0
Try the workaround "adding the KMS key to the Product key field", seeing if it works.
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
Friday, July 5, 2019 1:47 PM
Sorry to blow the dust from this year old topic. But I've got a similar issue, and I can't quite wrap my mind around it.
Recently we've started using SCCM OSD to upgrade Win2012 or R2 servers to Win2016 or 2019. That works reasonable well, but at times there some incompatibilities and my TS will fail. Troubleshooting the logs aren't that easy for our front office guys, so I'd like to offer a user-friendly pre-check which runs:
setup.exe */Auto Upgrade /Quiet /NoReboot /DynamicUpdate Disable /Compat ScanOnly /Compat IgnoreWarning
*I'm using the unmodified Win2016 iso from the MS VLSC, released November 2018.
While testing I'm getting unexpected error codes. On a Win2012R2 server of which I know upgrades just fine to both Win2016/2019 with OSD I'm getting error 0xC1900215 "Could not find an install image for this system".
Looking at the setupact.log I think this part is relevant:
15:25:06, Info MOUPG ProductKey: Product key found in Host OS.
15:25:06, Info MOUPG ProductKey: Populating Image info set.
15:25:07, Info MOUPG Action progress: [0%]
15:25:14, Info SPValidateProductKey: Calling PidGenX
15:25:15, Error CallPidGenX: PidGenX function failed on this product key. (hr = 0x8a010001)
15:25:15, Warning SPValidateProductKey: Failed to call PidGenX to validate product key
15:25:15, Error MOUPG CDlpActionProductKeyValidate::ReportDownlevelInstallChannel(2899): Result = 0x8A010001
15:25:15, Error MOUPG ProductKey: Failed to report Host OS channel to telemetry.
15:25:15, Info MOUPG ProductKey: Calling GatherOSState to generate GenuineTicket.xml
15:25:26, Info MOUPG ProductKey: GatherOsState Process returned : [0x0]
15:25:26, Info MOUPG ProductKey: Is Machine Active : [TRUE]
15:25:26, Info MOUPG ProductKey: Genuine ticket generated : [TRUE]
15:25:26, Info MOUPG ProductKey: Offer Config = [FALSE].
15:25:26, Info MOUPG ProductKey: Offer = [FALSE].
15:25:26, Info MOUPG GetProductKeyFromResponse: Attempting to get a product key from the response layer.
15:25:26, Info MOUPG GetProductKeyFromResponse: Using automation response.
15:25:26, Info MOUPG GetProductKeyFromResponse: Automation response not found.
15:25:26, Info MOUPG ProductKey: Looking for product key in Pid.txt file.
15:25:26, Info MOUPG ProductKey: Pid.txt file not found.
15:25:26, Info MOUPG ProductKey: Looking for product key in Digital Marker.
15:25:26, Info MOUPG ProductKey: No digital marker key found. hr=[0xc004f057]
15:25:26, Info MOUPG ProductKey: Looking for EICfg file.
15:25:26, Info MOUPG ProductKey: EI.cfg file found.
15:25:26, Info MOUPG ProductKey: Validating EI.cfg file.
15:25:26, Info MOUPG ProductKey: Extracting data from EI.cfg file.
15:25:26, Info MOUPG ProductKey: EI.cfg file did not contain an edition Id.
15:25:26, Info MOUPG ProductKey: EI.cfg file contained an install channel.
15:25:26, Info MOUPG ProductKey: Matching Install Wim For Exact Editions
15:25:26, Info MOUPG ProductKey: Matching Install Wim.
15:25:26, Info MOUPG ProductKey: Matching Install Wim: No edition provided, matching all images.
15:25:26, Info MOUPG ProductKey: Matching Install Wim: Found [4] matching images.
15:25:26, Info MOUPG ProductKey: Valid product key found = [TRUE].
15:25:26, Info MOUPG ProductKey: SelectImageIndex: Found multiple matching images. Querying for image index.
15:25:26, Info MOUPG ProductKey: SelectImageIndex: Selecting image index from response.
15:25:26, Info MOUPG ProductKey: Getting index from response.
15:25:26, Info MOUPG ProductKey: Image selection response not found.
15:25:26, Info MOUPG ProductKey: SelectImageIndex: Image index not found in response. Selecting image index from SkuLib.
15:25:26, Info MOUPG ProductKey: Getting index from SkuLib.
15:25:26, Info MOUPG ProductKey: Host OS edition is [ServerStandard].
15:25:26, Info MOUPG ProductKey: No SkuLib Upgrade edition available.
15:25:26, Info MOUPG ProductKey: Matching upgrade edition not found in SkuLib.
15:25:26, Error MOUPG CDlpActionProductKeyValidate::SelectImageIndex(1568): Result = 0xC1900215
15:25:26, Error MOUPG CDlpActionProductKeyValidate::ExecuteRoutinePkeyValidate(417): Result = 0xC1900215
15:25:26, Error MOUPG CDlpActionProductKeyValidate::ExecuteRoutine(358): Result = 0xC1900215
I think it can't automatically match the server's Standard Edition SKU with one of the 4 indexes in the ISO, and aborts.
My OSD TS actually preselects index 2 for 'ServerStandard' image, and provides the Product Key as well. That's the main difference, I think.
I've tried adding the /PKey parameter in the command line, but it results in the same error.
Any idea how to overcome this, preferably without having to create a customized wim?
edit: hunch confirmed. After removing the 3 other indexes from the wim and rebuilding the ISO, I get exit code 0xC1900210 (which means everything's fine to upgrade)
So the question stays: how can I run an automated compatibility scan with a stock ISO? Afaik, there's no way to specify the index by command line.