Copy To Cache: Failed. HRESULT: -2146467818 – Offline Cached Windows 11 Updates

[PhilTaylor]

Hi BatchPatch (Doug)

I have been using BatchPatch to perform offline updates to an airgapped infra at my location for a few years now, has worked perfectly.

We all need to update to Win11 before next year is out so I am starting to do it.

I have just upgraded one machine from Win10 to Win 11 24H2 but updates are no longer working. Batchpatch successfully identifies a communicative patch is missing and the URL for downloading the kit….once transferred to the airgapped server batchpatch then copies these to the end user machine and the batchpatch cache folder, however the part where it is supposed to then copy to the Windows Software Distribution folder just fails. Batchpatch errors out and then deletes the batchpatch cache folder. Below are logs:

12/02/2024 11:45:47

::Begin ‘offline sync service’ search

The search query “ImportantAndRecommended” returned 1 update(s):

1> 2024-11 Cumulative Update for Windows 11 Version 24H2 for x64-based Systems (KB5046617) (905 MB) (2024-11-11) – Security Updates
(Type-SoftwareUpdate | Downloaded-FALSE | RebootRequired-MAYBE)
http://support.microsoft.com/kb/5046617

::End search

::Begin filtering collection

adding> 2024-11 Cumulative Update for Windows 11 Version 24H2 for x64-based Systems (KB5046617)

::End filtering collection

There is 1 applicable update in the filtered collection

::Begin copying files to Windows Update cache

1> 2024-11 Cumulative Update for Windows 11 Version 24H2 for x64-based Systems (KB5046617)
1> lp_desktop_7c856293e949509c3625983400b8022c5be48f01.wim :: Copy To Cache: Failed. HRESULT: -2146467818
2> microsoft-windows-fodmetadataservicing-desktop-metadata-package_f20e6c202fdf6fb0fe509c6add9399b3e9165f38.cab :: Copy To Cache: Failed. HRESULT: -2146467818
3> microsoft-windows-fodmetadataservicing-desktop-compdb-package_04cff9358b2a5e8bec461e09b5a228dd05952b8a.cab :: Copy To Cache: Failed. HRESULT: -2146467818
4> fod_common_7491d52800c7d4df7fea3e873b935b6c1597bd4f.wim :: Copy To Cache: Failed. HRESULT: -2146467818
5> fod_desktop_71bd1653199cd19f3bbaca2aaf23c3b7e603cfd1.wim :: Copy To Cache: Failed. HRESULT: -2146467818
6> ssu-26100.2303-x64-express_50b591fde89c34ee88eefa1cacab7f689fcdc5b7.cab :: Copy To Cache: Failed. HRESULT: -2146467818
7> windows11.0-kb5043080-x64_953449672073f8fb99badb4cc6d5d7849b9c83e8.msu :: Copy To Cache: Failed. HRESULT: -2146467818
8> windows11.0-kb5046910-x64-baseless_5739dbf0eb3d199b34a488fd6f5c48d91372c502.cab :: Copy To Cache: Failed. HRESULT: -2146467818
9> windows11.0-kb5046617-x64_1e5d7b716c0747592ae80c218f1d81bbb7b0c7ab.msu :: Copy To Cache: Failed. HRESULT: -2146467818
10> fodmetadata_client_cc6fa0b098b179d2bbd1d53b91cc4de6b0eb5a88.cab :: Copy To Cache: Failed. HRESULT: -2146467818
11> windows11.0-kb5046910-x64-baseless_7948f7c76e9c024f1102340c3d9d4e55b7b9f6aa.psf :: Copy To Cache: Failed. HRESULT: -2146467818
12> ssu-26100.2303-x64_eebf1e75f612e3f27961ddbe66e4073e1cc7b098.psf :: Copy To Cache: Failed. HRESULT: -2146467818
13> edition_common_b01aaa34b66aca8fb45dd8fc6c1381c8579a9eaa.wim :: Copy To Cache: Failed. HRESULT: -2146467818
14> windows11.0-kb5046910-x64_6053cc0387657908cc388360432de32f51a29672.cab :: Copy To Cache: Failed. HRESULT: -2146467818
15> 29770bdb-ef7a-4f71-b51e-0cf9ff463203_wsus.aggregatedmetadata_c75f02055175f260e021ff806ea8254fe3c7ff07.cab :: Copy To Cache: Failed. HRESULT: -2146467818
16> desktopdeployment_01da2078a2c45012c87b2b92f4b802ee3378fb35.cab :: Copy To Cache: Failed. HRESULT: -2146467818

::End copying files to Windows Update cache

I did find another post in the forum with a different error mentioning the same and that Windows broke this process for communicative updates and windows 11. Doh! This will make things challenging going forward.

