Windows 10 1709 Compatability Check Failure

I have been working on an upgrade for machines in my company from Windows 7 Enterprise to Windows 10 1709 Enterprise.  All machines remotely activate their Windows license via KMS.  I have previously upgraded about half of our machines to Windows 10 1607, and I will be upgrading these machines to Windows 10 1709 as well.  I am using SCCM CB 1706 and an In-place Upgrade sequence to remotely execute a compatibility check in order to make sure this upgrade is going to work as intended before I push the full upgrade.  Here's the relevant step from the OSD:

I have about 1000 machines so far that have returned success (0xC1900210), but I have about 200 machines so far that are failing with error code 0xC1900204 .  The failures all seem to come from machines that are either Latitude E5570 or Optiplex 7040 so far.  I have upgraded all drivers including the BIOS to the latest versions, but the results from the compat scan don't change.  After digging thru logs, I found a section that does not match with machines that have passed the compat scan.  The section is as follows from C:\~Windows.~BT\Sources\Panther\setupact.log:

2018-03-27 09:21:50, Info                  MOUPG  GetProductKeyFromResponse: Attempting to get a product key from the response layer.
2018-03-27 09:21:50, Info                  MOUPG  GetProductKeyFromResponse: Using automation response.
2018-03-27 09:21:50, Info                  MOUPG  GetProductKeyFromResponse: Automation response not found.
2018-03-27 09:21:50, Info                  MOUPG  ProductKey: Looking for product key in Pid.txt file.
2018-03-27 09:21:50, Info                  MOUPG  ProductKey: Pid.txt file not found.
2018-03-27 09:21:50, Info                  MOUPG  ProductKey: Looking for product key in Host OS.

2018-03-27 09:21:50, Info                  MOUPG  ProductKey: Failed to extract key from Host OS. hr=[0x80070002]
2018-03-27 09:21:50, Info                  MOUPG  ProductKey: Looking for product key in Digital Marker.
2018-03-27 09:21:50, Info                  MOUPG  ProductKey: Product key found in Digital Marker.
2018-03-27 09:21:50, Info                  MOUPG  ProductKey: Validating Product Key for Image.
2018-03-27 09:21:50, Info                  MOUPG  ProductKey: Populating Image info set.
2018-03-27 09:22:18, Info                         SPValidateProductKey: Calling PidGenX
2018-03-27 09:22:18, Info                  MOUPG  ProductKey: Product key using pkey edition = [Professional].
2018-03-27 09:22:18, Info                  MOUPG  ProductKey: Matching Install Wim For Exact Editions
2018-03-27 09:22:18, Info                  MOUPG  ProductKey: Matching Install Wim.
2018-03-27 09:22:18, Info                  MOUPG  ProductKey: Matching Install Wim: Found [1] matching images.
2018-03-27 09:22:18, Info                  MOUPG  ProductKey: Extracting Eula
2018-03-27 09:22:18, Info                  MOUPG  ProductKey: Product key was successfully validated.
2018-03-27 09:22:18, Info                  MOUPG  ProductKey: Product EditionID = Professional
2018-03-27 09:22:18, Info                  MOUPG  ProductKey: Product InstallChannel = OEM
2018-03-27 09:22:18, Info                  MOUPG  ProductKey: Eula = C:\$WINDOWS.~BT\Sources\Panther\_s_57D8.tmp
2018-03-27 09:22:18, Info                  MOUPG  ProductKey: Valid product key found = [TRUE].
2018-03-27 09:22:18, Info                  MOUPG  ProductKey: SelectImageIndex: Only one image found. Selecting default.

