Autounattended.xml automation stops at Region and Kybd questions-V1909

Sure, I don't mind updating my post to conform to forum suggestions. However, I don't see an Edit option near the top of my post or near the bottom. Where is the Edit option?

-Spike

- - - Updated - - -

Is there a way to enable my ability to edit my posts? I looked around a bit, and it looks like some forums either don't allow editing or some sites don't allow new members to edit posts for X amount of time.

Thx.

-Spike

Spike, do you not see an option to edit in the lower as in image below?

Unfortunately not. Some forums seem to be malconfigured and do not allow all members the ability to edit. Hopefully, someone with the ability to enable my editing ability will do so soon so that I can continue with my troubleshooting requests. Thank you in advance.

-Spike

How about just re-posting the answer file in a new post with the CODE tags. Just highlight all the text from the answer file and select the code tag icon. Or place the code tag on the page first and then paste the answer file between the start and end code tags.

Here is my answer file that still requires a manual click for the first user logon step during auto-installation.

Thanks for the help.

Code:

<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
<settings pass="windowsPE">
<component name="Microsoft-Windows-International-Core-WinPE" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<SetupUILanguage>
<UILanguage>en-US</UILanguage>
</SetupUILanguage>
<InputLocale>en-US</InputLocale>
<SystemLocale>en-US</SystemLocale>
<UILanguage>en-US</UILanguage>
<UILanguageFallback>en-US</UILanguageFallback>
<UserLocale>en-US</UserLocale>
</component>
<component name="Microsoft-Windows-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<DiskConfiguration>
<Disk wcm:action="add">
<CreatePartitions>
<CreatePartition wcm:action="add">
<Order>1</Order>
<Size>450</Size>
<Type>Primary</Type>
</CreatePartition>
<CreatePartition wcm:action="add">
<Order>3</Order>
<Size>16</Size>
<Type>MSR</Type>
</CreatePartition>
<CreatePartition wcm:action="add">
<Order>2</Order>
<Size>100</Size>
<Type>EFI</Type>
</CreatePartition>
<CreatePartition wcm:action="add">
<Order>4</Order>
<Type>Primary</Type>
<Extend>true</Extend>
</CreatePartition>
</CreatePartitions>
<ModifyPartitions>
<ModifyPartition wcm:action="add">
<Format>NTFS</Format>
<Label>WinRE</Label>
<Order>1</Order>
<PartitionID>1</PartitionID>
<TypeID>DE94BBA4-06D1-4D40-A16A-BFD50179D6AC</TypeID>
</ModifyPartition>
<ModifyPartition wcm:action="add">
<Format>FAT32</Format>
<Label>System</Label>
<Order>2</Order>
<PartitionID>2</PartitionID>
</ModifyPartition>
<ModifyPartition wcm:action="add">
<Format>NTFS</Format>
<Label>Windows</Label>
<Order>4</Order>
<Letter>C</Letter>
<PartitionID>4</PartitionID>
</ModifyPartition>
<ModifyPartition wcm:action="add">
<Order>3</Order>
<PartitionID>3</PartitionID>
</ModifyPartition>
</ModifyPartitions>
<DiskID>0</DiskID>
<WillWipeDisk>true</WillWipeDisk>
</Disk>
</DiskConfiguration>
<ImageInstall>
<OSImage>
<InstallTo>
<DiskID>0</DiskID>
<PartitionID>4</PartitionID>
</InstallTo>
</OSImage>
</ImageInstall>
<UserData>
<ProductKey>
<Key>VK7JG-NPHTM-C97JM-9MPGT-3V66T</Key>
</ProductKey>
<AcceptEula>true</AcceptEula>
</UserData>
</component>
</settings>
<settings pass="oobeSystem">
<component name="Microsoft-Windows-International-Core" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<InputLocale>en-US</InputLocale>
<SystemLocale>en-US</SystemLocale>
<UILanguage>en-US</UILanguage>
<UILanguageFallback>en-US</UILanguageFallback>
<UserLocale>en-US</UserLocale>
</component>
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<OOBE>
<HideEULAPage>true</HideEULAPage>
<HideOEMRegistrationScreen>true</HideOEMRegistrationScreen>
<HideOnlineAccountScreens>true</HideOnlineAccountScreens>
<HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
<ProtectYourPC>1</ProtectYourPC>
<UnattendEnableRetailDemo>false</UnattendEnableRetailDemo>
</OOBE>
<UserAccounts>
<AdministratorPassword>
<Value>QQBkAG0AaQBuAGkAcwB0AHIAYQB0AG8AcgBQAGEAcwBzAHcAbwByAGQA</Value>
<PlainText>false</PlainText>
</AdministratorPassword>
<LocalAccounts>
<LocalAccount wcm:action="add">
<Password>
<Value>UABhAHMAcwB3AG8AcgBkAA==</Value>
<PlainText>false</PlainText>
</Password>
<DisplayName>Owner</DisplayName>
<Group>Administrators</Group>
<Name>Owner</Name>
<Description>Main local admin account</Description>
</LocalAccount>
</LocalAccounts>
</UserAccounts>
<TimeZone>U.S. Mountain Standard Time</TimeZone>
<DisableAutoDaylightTimeSet>true</DisableAutoDaylightTimeSet>
<AutoLogon>
<Password>
<Value>UABhAHMAcwB3AG8AcgBkAA==</Value>
<PlainText>false</PlainText>
</Password>
<Enabled>true</Enabled>
<LogonCount>1</LogonCount>
<Username>Owner</Username>
</AutoLogon>
<FirstLogonCommands>
<SynchronousCommand wcm:action="add">
<CommandLine>reg add &quot;HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon&quot; /v AutoLogonCount /t REG_DWORD /d 0 /f</CommandLine>
<Order>1</Order>
</SynchronousCommand>
</FirstLogonCommands>
</component>
</settings>
<settings pass="specialize">
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<TimeZone>U.S. Mountain Standard Time</TimeZone>
<DisableAutoDaylightTimeSet>true</DisableAutoDaylightTimeSet>
</component>
</settings>
<cpi:offlineImage cpi:source="wim:g:/iso_files/sources/install.wim#Windows 10 Pro" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>

