By using this site, you agree to the Privacy Policy.
Accept
EnterinITEnterinITEnterinIT
  • HOME
  • IT PRO
  • TECH
  • MICROSOFT
    • Azure
    • ConfigMgr/SCCM
    • DPM
    • Orchestrator
    • Hyper-V
    • Microsoft Edge Insider
    • MSI
    • Office 365
    • Office Insider
    • Power BI
    • Skype
    • SQL Server
    • Teams
  • WINDOWS
    • Windows Admin Center
    • Windows Client
    • Windows Server
  • SCCM Query Collection List
Reading: SCCM KB4535819
Font ResizerAa
EnterinITEnterinIT
Font ResizerAa
  • HOME
  • IT PRO
  • TECH
  • MICROSOFT
  • WINDOWS
  • SCCM Query Collection List
Search
  • HOME
  • IT PRO
  • TECH
  • MICROSOFT
    • Azure
    • ConfigMgr/SCCM
    • DPM
    • Orchestrator
    • Hyper-V
    • Microsoft Edge Insider
    • MSI
    • Office 365
    • Office Insider
    • Power BI
    • Skype
    • SQL Server
    • Teams
  • WINDOWS
    • Windows Admin Center
    • Windows Client
    • Windows Server
  • SCCM Query Collection List
ConfigMgr

SCCM KB4535819

Published February 18, 2024
6 Min Read
SHARE

SCCM KB4535819. Configuration Manager early update ring version 1910 KB4535819.

Contents
Issues that are fixedAdditional hotfixes contained in this update KB4535384

This update does not apply to sites that downloaded version 1910 on December 17, 2019, or a later date. Therefore, it will not be listed in the Configuration Manager console for those sites.

Issues that are fixed

  • “Violation of PRIMARY KEY constraint ‘OfficeAddinHealth_PK’.” appears in the statesys.log after updating to version 1910.
  • When using the search feature in a task sequence, the “Result X of Y” label appears does not have a fixed location within the console.
  • After updating to 1910, users are listed with their names as (lastname\) instead of (lastname, firstname) as it shows in Active Directory.
  • An App group with multiple deployments fails to show up in Software Center when targeted to users as available.
  • Enforcing TLS 1.2 can cause content download failures from a cloud distribution point.
  • Operating system in-place-upgrade task sequences may not start as expected on Windows 10, version 1709 clients.
  • The Configuration Manager console may terminate unexpectedly when configuring a Microsoft Edge Management policy.
  • The Configuration Manager console may terminate with an ArgumentOutOfRangeException if the user navigates away from the Deployments node while it is still returning results.
  • The Delete Aged Discovery Data task may incorrectly remove active records.
  • The SMS Agent Host service on Management Points may terminate unexpectedly after updating to version 1910.
  • The 1910 update process may fail due to a duplicate key violation. An error resembling the following is recorded in the ConfigMgrSetup.log. Violation of UNIQUE KEY constraint ‘SR_SummaryTasks_G_AK’. Cant insert dup. key in object ‘dbo.SR_SummaryTasks_G’. The dup.key value is (Office Pilot Collection Machines Task)
  • Bitlocker Management is an optional feature, now unchecked by default in the Configuration Manager update wizard.
  • Distribution Point Status does not load as expected after updating to version 1910.
  • The CMGatewaySyncNotificationWorker component reports status message every 1 minute.
  • Cloud Management Gateway servers may report authentication errors after updating to version 1910.
  • The MP_GetProxyMPListForSite stored procedure does not prefer the clients assigned site, resulting in random MP assignment when fallback is enabled for secondary sites.
  • The SMS Agent Host service (CCMExec.exe) may not restart as expected when the client computer reboots during an operating system deployment task sequence.
  • Content is not available for tasks sequences when the client is on an intranet network, and the Always Internet Facing (CCMALWAYSINF) parameter is set to 1.
  • CMPivot auto completion is not working for the first table in the query.
  • The Disable Bitlocker step in the Task Sequence Editor generates an exception when editing a task sequence created in version 1902 or earlier.
  • The Software Center client (SCClient.exe) terminates unexpectedly due to unhandled exception when downloading task sequence policy.

Additional hotfixes contained in this update KB4535384

An update is available for customers using the early update ring release of Microsoft Endpoint Configuration Manager current branch, version 1910. This update resolves the following issues.

  • The SMS Agent Host service (ccmexec.exe) may terminate unexpectedly when running a task sequence on Windows 10 client computers.
    This occurs when the task sequence and environment are configured as follows:
    • Peer cache support is enabled for the target collection.
    • A network access account is configured and in use.
    • The application deployment in the task sequence has on-demand content distribution enabled using the “Distribute the content for this package to preferred distribution points” option.

