Reflect 7.3 (free) Boot Menu Option Fails

Win10, Ver 2004, Build 19041.572
Reflect 7.3 Build 5321

Problem: Select Boot Menu option to restore image vs. continue to Windows 10. Once selected and restore process commences (progress bar), the progress bar stops at ~1/4 the way. This has happened repeatedly at least for the last year. I haven't looked into it--easier to just to carry on and boot from USB. After occurrence/failure last week, finally time to figure out the problem.

I've had this 'unable to boot using boot menu option at least through 2 disk restores, at least 3 major Win10 updates and Macrium updates (I'm always using the most current version).

I think the only move not done is an uninstall/reinstall of Reflect. Before I do this I'm checking here so I don't waste my time going in the wrong direction.

Suggestions?

Mark

markg2 said:

...This has happened repeatedly at least for the last year. I haven't looked into it--easier to just to carry on and boot from USB. After occurrence/failure last week, finally time to figure out the problem.

I've had this 'unable to boot using boot menu option at least through 2 disk restores, at least 3 major Win10 updates and Macrium updates (I'm always using the most current version).

I think the only move not done is an uninstall/reinstall of Reflect. Before I do this I'm checking here so I don't waste my time going in the wrong direction.

As this has been going on for over a year is seems unlikely to be a bug specific to any particular version of Macrium or Windows. It seems more likely to be specific to your particular PC's hardware or bios settings. What is the make and model of your PC? (Your profile's system specs just say PC/desktop).

Which base WIM are you using, WinRE or WinPE? Open Macrium's Rescue Media Builder to check.

markg2 said:

I agree with you. I don't know how to figure out what it is about my laptop that causes boot menu to choke.

I think these shots answer your two questions?

Not quite, the make and model of the PC is relevant as it may be a bios setting for that particular PC that's causing issues.

Rather than posting the details, it's better to add them to you profile specs here: https://www.tenforums.com/profile.php?do=extra so that it's available in any of your posts.

Thanks for updating your specs. Check you bios settings, in particular Secure Boot.


Lenovo P50 manual: https://download.lenovo.com/pccbbs/m.../p50_ug_en.pdf

Please run the V2 log collector and upload results into this thread:
BSOD - Posting Instructions

How to Upload and Post Screenshots and Files at Ten Forums

As requested...

Mark

Other than problems related to a WD flash drive and one crash the logs were unremarkable.:

Code:

Event[1535]:
  Log Name: System
  Source: Microsoft-Windows-Ntfs
  Date: 2020-10-20T15:08:25.4500000Z
  Event ID: 140
  Task: N/A
  Level: Warning
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: MarkP50
  Description: 
The system failed to flush data to the transaction log. Corruption may occur in VolumeId: E:, DeviceName: \Device\HarddiskVolume6.

           Failure status: A device which does not exist was specified.

           Device GUID: {89177bc1-2b6a-ed8d-9dc1-4cc3dc6dc572}
           Device manufacturer: WD      
           Device model: My Passport 0748
           Device revision: 1019
           Device serial number: WXQ1E82JKLY8    
           Bus type: USB

           Adapter serial number:

Code:

Event[778]:
  Log Name: System
  Source: Service Control Manager
  Date: 2020-10-15T07:49:56.9010000Z
  Event ID: 7045
  Task: N/A
  Level: Information
  Opcode: N/A
  Keyword: Classic
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: MarkP50
  Description: 
A service was installed in the system.

Service Name:  Macrium Service
Service File Name:  "C:\Program Files\Macrium\Common\MacriumService.exe"
Service Type:  user mode service
Service Start Type:  auto start
Service Account:  LocalSystem

Code:

Event[780]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-General
  Date: 2020-10-15T07:53:20.7530000Z
  Event ID: 15
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: MarkP50
  Description: 
Hive \??\c:\boot\macrium\WinREFiles\mount\Windows\System32\config\SOFTWARE was reorganized with a starting size of 9879552 bytes and an ending size of 9900032 bytes.

Event[781]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-General
  Date: 2020-10-15T07:53:37.3540000Z
  Event ID: 15
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-21-2391178922-4271941177-913693387-1001
  User Name: MARKP50\mark
  Computer: MarkP50
  Description: 
Hive \??\c:\boot\macrium\WinREFiles\mount\Windows\System32\config\SYSTEM was reorganized with a starting size of 69206016 bytes and an ending size of 68825088 bytes.

Event[782]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-General
  Date: 2020-10-15T07:53:37.5170000Z
  Event ID: 15
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-21-2391178922-4271941177-913693387-1001
  User Name: MARKP50\mark
  Computer: MarkP50
  Description: 
Hive \??\c:\boot\macrium\WinREFiles\mount\Windows\System32\config\DRIVERS was reorganized with a starting size of 1650688 bytes and an ending size of 1687552 bytes.

Event[783]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-General
  Date: 2020-10-15T07:58:02.7240000Z
  Event ID: 16
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: MarkP50
  Description: 
The access history in hive \??\c:\boot\macrium\WinREFiles\mount\Windows\System32\config\default was cleared updating 1 keys and creating 1 modified pages.

Code:

Event[1418]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-General
  Date: 2020-10-17T12:02:20.1110000Z
  Event ID: 15
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: MarkP50
  Description: 
Hive \??\c:\boot\macrium\WinREFiles\mount\Windows\System32\config\SOFTWARE was reorganized with a starting size of 9879552 bytes and an ending size of 9900032 bytes.

Event[1419]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-General
  Date: 2020-10-17T12:02:31.0970000Z
  Event ID: 15
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-21-2391178922-4271941177-913693387-1001
  User Name: MARKP50\mark
  Computer: MarkP50
  Description: 
Hive \??\c:\boot\macrium\WinREFiles\mount\Windows\System32\config\SYSTEM was reorganized with a starting size of 69206016 bytes and an ending size of 68825088 bytes.

Event[1420]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-General
  Date: 2020-10-17T12:02:31.2450000Z
  Event ID: 15
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-21-2391178922-4271941177-913693387-1001
  User Name: MARKP50\mark
  Computer: MarkP50
  Description: 
Hive \??\c:\boot\macrium\WinREFiles\mount\Windows\System32\config\DRIVERS was reorganized with a starting size of 1650688 bytes and an ending size of 1687552 bytes.

Event[1421]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-General
  Date: 2020-10-17T12:05:36.7550000Z
  Event ID: 16
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: MarkP50
  Description: 
The access history in hive \??\c:\boot\macrium\WinREFiles\mount\Windows\System32\config\default was cleared updating 1 keys and creating 1 modified pages.

Disabling secure boot had no effect. The progress line stopped straight away at the same location and no further drive action. Macrium's support suggestion (only one absent paid version) was to uninstall (not disable) AV. I have trouble buying the idea vs. time to uninstall/reinstall. It seems that removing AV is the go to suggestion from any support any problem. And removing Norton in the past for other problems has never resolved.

I'm thinking completely uninstalling Reflect and reinstalling might prove more effective.

I could post whether the AV has been reported as problematic in the past with Reflect on the Norton forum absent another suggestion here.

Mark