What else can I do with WinPE?

Posted at May 07, 11:03h in winpe Macrium Software, Marketing Categories: winpe, v, troubleshooting, microsoft, rescue-media

Macrium Reflect Rescue Media is a powerful tool that allows users to enter a lightweight Windows environment containing a version of Reflect. Its primary use is to restore images and fix a multitude of issues using ‘Fix Windows Boot Issues’ and ‘Macrium ReDeploy’, more information on these can be found at the knowledgebase links below:

https://knowledgebase.macrium.com/display/KNOW72/Fixing+Windows+boot+problems

https://knowledgebase.macrium.com/display/KNOW72/Re-deploying+Windows+to+new+hardware+using+Macrium+ReDeploy

However, your Rescue Media can do a lot more than this. Below are several uses for the Rescue Media you might not have considered.

Imaging without third-party interference

Macrium Reflect is susceptible to third-party interference. Macrium Reflect accesses a variety of locations on your computer when creating an image or clone. Some pieces of software will attempt to interfere with these processes. An example of this is antivirus software which, by design, will attempt to interfere with Macrium Reflect as it reads data from your disk. When booted into the Macrium Reflect Rescue Environment, no third-party software will be running, meaning that you can create images where third-party interference prevented it in Windows. Once you know third-party interference is preventing the operation of Reflect, you can begin adding exclusions where necessary.

Imaging without Volume Shadow Service (VSS)

Macrium Reflect utilises Microsoft Volume Shadow Service in order to create a backup. In a basic sense, VSS works by creating a snapshot of your computer when you launch a backup. Macrium Reflect will then create an image from that snapshot, meaning you are free to use your system while a backup takes place. More detailed information about VSS can be found at this blog post:

https://blog.macrium.com/backup-internals-what-is-vss-how-does-it-work-and-why-do-we-use-it-4e566223125a

However, issues can occasionally occur with VSS, potentially preventing you from creating an image. The Rescue Media does not use VSS, due to their being no system usage while the backup is taking place. This means you are free to take images of your computer using your Rescue Media while troubleshooting VSS further.

Troubleshooting and repairing

Since Windows PE and Windows RE include the command prompt, there are many steps you can take to troubleshoot and repair boot issues. An example of these commands is CHKDSK which checks the file system for logical and physical errors. This can be used with the /f switch to fix errors on the disk and /r to attempt to recover readable information.

Boot up logs

All systems are susceptible to boot errors, you may occasionally receive a BSoD when attempting to start Windows. This can be caused by anything from hardware issues to software conflicts:

When receiving an error like this, a .dmp file is often created in the pathway C:\Windows\Minidump, which contains information about the processes that were taking place when the system crashed. Without being able to access your Operating System, it can often be hard to view these files. Thanks to the Macrium Reflect Rescue Media, you can boot into Windows PE, get a copy of this .dmp file and provide it to a relevant computer professional to have it analysed.

File “Recovery”

Unfortunately, the steps discussed in this article may not be enough to get the system back up and running and a backup of the computer may not have been created yet. If you have ran Fix Windows Boot Problems and are still unable to boot into Windows, all is not lost. The Macrium Rescue Media includes a basic file explorer which can be used to navigate to your important files and copy them to another storage device, minimising the effects of potential data loss.

You can download a 30-Day Trial of Macrium Reflect Home, Workstation, Server, Server Plus, or Site Manager.


Previous Post

What else can I do with WinPE?

Next Post

What causes a CRC error?