The Deployment Status window in the Configuration Manager console will also show the following error related to the deployment in question.

Message ID: 10021
Status Type: Error
Description: Program failed (unexpected restart)
  • During the client upgrade process, previous client settings and policies may be reset to default values until the next time policy is applied. This can lead to symptoms such as hardware inventory resynchronization, or setting co-management workloads to the wrong management authority.
  • Office 365 updates fail to download in Configuration Manager environments with Windows Delivery Optimization (Allow clients to download delta content when available) enabled. Note enabling this setting should not apply to Office 365 updates.
    Errors resembling the following are recorded in the DeltaDownload.log file.
Update ID retrieved from header is: {OFfice 365 Update ID}
GetContentIDsFromLS with Update ID {OFfice 365 Update ID}
DDMCache has no data with FileHash = '{File Hash}'.
The Hash attribute is empty.
DDMCacheManager::InsertSqlCE failed with error 0x80004005
  • Content is not downloaded using an Alternate Content Provider for applications or software updates being installed during an operating system deployment task sequence. This issue occurs on clients in provisioning mode.
  • After updating to version 1910, clients may experience delays in moving policy assignments from the requested to actual configuration. This leads to multiple symptoms, such as deployment or client settings policies not being received or applied, or client status reporting as “Unknown” for monitored deployments.
