We’ll start by making sure that the latest WindFeature Upgrade is synchronized on our server:
If it’s the first time you are using Windows 10 servicing plans, follow our previous post that explains the requirements to set up your Software Update Point. If you’re already running Windows 10 in your organization, a Servicing plan is the simplest method to upgrade to an up-to-date Windows 10 version. Windows ADKīefore capturing and deploying a Windimage, make sure that you’re running a supported version of the Windows ADK. See the following support matrix if you’re running an outdated SCCM version and make sure to update your site. Update your Automatic Deployment Rules and Software Update groupsįor WindFall Creator Update, you need at least SCCM 1706 in order to support it as a client.Create a Windows 10 Upgrade Task Sequence for Windows 7 or 8.1 computers.Create a Windows 10 Task Sequence for new computers.Import the OS in SCCM to use with your deployment Task Sequence.Create a Servicing Plan to update your existing Windows 10.Check if you have an SCCM Supported version.This blog post will cover all the task needed to deploy the new Windusing SCCM: Treat it as a new operating system as if you were upgrading Windows 7 to Windows 10. Do not treat a feature upgrade as normal monthly software updates. Test it in a lab environment, deploy it to a limited group and test all your business applications before broad deployment. You may need to deploy it to your Windows 10 computer to stay supported or to benefits from the new features.īefore deploying a new Windows 10 feature upgrade, you need to have a good plan. It remains to be seen if these updates will install correctly though.Microsoft published the Windfeature update (aka Fall Creator Update), as Semi-Annual Channel on October 18th, 2017.
The next Patch Tuesday takes place on May 8, but other cumulative updates are likely to be posted later this month with more improvements and fixes (but no security patches though). Delta updates only include the changes that Microsoft developed since the previous patch, so they come as lighter packages.įurthermore, since they include fewer changes, they’re less likely to fail to install, possibly helping users who are hitting issues with KB4093112 to bypass them. This link points to the download mirrors for each version of KB4093112, so check twice that you get the correct one for your system.Īdditionally, in the case of systems that are already up-to-date and running the March 2018 cumulative updates, you can also download and try to install the delta updates for Windows 10, also available in the link above. If this workaround doesn’t make any difference and KB4093112 still fails on your system, you could try downloading the cumulative update manually from the Microsoft Update Catalog. Once you enter all commands, you should restart your PC and try to download and install the update once again from Windows Update.
In the Command Prompt window, you need to enter the following commands one by one and press Enter after each of them (you should copy and paste them from the box below to make sure there’s no typo): SC config wuauserv start= auto SC config bits start= auto SC config cryptsvc start= auto SC config trustedinstaller start= auto
This means you should be logged in with an administrator account, as standard users are restricted from launching apps with full rights.
On Windows 10 Fall Creators Update, you can type Command Prompt in the Start menu, right-click the result, and then hit the option that reads Run as administrator. The first thing you should do is launch a command prompt window with administrator privileges. We received confirmations that it could address errors like 0x80070bc2 when trying to install the cumulative update. Right now, it appears to be more of a matter of luck. There are users whose computers hit other bugs after actually installing this cumulative update, but in this case, no workaround other than removing the patch completely is known to do the magic.Īlso, this solution isn’t working for everybody, so while it fixes KB4093112 failed installs for some, it might not make any difference for others. In the meantime, the hundreds of users who took to the Microsoft Community forums to complain about issues with cumulative update KB4093112 came across a workaround that seems to fix problems on a number of systems.īefore detailing this method, it’s worth knowing that t he workaround is efficient only on a number of systems where KB4093112 fails to install.