IT FundamentalsA+

Windows Installation for CompTIA A+ 220-1102

Windows installation is a core CompTIA A+ 220-1102 skill. Technicians must perform clean installations, upgrades, and unattended deployments. Understanding the installation process, partition requirements, and post-installation steps ensures successful deployments. The exam covers installation types, media creation, partitioning, and common installation errors.

7 min
2 sections · 7 exam key points
1 practice questions

Installation Types and Methods

Clean installation: completely fresh Windows install — erases existing OS and data. Required when: major OS upgrade (Windows 10 → 11 on problematic system), malware removal, replacing a failing drive, deploying a new PC. Steps: create bootable USB with Windows Media Creation Tool, boot from USB (change boot order in BIOS), select language/time/keyboard, enter product key (or skip — activate later), select 'Custom: Install Windows only (advanced)', partition the drive, wait for installation to complete.

In-place upgrade: upgrades Windows version while keeping installed applications and user data. Available: Windows 10 → Windows 11 (if hardware compatible). Run setup.exe from Windows installation media and select 'Upgrade this PC now.' Less disruptive than clean install. Can resolve some OS issues while preserving data. Risks: can fail if the current installation is corrupted. Recommended: back up first.

Unattended installation: automated, hands-free installation using an answer file (unattend.xml) that provides all installation parameters without user input — used for deploying many PCs simultaneously. Tools: Windows SIM (System Image Manager), MDT (Microsoft Deployment Toolkit), SCCM/MEM (Microsoft Endpoint Manager). The answer file specifies: product key, locale, username, disk configuration, post-install scripts.

Image deployment: capture a 'golden image' (configured reference installation) with Sysprep (removes machine-specific info like SID, computer name) and deploy it to multiple PCs using WDS (Windows Deployment Services), MDT, or third-party imaging tools (Acronis, Clonezilla). Much faster than individual installations — most enterprise deployments use imaging.

Repair installation / Windows Recovery: Windows installer offers 'Repair' option that reinstalls Windows system files while preserving applications and user data. Available from: Windows installation media → Repair your computer, or from Windows Recovery Environment (WinRE). Also: 'Reset this PC' from Windows Settings — similar to repair/reinstall without installation media.

Partitioning and Post-Installation

Partitioning during installation: Windows setup automatically creates required partitions on unformatted drives: System Reserved partition (100–500 MB — contains boot files, BitLocker metadata), EFI System Partition (100 MB, FAT32 — on UEFI systems), Recovery partition (450 MB — for Windows Recovery Environment), C: partition (remaining space, NTFS — the Windows installation partition). Manual partitioning: delete all existing partitions and let setup create them, or use custom partition sizing.

Minimum requirements (Windows 11): 4 GB RAM, 64 GB storage, 64-bit CPU, UEFI with Secure Boot, TPM 2.0, internet connection for initial setup (can skip on Pro). Product key: entered during installation or at activation after install (Settings → Activation). OEM keys: embedded in UEFI firmware of branded PCs — Windows automatically activates without entering a key.

Post-installation checklist: install drivers (chipset, GPU, NIC, audio) from manufacturer. Run Windows Update (multiple rounds — cumulative updates). Install antivirus/security software. Activate Windows. Configure user accounts. Install required applications. Verify backup solution is in place.

Key exam facts — A+

  • Clean install: boot from USB, 'Custom' install, partitions created fresh
  • In-place upgrade: keeps apps/data; run setup.exe from media or Windows Update
  • Sysprep: prepares golden image for deployment — removes machine-specific identifiers
  • Unattend.xml: answer file for automated installations — specifies all setup parameters
  • Windows 11 minimum: 4 GB RAM, 64 GB storage, TPM 2.0, Secure Boot, UEFI
  • EFI partition (FAT32, 100 MB): required on UEFI systems for boot files
  • OEM key: stored in UEFI firmware — Windows auto-activates on branded PCs

Common exam traps

An in-place upgrade always keeps all applications and data

In-place upgrades typically keep installed applications and user data, but there are limitations: incompatible applications may be removed or may break. 32-bit applications may need reinstallation. Applications that store data outside of user profile folders may lose data if their installation folder is affected. Always back up before in-place upgrades, and verify critical applications function after the upgrade

Practice questions — Windows Installation

These questions are representative of what you will see on A+ exams. The correct answer and explanation are shown immediately below each question.

Q1.A technician needs to deploy Windows 11 to 100 new PCs simultaneously with a consistent configuration, pre-installed applications, and company settings. Which method is most efficient?

A.Perform a clean install on each PC individually from USB
B.Run Windows Update on each PC
C.Create a Sysprep'd golden image and deploy via imaging software
D.In-place upgrade each PC from Windows 10

Explanation: Creating a 'golden image' (a fully configured reference installation with all required applications, settings, and drivers), running Sysprep to generalize it, then deploying via WDS or MDT to all 100 PCs simultaneously is the most efficient method. Sysprep removes machine-specific identifiers (SID, computer name) so each deployed PC gets its own unique identity. Individual USB installs on 100 PCs would take hundreds of person-hours. Windows Update doesn't install the OS. In-place upgrade requires an existing Windows installation.

Frequently asked questions — Windows Installation

What is Sysprep and why is it needed for image deployment?

Sysprep (System Preparation tool) prepares a Windows installation for cloning to multiple PCs. Without Sysprep, every PC cloned from the same image would have: the same Security Identifier (SID) — causing security and domain join problems, the same computer name, and the same activation state. Running Sysprep with /oobe /generalize removes these machine-specific settings. When the image is deployed and the PC boots for the first time, Windows generates a unique SID and goes through the Out-of-Box Experience (OOBE) to set computer name, user account, etc. MDT and Windows Autopilot automate this process further.

Practice this topic

Test yourself on Windows Installation

JT Exams routes you to questions in your exact weak areas — automatically, after every session.

No credit card · Cancel anytime

Related certification topics