The same thing happened to me, I deleted and formatted the SSD. Then a new installation was carried out and it was a windows.old on C with no content.
about windows.old https://forums.mydigitallife.net/th...build-25941-preview.88019/page-8#post-1831020
If you're following this thread then you'd know that I am not the only one saying/experiencing this same. And about the reason, it's a bug that needs to be addressed via future LCU.
Hello Friends: Have any of you installed the 24h2 version on an older PC? Thanks in advance for your response. Regards! TecMan
My display priority and refresh rate are reset after each reboot with any NVidia drivers. So far that is the only bug I have. Does know how to resolve mentioned display/monitor issue? I tried disabling NVidia Display Container, but that didn't fix anything.
I have a 13 years old PC ( i5-2410M CPU), MBR Upgraded by inplace intallation from 23H2 to 24H2 enterprise edition created by uupdump.
The CUs do not update the Apps, it is therefore MS which modifies certain Apps directly in the ISO ? For example, with the 26100.1 ISO (UUP) : Same thing with an integrated CU With 26100.560 ISO (MS website) Just know out of curiosity Thanks
uup-converter integrates apps differently, by default it integrates stub versions to the client editions and full apps to the server editions also it integrates bundles instead of individual apps in MSFT ISO some apps are in stub versions and others are full sometimes they do update uup sets (for example, devhome for build 22631 was updated a ton of times), but 99% of apps get no updates at all in uup sets and ISO so always use the latest retail build for your base one as a reference 26100.560 uup set should contain all the apps available in 26100.560 MSFT ISO in terms of versions at the end it's the same thing, don't think about it
Ok thanks for the explanation, I always use the same ISO, where I integrate the CUs (never use WU or the Store on one of my PCs) I wonder if I will keep 26100.1 (as I have done so far for all versions of Windows) or keep 26100.560, I will see
If you do clean installs and update manually, there is little point in using anything else than .1, because it is reliable enough as clean base. If you do upgrades from a later updated previous version of the OS, then things change a lot.
@Windows_Addict Where can I find those files? Code: 26100.1.240331-1435.ge_release_arm64fre_CLIENT_LOF_PACKAGES_OEM.iso MD5: 090ced977d2eee90630be94117fbce5b SHA-1: dccf504be46f1d10d9181ca78d6574ef86fee88f SHA-256: cce90237f1dcb00840ca1a279b1f075a1df29787afa5a516b13db716fc6481fa 26100.1.240331-1435.ge_release_amd64fre_RDX_amd64fre_MULTI.iso MD5: 14f61e948978e2b08212a01b13b81b35 SHA-1: de9f2befd5861a4a6c718105feec4ab09680f648 SHA-256: a905dbe74edee3b024d4a3515ef1bfab3649e8f07564d92882caa9a6394bc760 26100.1.240331-1435.ge_release_arm64fre_RDX_arm64fre_MULTI.iso MD5: b16bb1f67a5e966bc3936d8dcf2d42d0 SHA-1: 8e7265af1b6339dc4cb49864315804055db1cd8c SHA-256: a645f42a8e3607d5afdb514ac076b44327d9ceee935d90c11878e6b65029df24
Below svf files should be small and can be nice for users not desire to use eval isos Windows11_InsiderPreview_Client_x64_en-us_26100_to_26100.1.240331-1435.ge_release_CLIENTENTERPRISE_OEM_x64FRE_en-us.svf Windows11_InsiderPreview_Client_x64_en-us_26100_to_26100.1.240331-1435.ge_release_CLIENT_CONSUMER_x64FRE_en-us.iso.svf
Firstly: Windows11_InsiderPreview_XXX_26100 iso's - is NOT "eval", and no conversion is required Secondly: Windows11_InsiderPreview_XXX_26100 iso's - contains integrated 26100.560 update and conversion to 26100.1 looks pretty stupid