mgajda83
KB File Size Reporting Is Severely Inaccurate
When retrieving Windows Update metadata, the reported Size value for certain KBs is grossly inaccurate. For example, the latest Windows 11 update KB5058411 is being reported as 89 GB, which is clearly incorrect.
This appears to stem from the use of the Microsoft.Update.Session COM object or related APIs where the Size or MaxDownloadSize field is:
- Either unpopulated or misreported
- Possibly reflecting superseded or cumulative package sizes
- Not adjusted based on the actual download footprint required by the local system
This results in confusion, especially when scripting or reporting patch sizes at scale.
Expected Behavior: Accurate or at least reasonably estimated file size that reflects the actual download size for the current system configuration.
Actual Behavior: Inflated or nonsensical values (e.g., 89 GB for a cumulative update that is in reality <1 GB).
Recommendation: Please either correct the underlying metadata in the update catalog or explicitly document that the Size property is unreliable and should not be used for download size estimation.
