Jump to content











Photo
- - - - -

Avoid that the input window of the product keys is displayed during the first installation phase of Windows 10 v1511


  • Please log in to reply
7 replies to this topic

#1 Balubeto Balubeto

Balubeto Balubeto

    Frequent Member

  • Advanced user
  • 130 posts
  •  
    Italy

Posted 09 March 2016 - 05:37 PM

Hi

 

Using Windows ADK 10 v1511, I injected the two product keys in the respective volume images of the Multiple Editions (MSDN) iso of Windows 10 v1511.

When, however, I boot this iso, the input window of the product keys is still displayed during the first installation phase of Windows 10. Why?

How do I avoid that this window appears in order to immediately display the window that allows to choose the edition to install?

 

Thanks

 

Bye



#2 IAmTheTrueMeaningOfCovfefe

IAmTheTrueMeaningOfCovfefe

    Silver Member

  • Advanced user
  • 555 posts
  • Location:In hiding
  • Interests:An investigation is underway to determine whether Trump has any ties to America.
  •  
    United States

Posted 10 March 2016 - 12:10 AM

Not sure if this will work with 10, but it did work for me when I still used 8.1 as my main Windows OS. Check the part about creating a pid.txt:

 

https://technet.micr...y/hh824952.aspx



#3 Balubeto Balubeto

Balubeto Balubeto

    Frequent Member

  • Advanced user
  • 130 posts
  •  
    Italy

Posted 10 March 2016 - 06:02 PM

Not sure if this will work with 10, but it did work for me when I still used 8.1 as my main Windows OS. Check the part about creating a pid.txt:

 

https://technet.micr...y/hh824952.aspx

 

It does not work with these two isos.

So, what is the new method for Windows 10.x to prevent that the input window of the product keys is displayed during the first phase of installation of Windows 10.x?

 

Thanks

 

Bye



#4 Alexander Ceed

Alexander Ceed

    Frequent Member

  • Advanced user
  • 207 posts

Posted 10 March 2016 - 06:23 PM

How did you inject the keys (by unattend.xml)?

Usually if added them, and the product key windows still pops up, it is a sign that your key was not correct or recognized. Meaning you have a key for one edition, and you are installing an entirely different edition. Might wanna check this out.

 

Try to install it using a trial-key and see if that works.



#5 Balubeto Balubeto

Balubeto Balubeto

    Frequent Member

  • Advanced user
  • 130 posts
  •  
    Italy

Posted 10 March 2016 - 06:58 PM

How did you inject the keys (by unattend.xml)?

Usually if added them, and the product key windows still pops up, it is a sign that your key was not correct or recognized. Meaning you have a key for one edition, and you are installing an entirely different edition. Might wanna check this out.

 

Try to install it using a trial-key and see if that works.

 

I injected the product keys directly into their respective volume images included in the install.wim file with the Dism /Image:"<Mount_Directory_Path>" /Set-ProductKey:<Product key> command.

 

Thanks

 

Bye



#6 Balubeto Balubeto

Balubeto Balubeto

    Frequent Member

  • Advanced user
  • 130 posts
  •  
    Italy

Posted 11 March 2016 - 11:05 AM

It is possible to include in pid.txt file or in some other file the various product keys corresponding to the respective volume images that exist in the install.wim file?

Thanks

Bye



#7 Balubeto Balubeto

Balubeto Balubeto

    Frequent Member

  • Advanced user
  • 130 posts
  •  
    Italy

Posted 11 March 2016 - 04:27 PM

It is possible to create an autounattend.xml file and insert in it the product keys related to all editions included in the install.wim file?

 

Thanks

 

Bye



#8 Balubeto Balubeto

Balubeto Balubeto

    Frequent Member

  • Advanced user
  • 130 posts
  •  
    Italy

Posted 11 March 2016 - 06:16 PM

If I create an autounattend.xml file in the root directory of the media and insert this block

<UserData>
   <ProductKey>
      <WillShowUI>Never</WillShowUI>
   </ProductKey>
</UserData>

I avoid displaying the input window of the product keys during the first phase of installation and therefore, the window, which lists the editions included in the install.wim file, is displayed immediately. Right?

Thanks

Bye




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users