Hubbry Logo
Windows Preinstallation EnvironmentWindows Preinstallation EnvironmentMain
Open search
Windows Preinstallation Environment
Community hub
Windows Preinstallation Environment
logo
7 pages, 0 posts
0 subscribers
Be the first to start a discussion here.
Be the first to start a discussion here.
Windows Preinstallation Environment
Windows Preinstallation Environment
Windows Preinstallation Environment
View on Wikipedia
from Wikipedia

Windows Preinstallation Environment
Windows PE 10.0 (based on Windows 11), showing Windows Command Prompt, Registry Editor and Windows Task Manager
DeveloperMicrosoft
Source model
Released to
manufacturing		2002; 23 years ago (2002)
Latest release10.0.26100.1 / May 22, 2024; 17 months ago (2024-05-22)
Kernel typeHybrid
LicenseFreeware
Official websitelearn.microsoft.com/windows-hardware/manufacture/desktop/winpe-intro

Windows Preinstallation Environment (also known as Windows PE and WinPE) is a lightweight version of Windows used for the deployment of PCs, workstations, and servers, or troubleshooting an operating system while it is offline. It is intended to replace MS-DOS boot disks and can be booted via USB flash drive, PXE, iPXE,[1] CD, DVD, or hard drive. Traditionally used by large corporations and OEMs (to preinstall Windows client operating systems on PCs during manufacturing), it is now widely available free of charge via Windows Assessment and Deployment Kit (WADK) (formerly Windows Automated Installation Kit (WAIK)).

Overview

[edit]

WinPE was originally intended to be used only as a pre-installation platform for deploying Microsoft Windows operating systems, specifically to replace MS-DOS in this respect. WinPE has the following uses:

  • Deployment of workstations and servers in large corporations as well as pre-installation by system builders of workstations and servers to be sold to end users.
  • Recovery platform to run 32-bit or 64-bit recovery tools such as Winternals ERD Commander (now known as Microsoft DaRT) or Windows Recovery Environment (Windows RE).
  • Platform for running third-party 32-bit or 64-bit disk cloning utilities.

The package can be used for developer testing or as a recovery CD/DVD for system administrators. Many customized WinPE boot CDs packaged with third-party applications for different uses are now available from volunteers via the Internet. The package can also be used as the base of a forensics investigation to either capture a disk image or run analysis tools without mounting any available disks and thus changing state.[2]

Version 2.0 introduced a number of improvements[3] and extended the availability of WinPE to all customers, not just corporate enterprise customers by downloading and installing Microsoft's Windows Automated Installation Kit (WAIK).

It was originally designed and built by a small team of engineers in Microsoft's Windows Deployment team, including Vijay Jayaseelan, Ryan Burkhardt, and Richard Bond.[4]

Versions

[edit]

The following versions are known to exist:

Version Description
1.0 The first release of Windows Preinstallation Environment, built from Windows XP RTM[5]
1.1 Built from Windows XP SP1[5]
1.2 Built from Windows Server 2003 RTM[5]
1.5 Built from Windows XP SP2[5]
1.6 Built from Windows Server 2003 SP1[5]
2.0[6][7] Built from the first edition of Windows Vista. This version differs from the other versions since it doesn't need the disc to load all the files.[citation needed] This means that the download is now 992 MB in size instead of 60 MB from the previous versions. It's possible to modify the default startup disc to have access to a few plug-ins like Windows Management Instrumentation, Windows Scripting Host, additional drivers and other 32-bit applications (or 64-bit applications for 64-bit versions). Other new features include the capability for a rewritable RAM disk since WinPE version 1.x only has a recordable RAM disk.
2.1[8] Built from Windows Server 2008
2.2 Built from Windows Server 2008 SP2[5]
3.0[9] Built from Windows 7 code base. It is included in WAIK 2.0.[5]
3.1[10] Built from Windows 7 SP1 code base. It is included in a WAIK supplementary update provided by Microsoft.
4.0[11] Built from Windows 8 code base. It is included in WADK for Windows 8.
5.0[12][13] Built from Windows 8.1 code base. It is included in Windows ADK for Windows 8.1.
5.1[14][13] It is an update for version 5.0 that is applied manually.[15]
10.0.10240.16384 Built from Windows 10 code base. It is included in Windows ADK for Windows 10.[16][17]
10.0.10586.0 Built from Windows 10, version 1511 code base. It is included in Windows ADK for Windows 10, version 1511.[18]
10.0.14393.0 Built from Windows 10, version 1607 code base. It is included in Windows ADK for Windows 10, version 1607.[19]
10.0.15063.0 Built from Windows 10, version 1703 code base.
10.0.16299.15 Built from Windows 10, version 1709 code base. First version supporting ARM32 and ARM64 architecture.
10.0.17134.1 Built from Windows 10, version 1803 code base.
10.0.17763.1 Built from Windows 10, version 1809 code base.
10.0.18362.1 Built from Windows 10, version 1903 code base.
10.0.19041.1 Built from Windows 10, version 2004 code base.
10.0.20348.1 Built from Windows Server 2022 code base.
10.0.22000.1 Built from Windows 11 code base. Last version supporting x86 and ARM32 architecture.
10.0.22621.1[20] Built from Windows 11, version 22H2 code base.
10.0.25398.1[21] Built from Windows Server, version 23H2 code base.
10.0.26100.1[22] Built from Windows 11, version 24H2 code base.

Derivatives

[edit]

Windows Recovery Environment

[edit]
System Recovery Options in Windows 7
Windows 11 Recovery Environment, Advanced Options section screen, showing six of the seven available options (System image recovery is shown when the "See more recovery options" button is clicked.)

Windows Recovery Environment (WinRE) is a set of tools based on Windows PE to help diagnose and recover from serious errors which may be preventing Windows from booting successfully. Windows RE is installed alongside Windows Vista and later, and may be booted from hard disks, optical media (such as an operating system installation disc) and PXE (e.g. Windows Deployment Services).[23] A copy of Windows RE is included in the installation media of the aforementioned operating systems. It is a successor to the Recovery Console.

Features

[edit]

