Offline Servicing - MECM

Eugene Verheem 51 Reputation points
2021-12-06T21:10:24.273+00:00

Hi Guys, I have a question regarding MECM and Offline Servicing we always used to be able to do offline servicing on our Windows 10 Enterprise 2004 wim's, but for some reason this has stopped working, once the updates gets scheduled and applied, it does not get applied, but skips the CU for the month. If we try and schedule the updates again it is not in the list anymore and looking at the WIM properties it comes back with those updates as not required, yet it is required and not applied on the WIM.

Have tried new ISO's directly from VLSC October 2021 patched and also having the same issue. Looking at the Offline Servicing log from MECM we can see the following error APPLICABILITY_CHECK_NOT_SUPPORTED 0x80070057. Can see there used to be an issue regarding this error and this has been resolved now if you use a build version of 985 or higher, the October one we are using is build 1288 and it does not seem like it is working for us in this matter more info on the error here: https://learn.microsoft.com/en-us/troubleshoot/mem/configmgr/offline-servicing-lcu-may-fail.

Used to have CM 2010 and ADK 10 version 10.1.19041 have since updated to CM 2107 and ADK 11 10.1.22000. Thought that the issue would disappear after the update, but it did not. Also another thing we have noticed trying to use the DISM commands on Server 2016 gives us an error 87 "the add-package option is unknown" (do note we are using /Add-Package) or if we use Add-WindowsPackage we also get an error code = 0x80004001 which is the same error code from above link. Not sure if this might be related to why the Offline Servicing in MECM is not working, because that the commands are not working for our Server 2016. I can run this exact same commands on my Windows 10 device without any errors and it adds the CU successfully to the WIM as well. Just want to know if there are anyone else experiencing this issue as well when it comes to Offline Servicing and if it is fixed and what have you done to fix it please.

Microsoft Configuration Manager Updates
Microsoft Configuration Manager Updates
Microsoft Configuration Manager: An integrated solution for for managing large groups of personal computers and servers.Updates: Broadly released fixes addressing specific issue(s) or related bug(s). Updates may also include new or modified features (i.e. changing default behavior).
925 questions
Microsoft Configuration Manager Deployment
Microsoft Configuration Manager Deployment
Microsoft Configuration Manager: An integrated solution for for managing large groups of personal computers and servers.Deployment: The process of delivering, assembling, and maintaining a particular version of a software system at a site.
859 questions
Microsoft Configuration Manager
0 comments No comments
{count} votes

Accepted answer
  1. abbodi86 3,776 Reputation points
    2021-12-07T11:22:05.57+00:00

    The issue is within the servicing stack update
    since SSU-19041.1145, it's not fully compatible with Host OS below Windows 10 v1803 (build 17134)

    to fix the issue on your Server 2016 Host OS, simply run these in command prompt as administrator

    copy /y %SystemRoot%\System32\slc.dll %SystemRoot%\System32\ext-ms-win-security-slc-l1-1-0.dll
    copy /y %SystemRoot%\SysWOW64\slc.dll %SystemRoot%\SysWOW64\ext-ms-win-security-slc-l1-1-0.dll
    

    you can keep the duplicated file, or remove it after servicing 19041 images

    2 people found this answer helpful.

1 additional answer

Sort by: Most helpful
  1. Rita Hu -MSFT 9,566 Reputation points
    2021-12-07T07:10:47.19+00:00

    @Eugene Verheem
    Thanks for your posting on Q&A.

    In order to help us research further, please try to share the DISM.log and OfflineServicingMgr.log for reference.

    In addition, please help to comfirm the following questions:

    1.Have tried new ISO's directly from VLSC October 2021 patched and also having the same issue. Looking at the Offline Servicing log from MECM we can see the following error APPLICABILITY_CHECK_NOT_SUPPORTED 0x80070057.
    What is the OS version and OS Build? Also Please help to comfirm the KB number of the CU which you want to inject into the Offline WIM file.
    2. As far as I know, we could not import the .MSU package into the Online WIM files.
    155565-4.png

    Also we could follow this link to import the update package manually.

    Please keep us in touch if there are any updates of the case. Have a great day.

    Regards,
    Rita


    If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments