How to use Windows Recovery Environment

Introduction

It’s frustrating when a Windows operating system fails to boot or restarts unexpectedly. Maybe the problem is a corrupted disk or missing files, or maybe you just can’t be sure. 

Regardless, the option to use Windows Recovery Environment (also known as WinER or Windows RE) is always available. WinRE executes commands that may resolve these problems and return the operating system to working order. 

Tools that can be found in WinRE include:

  • Troubleshooting and automatic repair tools to automate common diagnostic and repair tasks
  • Push-button reset, which enables quick repair without losing important data and customizations. This tool is only available for Windows 10 desktop editions, Windows 8.1 and Windows 8
  • System image recovery, which enables restoration of the entire hard drive from a system image that contains Windows and system settings, programs and files

To resolve common issues that might be causing system failure, use the following steps:

Step 1: Open Windows Recovery Environment

WinRE will launch automatically in any of the following scenarios:

  • After two consecutive failed attempts to start Windows
  • After two consecutive shutdowns occur unexpectedly within two minutes of boot completion
  • After two consecutive system reboots occur within two minutes of boot completion
  • When a Secure Boot error occurs (except for issues associated with Bootmgr.efi)
  • When a BitLocker error occurs (touch-only devices)

If WinRE does not launch automatically, you can access it through the Boot Options menu, which can be launched in any of the following ways:

  • Stuck on the login screen? Click on the Shutdown button and select Restart while holding down the Shift key
  • In Windows 10, select Start → Settings → Update & Security → Recovery and then select Restart now under Advanced startup
  • Boot with recovery media
  • Use a hardware recovery button

Once in (Read more...)

*** This is a Security Bloggers Network syndicated blog from Infosec Resources authored by Dan Virgillito. Read the original post at: http://feedproxy.google.com/~r/infosecResources/~3/U2Aa8zynDa4/