Windows RE features include:

  • Automatic Repair: Automatically finds and fixes boot errors in the Windows Vista Startup Process caused by issues such as corruption of the following components: Boot Configuration Data, disk and file system metadata, Master Boot Record, or Windows Registry, and issues caused by missing or damaged boot and system files, incompatible drivers, or damaged hardware. Prior to Windows 8, this mode was known as "Startup Repair."[24] The executable image for Automatic Repair is startrep.exe
  • System Restore: Same as the System Restore that is included in Windows, it allows a system's settings to be restored to those of a previous state.
  • System Image Recovery: Same as the Backup and Restore component of Windows, it allows restoring a previously created disk image.
  • Windows Memory Diagnostic Tool: Analyses the computer memory (RAM) for defects (not available on Windows 8 and later). The program does not run inside WinRE, but instead reboots the system and executes memtest.exe instead of loading the operating system. memtest.exe cannot be run inside Windows.
  • Windows Command Prompt: Gives command-line access to the file system, volumes and files. It can be used to run System File Checker (sfc /scannow) against an offline Windows installation and repair missing or corrupt files. Tools like robocopy, diskpart and DISM can be used to perform various system tasks like recovering or backing up files, managing partitions, and fix servicing-related issues respectively.[25] In order to use the command prompt, the user must sign into an administrator account.

Starting with Windows Server 2012/Windows 8, the following additional options are added:

  • "Refresh" or "Reset": Both re-install Windows from a copy of the operating system on the hard drive. The "Refresh" operation maintains files, settings, and Windows Store apps (but not other programs), while "Reset" performs a factory reset of Windows, optionally formatting the hard drive and performing disk wiping.[26][27] The Reset function does not perform a full reinstall; it merely performs a factory reset from a WIM image inside a hidden recovery partition. It is possible to create a custom WIM image based on which a Reset is performed.
  • Startup Settings: Enforces a series of safe settings during the startup.

Windows 10 adds the following:

  • Restore factory settings: Allows users who upgraded to Windows 10 to revert to their original operating system. Appears as Recover from the cloud on devices whose factory settings include Windows 10.[citation needed]
  • Go back to the previous build: Windows 10 is an operating system for which Microsoft occasionally releases newer builds. In the event that installation of a new build of Windows 10 becomes problematic, this option allows the user to revert to the previous build. Only appears if the previous build's files are not deleted.

Windows 11 adds the following:

  • Quick Machine Recovery: This is a variant of Automatic Repair, with the additional capabilities of Windows Recovery Environment being able to look for boot problem solutions via Windows Update.[28] This option replaces Startup Repair if turned on, starting with 24H2, build 26100.4770. Enabled and shown by default for Windows 11 Home devices.

Volumes encrypted with Bitlocker can be mounted if a recovery key is available.

Windows Recovery Environment can also be installed to a hard drive partition by OEMs,[29] and customized with additional tools such as a separate system recovery tool for restoring the computer back to its original state.[30] As of Windows Vista SP1, users can create their own bootable CD containing the recovery environment.

REAgentC

[edit]
REAgentC
DeveloperMicrosoft
Operating systemMicrosoft Windows
TypeCommand
Websitedocs.microsoft.com/en-us/windows-hardware/manufacture/desktop/reagentc-command-line-options

Windows includes the REAgentC command which is used to configure a Windows RE boot image and a push-button reset recovery image. It allows administration of recovery options and various customizations. The REAgentC tool can either be used on an offline Windows image or on a running Windows system.[31] The command requires administrator privileges.[32]

Microsoft DaRT

[edit]
Main article: Microsoft Desktop Optimization Pack

Microsoft Diagnostics and Recovery Toolset (DaRT), sold as a part of Microsoft Desktop Optimization Pack, is yet another toolset based on Windows PE that performs diagnostic and recovery on an offline copy of Windows. It can manage files, edit Windows Registry, uninstall previously installed Windows updates, scan system for malware and restore deleted files. There is currently no Windows 11 version of Microsoft DaRT. It is currently unknown if there will be a DaRT11, or that DaRT will just stay on Windows 10.

See also

[edit]
[edit]

References

[edit]
[edit]
Revisions and contributorsEdit on WikipediaRead on Wikipedia

Windows Preinstallation Environment

View on Grokipedia
from Grokipedia
The Windows Preinstallation Environment (WinPE) is a minimal, bootable operating system developed by as a lightweight subset of Windows, designed primarily for tasks such as preparing hard drives, deploying Windows installations from local or network sources, capturing and applying system images, and performing or repairs on Windows desktop editions, , and other Windows operating systems. It operates entirely from RAM, requiring a base of 512 MB of memory, and supports essential tools like command-line interfaces, (WSH), and optional , along with Win32 APIs, Deployment Image Servicing and Management (DISM), networking protocols, file system access via DiskPart, and security features including and (TPM) support. WinPE can be booted from USB drives, CD/DVDs, ISO files, or virtual hard disks (VHDs) and is compatible with both and firmware on 32-bit, 64-bit, and architectures, though 32-bit support ended with the Windows 10 version 2004 add-on. WinPE serves as a foundational tool in Microsoft's (ADK), where it is provided as a separate add-on starting with Windows 10 version 1809, enabling IT professionals and system builders to customize and automate Windows deployments without needing a full Windows installation. Key uses include setting up storage devices before OS installation, running scripts for automated recovery, integrating with for virtual machine testing, and supporting the Microsoft Validation OS for hardware certification. However, it has built-in limitations to prevent production use, such as an automatic shutdown after 72 hours of continuous operation, lack of domain joining capabilities, and no support for (.MSI) packages or certain multimedia drivers. WinPE evolved from earlier boot environments like and has versions aligned with major Windows releases, from WinPE 1.0 (2002) to the latest for (as of 2025). Detailed version history and enhancements are covered in subsequent sections.

Introduction

Definition and Purpose

The Windows Preinstallation Environment (WinPE) is a lightweight, bootable version of Windows designed for temporary use without a full operating system installation. It functions as a minimal operating system environment tailored for specific tasks within the Windows ecosystem, such as preparing devices for OS deployment or recovery. WinPE's core purposes encompass deploying Windows operating system images, capturing and applying system images, boot issues, and executing diagnostic scripts. It enables hard drive setup prior to Windows installation, facilitates OS installation through applications or scripts accessed from network or local drives, and supports recovery efforts including OS modifications, tool configurations for recovery, and from unbootable systems. WinPE emerged as a replacement for MS-DOS-based tools, such as those included in deployment kits, offering a standardized and more capable platform for deployment and recovery workflows. It runs entirely in RAM, necessitating at least 512 MB of memory (with additional requirements for drivers or applications), and accommodates scripting via batch files, , and optional to automate tasks.

Key Characteristics

