From a5d3a06bc24c44af288066cda523d5f878a3aab9 Mon Sep 17 00:00:00 2001 From: he3als <65787561+he3als@users.noreply.github.com> Date: Sun, 7 Jul 2024 12:40:51 +0100 Subject: [PATCH] feat(vm snapshots): clarify no updates, download links --- docs/contributing/playbook.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/contributing/playbook.md b/docs/contributing/playbook.md index 01f41024..cbcb6678 100644 --- a/docs/contributing/playbook.md +++ b/docs/contributing/playbook.md @@ -89,13 +89,13 @@ Additionally, you can save a VM while testing something specific and return to i ### Which snapshots to make !!! tip "Setup your snapshots ready for a Playbook" - It's best to make your initial snapshots already set up with AME Wizard and some essential utilities (e.g. [Sysinternals](https://learn.microsoft.com/sysinternals/)) so that you can just drag-and-drop a Playbook as soon as you go to a snapshot. + It's best to make your initial snapshots already set up with [AME Wizard](https://download.ameliorated.io/AME%20Wizard%20Beta.zip) and some essential utilities (e.g. [Sysinternals](https://learn.microsoft.com/sysinternals/downloads/)) so that you can just drag-and-drop a Playbook as soon as you go to a snapshot. We recommend making three initial snapshots: - Stock Windows **without** Windows Updates installed - - For testing updates after installing Atlas - - To ensure updates don't install, [pause updates indefinitely](../assets/other/pause-updates.reg) before connecting to the internet + - For testing installing Windows Updates after installing Atlas + - To ensure updates don't install, [pause updates indefinitely](../assets/other/pause-updates.reg) before connecting to the internet. Un-pause them later in Windows Settings - Stock Windows **with** Windows Updates installed - Consider updating Windows and remaking the snapshot every so often - **Optional:** A current release Atlas snapshot if you need to test anything there