Microsoft Language Pack Issue via SCCM

Dear Fuad Akif,

Thank you for reaching out to the Microsoft Q&A Forum.

The issue you are encountering with error 0x80070002 during language pack downloads or installations on Windows 11 version 24H2 devices, following an upgrade from Windows 10, likely stems from configuration settings in your WSUS environment or related SCCM policies that prevent the necessary content from being available.

You could try following these steps below to solve this issue:

1. Verify WSUS/SCCM SUP Configuration for FoDs:
   1. In WSUS Console:
      • Go to Options > Products and Classifications.
      • Under the Classifications tab, ensure "Features on Demand" (and potentially "Language Packs" if listed separately for your version) is checked.
      • Under the Products tab, ensure the relevant Windows 11 versions (including 24H2 specifics if available) are selected.
      • Run a synchronization in WSUS and wait for it to complete.
   2. In SCCM Console:
      • Go to Administration > Site Configuration > Sites. Select your primary site, then Configure Site Components > Software Update Point.
      • Go to the Classifications tab and ensure "Features on Demand" is checked.
      • Go to the Products tab and ensure the relevant Windows 11 versions are checked.
      • Run a full synchronization for your SUP (Software Library > Overview > Software Updates > All Software Updates > Synchronize Software Updates).
2. Approve and download FoDs/LPs in WSUS/SCCM:
   • After synchronization, check WSUS or the "All Software Updates" view in SCCM for newly synced "Features on Demand" related to Language Packs for Windows 11 24H2.
   • Approve the specific language packs your organization needs for a relevant deployment group.
   • Ensure the approved updates are downloaded into your deployment packages and that the packages are successfully distributed to your Distribution Points.
3. Configure Client Source Policy for FoDs/LPs:
   1. Using Group Policy (GPO):
      • Navigate to: Computer Configuration > Administrative Templates > System
      • Find the policy: "Specify settings for optional component installation and component repair".
      • Enable this policy.
      • Option 1 (Recommended if not hosting LPs locally): Check the box for "Download repair content and optional features directly from Windows Update instead of Windows Server Update Services (WSUS)." This allows clients to fetch LPs/FoDs directly from Microsoft even if other updates come from WSUS.
      • Option 2 (If hosting LPs on WSUS): Leave the checkbox unchecked, but ensure the WSUS server name specified in the related policy ("Specify intranet Microsoft update service location") is correct and that the content has been successfully downloaded to WSUS (Step 2).
   2. Using SCCM Client Settings:
      • Similar settings regarding update source locations might be configured in your SCCM Client Settings policies. Review these to ensure they align with your chosen strategy (allow MU for FoDs or point strictly to SUP).
4. Network connectivity & firewalls:
   • Ensure clients have network access to the WSUS content location (either the WSUS server itself or SCCM DPs).
   • If you enabled direct access to MU (Step 3, Option 1), ensure clients can reach the necessary Microsoft Update URLs through your firewalls/proxies.

If the answer is helpful, 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.

Dear Fuad Akif,

I haven't received the message from you yet. If there is anything more that I can do for you or if anything is unclear, please do not hesitate to let me know.

Warm regards,