Trying to figure out the size of Windows updates before actually downloading them? Sounds simple, but in Windows 11, the built-in Settings doesn’t quite show the size like it used to. If you’re on a capped data plan or just hate waiting for downloads to start, knowing the update size can be a lifesaver. The thing is, Windows doesn’t give you a straightforward way to see this info through the normal UI. So, the fallback is PowerShell with a little script magic. Yeah, it’s kind of weird that you have to install a third-party module just to peek at update sizes, but that’s the reality for now. This method is handy because once set up, it can be reused, and you can check pending update sizes without jumping through hoops each time.
Keep in mind, this only shows the sizes of updates that are waiting for install — not the ones already applied. Also, if it feels like a lot of steps, don’t worry. The commands are pretty straightforward, and once installed, the process is smooth. Sometimes, on some setups, the first run throws up a prompt that needs Y to continue, then it’s pretty easy sailing afterwards. So, here’s how to get that info with PowerShell, step by step.
How to find Windows Update Size using PowerShell
This method helps when you want to see just how hefty an update really is before pressing that ‘Download’ button. It applies especially if you’re low on bandwidth or just enjoy having more control. Expect it to list the update sizes in a clear column, so you can gauge what to prioritize or skip for now.
Installing the necessary module
- Open Windows Terminal (Admin). You can do this by pressing Win + X and choosing it from the menu. Yeah, of course, Windows makes this slightly more convoluted than it needs to be, but worth it.
- When prompted, click Yes to give admin rights.
- Type this command:
Install-Module -Name PSWindowsUpdate –Force. This downloads and installs a script that can query Windows updates. - Press Y, then hit Enter when asked about trusting the repository. It usually pops up on the first install.
Configuring PowerShell to run scripts
- Next, you need to loosen the execution policies so PowerShell can run your new script. Enter:
Set-ExecutionPolicy RemoteSigned. You might get a warning; just confirm by typing Y and pressing Enter.
Loading the update module and checking for sizes
- You now need to import the module:
Import-Module PSWindowsUpdate. This step enables the commands to list updates. - Finally, type:
Get-WUList. This one fetches a list of pending updates with detailed info, including the size column.
The size info appears in the list, helping identify which updates are bulky and which are light. On some machines, it might take a few seconds, or the first time might be a little buggy, but worth it once it works.
To learn more about the module or troubleshoot, check out this page. Sometimes, the command may not yield results immediately if policies or permissions get a bit hung up; just close and reopen PowerShell as admin and try again.
Extra tips and tips — what else might help
- If you prefer clicking around instead of command lines, some third-party tools or Windows update managers might show sizes, but they’re inconsistent.
- And, yeah, this whole process only works for pending updates. Installed ones don’t really have a size listed anymore.
- Sometimes, on different PCs, the first run needs a reboot or a re-log, so don’t get discouraged if it refuses to show sizes right away.
That’s pretty much the basics for checking update sizes without just blindly hitting ‘Download’.It’s not perfect, especially on newer Windows versions, but it’s better than nothing. Hope this saves some bandwidth or just satisfies your curiosity. Fingers crossed this helps someone avoid the dreaded “Wait, how big is this update?” dilemma.
Summary
- Open Windows Terminal as administrator
- Install the PSWindowsUpdate module
- Adjust execution policies if needed
- Run Get-WUList to see update details, including sizes
Wrap-up
Getting a handle on update sizes with PowerShell isn’t the most seamless process, but it works once you’ve set it up. On some setups, it’s a reliable way to avoid surprises during a bandwidth crunch. If this gets one update moving without a hitch, that’s a win. Just remember, patience and some console fumbling ahead, but hey, worth it for a clearer idea of what’s about to download.