HoloLens Emulator

HoloLens Emulator
Information
Type	Software
Developer	Microsoft
Operating System	Windows; Hyper-V host required
Release Date	2016-03-30 (first-generation emulator)
Website	https://learn.microsoft.com/en-us/windows/mixed-reality/develop/advanced-concepts/using-the-hololens-emulator

Reviewed 12 October 2026. Emulator identity, archived build dates, documented simulation and deployment behavior, dated host requirements, research limitations and device-support context checked against the cited sources. About review dates.

HoloLens Emulator is Microsoft's PC development tool for testing applications for Microsoft HoloLens and Microsoft HoloLens 2 without a physical headset. It runs a HoloLens operating-system image in a Hyper-V virtual machine and supplies simulated human and environmental input. Its purpose is software development and testing, including deployment and debugging through Visual Studio, rather than measuring the experience or performance of a wearer using real hardware.

The emulator is one component of the HoloLens development toolset. Microsoft's setup documentation separately describes the Windows SDK, Visual Studio, game engines and engine-level input simulation. An emulator installation does not itself provide an application engine or replace those project dependencies.

History and versions

Microsoft announced the emulator on March 2, 2016, alongside Windows Holographic learning materials. It expected availability around the first developer headsets' shipment later that month. Contemporary TechCrunch coverage independently reported the emulator announcement and its headset-free development purpose.

The first-generation and HoloLens 2 emulator packages can be installed side by side. The archive associates builds with particular Windows Holographic releases, allowing developers to select an older environment when testing version-specific behavior.

Date	Documented milestone
March 30, 2016	Initial first-generation build 10.0.11082.1033.
November 19, 2018	Final listed first-generation build 10.0.17763.134 (Windows 10 October 2018 Update).
April 16, 2019	Initial HoloLens 2 entry 10.0.18362.1005 (Windows Holographic version 1903).
May 12, 2020	Build 10.0.19041.1103 added Windows Mixed Reality stereo viewing and motion-controller input.
October 8, 2024	Top HoloLens 2 entry as checked October 12, 2026: 10.0.22621.1402 (Windows Holographic 24H1).

Simulation and interaction

Perception Simulation supplies the emulator's input. It substitutes simulated data for live sensors while applications continue to receive input through their normal APIs. The same library can also drive a physical HoloLens for automated testing; using that library on a headset and running an operating-system image in the emulator are separate configurations.

The input controls distinguish the simulated body, head, left hand, right hand and eyes. Motion controls can change position or orientation, while modifiers select the target. This allows developers to exercise Hand tracking and Eye tracking input paths with controlled values instead of requiring a person to reproduce a particular movement.

Simulated input	Documented desktop control or behavior
Body translation	W, A, S and D control horizontal movement; Page Up and Page Down change height.
Head orientation	Holding the H modifier while dragging the mouse or using arrow keys rotates the head independently of the body.
Left or right hand	Left Alt and Right Alt target the corresponding hand. Gamepad shoulder buttons provide hand modifiers.
Eye-gaze direction	The Y modifier or the Eyes pushpin targets simulated gaze.
Hand poses	Number keys select representative closed, open, point and pinch poses. Individual joint positions are controlled through the simulation API rather than the emulator's ordinary pose controls.
Tracking mode	Controls select default, orientation-only or positional tracking, allowing different tracking states to be exercised.

Rooms and recorded input

Room recordings provide Spatial mapping meshes. Bundled examples were captured in real rooms. To display the simulated environment, an application must render its mesh; the emulator does not reproduce the headset's optical view of the physical room.

The Windows Device Portal's Simulation page can capture a room mesh as an .xef file for loading into the emulator. It also supports recording and playback of input streams. Microsoft's April 2022 documentation distinguishes the generations: recording is available on first-generation HoloLens, while HoloLens 2 supports playback of existing recordings but does not support that recording feature.

Automated tests

The Perception Simulation API exposes an IPerceptionSimulationManager and a simulated human whose head, hands and gestures can be manipulated programmatically. A test connects to its target through Windows Device Portal and can send repeatable sequences of input. Microsoft's sample explicitly distinguishes demonstrating a sequence with delays from a proper automated test, which checks the application's response before advancing.

This arrangement supports tests of application behavior under specified input, including changes in pose or gesture state. It does not make the sensor hardware itself part of an emulator test: Perception Simulation bypasses live sensors.

Host requirements and deployment

Microsoft's emulator guide, dated September 2022, lists the following host requirements. These are that guide's requirements, rather than a guarantee for every later Windows release.

