Integrate new OOBE bypass (ms-cxh:localonly) in a autounattend.xml script??

hsehestedt said:

@rafaelsouzams,

Below is a sample answer file. This one does the following:

1) Bypass Win 11 system requirements (can be used on systems that do pass requirements as well)
2) Creates a local user account
3) Eliminates the need for networking during installation (ok if network is enabled)
4) Bypasses the installation of quality updates during Windows setup

It DOES NOT perform a completely unattended installation.

If you want other samples, for example, one that nothing but create a local user account, let me know and I can provide you with such.

XML:

<?xml version="1.0" encoding="utf-8"?>

<!--
Last updated on Mar 21, 2025

The purpose of this answer file is to bypass the Windows 11 system requirement checks, create a local user account, bypass
the automatic installation of quality updates during setup, and eliminate the need for an internet connection during setup.
It does NOT perform an unattended installation of Windows.

It includes a Windows 10 / 11 Pro key.

It will create a local user account named "WinUser" with a full name of "Windows User" and a password of "Password1".

END OF NOTES
-->

<unattend xmlns="urn:schemas-microsoft-com:unattend">
    <settings pass="windowsPE">
        <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">
            <UserData>
                <ProductKey>
                    <Key>VK7JG-NPHTM-C97JM-9MPGT-3V66T</Key>
                </ProductKey>
                <AcceptEula>true</AcceptEula>
            </UserData>
            <RunSynchronous>
                <RunSynchronousCommand wcm:action="add">
                    <Order>1</Order>
                    <Path>reg add HKLM\System\Setup\LabConfig /v BypassTPMCheck /t reg_dword /d 0x00000001 /f</Path>
                </RunSynchronousCommand>
                <RunSynchronousCommand wcm:action="add">
                    <Order>2</Order>
                    <Path>reg add HKLM\System\Setup\LabConfig /v BypassSecureBootCheck /t reg_dword /d 0x00000001 /f</Path>
                </RunSynchronousCommand>
                <RunSynchronousCommand wcm:action="add">
                    <Order>3</Order>
                    <Path>reg add HKLM\System\Setup\LabConfig /v BypassRAMCheck /t reg_dword /d 0x00000001 /f</Path>
                </RunSynchronousCommand>
            </RunSynchronous>
        </component>
    </settings>
    <settings pass="oobeSystem">
        <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">
            <UserAccounts>
                <LocalAccounts>
                    <LocalAccount wcm:action="add">
                        <Password>
                            <Value>UABhAHMAcwB3AG8AcgBkADEAUABhAHMAcwB3AG8AcgBkAA==</Value>
                            <PlainText>false</PlainText>
                        </Password>
                        <DisplayName>Windows User</DisplayName>
                        <Group>Administrators</Group>
                        <Name>WinUser</Name>
                    </LocalAccount>
                </LocalAccounts>
            </UserAccounts>
            <OOBE>
                <HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
                <UnattendEnableRetailDemo>false</UnattendEnableRetailDemo>
                <HideEULAPage>true</HideEULAPage>
                <HideOEMRegistrationScreen>true</HideOEMRegistrationScreen>
                <HideOnlineAccountScreens>true</HideOnlineAccountScreens>
                <ProtectYourPC>1</ProtectYourPC>
            </OOBE>
            <FirstLogonCommands>
                <SynchronousCommand wcm:action="add">
                    <Order>1</Order>
                    <CommandLine>powershell.exe -Command &quot;Get-NetAdapter | Enable-NetAdapter -Confirm:$false&quot;</CommandLine>
                </SynchronousCommand>
            </FirstLogonCommands>
        </component>
    </settings>
    <settings pass="specialize">
        <component name="Microsoft-Windows-Deployment" 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">
            <RunSynchronous>
                <RunSynchronousCommand wcm:action="add">
                    <Order>1</Order>
                    <Path>powershell.exe -Command &quot;Get-NetAdapter | Disable-NetAdapter -Confirm:$false&quot;</Path>
                </RunSynchronousCommand>
            </RunSynchronous>
        </component>
    </settings>
    <cpi:offlineImage cpi:source="catalog://godzilla/datadiskmy data/01 - software/06 - windows deployment tools/catalog files for windows sim/windows 11 pro 24h2 catalog file/install_windows 11 pro.clg" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>

Click to expand...

@hsehestedt​

rafaelsouzams said:

So just to be clear, I love the current possibilities of autounatted, but I believe it could be much better if we could insert ms-cxh:locanonly into it, to further speed up the Windows installation procedure! So that's my goal!

Click to expand...

hsehestedt said:

I don't understand. Forgive me if I'm being a little slow - have not had coffee yet. That's my excuse

My mental block is simply that an autounattend can skip all those parts anyway so the need for integration of that command makes no sense to me.

Or are you saying that you think an unattended setup will finish faster with that option integrated in? For me, I would actually rather it take a minute longer so I don't have to sit around and wait for it to get to that screen where I would need to respond. I just start unattended installation and when I come back 5 minutes later Windows is completely installed.

Click to expand...

garlin said:

O que acontece se corrermos "cmd /c start ms-cxh:localonly"do modo autônomo?

Após a saída do WinPE, existem (4) maneiras possíveis de executar um comando autônomo:

- especialize-se no passe antes do início do OOBE​

- criação de tarefas agendadas durante a especialização​

- SetupComplete.cmd, após o término do OOBE​

- Comando FirstLogon quando você estiver conectado pela primeira vez​

Os dois últimos estágios são tarde demais para evitar que você alcance a tela da Conta MS. Uma tarefa agendada pode executar o comando na hora em que o OOBE for iniciado, mas é difícil controlar o tempo preciso. A tarefa pode ser muito cedo ou muito tarde.

1. iniciar ms-cxh: apenas local não funciona a partir de specialize pass. É muito cedo porque o Windows não terminou de instalar.

View attachment 130185

2. Executar o comando manual na primeira tela do OOBE implica que você está ignorando as opções de idioma, teclado, região e nome do computador.

O que pode ser bom se você quiser os mesmos padrões da edição ISO que está instalando. Mas alguns usuários instalam conscientemente o Inglês (EUA) ISO, embora não sejam usuários baseados nos EUA. Ignorar o resto do OOBE pode não ser uma solução que economiza tempo, pois você terá que inserir Configurações para alterar o idioma, o teclado e a localidade.

View attachment 130186

3. Você ainda precisa executar a tela Privacidade do W11. Que pode ser ignorado usando o arquivo autônomo.

View attachment 130187

No final, executar o processo W10 "Criar um usuário para este PC" é uma correção imperfeita. Sim, evita a tela da conta MS, mas também cria outros problemas porque abrevia o processo OOBE.

Click to expand...