Search results

Finally i tried every possible combination. I enabled combatibility - manual setup an i removed only 1. custom update cleanup 2. winsxs backup 3. component store In every iso of the three upgrade was broken. I think that something in ntlite in combination with latest windows 24h2 is breaking...

Its no big deal. I like testing. Btw i tested 26100.1742, 26100.2314, 26100.2448, 26100.2454, 26100.2605 an the problem remains. I will try with 26100.2605 and an older ntlite version to see if something changed in ntlite. P.S.1 Used ntlite 2024-9-10073 with windows 26100.2605 and the problem...

Hi. I produced the following iso's with the 26100.2605 version 1. Only my above preset, iso size 2.67gb and in-place upgrade works fine 2. My preset + updates custom cleanup, 2.55gb iso ugrade broken 3. My preset + updates cleanup + winsxs backup, 2.49gb upgrade broken 4. My preset + updates...

Ok, i will fo the test you propose. In the next 2 days i will also find the windows version that started the problem. Regarless if you can remove store and database it contributes even more to the final size. We will be in touch.

Ok. Thank you very very much for the immediate response. I await news from you.

Without being absolutely sure i think that it worked for windows 24h2 26100.2448 and it stopped working for 26100.2454. For 26100.2454 i produced the iso with the same preset but the upgrade was broken. The ntlite version was the same so perhaps something changed in the iso. I am not sure i say...

Thank you. For me personally it would be a big deal if even removing only store + component didn't break the upgrade like it does now. Perhaps even when you choose to remove only these two it removes files that it should not so the upgrade is broken. I repeat that removing them (only the two or...

Also i say again that in an untouched iso you remove only store + component the iso is more than 1gb smaller and it also breaks in-place upgrade. So its not something in my preset i think.

I already disable servicing stack compatibility. If i keep store+database it results a 2.8gb iso (esd compression). If i don't keep store + database it results a 2.25gb iso. Its a huge difference for me and it worked a few weeks ago. Now as i said it breaks the in-place upgrade.

If you remove any of them it breaks the upgrade. Component store is crusial because the resulted iso size difference is huge.

Hi. Its very strange that for the last month approximately cleaning winsxs component database breaks in-place upgrade. The pc restarts but after the that at around 9% it restarts and undoes all the changes it made. This happens even if i remove only the winsxs component.