Good question — wusa can return you to the prompt before everything is obviously visible, so here are fast, reliable ways to tell whether the installer is still running and whether the update actually installed. Pick whichever is easiest.
1) Quick: check whether wusa is still running
Run this in an elevated PowerShell — if it returns nothing, the installer process has exited:
Get-Process -Name wusa -ErrorAction SilentlyContinue
If you prefer an automatic wait loop (it prints when finished):
while (Get-Process -Name wusa -ErrorAction SilentlyContinue) { Start-Sleep -Seconds 5 }
Write-Host "wusa finished"
2) Check whether the package is already installed (recommended)
Use DISM to list installed packages and search for the KB ID you expect (replace KB5070773 with the KB you wanted):
dism /Online /Get-Packages | findstr /I "KB5070773"
Or, since your filename shows KB5043080, check that too:
dism /Online /Get-Packages | findstr /I "KB5043080"
If the package is listed, the installer completed its job (a reboot may still be required to finish final steps).
3) Check Windows Update / HotFix listing
These can also show the installed KB:
Get-HotFix | Where-Object { $_.HotFixID -match 'KB5070773|KB5043080' }
Note: Get-HotFix doesn’t always list every cumulative update, so DISM is more reliable.
4) Check for pending reboot (if wusa used /norestart)
If the installer completed but hasn’t applied final steps, Windows may require a reboot. Check for a pending reboot entry:
Test-Path 'C:\Windows\WinSxS\pending.xml' ; # returns True if a pending XML exists
Or check the registry key (returns 0 if not present):
reg query "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\RebootRequired" /s
If you see a pending reboot, reboot to complete the install:
Restart-Computer
5) Check Windows Update log for install events (if you need details)
You already created WindowsUpdate.log; you can open it or search for the KB name:
Select-String -Path "$env:USERPROFILE\Desktop\WindowsUpdate.log" -Pattern "KB5070773","KB5043080","Install","error"
6) If you started wusa and it finished but the wrong KB was installed
I noticed you ran wusa with the file named kb5043080 (c:\windows11.0-kb5043080-...). If your goal was KB5070773 (the out‑of‑band Oct 2025 fix), check with DISM (step 2). If KB5070773 is not installed, download the correct KB5070773 .msu from the Microsoft Update Catalog and run wusa on that file (or I can fetch the exact catalog link for you).
7) If wusa appears to hang (rare)
- Look at the WindowsUpdate.log or check the Windows Modules Installer (TrustedInstaller) CPU activity in Task Manager; if it’s doing work then the install is still processing. If it hung for a very long time (30+ minutes with no disk/CPU IO from TrustedInstaller), you can stop it, collect logs, and retry manually.
Summary — the actionable short checklist you can run now
- See if wusa is still running:
Get-Process -Name wusa -ErrorAction SilentlyContinue
- If not running, confirm the KB is installed:
dism /Online /Get-Packages | findstr /I "KB5070773"
dism /Online /Get-Packages | findstr /I "KB5043080"
- If neither KB is listed, and wusa finished but nothing installed — download the correct KB5070773 .msu and run:
wusa "C:\Downloads\<KB5070773_filename>.msu" /quiet /norestart
(then Restart-Computer when you're ready)
If you’d like I can:
- Check for you which KB is installed now if you paste the output of the DISM command, or
- Fetch and paste the exact Microsoft Update Catalog link for KB5070773 so you can download and retry.
Which do you want me to do now — check whether the KB is installed (paste the DISM output), or get the KB5070773 catalog link for you to download?