Component	Listed requirement
Windows	64-bit Windows 10 Pro, Enterprise or Education; HoloLens 2 requires the October 2018 Update or later.
Processor and memory	Four CPU cores, 64-bit CPU and at least 8 GB RAM.
Virtualization	Enabled Hyper-V, hardware-assisted virtualization, SLAT and hardware-based DEP.
Graphics	DirectX 11 or later; WDDM 1.2 or later for first generation and WDDM 2.5 for HoloLens 2.

The broader tool-installation page discusses Windows 10 or Windows 11, Visual Studio 2022 and the Windows SDK. Its first-generation installation note names Visual Studio 2017 and tells Visual Studio 2022 users to deselect the bundled templates and obtain them separately from Visual Studio Marketplace. These notes concern development tooling; the host OS, emulator image and eventual headset OS are distinct parts of the setup.

First-generation hardware-accelerated emulation used RemoteFX, while HoloLens 2 emulation uses GPU-PV. Microsoft's RemoteFX vGPU notice says the component was disabled in July 2020 and removed by the April 13, 2021 security updates and later updates because of architectural security vulnerabilities. Older instructions for re-enabling that component therefore describe an obsolete graphics path.

Application architecture

Visual Studio targets the installed emulator as a deployment and debugging destination. For a Unity project, the generated Windows application solution is opened in Visual Studio. Native projects can use DirectX; the emulator is not limited to one engine.

Destination	Documented application build architecture
First-generation HoloLens Emulator	x86.
HoloLens 2 Emulator	x86 or x64.
Physical HoloLens 2	ARM or ARM64 in Microsoft's deployment guidance.

Selecting HoloLens 2 Emulator and starting debugging deploys the application to the virtual machine. An x64 emulator build is consequently a different build target from an ARM64 headset package. Visual Studio also provides profiling and graphics diagnostics for applicable targets, but Microsoft's testing guidance requires checking performance and experience on a physical headset.

Windows Device Portal can be opened through the emulator toolbar. Its documented development functions include managing application packages and processes, collecting crash dumps and viewing diagnostic information. Room/input recordings serve simulation, whereas a saved spatial mesh and exported system map are different forms of data.

Relationship to other development tools

The Windows Mixed Reality simulator was designed for PC-connected immersive headsets. Unlike the HoloLens Emulator, it runs applications in the desktop Windows user session without a virtual machine. The shared use of simulated input does not make these two tools interchangeable.

Mixed Reality Toolkit input simulation operates at another point in development: Microsoft's setup guide describes it as a way to test hand and eye interactions in Unity. It also identifies UX Tools for Unreal Engine projects. These editor tools accompany application development rather than constitute the HoloLens operating-system virtual machine.

Holographic Remoting streams content rendered on a PC to a HoloLens. The headset sends gaze, gestures, voice and spatial-mapping input to the PC, which sends rendered frames back. That workflow requires a headset for viewing and can preview editor content or run a remote application; it differs from deploying a package to a simulated HoloLens operating system.

The HoloLens 2 emulator's historical stereo mode used Windows Mixed Reality immersive headsets and motion controllers. That option depends on the desktop platform: Windows Mixed Reality, including Mixed Reality Portal, was removed from Windows 11 version 24H2. Its removal must be considered separately from the HoloLens operating system and the emulator archive.

Testing limits and research use

The emulator can exercise virtual rooms, different viewing angles and simulated user heights. Microsoft nevertheless directs developers to test on a physical HoloLens before store submission. Its test guidance covers lighting, reflective and transparent surfaces, motion, ambient noise, viewing distance, seated and standing use, battery consumption and power-state transitions. Those are real-world conditions and device behaviors that a successful emulator run alone does not validate.

A published research example is the 2019 AR-Therapist prototype. Saad Alqithami and colleagues used Unity to build a game with target and non-target balls and tested it through HoloLens Emulator. Their evaluation used simulated case-study values, and the paper left human-subject evaluation for future work. It establishes use of the emulator for prototyping, rather than evidence that the proposed treatment was effective in patients.

Documentation and support context

As checked on October 12, 2026, Microsoft's public emulator archive still publishes build links and its setup and input documentation remains readable. Its top archived HoloLens 2 build is from October 2024, while the separate device release notes list a September 2026 Windows Holographic update. The emulator archive should therefore not be used as a complete current headset-update history.

Microsoft's device release notes state that HoloLens devices were no longer manufactured as of December 2024 and that first-generation security updates and technical support ended after December 10, 2024. For HoloLens 2, the current UK PSTI statement specifies a minimum security-update period ending February 28, 2028 for units purchased through February 28, 2025. The retained November 2024 feature-release entry separately describes monthly security servicing through December 2027. These are device and operating-system provisions; they do not specify an independent support deadline for the emulator.