IUpdate2::CopyToCache method Windows 11

Simon Fonteneau 55 Reputation points
2024-12-12T12:09:00.7133333+00:00

It seems that this method no longer works on Windows 11:

https://learn.microsoft.com/en-us/windows/win32/api/wuapi/nf-wuapi-iupdate2-copytocache

Interface not registered

Do you have an idea?

Windows API - Win32
Windows API - Win32
A core set of Windows application programming interfaces (APIs) for desktop and server applications. Previously known as Win32 API.
2,734 questions
Windows 11
Windows 11
A Microsoft operating system designed for productivity, creativity, and ease of use.
10,809 questions
{count} votes

4 answers

Sort by: Most helpful
  1. Simon Fonteneau 55 Reputation points
    2025-01-02T17:12:04.89+00:00

    I was wrong, the problem only concerns Windows 11 24h2

    It could be related to this problem.:

    https://learn.microsoft.com/en-us/windows/release-health/status-windows-11-24h2#issues-might-occur-with-media-which-installs-the-october-or-november-update

    It doesn't mention copytocache but I hope that's where the problem comes from.

    0 comments No comments

  2. Simon Fonteneau 55 Reputation points
    2025-01-03T10:25:13.8466667+00:00

    I confirm that once kb5048667 is installed manually with the msu, copytocache seems to work correctly again.

    On the other hand, Microsoft continues to currently provide an ISO online that contains the bug, which is a shame...

    0 comments No comments

  3. Simon Fonteneau 55 Reputation points
    2025-01-20T13:24:36.4066667+00:00

    Ultimately the problem was still there...

    The problem appears with cumulative.

    We ended up realizing that the difference with the old version of Windows is that we now have a .msu which appears in the download urls of the cab.

    We therefore completely change our behavior for this specific case...

    We no longer use copytocache when a .msu file appears in the download urls, we forget all the download urls... and we download only the .msu file then we launch the installation of it with wusa.exe "{ }" /quiet /norestart.

    The behavior therefore completely changes compared to the method we used before. And no communication from Microsoft explains it....

    0 comments No comments

  4. Friese, Manuela 0 Reputation points
    2025-02-20T08:05:46.9866667+00:00

    We already had the problem with cumulative patch KB5048667 from January: CopyToCache returns “COM-Error: 0x80246fff” - according to the documentation:

    WU_E_DM_UNEXPECTED There was a download manager error that is not covered by another WU_E_DM_* error code.

    It is the case that each individual download file belonging to the patch causes this error, so that it cannot be linked to a single file.

    Seen on a Windows 11 24H2 client, also occurs directly during the first update check, so that no update cache etc. can be the source of the error.

    Unfortunately, the same problem exists in February with the cumulative patch KB5051987 - which replaces the above-mentioned patch. So the problem is still not solved.

    Data from the Windows 11 client on which the error is reproducible:
    Windows 11 24H2 - Build 26100.2605

    Installed hotfixes (get-hotfix):
    KB5042098, KB5048779, KB5050575, KB5049685

    KB5048667 is also installed, we have done this manually via the separately downloaded msu file - but this is not a permanent solution for us for all upcoming patches.

    Attached is an example in C++ with which this can be reproduced. It is a simple example, the patchscan.cab file is expected under c:\temp and the downloads are stored under c:\temp\WSUS - adjust the directory if necessary.

    Can we hope that the problem has now been solved in February and that CopyToCache will work again with the next update in March at the latest?

    We would be pleased to receive feedback on how to solve the problem.

    PatchUpdate.cpp.txt

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.