It seems that after a rollback SCCM is stuck in a loop and will reinstall the Feature Update again. There's most likley a better technical way but after the rollback I completely uninstalled the SCCM client from the machine and then reinstalled it and the Feature Update would recognise it was no longer deployed and would not longer be shown in Software Center
Windows 10 Feature Update continuing to install after rollback
Hi all,
I am having a bit of a nightmare. We upgrade some machines to 20H2 via SCCM. It was a mistake and we rolled them back. We deleted the SCCM deployment and checked\refreshed software center to make sure it would not redeploy, by running the SCCM Software Update Cycles. 10 days later some of the machines upgraded again, I check the SCCM log and it has no record of it installing, it only has a record of the original time 10 days earlier SCCM installed it.
When I check the c:\Windows.old\WINDOWS\SoftwareDistribution\Download the update is in there. Does anyone know how this redeployed if it wasn’t via SCCM?
Dual scan is disabled and users cannot manually search for updates. We have no other tools for deploying Windows Updates only SCCM.
2 answers
Sort by: Newest
-
-
Amandayou-MSFT 11,046 Reputation points
2021-10-15T05:57:58.737+00:00 Hi @DongleBerry-4652,
Please navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate to check which source the client is used. Here is the screenshot:
Besides, please check WindowsUpdate.log. Windows Update uses the thread ID filtering to concentrate on one particular task.
For example, here is record in the logs, Service Id is started with 7971, it means the source is from Microsoft Update.Here is the article we could refer to:
https://learn.microsoft.com/en-us/windows/deployment/update/how-windows-update-works
If the response is helpful, please click "Accept Answer" and upvote it.
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.