Does not recognize dual boot (W10 22H2)

P

petrus

Member
Good afternoon, the images I created until 12/18 with the same preset, always recognized dual boot, with two partitions, where if I had a Microsoft Windows Pro, and installed the edited iso on another partition, it recognized it and me allowed entry into any

however, now, I went to redo the iso, with the same edit preset, but to generate the new version of the microsoft iso, which updated, previously it used 19045 and now it would be 3996, however, even using the same preset as the iso created on 12/18 which recognizes dual boot, now this new iso is "excluding" the already installed OS, the files are still present on the partition, however in the boot menu, two OS options do not appear, and it simply enters the system, through MSconfig, too only the current OS of disk C appears, even though the files are present in the 2nd partition,


can anybody help me?
I've already redid the process about 6 times and every time it continues to remove the dual boot, now not only in the new version 3996, but also in the 2965 version, I tested the beta version from 12/26 and the stable version from the same day, but both versions continue to generate this image that is not recognizing dual boot,

As mentioned at the beginning, the image that works with dual boot was created 12/18, so the previous version was used, but I haven't tested it using the previous version yet...

If anyone can help me I will be eternally grateful, as it is something simple and I am not able to find the error, but when this happens, it makes me waste a lot of time, having to configure the pendrive again to the original iso, to format again a partition that is already with original windows
 
Last edited:
This is the preset I use, it was the same one that created the isos that recognize dual boot on 12/18, but now when I try again unfortunately this error is happening, and for me when I'm producing the iso, I format the secondary partition to carry out tests that can only be done within the system, and not through a virtual machine, and as this is happening, it makes it impossible for me to go back to the Windows I had before to continue the modifications to the iso, and it is taking me a lot of time, I still tried about 6x redo the process with great care, I tried to use the stable version instead of the beta, but I couldn't

The only thing I didn't really try was using the old version, which was the same version used when my created isos worked with dual boot

But I think maybe it's something simple
 

Attachments

  • Salvo automaticamente f5dc68e2.xml
    40.7 KB
NTLite itself doesn't do anything to impact dual-boot, other than applying an optional disk layout in Unattended.

WinPE Setup does the actual work of trying to recognize other Windows installs, and allowing dual-boot. The only factor which has changed since last December is the latest CU requires more room in the Recovery partition. What I would do is try this preset with Dec 2023's Monthly CU, and see if the problem repeats.
 
So garlin, do you suggest going back to the previous version that I used when creating the iso that was functional?
which in this case was the only solution that I haven't tried yet, I tried the beta and stable version, from the last update on December 26th, but as mentioned, the previously created iso with functional dual boot, was on December 18th, using the previous version of ntlite, and this same preset, would you suggest going back to the previous version?

Were you able to find something in my profile that could be affecting functionality? because some points of the update seem to be attractive
 
Again, NTLite doesn't do anything with dual-boot. Dual-boot is a function of Setup.exe updating the bcdstore right before it exits.

The version of NTLite won't make a difference. The only major change is what's contained in the latest Monthly CU, or more accurately the increased size of it which tends to break undersized Recovery partitions (if you have one). Your experiment would be replacing the preset's Monthly CU with Nov 2023, instead of Jan 2024.

Another possibility is Setup.exe has already clobbered your previous dual-boot config. Then you would have to manually restore the proper settings using bcdedit, or use a 3rd-party BCD repair tool that understands dual booting.
 
just by reformatting the original windows, on the secondary partition, it already restores the settings and recognizes dual boot correctly,

but I have also used the command
"bcdedit /set {bootmgr} displaybootmenu yes"
I tried to restore the function before formatting and it didn't work

I'm sorry I don't know the terms, but by monthly, do you mean Windows updates?
So the suggestion would be that I keep version 10.0.19045.2965?
 
19045.2965 is the W10 22H2 May 2023 release. Use that version without installing the Jan 2024 Monthly Update (for Windows). The other updates are for .NET libraries and don't matter in this discussion, you can keep those.

My point is there a lot of online complaints about the Jan 2024 update breaking Windows, and that would be the only major change from 12/18 until now.
 
Now I understand, do you think the most recent "cumulative update" kb packages from January could have caused this?

So in this case, can I do the test by creating the latest Windows 10 iso? version 3996

However, without installing the "cumulative update" update kb, would that be it?
 
I come here to update that the most recent update 5034203 actually presents this error and does not recognize an already installed system

update 5034122 does not present this error
 
KB5034122 is Jan 2024 CU
KB5034203 is Jan 2024 Preview

January 23, 2024—KB5034203 (OS Build 19045.3996) Preview
This non-security update includes quality improvements. When you install this KB:
  • This update affects Unified Extensible Firmware Interface (UEFI) Secure Boot systems. It adds a renewed signing certificate to the Secure Boot DB variable. You can now opt for this change.
 
You must log in or register to reply here.
Back
Top