DISKPART tried to create a Partition, has not worked

ZBook - not sure what you want me to do here:-

28) V: change the letter V to the drive letter that displays: perflogs, program files, program files (x86), users, windows, etc.)
29) cd \windows\system32\config
30) dir
31) cd..
32) exit

The following is probably wrong because of (28) :

C:\>cd \windows\system32\config

C:\Windows\System32\config>dir
Volume in drive C is OS
Volume Serial Number is 3E52-3D3B

Directory of C:\Windows\System32\config

05/23/2018 12:26 PM <DIR> .
05/23/2018 12:26 PM <DIR> ..
05/23/2018 12:18 PM 524,288 BBI
05/23/2018 01:04 PM <DIR> bbimigrate
06/10/2018 10:29 AM 28,672 BCD-Template
06/09/2018 09:19 AM 33,554,432 COMPONENTS
05/23/2018 12:30 PM 524,288 DEFAULT
06/09/2018 07:13 AM 6,029,312 DRIVERS
04/11/2018 05:04 PM 8,192 ELAM
04/11/2018 07:38 PM <DIR> Journal
05/23/2018 12:05 PM <DIR> RegBack
05/23/2018 12:30 PM 28,672 SAM
05/23/2018 12:30 PM 57,344 SECURITY
06/09/2018 12:08 PM 78,381,056 SOFTWARE
06/08/2018 04:04 PM 17,301,504 SYSTEM
04/11/2018 07:38 PM <DIR> systemprofile
05/23/2018 12:07 PM <DIR> TxR
05/22/2018 04:43 PM 8,192 userdiff
11 File(s) 136,445,952 bytes
7 Dir(s) 321,097,179,136 bytes free

C:\Windows\System32\config>cd..

C:\Windows\System32>

To me it looks like you need to run the following commands in the command prompt booted into the same Macrium Reflect USB:

diskpart
select disk 0
select part 1
delete part override
create part EFI
format FS=fat32 quick
assign letter=T
exit
bcdboot C:\Windows /s T: /f ALL
exit

Then reboot.

NOTE: make sure the C: is the actual drive letter containing the Windows files. It looks like it is. If the Windows files are on a different drive letter, change the C:\Windows to match the drive letter where they are.

The command that NavyLCDR posted: bcdboot c:\windows /s t: /f will create new boot files.
Once you boot you can backup all files to another drive or to the cloud and make a Macrium backup image.
Post number #98 displayed Windows 1607 or 14393?
Then run both of these log collectors: DM and BETA and post zips into this thread:
BSOD - Posting Instructions - Windows 10 Forums

zbook said:

The command that NavyLCDR posted: bcdboot c:\windows /s t: /f will create new boot files.
Once you boot you can backup all files to another drive or to the cloud and make a Macrium backup image.
Post number #98 displayed Windows 1607 or 14393?
Then run both of these log collectors: DM and BETA and post zips into this thread:
BSOD - Posting Instructions - Windows 10 Forums

Hi ZBook & NavyLCDR

I'll do it tomorrow. I'll do a back up before I start. In summary we are deleting 'Volume4 SYSTEM FAT32 PARTITION 260MB HEALTHY HIDDEN' and creating new boot files in C: Volume where the windows files are kept.

rebel1 said:

Hi ZBook & NavyLCDR

I'll do it tomorrow. I'll do a back up before I start. In summary we are deleting 'Volume4 SYSTEM FAT32 PARTITION 260MB HEALTHY HIDDEN' and creating new boot files in C: Volume where the windows files are kept.

No, not by my list of commands anyway. You are deleting "Volume 4 SYSTEM FAT32 Partition 260 MB Healthy Hidden", then recreating an EFI system partition in the same empty space and writing boot files to the newly created EFI system partition.

Hi NavyLCDR

O.K. got it. So the System Fat32 is not needed?

NavyLCDR said:

No, not by my list of commands anyway. You are deleting "Volume 4 SYSTEM FAT32 Partition 260 MB Healthy Hidden", then recreating an EFI system partition in the same empty space and writing boot files to the newly created EFI system partition.

The Macrium repair boot had failed.
It is unclear which steps it makes or does not make in its repair algorithm.
If anyone knows the steps that it makes please post.
Volume 4 or partition 1 is hidden ( Fat32 system).
It could be assigned a drive letter and is then no longer hidden.
Once it is no longer hidden commands can be run to repair the drive files on the partition (bcdedit /fixboot, bcdedit /rebuildbcd, etc.)
If the repairs fail then the EFI partition can be replaced with new drive files.
Alternatively the repairs can be skipped and the EFI partition can be replaced with new drive files.

Please comment on the Windows version and build: 1607 or 14393
What had happened with prior upgrades?

zbook said:

The Macrium repair boot had failed.
It is unclear which steps it makes or does not make in its repair algorithm.
If anyone knows the steps that it makes please post.
Volume 4 or partition 1 is hidden ( Fat32 system).
It could be assigned a drive letter and is then no longer hidden.
Once it is no longer hidden commands can be run to repair the drive files on the partition (bcdedit /fixboot, bcdedit /rebuildbcd, etc.)
If the repairs fail then the EFI partition can be replaced with new drive files.
Alternatively the repairs can be skipped and the EFI partition can be replaced with new drive files.

Please comment on the Windows version and build: 1607 or 14393
What had happened with prior upgrades?

Hi ZBook, I honestly don't know regards Windows version and build. I know there was an update in April 2018. I thought that had completed successfully early May. But in late May it again carried out the same update. This caused the 0xc0000017 error. I've posted a screenshot on this thread. I have AVAST security installed. When the laptop wouldn't boot, I called ASUS technical helpdesk; they said it was down to the April 2018 windows update. But then the April 2018 has been a huge issue for many users - so possibly convenient. But at the command prompt; [Version 10.0.14393] comes up.

What's new in Windows 10, version 1607 (Windows 10) | Microsoft Docs

Avast Confirms Windows 10 April 2018 Update Bug, Releases Fix