The Windows Preinstallation Environment (WinPE) is designed with a minimal footprint to facilitate rapid deployment and tasks. Its base image file (.wim) has a compact size, while requiring only 512 MB of RAM to run entirely in memory without needing a hard drive. This lightweight structure enables WinPE to efficiently as a RAM disk on compatible hardware. WinPE is built on the kernel but is heavily stripped down, excluding non-essential services and components to maintain its compactness. It includes networking capabilities, supporting TCP/IP and over TCP/IP via LAN, though additional drivers may be required for specific hardware. The default interface is a command-line environment without a full (GUI), though basic GUI elements can be incorporated if needed. It provides a subset of the Win32 API, ensuring compatibility with deployment tools and scripts that rely on standard Windows programming interfaces. WinPE supports x64 and ARM64 architectures (32-bit x86 support ended with the Windows 10 version 2004 add-on), allowing deployment across a wide range of devices from traditional PCs to ARM-based systems. It accommodates both UEFI and legacy BIOS boot modes, with the 64-bit version capable of booting UEFI or BIOS-based PCs. As the foundational environment for Windows installation, WinPE integrates as its primary imaging engine, leveraging tools like DISM for capturing and applying images during deployment. A key limitation of WinPE is its enforced runtime cap of 72 hours of continuous use, after which the shell automatically restarts to discourage prolonged operation as a general-purpose OS and align with licensing restrictions. This design choice underscores WinPE's role as a temporary environment for specialized tasks rather than a full-fledged operating .

Development History

Origins in Windows XP Era

The Windows Preinstallation Environment (WinPE) originated in 2002 as a component of the Windows XP 1 OEM Preinstallation Kit (OPK), designed to facilitate automated deployment and customization for original equipment manufacturers (OEMs) and system builders. This kit included WinPE as a lightweight bootable environment to replace older deployment methods, enabling preinstallation tasks such as applying images and configuring hardware during Windows XP setup. WinPE evolved from tools like Remote Installation Services (RIS) introduced in , which relied on a basic boot environment for network-based installations but suffered from limitations in hardware compatibility and . Automated Deployment Services (ADS) in further built on this foundation, but WinPE's inception marked a dedicated shift toward a standalone, NT-kernel-based platform for imaging and servicing. The primary motivation for this transition was to move away from -based utilities, which were becoming obsolete—Microsoft ceased licensing after 2005—and to leverage the NT kernel for superior hardware support, including 32-bit drivers and broader device compatibility. WinPE 1.0 was specifically based on the kernel (build 5.1.2600), providing a minimal 32-bit operating system for tasks like disk imaging with utilities such as RISetup.exe in conjunction with RIS servers. It supported only the x86 architecture and included core scripting capabilities via CMD, but lacked built-in networking stacks, requiring optional components or server-side updates (e.g., for RIS compatibility) to enable features like PXE or file transfers. This initial release was distributed primarily to OEMs via the OPK, with developer access available through channels to support early adoption in enterprise deployment scenarios.

Evolution from Windows Vista Onward

The evolution of the Windows Preinstallation Environment (WinPE) from onward marked a shift toward more robust deployment capabilities, aligning closely with major Windows releases and incorporating advanced imaging, architecture, and scripting features. With the release of WinPE 2.0 in 2006 alongside , significant enhancements were introduced, including the Windows Imaging Format (WIM), which enabled efficient, single-instance image capture and deployment by supporting multiple Windows editions within a compressed file structure. Native 64-bit support was also added, allowing WinPE to operate on x64 hardware for broader compatibility during installations and repairs. Subsequent versions of WinPE continued to evolve in tandem with Windows release cycles, emphasizing improved hardware integration and efficiency. WinPE 3.0, released in 2009 with , enhanced support by allowing the use of Windows 7 device drivers directly in the environment, which improved compatibility with contemporary hardware such as storage controllers and network adapters during deployment phases. This alignment facilitated smoother transitions for enterprise imaging and reduced the need for custom driver injections in many scenarios. By the time of in 2012, WinPE 4.0 incorporated support for Secure Boot, a UEFI-based security feature that verifies the integrity of boot components to prevent unauthorized code execution, ensuring WinPE could boot on modern without compromising security. It also introduced optional components to reduce the default image size, allowing administrators to customize WinPE by adding only necessary packages like networking or scripting tools, thereby optimizing boot times and resource usage on deployment media. Microsoft further advanced WinPE's role in enterprise environments through its integration with tools like the Microsoft Deployment Toolkit (MDT) and System Center Configuration Manager (SCCM, now Microsoft Endpoint Configuration Manager). These integrations enabled automated task sequences for OS deployment, where WinPE serves as the boot environment to apply images, drivers, and configurations at scale, streamlining processes in large-scale IT operations. In recent developments, WinPE has adapted to heightened security requirements in , released in 2021, by incorporating support for (TPM) 2.0 features through optional components like WinPE-SecureStartup. This allows WinPE to handle provisioning and TPM management during setup, ensuring compliance with Windows 11's mandatory hardware security standards while maintaining compatibility for deployment and recovery tasks.

Technical Architecture

Core Components and Structure

The Windows Preinstallation Environment (WinPE) is constructed from a base Windows PE image, primarily encapsulated in the boot.wim file, which includes a minimal Windows kernel (ntoskrnl.exe) and essential drivers for basic hardware support such as networking, , and mass storage. This core image provides the foundational operating system environment, stripped of unnecessary components to ensure a lightweight footprint suitable for deployment tasks. Essential components within WinPE include (setup.exe) for initiating installations, imaging tools such as DISM.exe for servicing and managing Windows images, and ImageX.exe for capturing and applying images in versions prior to Windows 8. Additionally, WinPE offers basic support for and , enabling read/write access to storage media during operations. WinPE employs a modular structure based on an optional components model introduced with , which permits the inclusion or exclusion of specific features to tailor the environment. Examples include WinPE-WMI for support in diagnostics and WinPE-Scripting for enabling automation scripts, added as cabinet (.cab) packages using tools like DISM. For runtime execution, WinPE utilizes a RAM disk implemented via ramdisk.sys to load the entire environment into memory, eliminating the need for a persistent hard drive and supporting boot from media like USB or optical discs. The core image is built and customized using the (ADK), which provides the necessary tools and add-ons for creating and modifying boot.wim. WinPE's functionality depends on the version of the underlying Windows kernel, ensuring API compatibility with the target operating system for tools and drivers.

Boot and Runtime Environment

