How to Make an Automated Windows 10 Boot CD Without User Intervention

2024/07/21 03:02

Here's a Windows 10 script you can build that will automatically install a CLEAN version of Windows 10 from a CD to a Hard Drive without user intervention

If your hard drive ever dies, or your computer is infected with the latest malware, there will come a time when you will need to do a clean install of Windows 10. If you are responsible for many computers do yourself a favor and build an unattended Windows 10 Installer CD.

This process typically involves creating an unattended installation file, also known as an answer file, that Windows Setup can use to bypass the usual prompts and questions during installation.

Here's a basic outline of how to do this:

1. Create an Answer File
The answer file (autounattend.xml) is the key to automating the installation. You'll need the Windows System Image Manager (WSIM), which is part of the Windows Assessment and Deployment Kit (ADK).

Here's a simplified version of what the autounattend.xml might look like:

<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
    <settings pass="windowsPE">
        <component name="Microsoft-Windows-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2006/State">
            <ImageInstall>
                <OSImage>
                    <InstallFrom>
                        <MetaData wcm:action="add">
                            <Key>/image</Key>
                            <Value>install.wim</Value>
                        </MetaData>
                    </InstallFrom>
                    <InstallTo>
                        <DiskID>0</DiskID>
                        <PartitionID>1</PartitionID>
                    </InstallTo>
                </OSImage>
            </ImageInstall>
            <UserData>
                <AcceptEula>true</AcceptEula>
                <FullName>Your Name</FullName>
                <Organization>Your Organization</Organization>
            </UserData>
            <DiskConfiguration>
                <Disk wcm:action="add">
                    <DiskID>0</DiskID>
                    <WillWipeDisk>true</WillWipeDisk>
                    <CreatePartitions>
                        <CreatePartition>
                            <Order>1</Order>
                            <Type>Primary</Type>
                            <Size>100</Size>
                        </CreatePartition>
                        <CreatePartition>
                            <Order>2</Order>
                            <Type>Primary</Type>
                            <Extend>true</Extend>
                        </CreatePartition>
                    </CreatePartitions>
                    <ModifyPartitions>
                        <ModifyPartition>
                            <Order>1</Order>
                            <PartitionID>1</PartitionID>
                            <Format>NTFS</Format>
                            <Label>System</Label>
                            <Active>true</Active>
                        </ModifyPartition>
                        <ModifyPartition>
                            <Order>2</Order>
                            <PartitionID>2</PartitionID>
                            <Format>NTFS</Format>
                            <Label>Windows</Label>
                        </ModifyPartition>
                    </ModifyPartitions>
                </Disk>
            </DiskConfiguration>
        </component>
    </settings>
    <settings pass="oobeSystem">
        <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2006/State">
            <OOBE>
                <HideEULAPage>true</HideEULAPage>
                <NetworkLocation>Work</NetworkLocation>
                <ProtectYourPC>1</ProtectYourPC>
            </OOBE>
            <UserAccounts>
                <AdministratorPassword>
                    <Value>your_admin_password</Value>
                    <PlainText>true</PlainText>
                </AdministratorPassword>
                <LocalAccounts>
                    <LocalAccount wcm:action="add">
                        <Name>Administrator</Name>
                        <Password>
                            <Value>your_admin_password</Value>
                            <PlainText>true</PlainText>
                        </Password>
                        <Group>Administrators</Group>
                    </LocalAccount>
                </LocalAccounts>
            </UserAccounts>
            <AutoLogon>
                <Password>
                    <Value>your_admin_password</Value>
                    <PlainText>true</PlainText>
                </Password>
                <Username>Administrator</Username>
                <Enabled>true</Enabled>
            </AutoLogon>
        </component>
    </settings>
</unattend>

2. Burn the Answer File to a CD
Burn a Windows 10 ISO to a CD.
Add the autounattend.xml file to the root directory of the CD.
3. Automate the Boot Process
Ensure the BIOS is set to boot from the CD drive.
Insert the CD and restart the computer.
4. Script for Additional Automation (Optional)
You can create a script to automate any post-installation tasks. Save this script and include it in the autounattend.xml file under the FirstLogonCommands section.

Final Steps
Test the CD on a virtual machine or a spare computer to ensure the unattended installation works as expected.
Adjust the autounattend.xml file as necessary to fit your specific needs.

This should help you create a script for an automated clean installation of Windows 10 from a CD.

Next Level: Auto-install your favorite apps during the Windows 10 Installation
In step 4 above, you can use a post-installation script to automate additional tasks, including installing applications.

Here’s how you can do it:

Automating Post-Installation Tasks
To run scripts or install applications automatically after the Windows installation, you can use the FirstLogonCommands in the autounattend.xml file.

Step-by-Step Guide:
1. Create Your Installation Script

Write a batch script (install-apps.bat) to install your applications. For example, to install an app silently, you might include commands like:

@echo off
REM Install ExampleApp
start /wait "" "C:\path\to\ExampleAppInstaller.exe" /quiet /norestart

Save this script to a location that will be accessible after the installation, such as a USB drive or a hard drive.

2. Modify autounattend.xml
Add the FirstLogonCommands section to your autounattend.xml file. This section will specify commands to run when the first user logs in.

Here’s an example:

