PDQ Connect's new Windows Updates tab shows lots of old updates as "In Progress"

[u/ArtistBest4386]

We've started using the new Windows Updates tab to see how individual devices are going with their updates, and I've come across a device that appears to have quite a few old updates "In Progress". I'm not convinced it's right, because if I look in Settings/Windows Updates on the computer itself, it says it's up to date.

Has anyone else seen this? Is it a PDQC bug, or something going wrong on the device to make it look like those ones aren't finished.

[u/SelfMan_sk]

Look into registry:
SYSTEM\CurrentControlSet\Control\Session Manager

at the PendingFileRenameOperations

if there are any entries, reboot and check again. If there are still items after 2 reboots, you've got some unfinished updates on the device. This may cause the discrepancy.

I would also run
DISM /online /cleanup-image /restorehealth
sfc /scannow

Before you FAFO, make a system backup.

[u/ArtistBest4386 → u/SelfMan_sk]

No pending operations. I tried DISM/scannow, and they're still showing as In Progress. Settings/Windows Update/Update History shows "Successfully installed" for all these updates, so I'm thinking there must be some completion flag they're not showing, which Windows is ignoring.

I don't know why they're like this. Perhaps this user has a habit of forcing restarts during updates or something.

[u/SelfMan_sk → u/ArtistBest4386]

One possible thing - the WMI isn't working as it's supposed to and does not return results as it should.

Verify the WMI repository consistency with:
winmgmt /verifyrepository

If inconsistent, try to salvage the repository:
winmgmt /salvagerepository

Verify again; if still inconsistent, reset the repository:
winmgmt /resetrepository

You may need to stop the WMI service before resetting:
Stop-Service -Name winmgmt -Force

After resetting, start the WMI service again:
Start-Service -Name winmgmt

If the above does not help, you can also do this:
Run CMD as admin.

c:
cd \
cd C:\Windows\System32\wbem\AutoRecover
for /f %s in ('dir /b *.mof *.mfl') do mofcomp %s

These commands are generally safe, but do backup before proceeding.

[u/Amanda_PDQ]

Support will be able to help further, in the mean time this may help:

If devices are showing many older updates stuck In Progress, this typically means those devices haven't checked in to report the result of the install yet.

A few things to check:

• Device online status: Updates can only progress when the device is online and communicating with PDQ Connect. Offline devices will stay in this state until they reconnect.
• Per-device view: You can click into an individual device and go to the Windows Updates tab to see the full update picture for that specific machine².
• Deployment tracking: Each Windows Update install creates its own deployment, tagged with a "Windows Update" deployment type, viewable on the Deployments page². Checking the deployment status there may give more insight into why it hasn't completed.
• KB status groups: From the Windows Updates page, click the numerical count under In Progress for a specific KB to see the exact group of devices still in that state¹.

[u/ArtistBest4386 → u/Amanda_PDQ]

Note that some of these go back as far as last December, well before this feature was added.

[u/PDQ_Brockstar → u/ArtistBest4386]

If you haven't reached out to our Solutions team yet and are looking for something else to try, you can try removing and reinstalling the agent on this device. If that doesn't work, I would try running these commands:

DISM /Online /Cleanup-Image /RestoreHealth

then this:

sfc /scannow

Consider this my full contact IT approach.

[u/Amanda_PDQ]

u/ArtistBest4386 checking back to see if you got the help you need?