The boot process for the Windows Preinstallation Environment (WinPE) begins with the system firmware—either or —loading the (bootmgr) from bootable media such as PXE networks, USB drives, or ISO files. The bootmgr then reads the Boot Configuration Data (BCD) store to identify and select the appropriate WinPE boot entry, initiating the loading of the operating system image. The boot stages proceed through the pre-execution environment, where winload.exe serves as the OS loader, transferring control to the kernel () and loading essential drivers into memory. Once the kernel initializes, WinPE transitions to its runtime phase, launching the default command-line shell () or a customized shell if specified via the Winpeshl.ini configuration file. This sequence ensures a minimal, RAM-based environment suitable for temporary operations. In runtime, WinPE functions within a execution context provided by the NT kernel, which handles through a lightweight set of drivers to enable basic device interaction. Administrators can inject custom drivers during the image build process using tools like Deployment Image Servicing and Management (DISM), allowing support for specialized hardware without altering the core kernel structure detailed in the Technical Architecture section. WinPE employs Event Tracing for Windows (ETW) to capture and log system events, facilitating diagnostics during its limited session. For error handling, critical failures trigger a (BSOD), with configurable support for generating memory dumps akin to those in full Windows environments through offline registry modifications.

Features and Tools

Built-in Utilities

The Windows Preinstallation Environment (WinPE) incorporates a suite of essential command-line tools in its standard image, enabling core operations for deployment and maintenance without requiring additional packages. These utilities focus on disk management, file handling, and image servicing, supporting the lightweight nature of the environment. Among the command-line tools, DiskPart provides interactive scripting for , volume management, and formatting, allowing administrators to prepare storage devices prior to Windows installation. The Format utility complements this by enabling quick or full formatting of drives in various file systems like or FAT32, essential for initializing media during setup processes. Robocopy offers advanced file copying with options for mirroring directories, handling large datasets, and resuming interrupted transfers, making it suitable for deploying files in constrained environments. For imaging utilities, the Deployment Image Servicing and Management (DISM) tool is central, supporting the capture, apply, and servicing of Windows Imaging Format (WIM) files, including mounting images for offline modifications like driver injection or package updates; it replaced the legacy ImageX utility starting with Windows Vista-based WinPE versions for enhanced compatibility and functionality. Diagnostic tools in the standard WinPE image include a limited for viewing and ending processes, though without full performance monitoring due to the minimal kernel; allows examination of system logs for troubleshooting boot or hardware issues, relying on available WMI components. Basic networking is handled via , which configures interfaces, IP settings, and firewalls when network drivers are present. WinPE supports version 5.1 via the optional WinPE-PowerShell package for scripting automation, extending beyond basic batch files to support complex cmdlets for tasks like image manipulation via DISM integration; this package requires WinPE-WMI, WinPE-NetFx, and WinPE-Scripting. Unlike full Windows installations, WinPE does not include complete applications such as Windows Explorer by default, booting instead to a command prompt to conserve resources. Hardware support in WinPE is limited to essential peripherals for operation, featuring built-in drivers for keyboards, mice, and common storage controllers (such as and USB) to facilitate input and data access during sessions; audio and printer drivers are not included in the standard image, prioritizing boot efficiency over multimedia or peripheral extensibility.

Optional Packages and Extensions

The Windows Preinstallation Environment (WinPE) supports a range of optional packages and extensions that extend its core functionality for specialized deployment, management, and diagnostic tasks. These add-ons are provided through the (ADK) and its WinPE add-on, allowing users to incorporate features not included in the minimal default image. Key examples include the WinPE-NetFx package, which provides a subset of the 4.5 for scripting and application support, though it excludes advanced components like (WPF) and COM Interop; it requires the WinPE-WMI package as a prerequisite. The WinPE-WMI package enables for system queries and diagnostics, serving as a foundation for many other extensions. Additionally, WinPE-DismCmdlets integrates Deployment Image Servicing and Management (DISM) cmdlets into , facilitating offline image servicing and requiring the WinPE-PowerShell package (along with WinPE-WMI, WinPE-NetFx, and WinPE-Scripting). WinPE also offers language packs for , including a language-neutral base and specific packs (e.g., for French or Japanese), as well as accessibility options like the WinPE-Fonts-Legacy package, which includes 32 legacy fonts, and region-specific font extensions for languages such as Japanese or Korean. Starting with the , version 24H2 ADK (version 10.1.26100.2454, released December 2024), the WinPE-HTA package has enabled support for Applications (HTA), allowing simple graphical user interfaces via scripting, provided the WinPE-Scripting package is included. In total, 37 such optional packages are available, each increasing the WinPE image size by approximately 50-200 MB, depending on the component and architecture (e.g., x64 or Arm64). For hardware compatibility in niche scenarios, WinPE integrates third-party drivers, such as those for controllers, which can be injected into the image to ensure access to specialized storage configurations during boot. However, limitations persist: WinPE does not support full Windows Store applications or modern (UWP) elements, focusing instead on lightweight, command-line oriented enhancements.

Usage Scenarios

Deployment and Installation

The Windows Preinstallation Environment (WinPE) serves as the initial boot environment during Windows Setup, enabling the application of operating system images through Setup.exe to prepare and install Windows on target devices. In this phase, WinPE loads essential drivers for hardware access, allowing Setup.exe to partition disks, apply the Windows image from installation media or a network share, and configure the system before the full operating system takes over. This lightweight environment ensures compatibility across diverse hardware by supporting cross-architecture deployments, such as using 32-bit WinPE to install 64-bit Windows editions (not supported for Windows 11). In imaging workflows, WinPE facilitates the capture of reference images from configured systems, typically using Deployment Image Servicing and Management (DISM) tools booted from WinPE media. Administrators boot a reference device into WinPE, then employ DISM commands to capture the customized Windows installation as a .wim file, incorporating add-ons for scripting and enhanced functionality during the process. These captured images are subsequently deployed to multiple target machines via tools such as (WDS) or the Microsoft Deployment Toolkit (MDT), where WinPE acts as the boot environment to apply the image over the network. WinPE supports multicast deployment for efficient distribution of images to multiple machines simultaneously, reducing network bandwidth usage in large-scale scenarios through the WinPE-WDS-Tools optional component. Additionally, it enables PXE over the network for enterprise deployments, allowing clients to load WinPE remotely via DHCP and TFTP protocols. WinPE integrates with Microsoft Endpoint Configuration Manager (formerly SCCM) for automated operating system rollouts, where custom WinPE boot images are distributed to PXE-enabled points for task sequence execution, including image application and post-install configuration. During these deployments, driver injection occurs directly in WinPE using DISM or Drvload.exe to incorporate hardware-specific drivers, ensuring the environment can access storage and network resources on target devices. Best practices for WinPE deployment emphasize pre-staging hardware drivers to mitigate compatibility issues, such as injecting only essential network, storage, and drivers into the base image to maintain its minimal footprint—typically requiring at least 512 MB of RAM—while testing for hardware-specific needs prior to rollout. This approach avoids boot failures by aligning WinPE's generic driver set with the deployment environment's requirements.

Troubleshooting and Repair

The Windows Preinstallation Environment (WinPE) serves as a recovery platform for diagnosing and repairing boot-related issues, particularly through the Bootrec.exe utility, which is accessible via the Command Prompt in the Windows Recovery Environment (WinRE), a WinPE derivative. Bootrec.exe enables targeted repairs to the (MBR), , and Boot Configuration Data (BCD) store, addressing common startup failures such as "Bootmgr is missing" errors or corrupted partition tables on both MBR and GPT disk layouts. For instance, the /FixMbr command writes a Windows-compatible MBR code to the system partition without modifying the partition table, effectively resolving MBR corruption caused by or disk errors. Similarly, /FixBoot overwrites the with a compatible version for the installed Windows edition, while /ScanOs identifies missing Windows installations and /RebuildBcd rescans all disks to reconstruct the BCD store, allowing users to add detected installations manually if needed. WinPE also facilitates system file integrity verification and disk health assessments using built-in tools like (SFC) and (CHKDSK), which operate in an offline mode to avoid interference from the main operating system. SFC, invoked as sfc /scannow /offbootdir=<drive>:\ /offwindir=<drive>:\Windows (where <drive>: is the letter assigned to the offline Windows volume in WinPE), scans protected system files against their cached versions in the component store and replaces corrupted ones from the WinPE image or installation media, helping to restore operational stability without booting the affected OS. Complementing this, examines the and metadata for logical and physical errors, with parameters like /f to fix errors and /r to locate bad sectors and recover readable information; it is particularly useful in WinPE for preemptively repairing volumes before attempting boot repairs. Note that as of 2025, WinPE drive letter assignments (e.g., C:) are persistent across sessions, which may impact recovery scripting. A key capability of WinPE for advanced troubleshooting involves offline registry editing, achieved through the reg load and reg unload commands, which mount and unmount registry hives from an unbootable Windows installation into the WinPE session's registry viewer (regedit.exe). For example, administrators can load a hive with reg load HKLM\TempHive C:\Windows\System32\config\SYSTEM to inspect or modify keys—such as disabling problematic drivers or services—then unload it with reg unload HKLM\TempHive to save changes without risking the live system; this approach simulates a safe mode environment, enabling malware removal or configuration fixes on compromised systems. Network diagnostics in WinPE leverage standard utilities like ipconfig and ping to isolate connectivity problems that may contribute to boot or recovery failures, especially in networked deployment scenarios. The ipconfig /all command displays detailed TCP/IP configuration, including IP addresses, DHCP status, and adapter details, allowing verification of network initialization during WinPE boot. Meanwhile, ping tests reachability to specific hosts or gateways (e.g., ping 8.8.8.8), confirming packet transmission and helping diagnose issues like firewall blocks or cable faults without requiring the full OS. Finally, WinPE supports data recovery from unbootable volumes by providing direct access to NTFS-formatted drives via command-line tools, enabling backup and restore operations in a controlled environment. Users can mount volumes using DiskPart, copy files to external media with xcopy or Robocopy, or capture entire images via Deployment Image Servicing and Management (DISM) for later restoration (e.g., dism /capture-image /imagefile:D:\backup.wim /capturedir:C:\ /name:"Recovery"), all while the main OS remains offline to prevent further data loss. Networking support in WinPE further allows transferring recovered data to remote servers over TCP/IP.

Versions

Pre-Windows Vista Versions

The Windows Preinstallation Environment (WinPE) prior to the redesign in consisted of a series of lightweight, 32-bit operating system versions derived from and , primarily intended for OEM deployment, scripted installations, and basic system recovery tasks. These early iterations were distributed exclusively through the OEM Preinstallation Kit (OPK) for system builders or via kits for enterprise customers, ensuring controlled access for authorized users. WinPE 1.0, released in 2001 alongside the Windows XP RTM, provided foundational support for PXE booting, CD-ROM booting, and hard drive booting via the Windows Recovery Console, enabling basic Win32 API functionality for tasks like device driver loading and simple scripting, but lacked advanced components such as .NET Framework or . Subsequent versions from WinPE 1.1 to 1.6, released between 2002 and 2005, offered incremental enhancements tied to service packs and updates, focusing on improved compatibility with deployment tools like Microsoft Systems Management Server (SMS) and early Systems Center Configuration Manager (SCCM) predecessors. WinPE 1.1, aligned with SP1, introduced support for standalone Distributed File System (DFS) roots and refined hard drive booting capabilities. WinPE 1.2, based on RTM, maintained core 32-bit architecture without major feature additions but ensured consistency for server imaging scenarios. A notable advancement came with WinPE 1.5 (also known as Windows PE 2004), released in 2004 with SP2 integration, which added (WMI) support, expanded device driver classes, rescan functionality, and integration to enhance security and automation during preinstallation. This version supported larger RAM disk sizes up to 512 MB for in-memory operations and was built from SP2 or media, further bolstering SMS/SCCM compatibility for enterprise imaging workflows. WinPE 1.6, released in 2005 with SP1, extended these features by introducing RAM disk booting and support (requiring compatible OEM ), while retaining WMI, driver enhancements, and firewall capabilities for more flexible boot options. Despite these improvements, pre-Vista WinPE versions shared significant limitations, including the absence of native Windows Imaging Format (WIM) support—introduced later in —for file-based imaging; instead, they relied on third-party tools like Norton Ghost or the built-in Automated System Recovery (ASR.exe) utility for disk imaging and restoration. All versions were strictly 32-bit only, with no 64-bit support until WinPE 2.0, and required manual integration of additional drivers for non-standard hardware. Mainstream support for these WinPE builds, aligned with , concluded on April 14, 2009.

Windows Vista to Windows 10 Versions

