Rebuild a Student Windows PC from Documentation

Test recovery before a device failure, but do not reset a working student computer for practice.

Run a non-destructive rehearsal: inventory accounts and recovery access, restore test files to another location, clone a project into a new directory, inspect package manifests, follow setup documentation, and run verification. Record every missing dependency.

An actual Windows reset or reinstall is a separate destructive operation. It requires a real need, complete backup, BitLocker recovery access, official instructions, time, power, network access, and authorization for managed devices.

If recovery-key custody is not already verified, pause here and review BitLocker and recovery keys without regret before any reset or firmware-related change.

Define the recovery target

A rebuild should restore required capability, not reproduce every historical detail.

Record:

Required accounts and recovery:
Windows edition and management:
Important files and backup locations:
BitLocker recovery-key access:
Course applications and runtimes:
Native Windows and WSL environments:
Project repositories:
Manual settings:
Verification outcomes:
Institution IT contact:

Separate must recover, useful later, and not needed. This prevents obsolete plugins and trial software from returning automatically.

Know what each recovery source provides

Microsoft’s Windows Backup documentation describes restoration of selected folders, settings, and application references through a Microsoft account. It also notes limitations for work or school accounts.

OneDrive synchronization can make selected files available on another device, but sync is not proof that every needed file exists or that deletion can always be reversed. Verify an actual restore.

Run the safe rehearsal

Use the current PC, another authorized environment, and disposable locations.

1. Test account access

From another trusted device, verify access to:

• personal Microsoft account recovery;
• work/school account and IT contact;
• password manager or approved credential method; and
• BitLocker recovery-key location and matching key ID.

Do not copy secrets into the rehearsal note.

2. Restore one test artifact

Choose a nonprivate file. Restore it to a different temporary folder. Open it, compare expected content, and record the source, destination, date, and result.

Microsoft documents OneDrive recovery and Windows Backup behavior, but account, subscription, retention, and organizational settings affect availability.

3. Restore a project separately

Clone one repository into a new practice location. Confirm that required untracked data, environment examples, and setup instructions are available from their documented sources.

Do not reuse the already configured project environment as proof.

4. Inspect packages without applying blindly

Open the WinGet export or configuration. Confirm current package IDs, sources, course requirements, and management restrictions.

Use documented read-only validation or display operations when available. Do not batch-install merely to test a working PC.

5. Follow setup documentation

Perform only safe steps in the new project location. Record:

• unclear prerequisites;
• commands that assume the wrong directory;
• missing versions;
• private values without an approved source;
• undocumented manual settings; and
• differences between native Windows and WSL.

6. Run verification

Check tool versions, build the practice project, run tests, and confirm expected artifacts. A successful login or package installation is not the final outcome.

Produce a gap report

# Windows Recovery Rehearsal

Date:
Scope:
No reset or reinstall performed: yes

## Verified
- Account recovery:
- BitLocker-key access:
- File restore:
- Project clone:
- Package manifest:
- Setup documentation:
- Tests:

## Gaps
- Missing artifact:
- Consequence:
- Corrective action:
- Owner:
- Due date:

Fix gaps in the source system: backup configuration, setup repository, project README, or account recovery. Do not create an undocumented copy only for the rehearsal.

Actual reset or reinstall is destructive

Microsoft’s Reset your PC documentation states that reset reinstalls Windows and, depending on the selected option, can remove apps, settings, and personal files. Microsoft advises backing up important files and having the BitLocker recovery key.

Do not proceed during this article’s exercise.

For a real authorized rebuild:

1. establish the reason and owner;
2. confirm backups through restoration;
3. verify recovery keys and accounts from another device;
4. obtain institution IT approval for managed hardware;
5. preserve licenses, installers, repositories, and required data;
6. use current official device and Microsoft instructions;
7. plan adequate time, power, and network access;
8. record the chosen reset or install option;
9. restore in dependency order; and
10. run the verification suite.

An organization may require its own reimaging process. Do not remove enrollment, security controls, or recovery partitions to bypass it.

Restore in dependency order

A practical order is:

1. ownership, account access, management, encryption recovery;
2. supported Windows and updates;
3. file and backup access;
4. package manager and required applications;
5. native or WSL runtime environments;
6. project repositories and separate data;
7. configuration and credentials through approved methods;
8. build, tests, and coursework verification.

This sequence avoids configuring a project before its environment or recovering files before the correct account and encryption state are understood.

Common mistakes

• Resetting to test documentation. Rehearse non-destructively.
• Treating sync as complete backup. Restore a file.
• Assuming Git contains everything. Check untracked data and secrets.
• Treating WinGet export as a machine image. Preserve settings and data separately.
• Forgetting BitLocker access. Verify before recovery.
• Rebuilding every old tool. Restore required capability.
• Reimaging a managed device independently. Work through IT.
• Stopping after installation. Run the project verification suite.

Do this now

Start with one non-destructive restoration target, such as a disposable project environment. Expand only after the documentation reproduces and verifies that target.

Complete the rehearsal and gap report. Restore one file and one project to new locations, inspect the manifest, and run verification. Do not reset Windows.

Log what you learned

Record only:

• Result: What did the action produce?
• Evidence: What observation, test, or source supports that result?
• Next action or unresolved question: What should happen next?