Windows Preinstallation Environment

From Infogalactic: the planetary knowledge core
(Redirected from Windows PE)
Jump to: navigation, search
Windows Preinstallation Environment
Windows PE screenshot.png
Developer Microsoft
Written in {{#property:p277}}
Source model Shared source
Latest release 10.1.10586
Kernel type Hybrid
License Freeware
Official website {{#property:P856}}

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-ROM, or hard disk. 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 the Windows Automated Installation Kit (WAIK).

Overview

WinPE was originally intended to be used only as a pre-installation platform for deploying Microsoft Windows operating systems, specifically to replace 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 or the 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

The following versions are known to exist:

Version Description
1.0 The first release of Windows Preinstallation Environment
1.1 Built from Windows XP Professional with Service Pack 1
1.2 Built from Windows Server 2003 family
1.5 Called Windows PE 2004; built from Windows XP Professional with Service Pack 2
1.6 Called Windows PE 2005; built from Windows Server 2003 with Service Pack 1
2.0[5] 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[6] Built from Windows Server 2008
2.2 Built from Windows Server 2008 SP2
3.0 Built from Windows 7 code base. It is included in WAIK 2.0.
3.1[7] Built from Windows 7 SP1 code base. It is included in Windows Automated Installation Kit (AIK) Supplement for Windows 7 SP1.
4.0[8] Built from Windows 8 code base. It is included in Windows ADK for Windows 8.0.
5.0[9] Built from Windows 8.1 code base. It is included in Windows ADK for Windows 8.1.
5.1[9] It is an update for version 5.0 that is applied manually.[10]
10.0.10240.16384 Has the same version number as Windows 10, as part of Microsoft's "One Windows" policy. It is included in Windows ADK (Windows Kits 10).[11][12]
10.0.10586.0 Has the same version number as Windows 10 version 1511, as part of Microsoft's "One Windows" policy. It is included in Windows ADK (Windows Kits 10.1).[13]

Derivatives

Windows Recovery Environment

Windows 8 Recovery Environment, Advanced Options section, showing four of the six available options

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 installed along Windows Vista, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8 and Windows Server 2012 and may be booted from hard disks, optical media (such as an operating system installation disc) and PXE (e.g. Windows Deployment Services).[14] A copy of Windows RE is included in the installation media of the aforementioned operating systems. It is a successor to Recovery Console.

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."[15] 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: Restores the entire system to a previous state by restoring a disk image created by Backup and Restore component of Windows. In Windows Vista, it was known as "Complete PC Restore".
  • Windows Memory Diagnostic Tool: Analyses the computer memory (RAM) for defects (not available on Windows 8). The program will not run inside WinRE, but instead reboot the system and execute memtest.exe prior to loading the operating system. The memtest.exe program cannot be run inside of Windows; it is not accessible within Win32 mode.
  • 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.[16] In order to use the command prompt, you must sign in to an administrator account.

In Windows Server 2012 and Windows 8, "Refresh" or "Reset" options are also available, both of which 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 desktop applications), while "Reset" performs a factory reset of Windows, optionally formatting the hard drive and perform disk wiping.[17][18] The Reset function does not perform a full reinstall; it merely performs a factory reset from a WIM image inside a hidden recovery partition. With this method, you can create a custom WIM image to perform a Reset on.

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

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

Microsoft DaRT

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

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.

See also

Concept
Related software

References

  1. Lua error in package.lua at line 80: module 'strict' not found.
  2. Lua error in package.lua at line 80: module 'strict' not found.
  3. Lua error in package.lua at line 80: module 'strict' not found.
  4. Lua error in package.lua at line 80: module 'strict' not found.
  5. Lua error in package.lua at line 80: module 'strict' not found.
  6. Lua error in package.lua at line 80: module 'strict' not found.
  7. Lua error in package.lua at line 80: module 'strict' not found.
  8. Lua error in package.lua at line 80: module 'strict' not found.
  9. 9.0 9.1 Lua error in package.lua at line 80: module 'strict' not found.
  10. Lua error in package.lua at line 80: module 'strict' not found.
  11. Lua error in package.lua at line 80: module 'strict' not found.
  12. Lua error in package.lua at line 80: module 'strict' not found.
  13. Lua error in package.lua at line 80: module 'strict' not found.
  14. Lua error in package.lua at line 80: module 'strict' not found.
  15. Lua error in package.lua at line 80: module 'strict' not found.
  16. The coolest new DISM command (to me at least)
  17. Lua error in package.lua at line 80: module 'strict' not found.
  18. Lua error in package.lua at line 80: module 'strict' not found.
  19. Lua error in package.lua at line 80: module 'strict' not found.
  20. Lua error in package.lua at line 80: module 'strict' not found.

External links