The Windows Preinstallation Environment (WinPE) underwent substantial enhancements from its integration with through , transitioning to a more modular, image-based that supported advanced deployment tools and scripting while maintaining a lightweight footprint for preinstallation tasks. These versions aligned directly with major Windows releases, incorporating kernel updates, optional components, and servicing mechanisms to facilitate OS installation, hardware configuration, and recovery operations. WinPE 2.0, introduced in 2006 alongside , marked a pivotal shift by adopting the Windows Imaging Format (WIM) for boot images, allowing for compressed, single-instance storage of OS files to streamline deployments. The environment utilized a minimal without the Aero visual theme, relying primarily on command-line tools, for automation, and limited Win32 subsystem support to ensure broad hardware compatibility via VESA video drivers. WinPE 2.1, released in 2008 with , extended these capabilities with refined driver injection and networking options for server-focused imaging. From WinPE 3.0 (2009, for ) through WinPE 5.0 (2013, for ), the environment emphasized scripting and management enhancements to support complex enterprise deployments. WinPE 3.0 added optional integration, enabling administrators to automate tasks like driver loading and directly in the preinstallation phase. WinPE 4.0, aligned with in 2012, introduced Deployment Image Servicing and Management (DISM) for offline image servicing and 3.0 as an optional component, alongside initial architecture support and .NET Framework 4.5 for richer application compatibility. This version also optimized the base image footprint, reducing it to approximately 150 MB to minimize boot media requirements. WinPE 5.0 for further refined networking with improved compatibility and enhanced storage tools, while renaming optional components like and .NET for consistency in the (ADK). WinPE 10.0, debuting in 2015 with , expanded architecture support to include robust ARM64 compatibility for emerging mobile and embedded devices, alongside minimal integration with Windows 10-specific APIs for deployment extensibility. Servicing evolved to tie cumulative updates directly to Windows feature releases via the ADK, such as build 10.0.19041 for the 20H2 update, ensuring WinPE remained synchronized with OS security and functionality patches. Following 's adoption of a semi-annual servicing model, WinPE shifted toward annual alignments in subsequent iterations, emphasizing optional components like enhanced and support for versatile troubleshooting and imaging scenarios.

Windows 11 and Beyond

The Windows Preinstallation Environment (WinPE) version 11.0, released in 2021 as part of the (ADK) for , is based on the initial build 10.0.22000. This version aligns closely with 's security architecture, supporting deployment to devices that meet 's mandatory hardware requirements, including (TPM) 2.0 and Secure Boot. Subsequent updates to WinPE 11.0 have enhanced its functionality, including version 11.0.22621 corresponding to version 22H2 in 2022, which introduced improved support for Virtualization-Based Security (VBS) to bolster isolation and protection during preinstallation tasks. As of November 2025, the latest servicing for WinPE is provided through the Windows ADK version 10.1.28000.1 (November 2025 release), with ongoing patches, emphasizing a shift away from legacy support toward as the standard boot mode for modern deployments. WinPE 11.0 and its updates are exclusively 64-bit architectures, eliminating 32-bit support to streamline development and reduce compatibility overhead. Additionally, optimizations for ARM64 architectures have been integrated, particularly for deploying on devices like Pro and Laptop models with processors, enabling efficient imaging and recovery on ARM-based systems. Looking ahead, WinPE continues to receive support through regular ADK updates and Long-Term Servicing Channel (LTSC) releases, with potential alignments to future Windows iterations such as the rumored Windows 12. These evolutions prioritize security and efficiency in enterprise environments.

Derivatives

Windows Recovery Environment

The Windows Recovery Environment (WinRE) is a specialized derivative of the Windows Preinstallation Environment (WinPE) tailored for diagnosing and repairing unbootable Windows installations. Introduced with Windows 7 in 2009, WinRE establishes a bootable recovery partition that leverages WinPE 3.0 or subsequent versions as its foundational operating system. This setup enables users to access recovery options without requiring external media, facilitating automated fixes for common boot failures such as corrupted system files or driver conflicts. At its core, WinRE provides essential troubleshooting capabilities, including Automatic Repair for detecting and resolving startup issues, to revert the system to a previous stable state, and a Command Prompt interface for advanced manual interventions. These functions operate through integrated scripts that prioritize consumer-oriented recovery, automatically scanning for and applying fixes like configuration repairs or diagnostics without user intervention in most cases. Unlike the base WinPE, which includes broader deployment tools such as imaging utilities, WinRE omits manual imaging options to focus exclusively on pre-configured scripts for routine repairs. Configuration of WinRE is managed via the REAgentC.exe command-line tool, which enables or disables the environment, sets the recovery image path, and verifies status. The core recovery image, winre.wim, measures approximately 500 MB and can be stored either within the install.wim file on the system partition or on a dedicated recovery partition formatted as . This partition typically requires 500-700 MB of space to accommodate the image and future updates. In , WinRE enhancements improve compatibility with Drive Encryption, ensuring recovery access even when the primary Windows partition is fully encrypted by suspending protection during boot into the environment. For systems with constrained space on the primary recovery partition—such as less than 250 MB free after image placement—WinRE updates may require resizing the partition or relocating the image to a secondary drive to maintain functionality and apply security patches. These adaptations emphasize WinRE's role in secure, space-efficient recovery for modern hardware configurations.

Microsoft Diagnostics and Recovery Toolset

The Microsoft Diagnostics and Recovery Toolset (DaRT) is an advanced collection of forensic and diagnostic utilities derived from the (WinPE), targeted at IT professionals for repairing non-booting or malfunctioning Windows systems in enterprise settings. Initially released in July 2007 as a component of the (MDOP), DaRT provides a bootable environment that operates independently of the installed operating system, enabling offline troubleshooting, , and system stabilization without risking further damage to the host OS. DaRT includes specialized tools such as Locksmith for resetting local user passwords and account locks, File Restore for recovering accidentally deleted files from volumes, Crash Analyzer for examining memory dump files to identify causes of screen errors, and for performing disk operations including surface scans to detect bad sectors. These utilities support detailed , such as event log inspection and verification, allowing administrators to isolate issues like infections, hardware failures, or configuration errors efficiently from a lightweight WinPE base. Representative examples of its application include using Crash Analyzer to pinpoint faulty drivers from a minidump file or employing File Restore to retrieve critical data prior to OS reinstallation, prioritizing minimal downtime in professional recovery scenarios. Version 10 of DaRT, released in 2015, is built on WinPE 10.0 and extends support to architectures, with extended maintenance until April 14, 2026. Distribution of DaRT has been restricted to subscribers of MDOP since its inception, with free trials discontinued after initial evaluations; post-2015, access shifted to enterprise subscriptions as MDOP components integrated into broader licensing models for volume customers. Recovery images for DaRT are generated using the DaRT Recovery Image Wizard, producing bootable ISO files or USB media that can incorporate via passwords to protect administrative tools during deployment. In enterprise deployments, DaRT integrates seamlessly with System Center Configuration Manager (SCCM) and Microsoft Deployment Toolkit (MDT) for automated creation and distribution of images, supporting remote connectivity features that enable off-site IT intervention—such as screen sharing and command execution—while focusing on non-destructive and repair without loading the affected operating system.

Customization

Building Custom Images

