Legacy Update show wrong size for Windows 10/11 UUP Feature Updates

[sal-ammoniac]

1.zip The website shows huge MB while downloading is normal.

[sal-ammoniac]

I cannot attach pictures, so i have to use zip

[sal-ammoniac]

Also,when upgrading to 22H2 to 1809 through Legacy Update,Download and install before rebooting can proceed,but will not enter upgrading after reboot.

[stdin82]

It’s not wrong size since Win10 1709, WUA api return the size for full UUP files set, which include all features and all languages https://learn.microsoft.com/en-us/answers/questions/1013918/iupdate-get-maxdownloadsize-returning-100s-of-gbs

plus, you are using Legacy for modern Windows and expect smooth experience?

[sal-ammoniac]

It’s not wrong size since Win10 1809, WUA api return the size for full UUP files set, which include all features and all languages https://learn.microsoft.com/en-us/answers/questions/1013918/iupdate-get-maxdownloadsize-returning-100s-of-gbs

plus, you are using Legacy for modern Windows and expect smooth experience?

No,just for fun

[kirb]

That makes a lot of sense, thanks @stdin82. In fact I remember this series of posts from Raymond Chen going over the new UUP delta system, worth a read for anyone curious.

So basically the max download size is unreliable for UUP updates, and if I understand right the min download size is also not particularly useful because it only represents the delta going directly from the previous release. There’s a few options then:

• Detect UUP updates (how?) and don’t display the download size.
• Don’t display download sizes at all if OS is Windows 10.0 or up.
• Display estimated install size instead of download size if UUP update.

There might be a property on IUpdate that indicates if it’s UUP, if not then can definitely look through the files of the update for expected UUP filenames.

[sal-ammoniac]

That makes a lot of sense, thanks @stdin82. In fact I remember this series of posts from Raymond Chen going over the new UUP delta system, worth a read for anyone curious.

So basically the max download size is unreliable for UUP updates, and if I understand right the min download size is also not particularly useful because it only represents the delta going directly from the previous release. There’s a few options then:

• Detect UUP updates (how?) and don’t display the download size.
• Don’t display download sizes at all if OS is Windows 10.0 or up.
• Display estimated install size instead of download size if UUP update.

There might be a property on IUpdate that indicates if it’s UUP, if not then can definitely look through the files of the update for expected UUP filenames.

really thanks

[stdin82]

There might be a property on IUpdate that indicates if it’s UUP, if not then can definitely look through the files of the update for expected UUP filenames.

There is no exposed property that define a UUP update, and the DownloadContents property is populated only after download request is made

however, there are some conditions that help identify a UUP update:

• it has no BundledUpdates property
• RevisionNumber property start with 1 (regular "legacy" updates start with 200 or 100 for Detectoids)
• HandlerID property for Cumulative Updates or Feature Updates is: http://schemas.microsoft.com/msus/2016/01/UpdateHandlers/OSInstaller
• DeploymentAction property value 4 "daOptionalInstallation" is exclusive to UUP updates (used to distinguish Optional Updates)

Examples:

regular update

Title: 2021-11 Cumulative Update Preview for .NET Framework 3.5 and 4.8 for Windows 10 Version 2004 (KB5007289)
KBArticleIDs: 5007289
UpdateID: 0e9ff135-8c17-44c8-a8e7-797e1ca7c537
RevisionNumber: 203
AutoSelectOnWebSites: False
BrowseOnly: False
AutoSelection: 1
AutoDownload: 2
DeploymentAction: 1
DownloadPriority: 2
Type: 1
MaxDownloadSize: 43768513
MinDownloadSize: 0
HandlerID: 
BundledUpdates:
  Windows10.0-KB5007289-x86-NDP48
  87505dc0-3037-4b15-ba22-22646178da7d

UUP updates

Title: 2021-12 Cumulative Update for Windows 10 Version 2004 for x86-based Systems (KB5008212)
KBArticleIDs: 5008212
UpdateID: 771292ec-3f94-4142-bf1a-8893d7513f06
RevisionNumber: 1
AutoSelectOnWebSites: True
BrowseOnly: False
AutoSelection: 1
AutoDownload: 2
DeploymentAction: 1
DownloadPriority: 2
Type: 1
MaxDownloadSize: 61419138760
MinDownloadSize: 0
HandlerID: http://schemas.microsoft.com/msus/2016/01/UpdateHandlers/OSInstaller

Title: VMware, Inc. - System - 9.8.18.0
UpdateID: 872febad-4975-4fd3-8bfe-681b2f609f9b
RevisionNumber: 1
AutoSelectOnWebSites: False
BrowseOnly: False
AutoSelection: 1
AutoDownload: 2
DeploymentAction: 1
DownloadPriority: 2
Type: 2
MaxDownloadSize: 54187
MinDownloadSize: 0
HandlerID: http://schemas.microsoft.com/msus/2002/12/UpdateHandlers/WindowsDriver

Title: VMware, Inc. - Display - 9.17.5.1
UpdateID: d941d5a1-6b66-4203-8a94-14507f214eac
RevisionNumber: 1
AutoSelectOnWebSites: False
BrowseOnly: False
AutoSelection: 1
AutoDownload: 2
DeploymentAction: 4
DownloadPriority: 2
Type: 2
MaxDownloadSize: 7788000
MinDownloadSize: 0
HandlerID: http://schemas.microsoft.com/msus/2002/12/UpdateHandlers/WindowsDriver

Title: Feature update to Windows 10, version 1909
KBArticleIDs: 4524570
UpdateID: 63c4af5d-5f8a-4dbb-aeae-cf65424bfb16
RevisionNumber: 1
AutoSelectOnWebSites: False
BrowseOnly: False
AutoSelection: 1
AutoDownload: 2
DeploymentAction: 4
DownloadPriority: 2
Type: 1
MaxDownloadSize: 62357104689
MinDownloadSize: 0
HandlerID: http://schemas.microsoft.com/msus/2016/01/UpdateHandlers/OSInstaller

Title: 2019-11 Cumulative Update for Windows 10 Version 1903 for x86-based Systems (KB4524570)
KBArticleIDs: 4524570
UpdateID: e086ffc7-0644-4463-bc1f-5290febb0b8a
RevisionNumber: 1
AutoSelectOnWebSites: False
BrowseOnly: False
AutoSelection: 1
AutoDownload: 2
DeploymentAction: 1
DownloadPriority: 2
Type: 1
MaxDownloadSize: 59660806155
MinDownloadSize: 0
HandlerID: http://schemas.microsoft.com/msus/2016/01/UpdateHandlers/OSInstaller

background: UUP subsystem introduced with Windows 10 v1703 (build 15063), and was used only for Upgrades since Windows 10 v1709 (build 16299), it's also used for Windows Cumulative Updates (not .NET) and Drivers since Windows 10 v1809 (build 17763), it's also used for the obnoxious update KB4023057 since Windows 10 v2004 (build 19041), it's also used for Update Stack Packages

[sal-ammoniac]

Also, there is a problem that upgrade did not proceed after restaring ( It will show upgrade successful and you need to restart your computer, but after restart , it did not start upgrade but entering the original system‘s desktop ) , as I had said first. I have no idea what caused that. Is this the inherent problem or just bug?