This section of the logs seems to suggest that the compatibility check looks at the digital Marker present in the BIOS, decides that Professional is right version (because that is what is burned into the BIOS), and then completely ignores my request to upgrade this machine from Enterprise to Enterprise and proceeds to process the compat scan with professional (which causes a fail because you can't upgrade win7 enterprise to win10 pro).

I do have one machine that is the exact same model running Windows 7 that ran the compat scan with success and here is the same section of logs:

2018-03-25 02:44:22, Info                  MOUPG  GetProductKeyFromResponse: Attempting to get a product key from the response layer.
2018-03-25 02:44:22, Info                  MOUPG  GetProductKeyFromResponse: Using automation response.
2018-03-25 02:44:22, Info                  MOUPG  GetProductKeyFromResponse: Automation response not found.
2018-03-25 02:44:22, Info                  MOUPG  ProductKey: Looking for product key in Pid.txt file.
2018-03-25 02:44:22, Info                  MOUPG  ProductKey: Pid.txt file not found.
2018-03-25 02:44:22, Info                  MOUPG  ProductKey: Looking for product key in Host OS.
2018-03-25 02:44:22, Info                  MOUPG  ProductKey: Product key found in Host OS.
2018-03-25 02:44:22, Info                  MOUPG  ProductKey: Validating Product Key for Image.
2018-03-25 02:44:22, Info                         SPValidateProductKey: Calling PidGenX
2018-03-25 02:44:24, Error                        CallPidGenX: PidGenX function failed on this product key. (hr = 0x8a010101)
2018-03-25 02:44:24, Warning                      SPValidateProductKey: Failed to call PidGenX to validate product key
2018-03-25 02:44:24, Info                  MOUPG  ProductKey: Product key is invalid.
2018-03-25 02:44:24, Info                  MOUPG  ProductKey: Looking for product key in Digital Marker.
2018-03-25 02:44:24, Info                  MOUPG  ProductKey: No digital marker key found. hr=[0xc004f057]
2018-03-25 02:44:24, Info                  MOUPG  ProductKey: Looking for EICfg file.
2018-03-25 02:44:24, Info                  MOUPG  ProductKey: EI.cfg file found.
2018-03-25 02:44:24, Info                  MOUPG  ProductKey: Validating EI.cfg file.
2018-03-25 02:44:24, Info                  MOUPG  ProductKey: Extracting data from EI.cfg file.
2018-03-25 02:44:24, Info                  MOUPG  ProductKey: EI.cfg file did not contain an edition Id.
2018-03-25 02:44:24, Info                  MOUPG  ProductKey: EI.cfg file contained an install channel.
2018-03-25 02:44:24, Info                  MOUPG  ProductKey: Matching Install Wim For Exact Editions
2018-03-25 02:44:24, Info                  MOUPG  ProductKey: Matching Install Wim.
2018-03-25 02:44:24, Info                  MOUPG  ProductKey: Matching Install Wim: No edition provided, matching all images.
2018-03-25 02:44:24, Info                  MOUPG  ProductKey: Matching Install Wim: Found [6] matching images.
2018-03-25 02:44:24, Info                  MOUPG  ProductKey: Valid product key found = [TRUE].
2018-03-25 02:44:24, Info                  MOUPG  ProductKey: SelectImageIndex: Found multiple matching images. Querying for image index.
2018-03-25 02:44:24, Info                  MOUPG  ProductKey: SelectImageIndex: Selecting image index from response.
2018-03-25 02:44:24, Info                  MOUPG  ProductKey: Getting index from response.
2018-03-25 02:44:24, Info                  MOUPG  ProductKey: Image selection response created.
2018-03-25 02:44:24, Info                  MOUPG  Automation: Entering Response Execute Method
2018-03-25 02:44:24, Info                  MOUPG  Automation: Leaving Response Execute Method
2018-03-25 02:44:24, Info                  MOUPG  ProductKey: SelectImageIndex: Selected image index [3].

This machine seems to be missing the digital marker that is causing the process to fail on the other machines.  It seems to be unable to match any edition, decides that it can use any of the images contained in the 1709 ISO, and then proceeds to use my choice (image index 3) to process the compat scan.

For comparison, here is the same section from a compat scan run on the exact same model of laptop that is running Windows 10 1607:

2018-03-26 11:21:31, Info                  MOUPG  GetProductKeyFromResponse: Attempting to get a product key from the response layer.
2018-03-26 11:21:31, Info                  MOUPG  GetProductKeyFromResponse: Using automation response.
2018-03-26 11:21:31, Info                  MOUPG  GetProductKeyFromResponse: Automation response not found.
2018-03-26 11:21:31, Info                  MOUPG  ProductKey: Looking for product key in Pid.txt file.
2018-03-26 11:21:31, Info                  MOUPG  ProductKey: Pid.txt file not found.
2018-03-26 11:21:31, Info                  MOUPG  ProductKey: Looking for product key in Host OS.
2018-03-26 11:21:31, Info                  MOUPG  ProductKey: Product key found in Host OS.
2018-03-26 11:21:31, Info                  MOUPG  ProductKey: Validating Product Key for Image.
2018-03-26 11:21:32, Info                         SPValidateProductKey: Calling PidGenX
2018-03-26 11:21:32, Info                  MOUPG  ProductKey: Product key using host OS edition = [Enterprise].
2018-03-26 11:21:32, Info                  MOUPG  ProductKey: Matching Install Wim For Exact Editions
2018-03-26 11:21:32, Info                  MOUPG  ProductKey: Matching Install Wim.
2018-03-26 11:21:32, Info                  MOUPG  ProductKey: Matching Install Wim: Found [1] matching images.
2018-03-26 11:21:32, Info                  MOUPG  ProductKey: Extracting Eula
2018-03-26 11:21:32, Info                  MOUPG  ProductKey: Product key was successfully validated.
2018-03-26 11:21:32, Info                  MOUPG  ProductKey: Product EditionID = Enterprise
2018-03-26 11:21:32, Info                  MOUPG  ProductKey: Product InstallChannel = Volume
2018-03-26 11:21:32, Info                  MOUPG  ProductKey: Eula = C:\$WINDOWS.~BT\Sources\Panther\_s_3627.tmp
2018-03-26 11:21:32, Info                  MOUPG  ProductKey: Valid product key found = [TRUE].
2018-03-26 11:21:32, Info                  MOUPG  ProductKey: SelectImageIndex: Only one image found. Selecting default.

This machine seems to be able to actually detect the Host OS and correctly notice that it is Enterprise.  It then chooses to use the only option that is deems to be correct (enterprise) to process the compat scan.

I have tried to run the full in-Place Upgrade on a couple machines that have failed with the 0xC1900204 compat scan error, and the full Upgrade also fails with the same error (because it runs the same compat scan before the upgrade takes place).  I tried running the compat scan with Windows 10 1703 ISO instead, and the compat scan runs to success.  I am currently assuming this worked because 1703 and previous ISO only contained one edition (I downloaded enterprise) so it can't get confused by being able to compare multiple editions that are contained in the 1709 ISO.  Here's the log for this one:

2018-03-27 11:06:32, Info                  MOUPG  GetProductKeyFromResponse: Attempting to get a product key from the response layer.
2018-03-27 11:06:32, Info                  MOUPG  GetProductKeyFromResponse: Using automation response.
2018-03-27 11:06:32, Info                  MOUPG  GetProductKeyFromResponse: Automation response not found.
2018-03-27 11:06:32, Info                  MOUPG  ProductKey: Looking for product key in Pid.txt file.
2018-03-27 11:06:32, Info                  MOUPG  ProductKey: Pid.txt file not found.
2018-03-27 11:06:32, Info                  MOUPG  ProductKey: Looking for product key in Host OS.
2018-03-27 11:06:32, Info                  MOUPG  ProductKey: Failed to extract key from Host OS. hr=[0x80070002]
2018-03-27 11:06:32, Info                  MOUPG  ProductKey: Looking for product key in Digital Marker.
2018-03-27 11:06:32, Info                  MOUPG  ProductKey: Product key found in Digital Marker.
2018-03-27 11:06:32, Info                  MOUPG  ProductKey: Validating Product Key for Image.
2018-03-27 11:06:32, Info                  MOUPG  ProductKey: Populating Image info set.
2018-03-27 11:06:40, Info                         SPValidateProductKey: Calling PidGenX
2018-03-27 11:06:40, Info                  MOUPG  ProductKey: Product key using pkey edition = [Professional].
2018-03-27 11:06:40, Info                  MOUPG  ProductKey: Matching Install Wim For Exact Editions
2018-03-27 11:06:40, Info                  MOUPG  ProductKey: Matching Install Wim.
2018-03-27 11:06:40, Info                  MOUPG  ProductKey: Matching Install Wim: Found [0] matching images.
2018-03-27 11:06:40, Info                  MOUPG  ProductKey: Matching Install Wim For Compatible Editions
2018-03-27 11:06:40, Info                  MOUPG  ProductKey: Matching Install Wim.
2018-03-27 11:06:40, Info                  MOUPG  ProductKey: Matching Install Wim: Found [0] matching images.
2018-03-27 11:06:40, Info                  MOUPG  ProductKey: Product key edition does not match an install wim.
2018-03-27 11:06:40, Info                  MOUPG  ProductKey: Looking for EICfg file.
2018-03-27 11:06:40, Info                  MOUPG  ProductKey: EI.cfg file found.
2018-03-27 11:06:40, Info                  MOUPG  ProductKey: Validating EI.cfg file.
2018-03-27 11:06:40, Info                  MOUPG  ProductKey: Extracting data from EI.cfg file.
2018-03-27 11:06:40, Info                  MOUPG  ProductKey: EI.cfg file contained an edition Id.
2018-03-27 11:06:40, Info                  MOUPG  ProductKey: EI.cfg file contained an install channel.
2018-03-27 11:06:40, Info                  MOUPG  ProductKey: Matching Install Wim For Exact Editions
2018-03-27 11:06:40, Info                  MOUPG  ProductKey: Matching Install Wim.
2018-03-27 11:06:40, Info                  MOUPG  ProductKey: Matching Install Wim: Found [1] matching images.
2018-03-27 11:06:40, Info                  MOUPG  ProductKey: Extracting Eula
2018-03-27 11:06:40, Info                  MOUPG  ProductKey: Valid product key found = [TRUE].
2018-03-27 11:06:40, Info                  MOUPG  ProductKey: SelectImageIndex: Only one image found. Selecting default.

Ultimately for the machines that are broken, how can I either block or remove the digital marker in the bios so that the compatibility check runs to success?  Barring that, is there something else that I can correct to make the compatibility check work? 

I have figured out the solution to this issue.  I am posting this just in case anyone else runs into this same issue.  What I did was use dism to delete all of the other image indexes from the .iso Except for the Enterprise version that I needed.  Re-ran the compact scan on machines that have failed with a 204 before and with the single image .iso they pass with flying colors.

12 people were helped by this reply

·

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.

For future reference, Enterprise products aren't supported here.  Better to use the Microsoft Technet Forums.

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.

 
 

Question Info


Last updated March 4, 2020 Views 1,779 Applies to: