- This topic has 3 replies, 2 voices, and was last updated 3 months, 2 weeks ago by .
-
Posts
-
Been using BatchPatch fine for a year, have an MECM environment and use BatchPatch to fix up anything that MECM misses due to broken clients etc. No changes to our hosts in terms of GPOs, Windows update settings remain the same as they always did, but now when I change from Default/Managed to Windows Update my hosts are returning nothing. For example we have not released the 2024-06 Cumulative update on MECM yet but any host I point to Windows Update returns nothing in terms of the 2024-06 update.
Have followed this but all checks out good: https://batchpatch.com/batchpatch-and-the-windows-update-control-panel-report-a-different-number-of-available-updates
WindowsUpdate.log seems to be good, hosts connecting to https://fe3cr.delivery.mp.microsoft.com/ClientWebService/client.asmx returning “Found 0 updates and 8 categories in search; evaluated appl. rules of 95 out of 92 deployed entities END * Finding updates CallerId = BatchPatch, Id = 6, Exit code = 0x00000000 (cV = taUOaLDHD0+hD2eB.1.1.0.2)
Any ideas?
Your posting was sitting in the spam bin, so I didn’t see this until now. Sorry for the delay. Generally the reason that this happens is due to the OS being out of support with Microsoft. I’m guessing the OS version that your targets are using is no longer supported. Time to upgrade them.
Another thing to consider that we have seen occasionally is where you need to apply the latest servicing stack update. There were some older versions of Win 10 where we saw Microsoft got things out of order somehow where a machine would not be able to use Windows Update to find any available updates until after manually applying the latest service stack update (SSU update). It seems like in these cases they got into a situation where Windows Update couldn’t be used without the latest SSU, but the latest SSU could therefore also not be obtained through Windows Update. So it required a manual intervention to install the latest SSU.
One thing you can try that might work is to try an offline scan in BatchPatch instead of online. To do that, enable offline mode under ‘Tools > Settings’ and then try. This might get you onto a SSU that is late enough to resolve the issue.
Another thing that you can do is manually download the desired monthly cumulative update and/or latest SSU directly from the Microsoft Update Catalog. Then use the ‘Deploy’ feature in BatchPatch to deploy it to your target computers all at once with just a few clicks.
When offline mode is enabled, the BP computer will attempt to perform the download itself. If it has access to the internet, it will download the updates to its local cache and then push them to the targets for installation. The targets will not make connections to Windows Update or Microsoft Update as part of this process.
You can read more about how offline mode operates at this link: https://batchpatch.com/cached-mode-and-offline-updates
- You must be logged in to reply to this topic.