Windows 10 – Feature Update 2004 not installing on reboot

Question

Hi,

we tried to run a first 2004 update test devices but sadly we have a strange problem.

After the clients installed the update in Software Center and click on restart now – Windows is not installing anything. After a reboot the Software Center says “Update installed” but after a policy rerun, it’s again showing as available.
Oh and yes the system is not on 2004 after the restart.
Does anyone have an idea? Its occuring on many different devices and also VMs we used for testing, no errors or whatever.

Left side is dism.log after the update was finished in Software Center

right side is CBS.log after restarting the device via “update and restart”

2020 07 24 142216 - How To Manage Devices Community Forum - Welcome to the world of Device Management! This is community build by Device Management Admins for Device Management Admins❤️ Ask your questions!! We are here to help you! - Windows 10 - Feature Update 2004 not installing on reboot

 

Kind regards,
Max

in progress 0
Mäx 2 months 5 Answers 195 views Beginner 0

Answers ( 5 )

  1. Finally i got some time. i checked the event logs between pressing installing and the machine restarting and the only thing thats getting logged addressing the update is this:

    Installation Started: Windows has started installing the following update: Featureupdate for Windows 10 (Business-Editions), Version 2004, en-us x64

    and after a few seconds – because the pre-reboot installation is already finished:

    Installation Successful: Windows successfully installed the following update: Featureupdate for Windows 10 (Business-Editions), Version 2004, en-us x64

    After pressing restart here are only the normal logon events etc.
    I don’t see a single event showing any errors besides DistributedCOM already minutes after the restart.

  2. Yes VMs and physical devices share the same bahivour. i will check the event logs later when i got some time.

    thanks!

  3. I hope same issue with both VMs and physical devices .. that means .. No driver issues…

    I can’t notice any significant entries in the logs …

    Wondering whether you checked the event logs to get more clue about this pls

  4. The Log files are here.
    https://1drv.ms/u/s!AvT7TXwtUgLcmflfDDk8wozsrpn4Zw?e=pz7Ppy

    Didn’t really know when which device restarted tbh but both log files are directly after the update finished and the only thing that changed is that this is added in the CBS.log everytime i restart the client:

    2020-07-24 13:43:18, Info CBS TI: — Initializing Trusted Installer —
    2020-07-24 13:43:18, Info CBS TI: Last boot time: 2020-07-24 13:40:40.113
    2020-07-24 13:43:18, Info CBS Starting TrustedInstaller initialization.
    2020-07-24 13:43:18, Info CBS Lock: New lock added: CCbsPublicSessionClassFactory, level: 30, total lock:4
    2020-07-24 13:43:18, Info CBS Lock: New lock added: CCbsPublicSessionClassFactory, level: 30, total lock:5
    2020-07-24 13:43:18, Info CBS Lock: New lock added: WinlogonNotifyLock, level: 8, total lock:6
    2020-07-24 13:43:18, Info CBS Ending TrustedInstaller initialization.
    2020-07-24 13:43:18, Info CBS Starting the TrustedInstaller main loop.
    2020-07-24 13:43:18, Info CBS TrustedInstaller service starts successfully.
    2020-07-24 13:43:18, Info CBS No startup processing required, TrustedInstaller service was not set as autostart
    2020-07-24 13:43:18, Info CBS Startup processing thread terminated normally
    2020-07-24 13:43:18, Info CBS TI: Startup Processing completes, release startup processing lock.
    2020-07-24 13:43:19, Info CBS WU creates the package, AppID:CcmExec, UpdateID:{12ED00BE-112D-4C06-9248-AD372104ECA9}, revision: 201
    2020-07-24 13:43:19, Info CBS Read out cached applicability from TiLight for package: Package_for_RollupFix~31bf3856ad364e35~amd64~~18362.959.1.9, ApplicableState: 112, CurrentState:112
    2020-07-24 13:43:19, Info CBS WU creates the package, AppID:CcmExec, UpdateID:{E05529E2-F0CC-4A01-BD06-BE5118BD8BBD}, revision: 200
    2020-07-24 13:43:19, Info CBS Read out cached applicability from TiLight for package: Package_for_DotNetRollup~31bf3856ad364e35~amd64~~10.0.4190.4, ApplicableState: 112, CurrentState:112
    2020-07-24 13:43:19, Info CBS WU creates the package, AppID:CcmExec, UpdateID:{E39EAF57-AA06-4FA5-B4BA-713A639652E0}, revision: 200
    2020-07-24 13:43:19, Info CBS Read out cached applicability from TiLight for package: Package_for_KB4561600~31bf3856ad364e35~amd64~~10.0.1.1, ApplicableState: 112, CurrentState:112
    2020-07-24 13:43:19, Info CBS WU creates the package, AppID:CcmExec, UpdateID:{AE9AB665-45E0-4B62-A7A3-54C0D00F6BE0}, revision: 200
    2020-07-24 13:43:19, Info CBS Read out cached applicability from TiLight for package: Package_for_KB4565554~31bf3856ad364e35~amd64~~18362.957.1.3, ApplicableState: 112, CurrentState:112
    2020-07-24 13:43:19, Info CBS WU creates the package, AppID:CcmExec, UpdateID:{D7BA2F37-C50E-4634-BA99-329DEE3A2AD2}, revision: 203
    2020-07-24 13:43:19, Info CBS Read out cached applicability from TiLight for package: Package_for_KB4497165~31bf3856ad364e35~amd64~~10.0.4.1, ApplicableState: 112, CurrentState:112
    2020-07-24 13:43:22, Info CBS WU creates the package, AppID:CcmExec, UpdateID:{12ED00BE-112D-4C06-9248-AD372104ECA9}, revision: 201
    2020-07-24 13:43:22, Info CBS Read out cached applicability from TiLight for package: Package_for_RollupFix~31bf3856ad364e35~amd64~~18362.959.1.9, ApplicableState: 112, CurrentState:112
    2020-07-24 13:43:22, Info CBS WU creates the package, AppID:CcmExec, UpdateID:{E05529E2-F0CC-4A01-BD06-BE5118BD8BBD}, revision: 200
    2020-07-24 13:43:22, Info CBS Read out cached applicability from TiLight for package: Package_for_DotNetRollup~31bf3856ad364e35~amd64~~10.0.4190.4, ApplicableState: 112, CurrentState:112
    2020-07-24 13:43:22, Info CBS WU creates the package, AppID:CcmExec, UpdateID:{E39EAF57-AA06-4FA5-B4BA-713A639652E0}, revision: 200
    2020-07-24 13:43:22, Info CBS Read out cached applicability from TiLight for package: Package_for_KB4561600~31bf3856ad364e35~amd64~~10.0.1.1, ApplicableState: 112, CurrentState:112
    2020-07-24 13:43:22, Info CBS WU creates the package, AppID:CcmExec, UpdateID:{AE9AB665-45E0-4B62-A7A3-54C0D00F6BE0}, revision: 200
    2020-07-24 13:43:22, Info CBS Read out cached applicability from TiLight for package: Package_for_KB4565554~31bf3856ad364e35~amd64~~18362.957.1.3, ApplicableState: 112, CurrentState:112
    2020-07-24 13:43:22, Info CBS WU creates the package, AppID:CcmExec, UpdateID:{D7BA2F37-C50E-4634-BA99-329DEE3A2AD2}, revision: 203
    2020-07-24 13:43:22, Info CBS Read out cached applicability from TiLight for package: Package_for_KB4497165~31bf3856ad364e35~amd64~~10.0.4.1, ApplicableState: 112, CurrentState:112
    2020-07-24 13:44:13, Info CBS Trusted Installer signaled for shutdown, going to exit.
    2020-07-24 13:44:13, Info CBS Trusted Installer is shutting down because: SHUTDOWN_REASON_NOTIFICATION:PRESHUTDOWN
    2020-07-24 13:44:13, Info CBS Ending the TrustedInstaller main loop.
    2020-07-24 13:44:13, Info CBS Starting TrustedInstaller finalization.
    2020-07-24 13:44:13, Info CBS Lock: Lock removed: WinlogonNotifyLock, level: 8, total lock:6
    2020-07-24 13:44:13, Info CBS Ending TrustedInstaller finalization.

    Thats just constantly added when i restart the device via “update and restart”

  5. Can you attach the timelines of reboot here

    also it would be easy if you can attach the logs here

    2020-07-24 11:17:25, Info CBS Failed to resolve the capability in the fod metadata:Hello.Face.Migration.18331~~~~0.0.1.0 [HRESULT = 0x80070490 – ERROR_NOT_FOUND]

    [0x8007000e] StateStoreGetMountedImageWimbootEntries:(1285): Not enough memory resources are available to complete this operation.

    Ref – Comments in https://www.anoopcnair.com/upgrade-to-windows-10-2004-using-sccm-configmgr-servicing/

Leave an answer

Sorry, you do not have a permission to answer to this question .