Building custom Windows Preinstallation Environment (WinPE) images allows users to tailor the lightweight operating system for specific hardware, scripting needs, or deployment scenarios by incorporating drivers, packages, and automated scripts. The process relies on the (ADK) and its WinPE add-on, which provide essential tools like copype.cmd for base image creation and Deployment Image Servicing and Management (DISM) for modifications. This customization ensures compatibility with target environments while minimizing the image size for efficient booting. As of November 2025, the ADK 10.1.28000.1 supports version 25H2, including updates for ARM64 architectures and Secure Boot enhancements. To begin, download and install the Windows ADK along with the WinPE add-on from the official site, selecting the appropriate architecture (typically amd64 for 64-bit systems). For support, use the latest version of the Windows ADK, such as 10.1.28000.1 (as of November 2025), which includes necessary optional components like WinPE-WMI and WinPE-SecureStartup for enhanced functionality. Launch the Deployment and Imaging Tools Environment as an administrator, then generate a base WinPE working directory using the copype.cmd script; for example, the command copype amd64 C:\WinPE_amd64 creates files including the boot.wim image in the specified path. Next, mount the WinPE image file for editing with DISM to apply customizations. Create a mount directory, such as md C:\WinPE_amd64\mount, and mount the image using Dism /Mount-Image /ImageFile:"C:\WinPE_amd64\media\sources\boot.wim" /index:1 /MountDir:"C:\WinPE_amd64\mount". Add drivers by specifying their .inf files with Dism /Add-Driver /Image:"C:\WinPE_amd64\mount" /Driver:"C:\path\to\driver.inf" /Recurse to inject them offline, ensuring hardware compatibility without rebuilding the entire image. Similarly, integrate optional packages for features like scripting or networking via Dism /Add-Package /Image:"C:\WinPE_amd64\mount" /PackagePath:"C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs\WinPE-WMI.cab". After modifications, unmount and commit changes with Dism /Unmount-Image /MountDir:"C:\WinPE_amd64\mount" /Commit. For automation, edit the startnet.cmd script located at C:\WinPE_amd64\mount\Windows\System32\startnet.cmd to include custom commands or scripts that run at , such as initializing network adapters with wpeinit or launching batch files for diagnostics. To produce bootable media, use oscdimg.exe to create an ISO file; the command oscdimg -m -o -u2 -udfver102 -bootdata:2#p0,e,bC:\WinPE_amd64\media\boot\etfsboot.com#pEF,e,bC:\WinPE_amd64\media\EFI\[Microsoft](/page/Microsoft)\Boot\efisys.bin C:\WinPE_amd64\media C:\WinPE_amd64\WinPE_amd64.iso generates a UEFI-compatible ISO. For UEFI boot support in environments requiring 2023 certificate compatibility (available in ADK versions 10.1.26100 and later, including the current 10.1.28000.1 as of November 2025), include the /bootex parameter in MakeWinPEMedia. Testing the custom image involves booting it in a like to validate functionality, such as driver loading and script execution, without risking physical hardware. Create a virtual hard disk (VHD) using diskpart for attachment, then apply the image with MakeWinPEMedia /UFD. To optimize size, remove unnecessary packages post-customization using DISM commands like Dism /Remove-Package /Image:"C:\WinPE_amd64\mount" /PackageName:WinPE-NetFx or apply component cleanup with Dism /Cleanup-Image /Image:"C:\WinPE_amd64\mount" /StartComponentCleanup /ResetBase, reducing the image from several hundred MB to under 300 MB depending on inclusions. In UEFI Secure Boot environments, custom drivers must be digitally signed by a trusted certification authority to prevent loading failures, as unsigned kernel-mode drivers are blocked to maintain system integrity. recommends using EV code signing certificates for production drivers, and testing should occur with Secure Boot disabled in the VM settings until signing is verified.

Integration with Deployment Tools

The Windows Preinstallation Environment (WinPE) integrates seamlessly with the Deployment Toolkit (MDT) to enable task sequences that automate zero-touch installations of Windows operating systems. In MDT workflows, WinPE serves as the initial environment, allowing administrators to orchestrate the deployment of operating systems, drivers, updates, and applications without manual intervention, thereby streamlining large-scale rollouts in enterprise settings. Within Microsoft Endpoint Configuration Manager (MECM, previously System Center Configuration Manager or SCCM), WinPE functions as the core boot image for Operating System Deployment (OSD) processes, facilitating network-based installations. This integration supports Preboot Execution Environment (PXE) booting for remote device access and multicast capabilities to efficiently distribute images to multiple clients simultaneously, reducing bandwidth usage during mass deployments. Windows , launched in 2017, can integrate with WinPE in scenarios like existing device reimaging to support cloud-native provisioning of Windows devices, enabling automated configuration and enrollment directly into management solutions like for . This approach allows IT administrators to preconfigure devices remotely, with WinPE handling initial hardware hash generation during certain deployment processes. WinPE also demonstrates compatibility with third-party open-source tools such as and the FOG Project through extensible scripting and PXE menu integrations. For instance, administrators can embed WinPE scripts to initiate imaging sessions or boot WinPE directly from FOG's PXE infrastructure, allowing hybrid workflows for and OS deployment across diverse hardware environments. A key best practice for WinPE integration involves matching its version to the target Windows operating system version to prevent API incompatibilities that could disrupt deployment scripts or driver loading. Using a WinPE version that aligns with or exceeds the target OS ensures optimal compatibility, as mismatches may lead to failures in system calls or feature support during installation.

