Wiki source code of Lokalen Windows Update Cache bereinigen
Last modified by Sabrina V. on 2026/06/01 05:57
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
 |
6.1 | 1 | = Initial situation = |
| |
1.1 | 2 | |
| |
6.1 | 3 | If you notice that all clients in your company except one are able to find updates without any problems, there may be a client-specific problem with the cache. This may be due to defective or corrupt metadata in the local Windows Update cache, which prevents the client from finding updates or new ones in general. |
| |
1.1 | 4 | |
| |
3.1 | 5 | {{aagon.infobox}} |
| |
6.1 | 6 | Third-party metadata is also taken into account and reset. |
| |
3.1 | 7 | {{/aagon.infobox}} |
| |
1.1 | 8 | |
| |
4.1 | 9 | {{aagon.versionierungsbox}} |
| |
6.1 | 10 | Up to ACMP version 6.9, you would have found instructions here detailing administrative tasks that you had to execute manually. These have been replaced by the system job "Reset Windows Update Cache". |
| |
4.1 | 11 | {{/aagon.versionierungsbox}} |
| 12 | |||
| |
6.1 | 13 | = Procedure = |
| |
1.1 | 14 | |
| |
6.1 | 15 | To clear a local Windows Update cache, you can use the system job of the same name, "Reset Windows Update Cache". To do this, add the job manually (push the job) or attach it to a Job Collection. For more information about the system job, see [[//Adding a Job Collection//>>doc:ACMP.610.ACMP-Solutions.Jobs.Job Collections.WebHome||anchor="HAddingaJobCollection"]]. |
| |
1.1 | 16 | |
| |
6.1 | 17 | After the cache has been cleared, the Windows Update Scanner or a corresponding update collection must be started and executed on the client. |
| |
1.1 | 18 | |
| |
6.1 | 19 | If the problem persists or, for example, no updates are detected on an agent (even though you are sure that there should be at least one), check the following steps to see if this could be the solution: |
| |
1.1 | 20 | |
| |
6.1 | 21 | * Is the agent //managed by WUM//? |
| 22 | * Are the correct products and classifications selected? | ||
| 23 | * Is the expected update available in the //Updates// tab? | ||
| 24 | * If not, is the update available exclusively via the Microsoft Update catalogue and can it be imported from there? | ||
| |
1.1 | 25 | |
| |
6.1 | 26 | If you can exclude all of these points, you should execute a full Metadata download. To do this, click on the //Status of WUM jobs //widget in the Windows Update Management dashboard and select the option ‘Start new, complete Metadata download’. |
| |
1.1 | 27 | |
| |
6.1 | 28 | Then confirm the dialogue box that appears with //Yes//. Depending on the number of products, classifications and languages selected, the download may take varying amounts of time and can take up to 90 minutes. |
| 29 | |||
| |
1.1 | 30 | {{aagon.warnungsbox}} |
| |
6.1 | 31 | The full Metadata download should only be used in exceptional cases, if you can exclude all of the above options. |
| |
1.1 | 32 | {{/aagon.warnungsbox}} |
| 33 | |||
| 34 | |||
| |
6.1 | 35 | [[Start a new, full metadata download>>image:67_CAWUM_Use Case Cache bereinigen_1128.png]] |
| |
1.1 | 36 | |
| 37 |