What I did in this instance was copy the entire set of files batchpatch told me to download based on the cumulative patch that was required, within the set of files was:

windows11.0-kb5043080-x64_953449672073f8fb99badb4cc6d5d7849b9c83e8.msu
windows11.0-kb5046617-x64_1e5d7b716c0747592ae80c218f1d81bbb7b0c7ab.msu

I installed KB5043080 manually assuming that one had to go first, then I installed KB50416617 manually, both installed fine.

Looking at the other post you made, is it just cumulative patches that are broken? So normal ones will work once a cumulative is performed manually?

If thats the case its not the end of the world but I have a problem still, even though I have manually installed those two updates and windows knows they are there, Batch Patch is still telling me that I need that patch…this is a scan on the same machine after:

The search query “ImportantAndRecommended” returned 1 update(s):

1> 2024-11 Cumulative Update for Windows 11 Version 24H2 for x64-based Systems (KB5046617) (905 MB) (2024-11-11) – Security Updates
(Type-SoftwareUpdate | Downloaded-FALSE | RebootRequired-MAYBE)
http://support.microsoft.com/kb/5046617

::End search

As I said, if cumulative patches have to be done this way I can live with it seeing as my machines are updated every month, there should be no need for cumulative….but if Batchpatch things it is not there still after I have installed it manually how are the normal updates going to work each month?

Any help will be great!

[doug]

The most recent version of BatchPatch is able to patch Windows 11 in offline mode without issues. We have not ever encountered the particular HRESULT value that you’re seeing (-2146467818), and I’m not quite sure what that HRESULT value means. That said, typically when there is an issue with CopyToCache it’s caused by not all of the required files being available in the cache. The offline mode procedure requires that you scan for updates on the target offline computer with Actions > Windows updates > Retrieve consolidated URL list of available updates. Then save that list and move it to a BatchPatch instance that has internet access. Use BatchPatch to download the 16 files that appear in that URL list. Then transfer those 16 files to the offline network in the BatchPatch cache folder, and then use Actions > Download and install updates

It seems to me like you probably did not follow the above process in one way or another. It seems like maybe your cache file was not populated with all of the correct/needed files for the operation to complete. I can’t say for sure.

You said that you manually installed two .MSU files. That’s fine. However, for reasons that are not clear to me, it does not look like you installed the November 2024 cumulative update even though you installed the two files that Microsoft had posted on the catalog for that KB number. My guess is that this might be part of an issue that Microsoft apparently had in November where they cataloged the updates incorrectly. I thought it had been all resolved, but maybe there is still something lingering that it’s incorrect on their end. I’m not sure.

It looks like the .MSU you installed is the SSU (servicing stack update), which is why BatchPatch is still telling you that the cumulative update is not installed. I would suggest you go back and follow the tutorial for scenario 4 at this link to get the remaining update installed: https://batchpatch.com/cached-mode-and-offline-updates

Alternatively, maybe try installing this update directly from the Microsoft Catalog: 2024-11 Cumulative Update for Windows 11 Version 24H2 for x64-based Systems (KB5046740)

[PhilTaylor]

Hi Doug.

I have been following the offline update process and it has worked flawlessly since we install BatchPatch, we installed it specifically for our AirGapped enviroment.

Process I follow is this and ill write it from memory so you can point out any errors:

1: Download Windows cat file on an internet connect machine from:
https://learn.microsoft.com/en-gb/windows/win32/wua_sdk/using-wua-to-scan-for-updates-offline?redirectedfrom=MSDN&tabs=vbscript

2: Take catalog file and place on airgapped server where batchpatch is installed

3: Retrieve consolidated URL list of available updates and save out url file

4: Take URL file to internet machine and load into batchpatch

5: Download all files listed within URL file

6: Take downloaded content from URL list back into air gapped network and place in the folder designated for offline updates

7: Download and install updates

At which point batchpatch goes through its process of copying the update files to the target machine, this works fine as they appear in the working directory on the target machine and then in the past on windows 10 they just install and have done without issue for years.

Since upgrading to Windows 11 the files copy to the target but then fail with the above logs. I think after they copy to the batchpatch working directory they are then support to copy to windows distribution folder, that part never happens. I have never had to install such a long list of updates, to be honest when it was windows 10 I dont remember really ever having to perform such a large list, it was only ever 1 or 2. Cumulative updates and servicing stack updates have come in one file, not this long list.

Maybe youre right and windows did have some issue in november, maybe December update will resolve all of this and it was just a coincidence.

I am going to take another look at it tomorrow and maybe ill dump out some screenshots to assist.

[Author]

Posts