New
#20
You are welcome.
By the way, my previous post contains a fundamental error, my apologies. COMMIT switch does not save the changes to a new WIM file, it saves the changes to the same WIM file you mounted.
In other words, it does not create a new WIM file, instead it modifies an existing one.
Kari
thank you. As you said, it replaces the existing install.wim by a new one, in which OOBE is bypassed except password.
- - - Updated - - -
Kari, I would like to ask a related question. In this tutorial, we can "have a Windows 10 install media which fully bypasses all steps of Windows Welcome (OOBE)". We still need to manually select installation disk, delete existing partition(s), and then install. Since I only have a primary partition, a recovery partition, is there a "simple" sample for configuring the "hard drive" and create default partitions? In this way, the entire installation is "un-attended". Thanks in advance.
Hello Kari,
I found myself diving into this recently and have a question for you about the users.
Scenario: deploy an image that only asks for Local User Name. That is the only part of the OOBE I want to keep so that systems can be customized with the actual EU name rather than admin. Is there a way to have OOBE ask ONLY for the username/password rather than have it specified in answer file?
TIA
During the installation, I enter where to install (HDD partition), then the name or password and that's it.
If that helps, here are my files:
autounattend.xml
unattend.xmlCode:<?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>cs-CZ</UILanguage> </SetupUILanguage> <InputLocale>0405:00000405</InputLocale> <SystemLocale>cs-CZ</SystemLocale> <UILanguage>cs-CZ</UILanguage> <UserLocale>cs-CZ</UserLocale> <UILanguageFallback>en-US</UILanguageFallback> </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"> <ImageInstall> <OSImage> <Compact>true</Compact> </OSImage> </ImageInstall> <UserData> <ProductKey> <Key>VK7JG-NPHTM-C97JM-9MPGT-3V66T</Key> </ProductKey> <AcceptEula>true</AcceptEula> <Organization>Warforum</Organization> </UserData> </component> </settings> <cpi:offlineImage cpi:source="wim:c:/iso_files/sources/install.wim#Windows 10 Pro" xmlns:cpi="urn:schemas-microsoft-com:cpi" /> </unattend>
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>cs-CZ</UILanguage> </SetupUILanguage> <InputLocale>0405:00000405</InputLocale> <SystemLocale>cs-CZ</SystemLocale> <UILanguage>cs-CZ</UILanguage> <UserLocale>cs-CZ</UserLocale> <UILanguageFallback>en-US</UILanguageFallback> </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"> <ImageInstall> <OSImage> <Compact>true</Compact> </OSImage> </ImageInstall> <UserData> <ProductKey> <Key>VK7JG-NPHTM-C97JM-9MPGT-3V66T</Key> </ProductKey> <AcceptEula>true</AcceptEula> <Organization>Warforum</Organization> </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>0405:00000405</InputLocale> <UILanguageFallback>en-US</UILanguageFallback> <UserLocale>cs-CZ</UserLocale> <UILanguage>cs-CZ</UILanguage> <SystemLocale>cs-CZ</SystemLocale> </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> <HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE> <HideOnlineAccountScreens>true</HideOnlineAccountScreens> <ProtectYourPC>1</ProtectYourPC> <UnattendEnableRetailDemo>false</UnattendEnableRetailDemo> </OOBE> </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>Warforum</Manufacturer> </OEMInformation> <CopyProfile>true</CopyProfile> <OEMName>Warforum</OEMName> <RegisteredOrganization>Warforum</RegisteredOrganization> <TimeZone>Central Europe Standard Time</TimeZone> </component> </settings> <cpi:offlineImage cpi:source="wim:c:/iso_files/sources/install.wim#Windows 10 Pro" xmlns:cpi="urn:schemas-microsoft-com:cpi" /> </unattend>
When switching versions of windows 11, do you just reuse your autounattend answer file or do you have to reassosiate the catalogue file with the new windows?
I use uupdump and pro is the only one I download.
Thanks Shane.