TAGGED:Active DirectoryMECMMEMCMMicrosoft Endpoint Configuration ManagerOffice ProPlusSystem Center Configuration ManagerWindows 10
Previous Article How to Fix PowerShell 0x800f0906 Error when Installing Windows Features
Next Article Windows Terminal Preview v0.8
2 Comments 2 Comments
  • Waynr DeJulia says:
    January 1, 2020 at 10:30 am

    There is a client piece to this: https://support.microsoft.com/en-gb/help/4535384/client-update-available-for-configuration-manager-current-branch-versi
    involves running the updater to register the client update after downloading the client update, and then it should appear in the updates and servicing node. I have had no such luck. I did have the 1910 early ring, and was offered the hotfix which installed without a problem. Never got the client piece to show up

    https://docs.microsoft.com/en-us/configmgr/core/servers/manage/use-the-update-registration-tool-to-import-hotfixes

    rebooted, stopped and restarted smsexec service. log file from after in installed the client piece to get it registered

    CMRegisterUpdate.log in systemroot\temp directory
    ______________________________________

    Configuration Manager Update Registration starting. CMRegisterUpdate 1/1/2020 10:29:13 AM 20704 (0x50E0)
    =================================================== CMRegisterUpdate 1/1/2020 10:29:13 AM 20704 (0x50E0)
    VERBOSE: Potential manifest file ‘c:\a71ebf10192caa81110d3242e71fb073\cm1910-kb4535384.configmgr.update.manifest.cab’ CMRegisterUpdate 1/1/2020 10:29:13 AM 20704 (0x50E0)
    Found Manifest file: ‘c:\a71ebf10192caa81110d3242e71fb073\cm1910-kb4535384.configmgr.update.manifest.cab’. CMRegisterUpdate 1/1/2020 10:29:13 AM 20704 (0x50E0)
    Extracting manifest.xml data stream from ‘c:\a71ebf10192caa81110d3242e71fb073\cm1910-kb4535384.configmgr.update.manifest.cab’ to retrieve update metadata… CMRegisterUpdate 1/1/2020 10:29:13 AM 20704 (0x50E0)
    VERBOSE: UpdateName:Configuration Manager 1910 Hotfix (KB4535384) CMRegisterUpdate 1/1/2020 10:29:13 AM 20704 (0x50E0)
    VERBOSE: UpdateDescription:Fixes issues explained in KB4535384 CMRegisterUpdate 1/1/2020 10:29:13 AM 20704 (0x50E0)
    VERBOSE: MinCMVersion:5.00.8913.0000 CMRegisterUpdate 1/1/2020 10:29:13 AM 20704 (0x50E0)
    VERBOSE: MaxCMVersion:5.00.8913.9999 CMRegisterUpdate 1/1/2020 10:29:13 AM 20704 (0x50E0)
    VERBOSE: MoreInfoLink:https://support.microsoft.com/help/4535384 CMRegisterUpdate 1/1/2020 10:29:13 AM 20704 (0x50E0)
    VERBOSE: ManifestFile:c:\a71ebf10192caa81110d3242e71fb073\cm1910-kb4535384.configmgr.update.manifest.cab CMRegisterUpdate 1/1/2020 10:29:13 AM 20704 (0x50E0)
    VERBOSE: UpdatePayload:092F0EDD-5793-48CA-882F-E85CB1B4A2D1.cab CMRegisterUpdate 1/1/2020 10:29:13 AM 20704 (0x50E0)
    VERBOSE: ShouldTriggerThreadRestartByDefault:True CMRegisterUpdate 1/1/2020 10:29:13 AM 20704 (0x50E0)
    VERBOSE: MaxRestartSeconds:120 CMRegisterUpdate 1/1/2020 10:29:13 AM 20704 (0x50E0)
    VERBOSE: UpdateInstallDocumentationLink:http://go.microsoft.com/fwlink/?LinkId=723801 CMRegisterUpdate 1/1/2020 10:29:13 AM 20704 (0x50E0)
    DMP Restart option False CMRegisterUpdate 1/1/2020 10:29:13 AM 20704 (0x50E0)
    Restart of DMP thread to False CMRegisterUpdate 1/1/2020 10:29:13 AM 20704 (0x50E0)
    Welcome page activated. CMRegisterUpdate 1/1/2020 10:29:13 AM 20704 (0x50E0)
    Sequencer: State change event recieved, new state is ‘WelcomeDisplayed’, reason for state change is ‘None’. CMRegisterUpdate 1/1/2020 10:29:13 AM 20704 (0x50E0)
    Navigating to next page. CMRegisterUpdate 1/1/2020 10:29:17 AM 20704 (0x50E0)
    VERBOSE: Starting background worker for page UpdateInstall.ViewModels.CheckConfigViewModel. CMRegisterUpdate 1/1/2020 10:29:17 AM 20704 (0x50E0)
    Configuration check page activated, checking applicability. CMRegisterUpdate 1/1/2020 10:29:17 AM 22808 (0x5918)
    Searching for local Configuration Manager installation properties. CMRegisterUpdate 1/1/2020 10:29:17 AM 22808 (0x5918)
    Retreived setup information from Software\Microsoft\SMS\Operations Management CMRegisterUpdate 1/1/2020 10:29:17 AM 22808 (0x5918)
    Installation Directory: CMRegisterUpdate 1/1/2020 10:29:17 AM 22808 (0x5918)
    Full Version : 5.0.8913.1000 CMRegisterUpdate 1/1/2020 10:29:17 AM 22808 (0x5918)
    Type : None CMRegisterUpdate 1/1/2020 10:29:17 AM 22808 (0x5918)
    Read SMS Identification from Software\Microsoft\SMS\Identification CMRegisterUpdate 1/1/2020 10:29:17 AM 22808 (0x5918)
    Installation Directory: C:\Program Files\Microsoft Configuration Manager CMRegisterUpdate 1/1/2020 10:29:17 AM 22808 (0x5918)
    Type : Primary CMRegisterUpdate 1/1/2020 10:29:17 AM 22808 (0x5918)
    Language : English:00000409 CMRegisterUpdate 1/1/2020 10:29:17 AM 22808 (0x5918)
    Site Server : SCCM.sniggitty.com CMRegisterUpdate 1/1/2020 10:29:17 AM 22808 (0x5918)
    Site Code : USD CMRegisterUpdate 1/1/2020 10:29:17 AM 22808 (0x5918)
    Read offline value from Software\Microsoft\SMS\Components\SMS_DMP_UPLOADER CMRegisterUpdate 1/1/2020 10:29:17 AM 22808 (0x5918)
    Offline Mode : 0 CMRegisterUpdate 1/1/2020 10:29:17 AM 22808 (0x5918)
    The update has a minimum version requirement : 5.0.8913.0 CMRegisterUpdate 1/1/2020 10:29:17 AM 22808 (0x5918)
    The update has a maximum version requirement : 5.0.8913.9999 CMRegisterUpdate 1/1/2020 10:29:17 AM 22808 (0x5918)
    The local site version is : 5.0.8913.1000 CMRegisterUpdate 1/1/2020 10:29:17 AM 22808 (0x5918)
    The local machine is a service connection point and version 5.0.8913.1000 is between(inclusive) version 5.0.8913.0 and 5.0.8913.9999 CMRegisterUpdate 1/1/2020 10:29:17 AM 22808 (0x5918)
    Sequencer: State change event recieved, new state is ‘CheckConfigSucceeded’, reason for state change is ‘None’. CMRegisterUpdate 1/1/2020 10:29:17 AM 22808 (0x5918)
    Background worker has completed for page ‘UpdateInstall.ViewModels.CheckConfigViewModel’. CMRegisterUpdate 1/1/2020 10:29:17 AM 20704 (0x50E0)
    Navigating to next page. CMRegisterUpdate 1/1/2020 10:29:17 AM 20704 (0x50E0)
    VERBOSE: Starting background worker for page UpdateInstall.ViewModels.RegisterUpdateViewModel. CMRegisterUpdate 1/1/2020 10:29:17 AM 20704 (0x50E0)
    Registering update ‘Configuration Manager 1910 Hotfix (KB4535384)’ with Configuration Manager… CMRegisterUpdate 1/1/2020 10:29:17 AM 22808 (0x5918)
    VERBOSE: manifest full path ‘c:\a71ebf10192caa81110d3242e71fb073\cm1910-kb4535384.configmgr.update.manifest.cab’ CMRegisterUpdate 1/1/2020 10:29:17 AM 22808 (0x5918)
    VERBOSE: payload full path ‘c:\a71ebf10192caa81110d3242e71fb073\092F0EDD-5793-48CA-882F-E85CB1B4A2D1.cab’ CMRegisterUpdate 1/1/2020 10:29:17 AM 22808 (0x5918)
    Copying file ‘cm1910-kb4535384.configmgr.update.manifest.cab’ to location ‘C:\Program Files\Microsoft Configuration Manager\EasySetupPayload\offline.’ CMRegisterUpdate 1/1/2020 10:29:17 AM 22808 (0x5918)
    Copying file ‘092F0EDD-5793-48CA-882F-E85CB1B4A2D1.cab’ to location ‘C:\Program Files\Microsoft Configuration Manager\EasySetupPayload\offline’. CMRegisterUpdate 1/1/2020 10:29:17 AM 22808 (0x5918)
    User has requested that no DMP thread restart should occur, all done. CMRegisterUpdate 1/1/2020 10:29:18 AM 22808 (0x5918)
    Sequencer: State change event recieved, new state is ‘RegisterUpdateSucceeded’, reason for state change is ‘None’. CMRegisterUpdate 1/1/2020 10:29:18 AM 22808 (0x5918)
    Background worker has completed for page ‘UpdateInstall.ViewModels.RegisterUpdateViewModel’. CMRegisterUpdate 1/1/2020 10:29:18 AM 20704 (0x50E0)
    Navigating to next page. CMRegisterUpdate 1/1/2020 10:29:18 AM 20704 (0x50E0)
    Configuration Manager Update Registration is exiting. CMRegisterUpdate 1/1/2020 10:29:23 AM 20704 (0x50E0)

    -Help! Thanks

    Reply
    • Andrej Prijmak says:
      January 2, 2020 at 2:02 am

      Hello, did you get https://support.microsoft.com/help/4535819 in Updates and Servicing node? If yes – then you already have KB4535384.
      Additional hotfixes contained in KB4535819
      KB 4535384: Client update available for Configuration Manager current branch, version 1910 early update ring
      Also, did you run this file https://download.microsoft.com/download/6/7/d/67d8d96c-86c4-4337-b949-e2b3187e2bbb/KB4535384/CM1910-KB4535384.ConfigMgr.Update.exe?

      Reply

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Translation

English中文(简体)DanskNederlandsFrançaisDeutschItaliano한국어PolskiPortuguêsRomânăEspañolУкраїнська
by Transposh - translation plugin for wordpress

Popular Posts

System Requirements for Windows Server 2016
Windows Server
Configuration Manager Query Collection List
Configuration Manager Query Collection List
ConfigMgr
Structured/Managed Navigation enabled on Modern Pages in Classic Team Sites
Tech
SCCM Failed to get DP locations as the expected version from MP
ConfigMgr

Recent Posts

Installing and Configuring Fail2ban for SSH Protection on Ubuntu 24.04
Linux
Enabling and Configuring FirewallD on AlmaLinux
Linux
User Creation and SSH Key Setup in AlmaLinux
Linux
How to reset password on AlmaLinux
Linux

© 2023 EnterinIT

Go to mobile version
adbanner
Welcome Back!

Sign in to your account

Username or Email Address
Password

Lost your password?