Boot failure after chkdsk /r No bootable image found

This is the Macrium backup of users aaaaaaaaa in progress.
The detination drive is the E: drive or 4 TB drive.
A new folder was not created for the Macrium menu and it is moving to a default new folder?
There are many errors reading.
Should Microsoft Office be reinstalled and then another image created?
Will this prevent the errors or make it easier once the image is restored?
Or will the result be the same if Microsoft Office is reinstalled after the backup folder image is restored?

Using the BIOS disk sanitizer should provide a deeper clean of the drive than clean install.
HP seems to only believe in hardware HD failure and not logical drive failure.
The folder restore is an image and not a clone so any chkdsk corrections problems/fixes should be fixed by the the disk sanitizing and not reversed by the restore of an image?




There were different methods in this link:
How to make GPT volume bootable - Page 2 - Windows 10 Forums

In post # 134 there are minitool partition images.
The .chk appear to be in a different folder than the EFI folder.
They are in disk 2 partition 2 but not part of the EFI partition?
So they will remain?
Should they be deleted manually then?
Or do the commands format the whole partition?
When the boot sector is recreated how does it get integrated into the Windows operating system so that it functions smoothly? Is this by default or do other steps need to be made? For example scannow and restorehealth displayed unfixed corruption problems. What pitfalls are there in the different methods?

The Macrium backup of the users aaaaaaa completed with the errors as in the earlier post:



The browser bookmarks are ok to lose and can be restarted.

Office had been installed and was uninstalled to make sure that the servers could see that it was uninstalled and make it easier to reinstall.

Does the Windows 10 method work the same as Windows 8 (topgundcp)?
In the link he had delete everything under U:\EFI folder
The chk folder appears to be separate. Once in U if the other folder is visible the it should be able to be deleted too?

Code:

mountvol U: /s
del /s /f /q U:\efi\*.*
bcdboot c:\windows /s U: /f UEFI
mountvol U: /d

Shutdown and Reboot

1st command: UEFI firmware looks for EFI System Partition, mount it then assign the drive letter U:
(More efficient than using diskpart).
2nd command: Delete everything under U:\EFI folder
3rd command: Rebuild the BCD to boot from. NOTE: Macrium does the same thing to fix the boot problems
4th command: Unmount EFI System partition and unassign the drive letter U:

NOTE: there's a space before the forward slash (/) in each command

For the backups the most important backups are from Microsoft office file endings, tax file endings, PDF, etc.
The browsers can be reinstalled.
Once bookmarks are created and there is a failure in the future how would they be backed up if there were anticipated problems with Macrium

The EFI partition boot sector is like its own operating system? Are there any steps once it is deleted and created to have it work properly with the Windows operating system or can that be anticipated? With this drive having a corrupt operating system by scannow and restorehealth is there anything extra that may need to be done?

This is the current file explorer after the Macrium folder users aaaaaaa backup:

The Macrium backup image was made using Kyhi boot rescue.
The computer is now booted to Windows using the control + L keys.
Macrium was opened.

I've forgotten and it was earlier in the thread.

What are the steps for verification?

What are the steps for restore? Which drive are used for restore from and restore to? any drives? With these only being the users folders it does not matter? If it were the whole drive with boot and system would that cause problems? Would it need to be a clean drive or would there be problems with multiboot and other problems?

Clicking the restore tab then browse image displayed four boxes all with dates from 7/18/2018 all on F:

Navigating to E: this is what was seen:

These are the images using Kyhi boot rescue > Macrium








This is Macrium from a Windows boot:

Code:

(Gathering writer metadata...)(Waiting for the asynchronous operation to finish...)
Initialize writer metadata ...
- Get exclude files
- Enumerate components
- Get file list descriptors
- Get database descriptors
- Get log descriptors
- Get exclude files
- Enumerate components
- Get file list descriptors
- Get database descriptors
- Get log descriptors
- Get exclude files
- Enumerate components
- Get file list descriptors
- Get database descriptors
- Get log descriptors
- Get exclude files
- Enumerate components
- Get file list descriptors
- Get database descriptors
- Get log descriptors
- Get exclude files
- Enumerate components
- Get file list descriptors
- Get database descriptors
- Get log descriptors
- Get exclude files
- Enumerate components
- Get exclude files
- Enumerate components
- Get exclude files
- Enumerate components
- Get file list descriptors
- Get database descriptors
- Get log descriptors
Discover directly excluded components ...
- Excluding writer '' since it has no selected components for restore.
- Excluding writer '' since it has no selected components for restore.
- Excluding writer 'MSSearch Service Writer' since it has no selected components for restore.
- Excluding writer 'Shadow Copy Optimization Writer' since it has no selected components for restore.
Discover components that reside outside the shadow set ...
Discover all excluded components ...
Discover excluded writers ...
Discover explicitly included components ...
Verifying explicitly specified writers/components ...
Select explicitly included components ...
 * Writer 'Task Scheduler Writer':
   - Add component \TasksStore
 * Writer 'VSS Metadata Store Writer':
   - Add component \WriterMetadataStore
 * Writer 'Performance Counters Writer':
   - Add component \PerformanceCounters
 * Writer 'COM+ REGDB Writer':
   - Add component \COM+ REGDB
 * Writer 'Registry Writer':
   - Add component \Registry
 * Writer 'WMI Writer':
   - Add component \WMI
Creating shadow set {99fc589a-a903-46cc-a399-0d011045b32a} ...
- Adding volume \\?\Volume{00704c0d-3860-4dbf-9d6b-adcef9ed2178}\ [C:\] to the shadow set...
Preparing for backup ... 
(Waiting for the asynchronous operation to finish...)
(Waiting for the asynchronous operation to finish...)
Creating the shadow (DoSnapshotSet) ... 
(Waiting for the asynchronous operation to finish...)
(Waiting for the asynchronous operation to finish...)
Shadow copy set succesfully created.
Saving the backup components document ... 


List of created shadow copies: 




Querying all shadow copies with the SnapshotSetID {99fc589a-a903-46cc-a399-0d011045b32a} ...


* SNAPSHOT ID = {e568de12-0774-4203-a98c-2ae1748d1067} ...
   - Shadow copy Set: {99fc589a-a903-46cc-a399-0d011045b32a}
   - Original count of shadow copies = 1
   - Original Volume name: \\?\Volume{00704c0d-3860-4dbf-9d6b-adcef9ed2178}\ [C:\]
   - Creation Time: 9/19/2018 2:00:36 AM
   - Shadow copy device name: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy5
   - Originating machine: DESKTOP-BH9NBPV
   - Service machine: DESKTOP-BH9NBPV
   - Not Exposed
   - Provider id: {b5946137-7b9f-4925-af80-51abd60b20d5}
   - Attributes:  Auto_Release Differential

With the surprise VSS fix are there any other steps to perform before disk sanitization?
With the Kyhi boot Macrium images are there any other steps to perform before disk sanitization?