WinNTSetup v5.4.2

[abbodi1406]

External report

https://forums.mydigitallife.net/threads/is-anyone-here-has-msfn-org-account-or-knows-how-to-contact-jfx.90161/

[Antonino]

I saw what u posted, and I think it might be some bad timing in the permission system, or just the fact that some files or folders are not "allowed" at any time during the basic automation process. what u can do is write a folder-copying script and place it in the last hatch as a .bat file , before the installation ends. if it does not copy the whole directory, do it yourself by launching that bat file before rebooting.  it is not a solution, but u can try it as a remedy for the time being.

and if it is a copy session instead of an install session, for that matter, u can launch the folder-copying script just the same. i hope it will do the job.

Edited March 14 by Antonino

[click-click]

WinNTSetup no longer lets me update the BCD for UEFI when only selecting Boot drive and Install drive. I am getting msg below after applying setup.

It will update the BIOS BCD, but not for UEFI one. I can boot all entries listed in the UEFI BCD in the classic boot menu. I haven't tried to change anything in the bcd for a while, so I don't know if any patch-tuesdays may have screwed things up. Bootice shows the active BCD without problems and I made a few name changes with it for the boot menu which worked fine.

@JFX or anyone else, I need your expertise  as to what I can try to fix this

Edited March 21 by click-click

[click-click]

Here is a recent log file compared to an older one from 25-01 

Creating boot files with BCDBoot.exe: Z:\Windows /s Y: /f UEFI
bcdboot version: 10.0.26100.1 (WinBuild.160101.0800)
bcdboot cmdline: Z:\Windows /s Y: /f UEFI
bcdboot Return : -2146885629

Failure when attempting to copy boot files.

Previously

Creating boot files with BCDBoot.exe: Z:\Windows /s Y: /l en-US /f UEFI
bcdboot version: 10.0.22621.3880 (WinBuild.160101.0800)
bcdboot cmdline: Z:\Windows /s Y: /l en-US /f UEFI
bcdboot Return : 0

Boot files successfully created.

 

Edited March 22 by click-click

[click-click]

I assigned  the ESP partition  a drive letter so I could run the bcdboot from a command line intsead of with WinNTSetup and I got the same error:

C:\>bcdboot Z:\Windows /s S: /l en-US /f UEFI /v
BFSVC: ServiceBootFiles MuiOnly:n Res:y Fonts:y BootMgrOvw:n BootStatOvw:n DbgTrn:y SuspendBDE:n Offline:n
BFSVC: Using EX bins because bootmgfw on ESP is 2023 already.
BFSVC Error: WinVerifyTrust failed. Error code = 0x80092003
BFSVC Error: ServicingBootFiles failed. Error = 0x80092003
Failure when attempting to copy boot files.

Seems like bcdboot will fail if the boot files from the EFI partition are newer than what is in the source ?\Windows

Edited March 22 by click-click

[JFX]

18 hours ago, click-click said:

Seems like bcdboot will fail if the boot files from the EFI partition are newer than what is in the source ?\Windows

Maybe, but if WinVerifyTrust fails, i would guess that your HostOS is very old.

[click-click]

I run WinNTSetup on updated Win10 LTSC and W11 systems and use it to install, fix mount points, or add new systems to the BCD. I noticed an entry in the BCD that was not showing in the boot menu so I tried to add the entry again with WinNTSetup, but got the error. All of my local up-to-date systems where I tried this showed the same error. I then booted and used an 1809 LTSC VHDx from 2023-12 which did not give me an error. I deleted the old entry with bootice and the newly added entry now shows in the boot menu.

I don't have a clue as to what was going on, or fully understand how bcdboot decides what to do. I ran the same command mentioned in my previous post and this time bcdboot had completely different verbose messages indicating Boot files successfully created. No WinVerifyTrust this time and I must wonder if any files actually get copied/replaced in the EFI partition when the stuff in z:\Windows is older.

My guess is the missing boot menu entry for the system in the BCD was an indication of some type of corruption that was causing the error, even though booting the rest was not a problem.

 

c:\>bcdboot Z:\Windows /s S: /l en-US /f UEFI /v
BFSVC: ServiceBootFiles MuiOnly:n Res:y Fonts:y BootMgrOvw:n BootStatOvw:n DbgTrn:y SuspendBDE:n BootEx:y Offl
ine:n
BFSVC: Using EX bins because bootmgfw on ESP is 2023 already.
BFSVC Warning: EX boot manager source file Z:\Windows\boot\EFI_EX\bootmgfw_EX.efi does not exist, failing grac
efully to avoid block servicing.
BFSVC: BfsInitializeBcdStore flags(0x0000021c) RetainElementData:n DelExistinObject:n
BFSVC: VolumePathName for Z:\Windows is Z:\
BFSVC: SystemRoot is \Windows
BFSVC: Opening template from \Device\HarddiskVolume13\Windows\System32\config\BCD-Template.
BFSVC: Opening store from \Device\HarddiskVolume1\EFI\Microsoft\Boot\BCD
BFSVC: Creating General objects.
BFSVC: Creating Resume object.
BFSVC: Creating MemTest object.
BFSVC: Creating OsLoader object.
BFSVC: OsLoader identifier: {04924720-269c-11f1-8157-dd48fe8b5d84}
BFSVC: Removing duplicate entries.
BFSVC: Create BOOTMGR object RetainBootDefault:n
BFSVC: Setting {default} to {04924720-269c-11f1-8157-dd48fe8b5d84}
BFSVC: Cleaning up debugger settings.
BFSVC: Cleaning up hypervisor settings.
BFSVC: Opening recovery store from \Device\HarddiskVolume1\EFI\Microsoft\Recovery\BCD
BFSVC: Creating General objects.
BFSVC: Create BOOTMGR object RetainBootDefault:y
BFSVC: Setting {default} to {5ae80ebc-b03e-11f0-ad44-b5dd86473841}
Boot files successfully created.

 

Edited March 23 by click-click