<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
    <settings pass="windowsPE">
        <!-- Your existing configuration -->
    </settings>
    <settings pass="oobeSystem">
        <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2006/State">
            <OOBE>
                <HideEULAPage>true</HideEULAPage>
                <NetworkLocation>Work</NetworkLocation>
                <ProtectYourPC>1</ProtectYourPC>
            </OOBE>
            <UserAccounts>
                <AdministratorPassword>
                    <Value>your_admin_password</Value>
                    <PlainText>true</PlainText>
                </AdministratorPassword>
                <LocalAccounts>
                    <LocalAccount wcm:action="add">
                        <Name>Administrator</Name>
                        <Password>
                            <Value>your_admin_password</Value>
                            <PlainText>true</PlainText>
                        </Password>
                        <Group>Administrators</Group>
                    </LocalAccount>
                </LocalAccounts>
            </UserAccounts>
            <AutoLogon>
                <Password>
                    <Value>your_admin_password</Value>
                    <PlainText>true</PlainText>
                </Password>
                <Username>Administrator</Username>
                <Enabled>true</Enabled>
            </AutoLogon>
            <FirstLogonCommands>
                <SynchronousCommand wcm:action="add">
                    <CommandLine>cmd /c C:\path\to\install-apps.bat</CommandLine>
                    <Description>Install Applications</Description>
                    <Order>1</Order>
                </SynchronousCommand>
            </FirstLogonCommands>
        </component>
    </settings>
</unattend>

In this example, cmd /c C:\path\to\install-apps.bat will run your script after the first logon.

3. Save and Include Your Script
Save your install-apps.bat script in a location that will be accessible during the Windows installation. Common options include:
Placing it on the same CD as the Windows installation files.
Copying it to a specific directory on the hard drive during the setup.

4. Testing
Test your setup to ensure that:

Windows installs without user intervention.
The first logon automatically runs your script to install the applications.
Example Application Installation Script

Here’s a more detailed example of what your install-apps.bat script might look like if you’re installing multiple applications:

@echo off

REM Install Google Chrome
start /wait "" "C:\Installers\ChromeSetup.exe" /silent /install

REM Install VLC Media Player
start /wait "" "C:\Installers\vlc-setup.exe" /S

REM Install Notepad++
start /wait "" "C:\Installers\npp.7.9.5.Installer.exe" /S

REM All installations completed
echo All applications have been installed.

Place the installer files and the script in a directory like C:\Installers, and make sure the paths in your script match the actual locations of your installer files.

By following these steps, you can automate the installation of both Windows 10 and your preferred applications with minimal user intervention.

Add Messaging During the Automated Install to Inform Users

To display a message to the user during the installation process. Use the msg command in your batch script to show a message, or you can use a more sophisticated tool like PowerShell for more control over the message box.

Using msg Command
The msg command is simple but may have some limitations on different versions of Windows.

Here’s how you can use it in your batch script:

@echo off

REM Display a message to the user
msg * "The installation is starting. Please wait..."

REM Install Google Chrome
start /wait "" "C:\Installers\ChromeSetup.exe" /silent /install

REM Display another message to the user
msg * "Google Chrome installation completed."

REM Install VLC Media Player
start /wait "" "C:\Installers\vlc-setup.exe" /S

REM Display another message to the user
msg * "VLC Media Player installation completed."

REM Install Notepad++
start /wait "" "C:\Installers\npp.7.9.5.Installer.exe" /S

REM Display final message to the user
msg * "All applications have been installed. Enjoy!"

Using PowerShell

For a more customizable message box, use PowerShell within your batch script.

Here’s an example:

@echo off

REM Display a message to the user using PowerShell
powershell -command "Add-Type -AssemblyName PresentationFramework; [System.Windows.MessageBox]::Show('The installation is starting. Please wait...', 'Installation Notice')"

REM Install Google Chrome
start /wait "" "C:\Installers\ChromeSetup.exe" /silent /install

REM Display another message to the user using PowerShell
powershell -command "Add-Type -AssemblyName PresentationFramework; [System.Windows.MessageBox]::Show('Google Chrome installation completed.', 'Installation Notice')"

REM Install VLC Media Player
start /wait "" "C:\Installers\vlc-setup.exe" /S

REM Display another message to the user using PowerShell
powershell -command "Add-Type -AssemblyName PresentationFramework; [System.Windows.MessageBox]::Show('VLC Media Player installation completed.', 'Installation Notice')"

REM Install Notepad++
start /wait "" "C:\Installers\npp.7.9.5.Installer.exe" /S

REM Display final message to the user using PowerShell
powershell -command "Add-Type -AssemblyName PresentationFramework; [System.Windows.MessageBox]::Show('All applications have been installed. Enjoy!', 'Installation Notice')"

Integrating with autounattend.xml

You can include this batch script as a FirstLogonCommand in your autounattend.xml file:

<FirstLogonCommands>
    <SynchronousCommand wcm:action="add">
        <CommandLine>cmd /c C:\path\to\install-apps.bat</CommandLine>
        <Description>Install Applications and Show Messages</Description>
        <Order>1</Order>
    </SynchronousCommand>
</FirstLogonCommands>

This way, when the user logs in for the first time, the script will run, install the applications, and display messages to the user. Adjust the paths and messages as needed for your specific setup.

More Tech, Streaming TV, and Other Latest Breaking News in 24 Categories! 📰🌍📢

How to Make an Automated Windows 10 Boot CD Without User Intervention

How to Make an Automated Windows 10 Boot CD Without User Intervention

Suggested Topics

Want to read more? Browse all categories or view latest topics.