think it was mentioned here during a fresh install choose previous setup and no windows. Old folder file explorer and mostly everything sets up as 23/h2 like , only thing I have done was not plan to the .1882 waiting for oct 8th only want 2nd Tuesday updates for now on only thing that is bogged down in benchmarks is how can I turn of this I tried from PowerShell Admin "Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-Hypervisor" didn't turn off after I rebooted?
i have a question maybe its stupid but can i create the latest iso build from uupdump for 24h2 because i like to do clean install ?
really? https://forums.mydigitallife.net/posts/1847193 hypervisor is always active in 26100 if not disabled in bootloader, auto = on
ms print to pdf missing in 24h2 it shows as enabled, but the printer itself doesn't show in the devices & printers error code: 0x800F0922 when re-enabled
You need update to .1882 https://forums.mydigitallife.net/th...on-24h2-windows-11-consumer-26100-1742.88656/
DISM command did not work for me. Still have Disk Clean up with Gb's of junk files. SFC /scannow still reporting corrupt files. Task manager buggy as sluggish were it stops working. Let's release 24H2. Good enough
not really on 22621 and lower builds it was possible to keep only the latest packages on 26100 it is the same but only if the latest LCU is the baseline, which at the moment is 26100.1742 so if you have LCU 26100.1882 installed, you have 1742 staged stuff and 1882 as installed = it takes more space for ISO / installed image when they release a new checkpoint update, the old one is removed, like 26100.1 at this point, so packages size is still under control
Is there a difference between manually integrating the LCU on a .1 Build ISO or creating an ISO already with the latest Build from UUP Dump?
not much uup-converter integrates safeos DU to boot.wim to save time you are also doomed if DisableUpdatingUpgrade=0 and you have more than one base edition, it saves time but messes with the packages base edition + W10UI is more "correct" way, current W10UI is not ready for 26100, use 10.46-rc
And what's the difference between downloading an ISO from Microsoft's site or creating it from UUP Dump?
msft ISO = 26100.1742 with uup-converter (UUP dump) or W10UI you can get the latest version, 26100.1882
So what U say about this situation then, this is after resetbase. RestoreHealth do nothing this time as it fix me this situation last time.