Octopuss Posted June 8, 2018 Posted June 8, 2018 (edited) I have a brand new VM, meaning the virtual disk is completely clean. I have (I believe) properly written answer file, but no partitions are being created. Could anyone figure out why? This is the relevant part of WindowsPE pass: <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> <WillShowUI>OnError</WillShowUI> <Disk wcm:action="add"> <DiskID>0</DiskID> <WillWipeDisk>true</WillWipeDisk> <CreatePartitions> <CreatePartition wcm:action="add"> <Order>1</Order> <Type>Primary</Type> <Size>100</Size> </CreatePartition> <CreatePartition wcm:action="add"> <Order>2</Order> <Type>Primary</Type> <Extend>true</Extend> </CreatePartition> </CreatePartitions> <ModifyPartitions> <ModifyPartition wcm:action="add"> <Order>1</Order> <PartitionID>1</PartitionID> <Active>true</Active> <Format>NTFS</Format> <Label>Boot</Label> </ModifyPartition> <ModifyPartition wcm:action="add"> <Order>2</Order> <PartitionID>2</PartitionID> <Format>NTFS</Format> <Letter>C</Letter> <Label>Windows</Label> </ModifyPartition> </ModifyPartitions> </Disk> </DiskConfiguration> <ImageInstall> <OSImage> <InstallFrom> <MetaData wcm:action="add"> <Key>/IMAGE/INDEX</Key> <Value>2</Value> </MetaData> </InstallFrom> <!--<InstallTo> <DiskID>0</DiskID> <PartitionID>2</PartitionID> </InstallTo>--> </OSImage> </ImageInstall> <UserData> <ProductKey> <Key>xxx</Key> </ProductKey> <AcceptEula>true</AcceptEula> </UserData> </component> I had to comment one part of the imageinstall because there are no partitions at this point due to some obscure problem. Edited June 8, 2018 by Octopuss
Tripredacus Posted August 15, 2019 Posted August 15, 2019 2 hours ago, LIUYUQING said: I have the same problem too. Using the exact same XML and using an un-named virtual machine?
LIUYUQING Posted August 15, 2019 Posted August 15, 2019 4 hours ago, Tripredacus said: Using the exact same XML and using an un-named virtual machine? NO,I installed windows 10 in a physical machine.
Tripredacus Posted August 16, 2019 Posted August 16, 2019 Ok then, create a new topic and post your XML and we can take a look. But one thing to remember, you can have either XML to create partitions on UEFI/GPT or Legacy/MBR. If your XML is written to create Legacy partitions, but your boot your install media in UEFI mode, Setup either will show the formatting prompt (as shown above) or give an error. Vice Versa has similar issues. So always make sure you are booting correctly, and for this I recommend using the one-time boot menu for your system.
LIUYUQING Posted August 31, 2019 Posted August 31, 2019 <?xml version="1.0" encoding="utf-8"?> <unattend xmlns="urn:schemas-microsoft-com:unattend"> <servicing> <package action="configure"> <assemblyIdentity name="Microsoft-Windows-Foundation-Package" version="10.0.18965.1000" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="" /> <selection name="Internet-Explorer-Optional-amd64" state="false" /> </package> </servicing> <settings pass="windowsPE"> <component name="Microsoft-Windows-PnpCustomizationsWinPE" 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"> <DriverPaths> <PathAndCredentials wcm:keyValue="b4cbfc28" wcm:action="add"> <Path>D:\sources\accessories\drivers</Path> </PathAndCredentials> </DriverPaths> </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>260</Size> <Type>EFI</Type> </CreatePartition> <CreatePartition wcm:action="add"> <Order>2</Order> <Type>Primary</Type> </CreatePartition> </CreatePartitions> <ModifyPartitions> <ModifyPartition wcm:action="add"> <Extend>false</Extend> <Order>1</Order> <Format>FAT32</Format> <PartitionID>1</PartitionID> <TypeID>c12a7328-f81f-11d2-ba4b-00a0c93ec93b</TypeID> </ModifyPartition> <ModifyPartition wcm:action="add"> <Format>NTFS</Format> <Letter>C</Letter> <Order>2</Order> <PartitionID>2</PartitionID> <TypeID>ebd0a0a2-b9e5-4433-87c0-68b6b72699c7</TypeID> </ModifyPartition> </ModifyPartitions> <WillWipeDisk>true</WillWipeDisk> <DiskID>0</DiskID> </Disk> </DiskConfiguration> <ImageInstall> <OSImage> <InstallTo> <DiskID>0</DiskID> <PartitionID>2</PartitionID> </InstallTo> </OSImage> </ImageInstall> <UserData> <ProductKey> <Key>...</Key> </ProductKey> <AcceptEula>true</AcceptEula> </UserData> <WindowsDeploymentServices> <ImageSelection> <InstallTo> <DiskID>0</DiskID> <PartitionID>2</PartitionID> </InstallTo> </ImageSelection> </WindowsDeploymentServices> </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"> <OEMInformation> <Manufacturer>Hewlett-Packard</Manufacturer> <Logo>%systemroot%\system32\oobe\info\HPLOGO.BMP</Logo> </OEMInformation> <BluetoothTaskbarIconEnabled>false</BluetoothTaskbarIconEnabled> <ComputerName>...</ComputerName> <ProductKey>...</ProductKey> </component> </settings> <cpi:offlineImage cpi:source="wim:c:/users/administrator/documents/install.wim#Windows 10 Education" xmlns:cpi="urn:schemas-microsoft-com:cpi" /> </unattend>
Tripredacus Posted September 2, 2019 Posted September 2, 2019 Verify that you are manually starting your install in EFI mode. You need to create the MSR partition in your XML. Ref: https://msfn.org/board/topic/154404-how-to-clean-gpt-hard-disk-using-autounattendxml/
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now