[SOLVED] Cumulative Update for Windows Server 2016 for x64-based Systems (KB4338814) Fails

T

talishka

Well-known member
Joined
May 28, 2018
Posts
102
Location
Buenos Aires, AR.
Hi!

Im having issues applying this Cumulative update (KB4338814) on one of my 2016 servers.

I've already checked sfc and dism and the results are ok.

The CBS reports are attached.

Thanks in advance!
 

Attachments

Hi!

Code: 
2018-08-01 09:54:54, Info                  CSI    00000353 Performing 1 operations as follows:
  (0)  LockComponentPath: flags: 0 comp: {l:16 b:aa8121d89629d4013c030000f4051406} pathid: {l:16 b:aa8121d89629d4013d030000f4051406} path: [l:115]'\SystemRoot\WinSxS\x86_microsoft.windows.s..ation.badcomponents_31bf3856ad364e35_10.0.14393.0_none_09e78f632173f4c5' pid: 5f4 starttime: 131776012130139087
2018-08-01 09:54:54, Error      [0x01805b] CSI    00000354 (F) Failed execution of queue item Installer: Network Drivers ({a111f280-5923-47c0-9a68-d0bafb577901}) with HRESULT 800106d9 [Error,Facility=(0001),Code=1753 (0x06d9)].  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]
2018-08-01 09:54:54, Info                  CBS    Added C:\Windows\Logs\CBS\CBS.log to WER report.
2018-08-01 09:54:54, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20180801124650.log to WER report.
2018-08-01 09:54:54, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20180705144613.log to WER report.
2018-08-01 09:54:55, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20180705122043.log to WER report.
2018-08-01 09:54:55, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20180530130610.log to WER report.
2018-08-01 09:54:55, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20180530123301.log to WER report.
2018-08-01 09:54:55, Info                  CBS    Could not get active session for current session file logging [HRESULT = 0x80004003 - E_POINTER]
2018-08-01 09:54:55, Info                  CBS    Not able to add pending.xml.bad to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2018-08-01 09:54:55, Info                  CBS    Not able to add SCM.EVM to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2018-08-01 09:54:55, Info                  CSI    00000355 Creating NT transaction (seq 2), objectname '(null)'
2018-08-01 09:54:55, Info                  CSI    00000356 Created NT transaction (seq 2) result 0x00000000, handle @0x3f4
2018-08-01 09:54:55, Info                  CSI    00000357@2018/8/1:12:54:55.536 Beginning NT transaction commit...
2018-08-01 09:54:55, Info                  CSI    00000358@2018/8/1:12:54:55.615 CSI perf trace:
CSIPERF:TXCOMMIT;76059
2018-08-01 09:54:55, Info                  CSI    00000359 Begin executing advanced installer phase 31 index 0 (sequence 0)
    Old component: [l:0]''
    New component: [l:0]''
    Install mode: delta
    Smart installer: TRUE
    Installer ID: {f60fff05-7c5c-48dd-a1d2-b75aa14ad9b4}
    Installer name: 'Per-User Registry Installer'
2018-08-01 09:54:55, Info                  CSI    0000035a Warning - Overlap: Registry key collision for key \REGISTRY\USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Store\Configuration\, it is owned twice or has its security set twice


Please export the following key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList
Afterwards, please find the following folder in your WinSxS dir and copy it to your Desktop, zip it and attach it.
x86_microsoft.windows.s..ation.badcomponents_31bf3856ad364e35_10.0.14393.0_none_09e78f632173f4c5
 
Yes, only one nic. The Hyper-V role is installed but not configured at all. Not even the virtual switch. No vpn, nothing extra.

I've attached the img with the name of the nic and the actual driver.
 

Attachments

Open CMD as administrator, and type in these commands one by one pressing Enter after each.

SC config wuauserv start= auto
SC config bits start= auto
SC config cryptsvc start= auto
SC config trustedinstaller start= auto

Reboot.
 
Step#1 - Capture Process Monitor Trace
 1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Try installing the update just like you have in the past.
3. Stop Process Monitor as soon as it fails. You can simply do this by clicking the magnifying glass on the toolbar as shown below.
11908d1430506241-windows-updates-fail-repeatedly-stop-jpg


4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine.
5. Zip up and attach the LogFile.PML file as well as your CBS.log
 
Then a little adjustment in the ProcMon settings should be made:

1. Download this file: http://live.sysinternals.com/procmon.exe
2. Run ProcMon.exe
3. Go to the Options menu, and click Enable Boot Logging and then close Procmon.
4. Create a folder on your Desktop in which you'll save the logs.
5. Try installing only KB4056894 as you usually would.
6. Reboot your computer when requested.
7. Relaunch ProcMon. A dialogue box will appear asking if you wish to save the collected data. Please click Yes.
8. Save the file in the default format (.PML)
9. Save the file in a folder on your Desktop that you have created in Step 4.
10. Close ProcMon.
11. Zip up the entire folder containing ProcMon logs and upload to a filesharing service for me to review along with your CBS.log.
 
Well, suddenly the update installed correctly. I've installed from Microsoft instead of my WSUS Server.. mmm.. weird. The same update installed with no problem in a few servers.

Anyway, now it's working, thank you softwaremaniac! :)
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top