- - - Updated - - -

Please don't spend much time pouring over the details of my answer file unless something pops out at you. I'm going to review the process again, create another file, and test it again to see if I can find anything I have missed. I'll post an update after I look into it some more.

Thanks.

-Spike

Spike, it's going to be a few hours before I have time to look in detail, but later this evening I promise that I will. I'm curious to see what is happening myself.

I'll let you know what I find.

No rush...I'm currently reviewing Kari's steps, and there is so much content that it's easy to get caught up in the weeds. The steps are laid out quite clearly with plenty of links to detailed external steps, but at times it's easy to not "see the forest because of the trees". l'm taking some time to research more detail behind some of the steps to add more context to the process.

Spike, I think that I may see the problem but I'll have to test this in the morning to be sure.

I noticed in your answer file that you have specified a password for the Administrator account in addition to the Admin level user account you are creating. I'll try your answer file in the morning.

If you beat me to it, try removing that from your answer file and see if that solves the difficulties.

Otherwise, I'll let you know what happens when I try it.

Spike,

I figured I'd do the test before I go to bed since it would take me no more than 10 minutes, so I did.

I have good news and bad news. The bad news is that I could not reproduce any problem using the very answer file that you supplied. The good news is that using that answer with no modifications whatsoever, Windows 10 Pro 1909 installed for me with no difficulties at all. I was never prompted for a single thing. It went all the way to my being logged on to the desktop as a user named "owner".

Here is my test scenario:

I used VMware Workstation Pro 15.5. I created a a new virtual machine and pointed it to a Windows 10 1909 Consumer Editions ISO image. Rather than modify that image and add the answer file to it, I simply created another ISO image that had only a single file in it: the autounattend.xml answer file. I connected that to the VM as a second optical disc.

NOTE: You can put the answer file on any drive. Windows setup looks on the root of all drives for an answer file.

Could you describe your test situation and exactly what difficulties you are still encountering?

Bottom line is that there is no problem with the answer file. Adding a password to the Administrator account is not causing a problem.