M
Mertz2019
Hello,
Hoping someone can help me with a miracle so I won't have to call Microsoft. I have one 2016 server that will not run cumulative updates. The smaller updates/office updates run fine. Just the cumulative fail. I've been combing the forums and the few people that have the exact same error had the App Readiness services disabled. I do not.
The update appears to install whether I install it manually or via Windows Update and during reboot it gets to 99% then says there was an error and it rolls back the update.
I've tried the sfc /scannow (which always performs a repair, but has issues access windows update during these) and the dism /online /cleanup-image /restorehealth without any success. I've reset Windows update components multiple times. I've tried the sconfig install updates without any luck. Pretty much at wit's end.
Error from the CSB.log file is below and it's the same every time.
Any help would be appreciated. thanks.
\Software\Microsoft\Windows\CurrentVersion\Appx\AppxAllUserStore\S-1-5-21-44198310-653672281-4167094726-500.
2019-01-22 14:20:18, Error CSI 000004ff@2019/1/22:20:20:18.563 (F) onecore\base\appmodel\inboxappinstallerai\appxreg.cpp(94): Error HRESULT_FROM_WIN32(ERROR_FILE_NOT_FOUND) originated in function Windows::WCP::AppXRegistration::BasicInstaller::Install expression: RDSAppXOnlineNotifyPackageChanges(APPCHANGETYPE_INBOX)
[gle=0x80004005]
2019-01-22 14:20:18, Info CBS Added C:\Windows\Logs\CBS\CBS.log to WER report.
2019-01-22 14:20:18, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20190122200752.log to WER report.
2019-01-22 14:20:18, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20190122170905.log to WER report.
2019-01-22 14:20:18, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20190118205349.log to WER report.
2019-01-22 14:20:18, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20190118191821.log to WER report.
2019-01-22 14:20:18, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20190118184137.log to WER report.
2019-01-22 14:20:18, Info CBS Could not get active session for current session file logging [HRESULT = 0x80004003 - E_POINTER]
2019-01-22 14:20:18, Info CBS Not able to add pending.xml.bad to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2019-01-22 14:20:18, Info CSI 00000500 Performing 1 operations as follows:
(0) LockComponentPath: flags: 0 comp: {l:16 b:da47a8e48fb2d401e8030000440b980b} pathid: {l:16 b:da47a8e48fb2d401e9030000440b980b} path: [l:115]'\SystemRoot\WinSxS\x86_microsoft.windows.s..ation.badcomponents_31bf3856ad364e35_10.0.14393.0_none_09e78f632173f4c5' pid: b44 starttime: 131926619010027014
2019-01-22 14:20:18, Error [0x018051] CSI 00000501 (F) Failed execution of queue item Installer: AppX Registration Installer ({f1aab1ba-6ee0-4d94-baeb-c9fd61f365cf}) with HRESULT HRESULT_FROM_WIN32(ERROR_FILE_NOT_FOUND). Failure will not be ignored: A rollback will be initiated after all the operations in the installer queue are completed; installer is reliable[gle=0x80004005]
2019-01-22 14:20:18, Info CBS Added C:\Windows\Logs\CBS\CBS.log to WER report.
Continue reading...
Hoping someone can help me with a miracle so I won't have to call Microsoft. I have one 2016 server that will not run cumulative updates. The smaller updates/office updates run fine. Just the cumulative fail. I've been combing the forums and the few people that have the exact same error had the App Readiness services disabled. I do not.
The update appears to install whether I install it manually or via Windows Update and during reboot it gets to 99% then says there was an error and it rolls back the update.
I've tried the sfc /scannow (which always performs a repair, but has issues access windows update during these) and the dism /online /cleanup-image /restorehealth without any success. I've reset Windows update components multiple times. I've tried the sconfig install updates without any luck. Pretty much at wit's end.
Error from the CSB.log file is below and it's the same every time.
Any help would be appreciated. thanks.
\Software\Microsoft\Windows\CurrentVersion\Appx\AppxAllUserStore\S-1-5-21-44198310-653672281-4167094726-500.
2019-01-22 14:20:18, Error CSI 000004ff@2019/1/22:20:20:18.563 (F) onecore\base\appmodel\inboxappinstallerai\appxreg.cpp(94): Error HRESULT_FROM_WIN32(ERROR_FILE_NOT_FOUND) originated in function Windows::WCP::AppXRegistration::BasicInstaller::Install expression: RDSAppXOnlineNotifyPackageChanges(APPCHANGETYPE_INBOX)
[gle=0x80004005]
2019-01-22 14:20:18, Info CBS Added C:\Windows\Logs\CBS\CBS.log to WER report.
2019-01-22 14:20:18, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20190122200752.log to WER report.
2019-01-22 14:20:18, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20190122170905.log to WER report.
2019-01-22 14:20:18, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20190118205349.log to WER report.
2019-01-22 14:20:18, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20190118191821.log to WER report.
2019-01-22 14:20:18, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20190118184137.log to WER report.
2019-01-22 14:20:18, Info CBS Could not get active session for current session file logging [HRESULT = 0x80004003 - E_POINTER]
2019-01-22 14:20:18, Info CBS Not able to add pending.xml.bad to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2019-01-22 14:20:18, Info CSI 00000500 Performing 1 operations as follows:
(0) LockComponentPath: flags: 0 comp: {l:16 b:da47a8e48fb2d401e8030000440b980b} pathid: {l:16 b:da47a8e48fb2d401e9030000440b980b} path: [l:115]'\SystemRoot\WinSxS\x86_microsoft.windows.s..ation.badcomponents_31bf3856ad364e35_10.0.14393.0_none_09e78f632173f4c5' pid: b44 starttime: 131926619010027014
2019-01-22 14:20:18, Error [0x018051] CSI 00000501 (F) Failed execution of queue item Installer: AppX Registration Installer ({f1aab1ba-6ee0-4d94-baeb-c9fd61f365cf}) with HRESULT HRESULT_FROM_WIN32(ERROR_FILE_NOT_FOUND). Failure will not be ignored: A rollback will be initiated after all the operations in the installer queue are completed; installer is reliable[gle=0x80004005]
2019-01-22 14:20:18, Info CBS Added C:\Windows\Logs\CBS\CBS.log to WER report.
Continue reading...