Windows Updates Server 2016 doesn 't work

[Milkachillt13]

Thats the link of the log before dism:

CBS.zip

 

[philc43]

Yes, you can send the folder now so I can be looking into it for you while you try DISM.

Thanks!

 

[Milkachillt13]

I say Thank you for yout Support =)

 

[Milkachillt13]

CBS.zip

 

[Milkachillt13]

I'm not sure if DISM works cause there ist the same window since 15/ 20 min

 

[Milkachillt13]

 

[Milkachillt13]

Sry now it starts

 

[Milkachillt13]

Also the Dism log if its important.
The DISM is at 8,5 % so that needs time =/

 

[philc43]

Yes, patience is required for it to complete.

The problem which is identified in the logs relates to some components that are updated as part of the KB5010359 update. Here are the sections from the logs:

2022-03-01 12:34:13, Info                  CSI    000004a6 Begin executing advanced installer phase 34 index 1768 (sequence 1803)
    Old component: [l:186 ml:187]'Microsoft-Windows-Security-SPP-Component-SKU-csvlk-pack-License, Culture=neutral, Version=10.0.14393.2969, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=x86, versionScope=NonSxS'
    New component: [l:186 ml:187]'Microsoft-Windows-Security-SPP-Component-SKU-csvlk-pack-License, Culture=neutral, Version=10.0.14393.4946, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=x86, versionScope=NonSxS'
    Install mode: install
    Smart installer: FALSE
    Installer ID: {1b265fd2-721c-4e59-ad55-9d102a5d1d7f}
    Installer name: 'SppInstaller'
2022-03-01 12:34:13, Info                  CSI    000004a7 Performing 1 operations as follows:
  (0)  LockComponentPath: flags: 0 comp: {l:16 b:c240c446602dd8016c040000bc07ec07} pathid: {l:16 b:c240c446602dd8016d040000bc07ec07} path: [l:118]'\SystemRoot\WinSxS\x86_microsoft-windows-s..-csvlk-pack-license_31bf3856ad364e35_10.0.14393.2969_none_82719a20c7070769' pid: 7bc starttime: 132906079298834264
2022-03-01 12:34:13, Info                  CSI    000004a8 Performing 1 operations as follows:
  (0)  LockComponentPath: flags: 0 comp: {l:16 b:ecaec446602dd8016e040000bc07ec07} pathid: {l:16 b:ecaec446602dd8016f040000bc07ec07} path: [l:118]'\SystemRoot\WinSxS\x86_microsoft-windows-s..-csvlk-pack-license_31bf3856ad364e35_10.0.14393.4946_none_826fe1b0c7088226' pid: 7bc starttime: 132906079298834264
2022-03-01 12:34:14, Info                  CBS    Progress: UI message updated. Operation type: Update. Stage: 1 out of 1. Percent progress: 79.
2022-03-01 12:34:24, Info                  CSI    000004a9@2022/3/1:11:34:24.732 'SPP Installer: SLpUpdateComponentTokens completed with hr=0x8007000d'

2022-03-01 12:34:24, Info                  CSI    000004aa@2022/3/1:11:34:24.733 'SPP Installer: ProcessInstallOrUninstall (x86_Microsoft-Windows-Security-SPP-Component-SKU-csvlk-pack-License_31bf3856ad364e35_10.0.14393.4946_neutral_abf80624) completed with hr=0x8007000d'

