Recent content by hader

That is not possible. As soon a new install is finished all programs are gone and the registry contain no formers apps info. I know of a program that moves any program to another disk and change the registry to reflect the new location. In this case? Worthless. During a new install an empty...

No. Not anymore. If the update still fails then a new install is the only solution. I ran out of idea's..... Make a backup of your complete C-disk. Use the Win11_25H2_<lang>_x64_v2.iso to start the new installation. After that the system will update itself to build 26200.8655 and then towards...

That's strange.... With those 2 scripts your DBX and SVN's should be updated. The script is invoking a scheduled task: \Microsoft\Windows\PI\Secure-boot-update Sometimes a reboot of the PC is necessary to push the changes through. Do that first!. Then run that check script again and see if the...

Yes and I responded with run those 2 scripts..... Send the check results like #101 after you have run those 2 scripts.....

@lafargeotte The information of posts 107 and 108 are to extensive. I can't make head or tails of the details to look if there is something wrong. Just send after running those 2 scripts just the result of "Check UEFI PK, KEK, DB and DBX.cmd" It will procuce a more compact overal check. That...

Don't worry. 99% are old messages. The last message is a good sign; The boot manager applied the CA2023 with succes. Those annoying 1808 message each time will disappear now. Now in some cases you will see 1x 1808, 1025, 1282 and 1041. Windows is checking on a regular bases the status of those...

It means that your certificates are all OK. The only thing that must be corrected is the DBX and the Versions of those SVN's (It says none. There must be a version number I think in your case 7.0, 3.0 and 3.0) *7.0: Maybe now 9.0* Just run "Apply 2023 KEK, DB and bootmgfw update.cmd" and "Apply...

Do you want to stay on that Build or do you want to update your system to the latest build 8737? I remember 8117. It was an OOB update because 8116 had issues. Since then MS put more effort into implementing that CA2023 certificate for security reasons. To look at the status of your machine...

Good to hear that the ESP partition has been erased and rebuild with succes. (y) Remember SFC and DISM only checks the integrity of the Windows files on the C-drive. It does not check the ESP-partition. bcdedit shows if there is something wrong. At what build are you sitting now? 26200.8737? Or...

With that "bcdboot C:\Windows /s Z: /f UEFI" command you are right. Have to be said that Z: is the drive that by using Diskpart is pointing to the made visible ESP partition. So first: diskpart list vol select vol <number_of_your_FAT32_EFI_volume. Tagged: system> assign letter=Z exit For the...

You can answer with Y. This because Windows has active processes that have access to certain files on that disk. Chkdsk can't do it job if an other proces is changing stuff. When done. You may reboot to let have windows access to this disk again. Did the C-drive checked out OK? (chkdsk. did it...

Look back. You showed error of your CBS.log file. (Thread: #53) That CBS.log file certain errors are to be seen. I mentioned that earlier: Looking at the errors that occur the most; 0xd000003a - NTSTATUS Error = Windows cannot locate a specific file, service, or driver required to...

I can't imagine that you unknowingly using a insider version. You must make a conscious decision to take part of this program. It's not intended for normal users. Running "winver" will show you the version of your installation. If it was an insider version it would show up there. If you are...

I think this because that directory does not exist. You have to make one. or there is one extra step for it; let Windows know on what disk Windows is installed with issuing bcdboot c:\windows /s c SO..... AI had it wrong. Now if I looking into this; this can not be done in normal Windows...

Looked at the CBS.log. Is litterly full with STATUS_SXS_FILE_HASH_MISMATCH error messages. "The error STATUS_SXS_FILE_HASH_MISMATCH (Code 0xC015001B) indicates that a program's actual file contents do not match the hash recorded in its installation manifest [1, 2]. This is typically caused by a...