Generator autounattend.xml pentru Windows 11 24H2 si 25H2
Genereaza fisier de configurare unattended pentru Windows 11 in 60 secunde.
100% in browser — nu trimitem date pe server.
Configureaza optiunile de mai jos
Click „Genereaza si descarca"
Pune fisierul pe USB-ul Windows 11
Vezi ghidul complet pas-cu-pas → Bypass Microsoft Account Windows 11 — Ghid Complet 2026
Configurare
Max 15 caractere. Lasa gol pentru nume aleator generat de Windows.
Preview autounattend.xml
<?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">
<SetupUILanguage>
<UILanguage>en-US</UILanguage>
</SetupUILanguage>
<InputLocale>0409:00000409</InputLocale>
<SystemLocale>en-US</SystemLocale>
<UILanguage>en-US</UILanguage>
<UserLocale>ro-RO</UserLocale>
</component>
<component name="Microsoft-Windows-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS">
<UserData>
<AcceptEula>true</AcceptEula>
</UserData>
</component>
</settings>
<settings pass="specialize">
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS">
<ComputerName>PC-LOCAL-01</ComputerName>
</component>
<component name="Microsoft-Windows-Deployment" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS">
<RunSynchronous>
<RunSynchronousCommand wcm:action="add">
<Order>1</Order>
<Path>reg add HKLM\SOFTWARE\Policies\Microsoft\Windows\DataCollection /v AllowTelemetry /t REG_DWORD /d 0 /f</Path>
<Description>Privacy: AllowTelemetry</Description>
</RunSynchronousCommand>
<RunSynchronousCommand wcm:action="add">
<Order>2</Order>
<Path>reg add HKLM\SOFTWARE\Policies\Microsoft\Windows\AdvertisingInfo /v DisabledByGroupPolicy /t REG_DWORD /d 1 /f</Path>
<Description>Privacy: DisabledByGroupPolicy</Description>
</RunSynchronousCommand>
<RunSynchronousCommand wcm:action="add">
<Order>3</Order>
<Path>reg add HKLM\SOFTWARE\Policies\Microsoft\Windows\LocationAndSensors /v DisableLocation /t REG_DWORD /d 1 /f</Path>
<Description>Privacy: DisableLocation</Description>
</RunSynchronousCommand>
<RunSynchronousCommand wcm:action="add">
<Order>4</Order>
<Path>reg add HKLM\SOFTWARE\Policies\Microsoft\Windows\CloudContent /v DisableTailoredExperiencesWithDiagnosticData /t REG_DWORD /d 1 /f</Path>
<Description>Privacy: DisableTailoredExperiencesWithDiagnosticData</Description>
</RunSynchronousCommand>
<RunSynchronousCommand wcm:action="add">
<Order>5</Order>
<Path>reg add HKLM\SOFTWARE\Policies\Microsoft\InputPersonalization /v AllowInputPersonalization /t REG_DWORD /d 0 /f</Path>
<Description>Privacy: AllowInputPersonalization</Description>
</RunSynchronousCommand>
<RunSynchronousCommand wcm:action="add">
<Order>6</Order>
<Path>reg add HKLM\SOFTWARE\Policies\Microsoft\Windows\TextInput /v AllowLinguisticDataCollection /t REG_DWORD /d 0 /f</Path>
<Description>Privacy: AllowLinguisticDataCollection</Description>
</RunSynchronousCommand>
</RunSynchronous>
</component>
</settings>
<settings pass="oobeSystem">
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS">
<UserAccounts>
<LocalAccounts>
<LocalAccount wcm:action="add">
<Name>Administrator</Name>
<Group>Administrators</Group>
<DisplayName>Administrator</DisplayName>
</LocalAccount>
</LocalAccounts>
</UserAccounts>
<OOBE>
<HideEULAPage>true</HideEULAPage>
<HideOEMRegistrationScreen>true</HideOEMRegistrationScreen>
<HideOnlineAccountScreens>true</HideOnlineAccountScreens>
<HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
<NetworkLocation>Work</NetworkLocation>
<ProtectYourPC>3</ProtectYourPC>
<SkipMachineOOBE>true</SkipMachineOOBE>
<SkipUserOOBE>true</SkipUserOOBE>
</OOBE>
<RegisteredOrganization>Workstation</RegisteredOrganization>
<RegisteredOwner>Administrator</RegisteredOwner>
<TimeZone>GTB Standard Time</TimeZone>
</component>
</settings>
</unattend>4.2 KB · UTF-8 · client-side
Cum se foloseste fisierul
- 01
Descarca Windows 11 ISO oficial
De la microsoft.com/software-download/windows11. Selecteaza limba si edition (Pro pentru utilizare business). Fisier ~5-6 GB. - 02
Creeaza USB bootabil cu Rufus
Descarca Rufus 4.x de la rufus.ie. Insereaza USB minim 8GB, selecteaza ISO-ul, click START. In dialogul „Windows User Experience\" debifeaza optiunile (vom folosi autounattend.xml manual). - 03
Pune autounattend.xml in root-ul USB-ului
Deschide USB in File Explorer si copiaza fisierul descarcat de la noi in primul nivel. Verifica langa folderele sources/, boot/, efi/.USB:\ ├── autounattend.xml ← AICI ├── boot/ ├── efi/ ├── sources/ └── ...
- 04
Boot de pe USB
Reporneste PC-ul, intra in BIOS/UEFI boot menu (F12 / F2 / Del / Esc, in functie de motherboard) si selecteaza USB stick-ul. - 05
Asteapta — setup-ul ruleaza singur
Windows va detecta autounattend.xml automat: va sari peste ecranele OOBE, NU va cere internet, NU va cere cont Microsoft, va crea contul local specificat. Boot final pe Desktop in 15-30 minute.
Microsoft poate bloca aceasta metoda?
Foarte putin probabil. autounattend.xml e parte fundamentala din Windows Setup, folosit de SCCM, MDT, Intune si Autopilot. Blocarea ar afecta deployment enterprise masiv si ar contrazice contractele de Volume Licensing.
E sigur sa pun parola in clear text?
Pentru testare sau un singur PC personal: acceptabil daca distrugi USB-ul dupa instalare. Pentru deployment enterprise, foloseste credentials encryption prin MDT/SCCM sau lasa parola goala si o setezi la primul login.
Functioneaza pe Windows 11 25H2?
Da. E una dintre putinele metode care functioneaza pe build 26200+ unde oobe\BYPASSNRO si ms-cxh:localonly sunt blocate.
Functioneaza pe Windows 11 Home?
Da, toate functiile (cont local, bypass hardware, FirstLogonCommands) functioneaza identic. Diferenta majora: Domain Join nu functioneaza pe Home, doar pe Pro/Enterprise/Education.
Pot folosi acelasi fisier pe mai multe PC-uri?
Da, asta e exact cazul de uz pentru care a fost creat formatul - deployment masiv. Singurul element care trebuie diferit e ComputerName. Toate celelalte setari raman identice.
Ai nevoie de deployment masiv?
Pentru flote de 50+ statii, integram autounattend.xml in MDT/SCCM/Intune cu profiluri NIS2-compliant, BitLocker la prima boot si audit trail complet.
Contacteaza-ne