Use Macrium Reflect Rescue Media to Fix Windows Boot Issues  

Kari said:

Of course on a single OS system, boot menu is not used nor needed. On dual / multi boot systems it can be restored manually as shown in my last post. I wanted to avoid replies like "You don't have to export and import boot menu, you can do it manually with bcdboot and bcdedit commands or using third party software like EasyBCD".

That's why I marked parts 1. and 3. as Optional; an effort to avoid wise a** replies like that




As always, I cheated :)

There's no way to make screenshots from first phase of Windows installation (before OOBE), or from PC / Windows boot phase. You just have to "cheat" in every tutorial and / or video showing Windows setup or boot.

As a Macrium Reflect user, I always have quite recent system images available. With free Macrium viBoot tool (see TenForums viBoot tutorial) I can mount and use any Macrium system image as a Hyper-V virtual machine, allowing me to run an exact copy of my physical Windows installation in Hyper-V.

To get boot menu screenshot, I mounted my most recent system image in viBoot as a virtual machine:
Attachment 136619

Now I have a 100% identical copy of my laptop running as a VM:
Attachment 136621

To get screenshot of boot menu, I simply restart the viBoot VM and take screenshot when boot menu is shown:
Attachment 136622

Cheating is the key to good screenshots

Kari

Thanks, Kari!! It's not cheating. Rather....creative documentation!

f14tomcat said:

Thanks, Kari!! It's not cheating. Rather....creative documentation!

Actually, one of the good things about videoing a vm is that you record all the cursor movements. A lot of recording tools do not record the cursor movement on host pc.

cereberus said:

Actually, one of the good things about videoing a vm is that you record all the cursor movements. A lot of recording tools do not record the cursor movement on host pc.

I have to say my experiences have been exactly the opposite!

All screen capture tools I have used to capture video can always capture the cursor / pointer on host, but as many of my videos handle installation / customisation and such where I have to use a VM to get something captured that would normally not be possible, I have found out that only some very few screen capture tools capture the VM pointer, too. There are not many alternatives available if you want to capture pointer on VM.

I am using Microsoft Expression Encoder 4 SP2 and VSDC capture tools to make videos, only two I have found that can capture VM pointer.

Kari

Kari said:

I have to say my experiences have been exactly the opposite!

All screen capture tools I have used to capture video can always capture the cursor / pointer on host, but as many of my videos handle installation / customisation and such where I have to use a VM to get something captured that would normally not be possible, I have found out that only some very few screen capture tools capture the VM pointer, too. There are not many alternatives available if you want to capture pointer on VM.

I am using Microsoft Expression Encoder 4 SP2 and VSDC capture tools to make videos, only two I have found that can capture VM pointer.

Kari

It would be a dull world if we always agreed!

I use aimersoft video recorder.

cereberus said:

I use aimersoft video recorder.

Does it capture pointer in virtual machines?

Kari said:

Does it capture pointer in virtual machines?

Oh now I am puzzled as I always used to be able to do it iirc. Maybe grey matter is failing again - lol.

EDIT: I have come up with a cursor recording solution that I think will work with any pc or recording software using touchmousepointer. As I have never seen this posted anywhere, I think it qualifies for inclusion in the "you saw it here first" thread.

Tips and tricks - You saw it first on TenForums! Solved - Page 4 - Windows 10 Forums

dictum said:

I have a question about step 2.12 and 2.13. I am going through precisely such process. My EFI or BCD are damaged, it will not boot. I managed to boot into Windows rescue disk (PE 10 UEFI)

What happens when I click on "Finish" in 2.13, is there any possibility it will damage the data on the disk? The data is fine but either the EFI is damaged or the BCD or both.

When I run bcdedit, I get:

The boot configuration data store could not be opened.
The requested system device cannot be identified due to multiple indistinguishable devices potentially matching the identification criteria.

No - data is not affected.