Windows 10 not booting - install log location?

i was going to try a live cd/usb of some sort, but the only machine I have access to requires bitlocker for write access to a usb drive, so that's probably out. i'll see if I can find my veeam disk.
otherwise it's a reset (via PE) or image restore, yeah.
wondering if that update to an update might have played a part

- - - Updated - - -

hmm, unless I can encrypt, copy the additional files to the boot stick and decrypt again, will give that a go

- - - Updated - - -

Wondering if anyone might know why Sys Restore fails to extract AppData to AppxStaging?

1) Update the specs in the "My Computer" section:

System Specs - Fill in at Ten Forums | Tutorials
In the left corner below in your post you find 'My System Specs'.
After clicking it you can find a link a little below that says 'Update your System Spec', click on this link to get to the page where you can fill in your system specs.
System Info - See Your System Specs - Windows 7 Help Forums

Include PSU. cooler, case, peripherals and anything attached to the computer by wired or wireless (mouse, keyboard, headset, printer, xbox, USB wireless network card, etc.)



2) See if you can find this file on the computer:
C:\windows\logs\systemrestore
If it is found then zip and post a share link into the thread using one drive, drop box, or google drive.

3) What are the status of the files on the computer?

4) When the computer is powered on what do you see?

5) If you had to perform a reset save files or a reset save files equivalent would that be a viable fix?

1) done, it's a laptop and I don't think hardware is the culprit
2) latest uploaded here, as below
3) files are accessible and in place
4) an attempt to boot (boot logo loading screen), startup repair, PE
5) I am trying to avoid a reset until I can ascertain what else can be done and at least move some critical configs off the system drive

digging through the system drive, I note the following as being last modified:
- in Program Files, LaptopTools (a manual driver checker, unlikely to be the issue) and rempl (the infamous KB4023057 again, and again I feel like it might have something to do with all this)
- Windows root: bootstat (can't read it - presumably stores BCD/boot status, uploaded here and WindowsUpdate (reminder to run an EWT conversion, very helpful Msft - will need to do later)
- SysWow64, a gms log (Intel ME I think, don't see exceptions), and an ancient libusb in Drivers I installed a day before boot failure
- Sys32: some perf files in root, SRU (the db seems in place, but there is also a .chk file in the folder - not sure if it might be of any use to comb through these, I think they are essentially logs? modified an hour before boot failure)
- Temp, obviously. reminds I still have/had Acronis MMS but nothing of interest seemingly
- Prefetch - does it impact booting, or is it just logon/startup phase?
- Logs - pulled both the PE logs and Windows dir logs. Curiously SrtTrail shows last succesfull boot on 05/04, while it was actually 07/04. Dism. MeasuredBoot seems useless. There are etl traces for SystemRestore (all 10mb, latest uploaded here) and WinUpdate - I don't have NetwMonitor/Message analyser installed to view them properly, maybe someone on here could open and share the output. The DISM repair log is quite long but don't see anything familiar.

some logs from the WinPE partition, namely setupact and setuperr:

Code:

2019-04-12 22:13:50, Error                        Invalid path specified
2019-04-12 22:14:30, Error                        0x80070490 in PushButtonReset::OEMConnection::Create (base\reset\engine\cloud\src\oemconnection.cpp:57): Did not find OEM plugin [X:\sources\recovery\tools\cloudrecplugin.dll] in running OS[gle=0x00000003]
2019-04-12 22:14:30, Error                        0x80070490 in PushButtonReset::CloudConnection::Create (base\reset\engine\cloud\src\connection.cpp:60): Failed to create connection of type [1][gle=0x00000003]

diagerr also compains about cloudrecplugin.

loads of text - if anyone can point me in the direction of where I should be investigating would appreciate it, otherwise will keep looking at it until I get bored and do a reset.

- - - Updated - - -

Interestingly, scanos identifies 0 Windows installations, hm

When computer boots into Windows Recovery Environment (WinRE) environment the drive letter assign to Windows partition may not be C: drive letter because Windows 7, 8 , 8.1 and 10 creates a separate System partition when it's installed from scratch. The System partition contains boot files WinRE assigns the System partition the C: drive letter and the Windows installed partition will be assign any other drive letter usually D: drive letter is assign to Windows installed partition. The Bcdedit /enum | find "osdevice" command can be use to find out the drive letter of the Windows installed partition the output of the Bcdedit command is similar to this osdevice partition=D:. The drive letter after partition= is the drive letter of the Windows partition.

The Part2 System 99mb is your System partition.

Were you able to find this text file?
C:\windows\logs\systemrestore

The above link was not able to be opened.

Please post using one drive, drop box, or google drive.

FreeBooter, indeed that's what I thought, but it looks like none of my partitions (apart from the shadow copy link) are identified as having the OS installed - so pointing bcdedit to S: (which is what I named the System volume) did nothing.

zbook, there were no txt files in my Logs/SystemRestore, only etl traces, all of them 10,240kb. I've reuploaded the latest one here

If Windows 10 installed HDD missing a EFI System Reserved partition you can create one by following below instructions.

Please boot your computer with Windows Installation Media and from Windows Recovery Environment start the Command Prompt.

From Command Prompt execute below commands one at a time:

Code:

Diskpart

List Disk 

Select Disk 0

List Partition

Select Partition X

Shrink desired=100

Create Partition EFI

FORMAT FS=FAT32 LABEL="ESP"

Assign Letter=W

Exit

 bcdboot C:\Windows /s W: /f  ALL

Use "List Disk" command to find out disk number assign to Windows 10 installed drive.

Replace number 0 zero with disk number assign to Windows 10 installed drive

Use "List Partition" command to find out Windows 10 installed partition assigned number.

Replace X letter with Windows 10 installed partition assigned number.

You may need to replace C: drive letter with Windows 10 installed partition drive letter.

I have to warn you Diskpart tool is very dangers so please make sure to execute Diskpart command carefully.

no, I am not missing the partition (you can see I mentioned it above in my diskpart outputs), my problem is that the windows installation is not visible to the bootloader for some reason.
and I've already tried your last bcdboot command, see the bottom of my post #15