Memory hook: Choose the supported path before changing the boot disk.
Must remember
Check hardware requirements, firmware/boot mode, edition, architecture, licensing, application compatibility and data backup before installing or upgrading. An in-place upgrade preserves supported settings/apps under its compatibility rules; a clean installation creates a fresh environment. Imaging and unattended deployment need correct drivers, identity and licensing handling.
GPT commonly pairs with modern UEFI boot; legacy MBR has different partition/size limits. NTFS supports Windows permissions and features; exFAT supports useful cross-platform removable storage; FAT32 has a 4 GiB single-file limit. Filesystem choice depends on device/OS compatibility and required security/recovery features.
Disk Management handles volumes, partitions, drive letters and supported conversions. BitLocker protects volumes; retain the recovery key in an approved location before firmware/TPM or disk changes. Encryption protects confidentiality, not against accidental deletion or all malware while the user is signed in.
Windows Recovery Environment offers tools for startup repair and recovery. Safe Mode loads a reduced environment for diagnosis. Restore points address supported system configuration changes, not a complete user-file backup. Reset/reinstall options differ in what they retain; verify the exact option before proceeding.
Use supported installation media and verify backups through restoration. Driver architecture/version, storage controller support, insufficient space, interrupted updates and firmware settings can each block installation or boot. Do not format a disk merely because an installer cannot see it; investigate the controller/driver path first.
Choose under exam pressure
| Requirement | Choice and reason |
|---|---|
| Preserve supported apps/settings | A compatible in-place upgrade with backup. |
| Recover after a bad driver | Appropriate Safe Mode, rollback or restore/recovery tool. |
| Move large files between supported systems | Consider exFAT when its compatibility/security tradeoffs fit. |
Traps
- A restore point is not a full data backup.
- A BitLocker recovery prompt after firmware change does not necessarily mean the disk failed.
Active recall
1. FAT32’s single-file size limit?
4 GiB minus one byte.
2. What should be secured before TPM/firmware changes?
The required encryption recovery keys and a tested backup.
3. Clean install versus in-place upgrade?
Clean install starts fresh; a supported in-place upgrade preserves selected existing configuration/apps.
4. Why might an installer not see a healthy drive?
Storage controller mode or drivers may be missing/incompatible.
5. What must be checked before a reset option?
Exactly which files, applications and settings it retains or removes.