2022-03-01 12:34:24, Error                 CSI    000004ab@2022/3/1:11:34:24.734 (F) CMIADAPTER: Inner Error Message from AI HRESULT = HRESULT_FROM_WIN32(ERROR_INVALID_DATA)
 [
'Die Daten sind unzul\u00e4ssig.

2022-03-01 12:34:29, Info                  CSI    000004b6 Begin executing advanced installer phase 34 index 1769 (sequence 1804)
    Old component: [l:188 ml:189]'Microsoft-Windows-Security-SPP-Component-SKU-csvlk-pack-License, Culture=neutral, Version=10.0.14393.2969, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS'
    New component: [l:188 ml:189]'Microsoft-Windows-Security-SPP-Component-SKU-csvlk-pack-License, Culture=neutral, Version=10.0.14393.4946, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS'
    Install mode: install
    Smart installer: FALSE
    Installer ID: {1b265fd2-721c-4e59-ad55-9d102a5d1d7f}
    Installer name: 'SppInstaller'
2022-03-01 12:34:29, Info                  CSI    000004b7 Performing 1 operations as follows:
  (0)  LockComponentPath: flags: 0 comp: {l:16 b:8fb06d50602dd80173040000bc07ec07} pathid: {l:16 b:8fb06d50602dd80174040000bc07ec07} path: [l:120]'\SystemRoot\WinSxS\amd64_microsoft-windows-s..-csvlk-pack-license_31bf3856ad364e35_10.0.14393.2969_none_de9035a47f64789f' pid: 7bc starttime: 132906079298834264
2022-03-01 12:34:29, Info                  CSI    000004b8 Performing 1 operations as follows:
  (0)  LockComponentPath: flags: 0 comp: {l:16 b:d4fe6d50602dd80175040000bc07ec07} pathid: {l:16 b:d4fe6d50602dd80176040000bc07ec07} path: [l:120]'\SystemRoot\WinSxS\amd64_microsoft-windows-s..-csvlk-pack-license_31bf3856ad364e35_10.0.14393.4946_none_de8e7d347f65f35c' pid: 7bc starttime: 132906079298834264
2022-03-01 12:34:30, Info                  CBS    Startup: Changing logon timeout to a sliding window timeout: 900000
2022-03-01 12:34:31, Info                  CSI    000004b9@2022/3/1:11:34:31.449 'SPP Installer: SLpUpdateComponentTokens completed with hr=0x8007000d'

2022-03-01 12:34:31, Info                  CSI    000004ba@2022/3/1:11:34:31.450 'SPP Installer: ProcessInstallOrUninstall (amd64_Microsoft-Windows-Security-SPP-Component-SKU-csvlk-pack-License_31bf3856ad364e35_10.0.14393.4946_neutral_de01ec04) completed with hr=0x8007000d'

2022-03-01 12:34:31, Error                 CSI    000004bb@2022/3/1:11:34:31.450 (F) CMIADAPTER: Inner Error Message from AI HRESULT = HRESULT_FROM_WIN32(ERROR_INVALID_DATA)
 [
'Die Daten sind unzul\u00e4ssig.

2022-03-01 12:34:31, Info                  CSI    000004c1 Begin executing advanced installer phase 34 index 1770 (sequence 1805)
    Old component: [l:192 ml:193]'Microsoft-Windows-Security-SPP-Component-SKU-ServerStandard-License, Culture=neutral, Version=10.0.14393.2969, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS'
    New component: [l:192 ml:193]'Microsoft-Windows-Security-SPP-Component-SKU-ServerStandard-License, Culture=neutral, Version=10.0.14393.4946, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS'
    Install mode: install
    Smart installer: FALSE
    Installer ID: {1b265fd2-721c-4e59-ad55-9d102a5d1d7f}
    Installer name: 'SppInstaller'
2022-03-01 12:34:31, Info                  CSI    000004c2 Performing 1 operations as follows:
  (0)  LockComponentPath: flags: 0 comp: {l:16 b:ba6d7a51602dd80177040000bc07ec07} pathid: {l:16 b:ba6d7a51602dd80178040000bc07ec07} path: [l:120]'\SystemRoot\WinSxS\amd64_microsoft-windows-s..verstandard-license_31bf3856ad364e35_10.0.14393.2969_none_051b2c3957ed42bc' pid: 7bc starttime: 132906079298834264
2022-03-01 12:34:31, Info                  CSI    000004c3 Performing 1 operations as follows:
  (0)  LockComponentPath: flags: 0 comp: {l:16 b:a1947a51602dd80179040000bc07ec07} pathid: {l:16 b:a1947a51602dd8017a040000bc07ec07} path: [l:120]'\SystemRoot\WinSxS\amd64_microsoft-windows-s..verstandard-license_31bf3856ad364e35_10.0.14393.4946_none_051973c957eebd79' pid: 7bc starttime: 132906079298834264
2022-03-01 12:34:33, Info                  CSI    000004c4@2022/3/1:11:34:33.026 'SPP Installer: SLpUpdateComponentTokens completed with hr=0x8007000d'

2022-03-01 12:34:33, Info                  CSI    000004c5@2022/3/1:11:34:33.027 'SPP Installer: ProcessInstallOrUninstall ([HI]amd64_rosoft-Windows[/HI]-Security-SPP-Component-SKU-ServerStandard-License_31bf3856ad364e35_10.0.14393.4946_neutral_4829ace3) completed with hr=0x8007000d'

2022-03-01 12:34:33, Error                 CSI    000004c6@2022/3/1:11:34:33.027 (F) CMIADAPTER: Inner Error Message from AI HRESULT = HRESULT_FROM_WIN32(ERROR_INVALID_DATA)
 [
'Die Daten sind unzul\u00e4ssig.

In each case there is an attempt to bring the old component (ver 10.0.14393.2969) to the new component (ver 10.0.14393.4946), it looks as if there is invalid data.

In the last case I can see corruption of the data as highlighted. It should read amd64_Microsoft-Windows...

This suggests to me there may have been some data corruption during the downloading of data for the updates. Have you experienced any issues on the server that might suggest you have drive problems or data corruption?

 

[Milkachillt13]

No I didnt experienced any issues on the server about drive problems or data corruption.
Its a virtuell drive.

Do you have any idea for a solution?

Or did the DISM help if it will be finished ?
DISM is at 19% so it takes lot of time.
If we cant find a solution for today i will go to the snapshot from the moring and we try to fix with that snapshot ?

 

[philc43]

Yes, I agree with you that if you can revert to the point before you started doing the updates it will allow you to use the server as long as you do not install the KB5010359 update.

I would be happy to help you work on fixing it - would you set up a separate Virtual Server for doing this?

 

[Milkachillt13]

I'm really thankful for your help.
No i have lots of Snapshot of the Server but its a good idea maybe i do a extern virtual Server to try this.
But maybe i will install a new.
Should i try to uninstall KB5010359?

 

[philc43]

I did wonder about trying to uninstall KB5010359 but I am not sure if it even got that far to allow you to uninstall it. You could try and let me know. See if it is listed as one of the installed updates in Control Panel. If so you should be able to uninstall it.

 

[Milkachillt13]

so that doesnt work i went back to the snapshot from the morning and start running the Dism there so it can run over night.
Maybe there is a solution.
I let you know tomorrow how it looks.
thank you so much for your help =)

 

[Milkachillt13]

Hi philc43,

so i go back to the snapshot of yesterday morning and run a sfc /scannow.
All of this was okay. Now the Server runs the Windows updates. After that i do a snapshot and uninstall the KB5010359.
At the evening i will do a sfc /scannow again and make a snapshot the i try to reboot.
what do you think ?
Here ist the link for the CBS folder after the sfcfix an the sfc /scannow =)
CBS Neu.zip

 

[Milkachillt13]

and also the Dism file from now i hope we can find a solution together =)

 

[philc43]

I will also need the CBS.log after the DISM restore completed.

 

[philc43]

Hi philc43,

so i go back to the snapshot of yesterday morning and run a sfc /scannow.
All of this was okay. Now the Server runs the Windows updates. After that i do a snapshot and uninstall the KB5010359.
At the evening i will do a sfc /scannow again and make a snapshot the i try to reboot.
what do you think ?
Here ist the link for the CBS folder after the sfcfix an the sfc /scannow =)
CBS Neu.zip

Did you let the DISM restore run to completion? DISM is able to fix corruption but sometimes it can't and it reports the problem in the CBS.log. That is why it is important for me to see the CBS log after the DISM restore has finished.

 

[philc43]

I have been through the latest logs and gone back to early February where I found some more corruption which needs fixing. It would be worth doing this fix before you start any updates or reboots. This fix provides a new zip file which has the same name as the previous one. The older one can be deleted.

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
2. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
3. Save any open documents and close all open windows.
4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
6. SFCFix will now process the script.
7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
8. Attach this file into your next post for me to check.

 

[Milkachillt13]

Hi this is the log after the dism.
and also dism

dism says error 14 not enough storage but i have lots of storage and ram too