# Choose Hyper-V import identity and running-file locations

> When should an imported virtual machine keep its identity or receive a new one?

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260908-248-choose-hyper-v-import-identity-and-running-file-locations/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-08T18:13:03+00:00
- Modified: 2026-09-08T18:29:34+00:00
- Last reviewed by DSE: 2026-09-08
- Resource type: Guide
- DSE priority: Information
- Topics: Business Continuity, IT
- Reading time: 1 minutes

## What you need to know

When should an imported virtual machine keep its identity or receive a new one?

## Potentially affected

Operators importing exported Hyper-V virtual machines into a host.

## DSE recommendation

Write down the intended identity relationship between the original and imported machine, along with the final configuration and disk locations.

## Article

## Source facts

Registering a virtual machine in place preserves its identity and turns the export location into its running-file location. The copy import option lets the operator choose a file location and assigns a new virtual-machine identity, allowing repeated imports to the same host. [Microsoft Learn](https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/deploy/Export-and-import-virtual-machines).

## Applicability

Decide whether the request is to register an existing workload or create a separate copy before choosing the import type. Identify any already-registered instance. Treat the export directory as potentially live storage until the selected import behavior is understood.

## DSE recommendation

Write down the intended identity relationship between the original and imported machine, along with the final configuration and disk locations. Keep the source export under change control while the choice is reviewed. For a separate test copy, plan its network isolation and application identity handling with the workload owner. Do not remove an existing registration merely to clear an import error without that owner’s approval.

## Verification

Inspect the imported machine identifier and all attached disk paths before starting it. Confirm that the running-file locations match the chosen import type. Mark any export directory now serving as live storage so it is not cleaned up as disposable transfer material. Start the workload only in its approved network context.

## Official references

[Microsoft Learn: Export and import virtual machines](https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/deploy/Export-and-import-virtual-machines). Source reviewed September 8, 2026.

## Primary reference

- Name: Export and import virtual machines
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/deploy/Export-and-import-virtual-machines
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Choose Hyper-V import identity and running-file locations,” DSE Security, https://update.dsesecurity.com/updates/dse-20260908-248-choose-hyper-v-import-identity-and-running-file-locations/
Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/
Usage and citation policy: https://update.dsesecurity.com/usage/
Copyright © 2026 Detection Systems & Engineering. All rights reserved.