Software Updates feature is disabled

Atorli 56 Reputation points
2020-09-02T14:16:43.077+00:00

I have recently enabled Software Updates in MECM after having used WSUS for this for a long time. I've used the guides at https://www.prajwaldesai.com/install-sccm-software-update-point-role/ and https://www.prajwaldesai.com/deploy-software-updates-using-sccm-2012-r2/ to do this. Now the whole thing is partially working, I can synchronize updates, distribute them, and some PCs successfully install them.

However, other PCs do nothing. I have checked the log files on the PCs and can see the following in UpdatesDeployment.log (important lines in bold) 

Service startup system task	UpdatesDeploymentAgent	09/09/2020 09:01:12	13660 (0x355C)  
Software Updates feature is disabled	UpdatesDeploymentAgent	09/09/2020 09:01:12	13660 (0x355C)  
No current service window available to run updates assignment with time required = 1	UpdatesDeploymentAgent	09/09/2020 09:01:12	13660 (0x355C)  
CUpdatesLocalSettings::GetUserExperienceFlag - Got UserExperienceFlag = Default	UpdatesDeploymentAgent	09/09/2020 09:01:12	13660 (0x355C)  
CTargetedUpdatesManager::RegPostRebootFullScan - Total Pending reboot updates = 0	UpdatesDeploymentAgent	09/09/2020 09:01:12	13660 (0x355C)  
CTargetedUpdatesManager::RegPostRebootFullScan - IsReqPostRebootFullScan = 0	UpdatesDeploymentAgent	09/09/2020 09:01:12	13660 (0x355C)  
No CCM Identification blob	UpdatesDeploymentAgent	09/09/2020 09:01:12	13660 (0x355C)  
CTargetedUpdatesManager::IsInServiceMode = 0 	UpdatesDeploymentAgent	09/09/2020 09:01:12	13660 (0x355C)  
CTargetedUpdatesManager::DetectRebootPendingUpdates - Total Pending reboot updates = 0	UpdatesDeploymentAgent	09/09/2020 09:01:12	13660 (0x355C)  
Schedule a CEvalO365ManagementTask to happen in 720 seconds and repeat every 24 hours	UpdatesDeploymentAgent	09/09/2020 09:01:12	13660 (0x355C)  
Startup task completed	UpdatesDeploymentAgent	09/09/2020 09:01:12	13660 (0x355C)  
User logon system task	UpdatesDeploymentAgent	09/09/2020 09:01:16	10756 (0x2A04)  
EnumerateUpdates for action (UpdateActionInstall) - Total actionable updates = 0	UpdatesDeploymentAgent	09/09/2020 09:01:34	12236 (0x2FCC)  
CEvalO365ManagementTask::Execute()	UpdatesDeploymentAgent	09/09/2020 09:13:11	6408 (0x1908)  
This device is not enrolled into Intune.	UpdatesDeploymentAgent	09/09/2020 09:13:11	6408 (0x1908)  
Device is not MDM enrolled yet. All workloads are managed by SCCM.	UpdatesDeploymentAgent	09/09/2020 09:13:11	6408 (0x1908)  
Message received: '<?xml version='1.0' ?><SoftwareUpdatesMessage MessageType='EvaluateAssignments'><UseCachedResults>True</UseCachedResults></SoftwareUpdatesMessage>'	UpdatesDeploymentAgent	09/09/2020 10:41:05	6408 (0x1908)  
Message ignored as component is disabled.	UpdatesDeploymentAgent	09/09/2020 10:41:05	6408 (0x1908)

It looks like the computers that don't install updates believe that the feature is disabled. But, I have the "Enabled software updates on clients" set to "Yes" in the default client settings. There are no higher priority client settings that are disabling it again either, I have checked that. If I right click an affected PC and go to "Resultant Client Settings" I also see that the Software Updates are enabled:

![22174-updates.png][1]

The weird thing is that some computers in the same office, same network, same collection are successfully installing the updates. While others don't. Does anyone have an idea what i might be missing here? Or knows what other log file I could look in to see why the computers believe that the feature is disabled? [1]: /api/attachments/22174-updates.png?platform=QnA

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).
1,005 questions
Accepted answer
  1. Harjit Dhaliwal - MSFT 166 Reputation points Microsoft Employee
    2020-09-03T00:51:46.573+00:00

    Do these problematic computers have the same ConfigMgr client version? Completely uninstall the ConfigMgr client on one or two of them, reinstall the client and check to see if this resolves the issue.

    1 person found this answer helpful.
    0 comments

2 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Amandayou-MSFT 11,051 Reputation points
    2020-09-03T07:40:30.753+00:00

    Hi @Atorli

    It seems that there is no obvious error in this log. Maybe we could use seven steps to troubleshoot the common issues.

    Step 1: We could check Policyagent.log. When policy is received, the following entry is logged in PolicyAgent.log:

    22399-932.png

    We could check if Deployment Unique Id on the console is consistent with policy id displayed in PolicyAgent.log.
    22338-933.png

    Step 2: Software update would be checked if it is required by client , kindly check UpdatesStore.log. UpdateStore.log would record updates as missing if they are required. If it is not required or has been installed by client, there is no record in this log.

    Step 3: If the update is required, the content could be detected before downloading. We could refer to UpdatesDeploymentAgent.log.

    Step 4: The content could be downloaded. we could refer to UpdatesHandler.log, CAS.log, and ContentTransferManager.log. Here is a screenshot about ContentTransferManager.log.

    Step 5: After the download is completed, detection could be followed before installation. We could refer to UpdatesHandler.log,ScanAgent.log, UpdateStore.log, WindowsUpdate.log and WUAHandler.log.

    Step 6: Software update could be installed. We could refer to Windowsupdate.log and UpdatesDeployment.log.

    Step 7: After the updates are installed, Updates Deployment Agent checks whether any updates require a reboot, and then it notifies the user if client settings are configured to allow such notification. We could refer to UpdatesDeployment.log and UpdateStore.log.

    Here is an article about some detailed log screenshots.
    Using log files to track the software update deployment process

    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.

    If the response is helpful, please click "Accept Answer" and upvote it.

    1 person found this answer helpful.
  2. Atorli 56 Reputation points
    2020-09-03T14:20:17.867+00:00

    Thank you for the answers, harjit and Amandayou.

    I have checked the client versions, they are all on the same one (the newest one).
    If I do an "Install Client" on an affected client, then choose "Always install the client software" and "Uninstall existing ConfigMgr client", then it fixes the issue. The client then installs software updates.
    If I however leave the "Uninstall existing ConfigMgr client" checkbox unchecked, then reinstalling the client doesn't fix the issue.

    Unfortunately that means I just "fixed" the problem on all my testing PCs, so I have to organize a few more PCs from users to check the issue and have a look at the log files mentioned by Amandayou.