it's just one package, and this one has correct version, so who cares? btw it's called "FodMetadataServicing-Desktop-Metadata-Package", and FoDs reinstallation is a big issue in this checkpoint updates drama, it might be this way on purpose we need new MVS ISO to check this, so ask again in 2 weeks
Wow, 65 GB is a lot of disk space required just to do an in-place upgrade. I guess I will do a fresh install when I have some free time. Just for your info, when I did a fresh install of Windows 11 many months ago, I allocated a maximum of 64 GB of disk space for it. After installing the OS and other software, I still managed to squeeze 11.3 GB of free disk space. I did remove the hibernation file, etc.
The needed space to be able to perform an (inplace) upgrade depends heavily on the amount of space used by the current install. Most of my Test VMs are just 60GB and have a fully installed OS on it and they upgrade to the latest build (canary and before dev channel too), mostly i can cleanup 20GB afterwards by deleting the temp files.
IS there a KB update to 24h2 (26100.1742) yet? Would love to do an update from 226x1 machines without running a re-install of the OS.....
Last time it was only 52GB, I guess they bumped it up. So 66666MB will do, but I went with 128GB, just to be sure, since 12 is behind doors. I actually got it down to 12GB of used space using LZX compression, but it introduced a little CPU lag, so not worth it, unless low on space.
I mean, between ISOs with the same build. Are ISOs created from UUP files differebt than Microsoft's and so they aren't 100% original? Also, why do I have to wait until Patch Tuesday for 24H2 to be offered by WU when it was supposedly out 3 days ago and even then I might have to wait some more time until it's offered by WU according to what I was told here?
there is KB5043178 (26100.1882) on my side it throws a Windows Update error (I updated 23h2 to 24h2 by .iso) it needs to manually install first KB5043080 from Microsoft Catalog
This option was moved to Settings > Time and Language > Date and Time, collapse "Show time and date in the System Tray" and the option will be there.
If resolving the repeating sfc /scannow corrupt-files report is important to you, then I found that running an in-place-downgrade to 26100.1742 fixes that problem. I'm suspicious that cleanup, sfc, and the checkpoint updating issues are not fully finalized. So I'm staying at 26100.1742 until patch Tuesday (10/8/24). Code: Microsoft Windows [Version 10.0.26100.1742] (c) Microsoft Corporation. All rights reserved. C:\>sfc /scannow Beginning system scan. This process will take some time. Beginning verification phase of system scan. Verification 100% complete. Windows Resource Protection did not find any integrity violations. C:\Users\User008>
On my system, cleanup leaves twelve(12) 26100.1 packages in component store in a "staged" state, several 1742 files in a "staged" state and 1876 or 1882 files in an "installed" state, depending on which update was ran. The left over 26100.1 packages mean that 1742 isn't a complete baseline replacement for 26100.1. This is why I am suspicious that cleanup, sfc, and the checkpoint updating process may not be finalized yet. Dism /Online /Get-Packages /Format:Table
language specific packages will always stay as .1, nothing new here compare your results with this https://forums.mydigitallife.net/posts/1854776
I'm not completely convinced the language specific assertion is completely relevant. I still suspect that the cleanup, sfc, and the checkpoint processes are not completely finalized.
i disagree, check MSFT ISO here https://forums.mydigitallife.net/posts/1854761 and I got exactly the same results here https://forums.mydigitallife.net/posts/1854819
There's plenty of 1742 packages that are language dependent. In previous versions of Windows, the LCUs would replace older packages and cleanup just fine.