Objective
Create, validate, apply, and remove a Hyper-V checkpoint safely without treating it as a backup, preferring production checkpoints and verifying AVHDX merge completion afterward.
- Never delete restore points, snapshots or repository data at random while diagnosing a backup chain.
- A green backup job is not proof of recoverability; at least one controlled restore must be tested.
- Record the current state before making a production change and keep a tested rollback path.
- Change one variable at a time. Preserve timestamps, logs and configuration evidence so the result can be explained afterward.
- Use a pilot scope whenever possible and avoid broad service restarts, policy relaxations or destructive cleanup as a first diagnostic step.
Prerequisites
- Documented protected workloads, repositories, retention and expected RPO/RTO.
- A restore target or isolated test location that cannot overwrite production data.
- Administrative access appropriate to the system being changed or diagnosed.
- A clearly identified scope: affected users, systems, addresses, services and the time of the observed problem.
- A maintenance or test window when the procedure can affect production traffic or availability.
- A copy of the current configuration or other recovery material before any irreversible action.
Step-by-step procedure
Establish the baseline and scope
Before changing anything, reproduce the issue or document the requested change on a representative system. Record the affected users or services, exact time, current configuration, recent changes and a known-good comparison point. This baseline is the reference used to decide whether each later step improves the situation.
- The scope and current state are documented well enough to reproduce or verify the procedure.
Create
Implement this requirement in a controlled scope: Create. Capture the previous value or configuration first, make the smallest change that satisfies the design, and validate the effective state rather than assuming that a saved setting is active. If the expected result is not obtained, stop, restore the previous state, and reassess before expanding the change.
- Evidence for this area is explicit, reproducible and consistent with the intended design.
Validate
Implement this requirement in a controlled scope: validate. Capture the previous value or configuration first, make the smallest change that satisfies the design, and validate the effective state rather than assuming that a saved setting is active. If the expected result is not obtained, stop, restore the previous state, and reassess before expanding the change.
- Evidence for this area is explicit, reproducible and consistent with the intended design.
Apply
Implement this requirement in a controlled scope: apply. Capture the previous value or configuration first, make the smallest change that satisfies the design, and validate the effective state rather than assuming that a saved setting is active. If the expected result is not obtained, stop, restore the previous state, and reassess before expanding the change.
- Evidence for this area is explicit, reproducible and consistent with the intended design.
Remove a Hyper-V checkpoint safely without treating it as a backup
Implement this requirement in a controlled scope: remove a Hyper-V checkpoint safely without treating it as a backup. Capture the previous value or configuration first, make the smallest change that satisfies the design, and validate the effective state rather than assuming that a saved setting is active. If the expected result is not obtained, stop, restore the previous state, and reassess before expanding the change.
- Evidence for this area is explicit, reproducible and consistent with the intended design.
Preferring production checkpoints
Implement this requirement in a controlled scope: preferring production checkpoints. Capture the previous value or configuration first, make the smallest change that satisfies the design, and validate the effective state rather than assuming that a saved setting is active. If the expected result is not obtained, stop, restore the previous state, and reassess before expanding the change.
- Evidence for this area is explicit, reproducible and consistent with the intended design.
Verifying AVHDX merge completion afterward
Implement this requirement in a controlled scope: verifying AVHDX merge completion afterward. Capture the previous value or configuration first, make the smallest change that satisfies the design, and validate the effective state rather than assuming that a saved setting is active. If the expected result is not obtained, stop, restore the previous state, and reassess before expanding the change.
- Evidence for this area is explicit, reproducible and consistent with the intended design.
Validate the complete service
Repeat the original user, system or application workflow from the real source and verify the complete result, not only one command or one local check. Confirm that logs and monitoring show the expected behavior and that no temporary debug, bypass, test account, rule or maintenance setting remains enabled.
- The end-to-end service works or the remaining failure is isolated to a clearly identified component.
Technical commands from the original procedure
These technical blocks are preserved byte-for-byte from the historical procedure and kept in their original order. Review names, addresses, paths and parameters before use.
Technical block 1
Get-VM -Name "<VM-NAME>" | Select-Object Name,State,CheckpointType,AutomaticCheckpointsEnabledTechnical block 2
Get-VMCheckpoint -VMName "<VM-NAME>"Technical block 3
Get-VMHardDiskDrive -VMName "<VM-NAME>" | Select-Object PathTechnical block 4
Get-VM -Name "<VM-NAME>" | Select-Object Path,SnapshotFileLocationTechnical block 5
Set-VM -Name "<VM-NAME>" -CheckpointType ProductionOnlyTechnical block 6
Checkpoint-VM -Name "<VM-NAME>" -SnapshotName "PRE-CHANGE-YYYYMMDD"Technical block 7
Get-VMCheckpoint -VMName "<VM-NAME>" | Select-Object Name,CreationTime,CheckpointTypeTechnical block 8
Restore-VMCheckpoint -VMName "<VM-NAME>" -Name "PRE-CHANGE-YYYYMMDD" -Confirm:$falseTechnical block 9
Remove-VMCheckpoint -VMName "<VM-NAME>" -Name "PRE-CHANGE-YYYYMMDD"Technical block 10
Get-VMCheckpoint -VMName "<VM-NAME>"Technical block 11
Get-VMHardDiskDrive -VMName "<VM-NAME>" | Select-Object ControllerType,ControllerNumber,ControllerLocation,PathValidation
The procedure is validated when:
- The original symptom or change request has been tested end to end.
- The effective configuration matches the intended design and no unexplained error remains in the relevant logs.
- Temporary troubleshooting controls have been removed and monitoring remains normal.
- The result, evidence and any follow-up action are documented.
Rollback
- Restore the configuration, policy, binding, route, credential assignment or service state recorded in the baseline when the change does not meet its success criteria.
- Remove temporary rules, test objects and diagnostic settings that were introduced only for the procedure.
- After rollback, repeat the minimum health checks to confirm that the previous service level has been restored.
Troubleshooting / common errors
- Separate source snapshot failures, transport failures, repository failures and application-consistency failures.
- If a repair requires deleting a chain, create or verify another recoverable copy first.
- If the result changes between tests, compare source, destination, identity, time and policy context before changing additional settings.
- If a command succeeds but the application still fails, continue at the next protocol or application layer instead of widening access.
- If the expected evidence is missing, verify that logging, auditing and the test path actually cover the failing component.
- If the change does not improve the measured symptom, restore the previous state and reassess the working hypothesis.
Official and vendor references preserved from the original procedure
- https://learn.microsoft.com/fr-fr/windows-server/virtualization/hyper-v/checkpoints
- https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/hyper-v-feature-compatibility-by-generation-and-guest
Adapt names, addresses, paths and parameters to your environment. Back up the configuration and test on a limited scope first.