References

  1. https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/winpe-intro?view=windows-11
  2. https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/whats-new-in-windows-pe-s14?view=windows-11
  3. https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/download-winpe--windows-pe?view=windows-11
  4. https://learn.microsoft.com/en-us/mem/configmgr/core/plan-design/configs/support-for-windows-adk
  5. https://archive.org/details/XP_OPK_ENU
  6. https://www.serverwatch.com/servers/deploying-windows-xp-using-the-windows-pe-page-2/
  7. https://download.microsoft.com/download/5/b/5/5b5bec17-ea71-4653-9539-204a672f11cf/windowspe_tech.doc
  8. https://www.serverwatch.com/guides/deploying-windows-server-2003-using-ads-page-2/
  9. https://www.autoitconsulting.com/site/deployment/winpe-version-list/
  10. https://download.microsoft.com/download/5/A/E/5AE5C363-E91C-401C-86A7-D817956DF629/WinXP_OPK_training_final.pdf
  11. https://download.microsoft.com/download/6/E/8/6E879EE6-F02A-40E4-99E5-8DCC7C49D28A/DeployingWindows7EssentialGuidance.pdf
  12. https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/winpe-add-packages--optional-components-reference?view=windows-11
  13. https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-10/deployment/deploy-windows-cm/create-a-task-sequence-with-configuration-manager-and-mdt
  14. https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/winpe-mount-and-customize?view=windows-11
  15. https://learn.microsoft.com/en-us/answers/questions/2188536/startup-sequence-for-windows-pe
  16. https://learn.microsoft.com/en-us/windows/deployment/configure-a-pxe-server-to-load-windows-pe
  17. https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/winpeshlini-reference-launching-an-app-when-winpe-starts?view=windows-11
  18. https://learn.microsoft.com/en-us/windows-hardware/drivers/devtest/bcdedit--set
  19. https://learn.microsoft.com/en-us/powershell/module/booteventcollector/enable-sbecbootimage?view=windowsserver2025-ps
  20. https://www.deploymentresearch.com/debugging-bsod-in-winpe/
  21. https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/deployment-image-servicing-and-management--dism--command-line-options?view=windows-11
  22. https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/dism-image-management-command-line-options-s14?view=windows-11
  23. https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/netsh
  24. https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/winpe-adding-powershell-support-to-windows-pe?view=windows-11
  25. https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/oem-deployment-of-windows-desktop-editions?view=windows-11
  26. https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/add-and-remove-drivers-to-an-offline-windows-image?view=windows-11
  27. https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/windows-setup-supported-platforms-and-cross-platform-deployments?view=windows-11
  28. https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/capture-and-apply-windows-using-a-single-wim?view=windows-11
  29. https://learn.microsoft.com/en-us/intune/configmgr/osd/get-started/manage-boot-images
  30. https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/add-and-remove-drivers-to-an-offline-windows-image
  31. https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/add-device-drivers-to-windows-during-windows-setup?view=windows-11
  32. https://support.microsoft.com/en-us/topic/use-bootrec-exe-in-the-windows-re-to-troubleshoot-startup-issues-902ebb04-daa3-4f90-579f-0fbf51f7dd5d
  33. https://learn.microsoft.com/en-us/answers/questions/5577110/trying-to-swap-drive-now-pc-is-dead-in-the-water
  34. https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/chkdsk
  35. https://learn.microsoft.com/en-us/answers/questions/2182667/in-windows-server-2025-it-appears-that-winpes-c-as
  36. https://techcommunity.microsoft.com/blog/windows-itpro-blog/windows-recovery-environment-explained/2273533
  37. https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/manufacturing-windows-engineering-guide?view=windows-11
  38. https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/ipconfig
  39. https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/ping
  40. https://learn.microsoft.com/en-us/troubleshoot/mem/configmgr/os-deployment/advanced-troubleshooting-pxe-boot
  41. https://www.datamation.com/applications/deploying-windows-xp-using-the-windows-pe/
  42. https://download.microsoft.com/documents/uk/technet/downloads/technetmagazine/issue2/36_39_get_started.pdf
  43. https://learn.microsoft.com/en-us/lifecycle/products/windows-xp
  44. https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/arm64-device-manufacturing?view=windows-11
  45. https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/winpe-create-usb-bootable-drive?view=windows-11
  46. https://learn.microsoft.com/en-us/windows-hardware/get-started/adk-install
  47. https://learn.microsoft.com/en-us/surface/surface-pro-arm-app-management
  48. https://www.ghacks.net/2025/01/31/why-microsoft-doesnt-want-to-talk-about-windows-12/
  49. https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/windows-recovery-environment--windows-re--technical-reference?view=windows-11
  50. https://download.microsoft.com/documents/rus/oem/oemradio/windows7_harddisk_recovery_quick_implementation_overview-1-1.pdf
  51. https://www.microsoft.com/en-gb/download/details.aspx?id=5188
  52. https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/windows-re-troubleshooting-features?view=windows-11
  53. https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/reagentc-command-line-options?view=windows-11
  54. https://learn.microsoft.com/en-us/troubleshoot/windows-client/windows-security/disk-partition-requirement-use-windows-re-tool
  55. https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/configure-uefigpt-based-hard-drive-partitions?view=windows-11
  56. https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/add-update-to-winre?view=windows-11
  57. https://support.microsoft.com/en-us/topic/kb5028997-instructions-to-manually-resize-your-partition-to-install-the-winre-update-400faa27-9343-461c-ada9-24c8229763bf
  58. https://news.microsoft.com/source/2007/06/04/microsoft-details-dynamic-it-strategy-at-teched-2007/
  59. https://learn.microsoft.com/en-us/microsoft-desktop-optimization-pack/
  60. https://learn.microsoft.com/en-us/microsoft-desktop-optimization-pack/dart-v10/overview-of-the-tools-in-dart-10
  61. https://learn.microsoft.com/en-us/previous-versions/windows/microsoft-desktop-optimization-pack/dart-v7/overview-of-the-tools-in-dart-70-new-ia
  62. https://learn.microsoft.com/en-us/microsoft-desktop-optimization-pack/dart-v10/diagnosing-system-failures-with-crash-analyzer-dart-10
  63. https://learn.microsoft.com/en-us/microsoft-desktop-optimization-pack/dart-v10/about-dart-10
  64. https://learn.microsoft.com/en-us/lifecycle/announcements/mdop-extended
  65. https://techcommunity.microsoft.com/blog/windows-itpro-blog/new-extended-support-dates-for-mdop-tools/837312
  66. https://learn.microsoft.com/en-us/microsoft-desktop-optimization-pack/dart-v10/creating-the-dart-10-recovery-image
  67. https://learn.microsoft.com/en-us/microsoft-desktop-optimization-pack/dart-v10/how-to-recover-remote-computers-by-using-the-dart-recovery-image-dart-10
  68. https://learn.microsoft.com/en-us/windows-hardware/get-started/what-s-new-in-kits-and-tools
  69. https://learn.microsoft.com/en-us/windows-hardware/drivers/dashboard/code-signing-reqs
  70. https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-10/deployment/deploy-windows-mdt/get-started-with-the-microsoft-deployment-toolkit
  71. https://learn.microsoft.com/en-us/intune/configmgr/mdt/use-the-mdt
  72. https://learn.microsoft.com/en-us/intune/configmgr/osd/deploy-use/use-pxe-to-deploy-windows-over-the-network
  73. https://www.prajwaldesai.com/boot-images-distribution-point-configuration-osd-sccm-2012-r2/
  74. https://learn.microsoft.com/en-us/autopilot/existing-devices
  75. https://clonezilla.org/show-live-doc-content.php?topic=clonezilla-live%252Fdoc%252F07_Customized_script_with_PXE
  76. https://forums.fogproject.org/topic/17325/basics-for-winpe-pxe-boot-using-fog
Add your contribution
Related Hubs
User Avatar
No comments yet.