SCCM Current Branch OSD Tasksequence Problem starting with Windows 10 20H1 (also 20H2) RRS feed

  • Question

  • Hi we got the Problem that all Systems installed with OSD Tasksequence (Windows 20H1 and H2) got a broken Windows Store. The Problem shows when Updating the Store Apps. The Apps update like normal but after re-checking for Updates, all Updates show again and the update again. Wsreset didn't solve the problem.

    First we thought it was about our install.wim but even when we use the untouched wim from an Windows ISO the problem for new installed Machine persists.

    Also rollback of the ADK from 20H1 to 19H1 didn't change that.

    Our SCCM Environment is a Single Server with Windows Server 2019, SQL 2019 and SCCM Current Branch 2006.

    If we use an Upgrade Tasksequence with the same Source for a existing 19H1 Windowsinstallation the Windows Store work like it should and after one Successfull Update-round it show after a second check Up to Date.

    We could replicate the Problem on our Test Environment with a Windows Server 2016, SQL 2016 and SCCM Current Branch 2006.

    Existing Computers with windows 10 19H2 could also update perfectly with with normal Windowsupdate if allowed but we could not install any System using a OSD Tasksequence without having the Bug with the Windows Store.

    As we would soon begin to test the Upgrade Rollout for out Pilot Users this doesn't interfere with it but after the Piloting Stage we would normaly install new Clients with the new Windows 10 instead of using an older Release and then having to Upgrade it again.

    I really hope anyone has a tipp how we can resolve this bug.



    Monday, October 26, 2020 2:25 PM

All replies