Windows Updates Server 2016 doesn 't work

There was nothing useful in those logs. Have you run the fix provided in post #39 yet?

Once you have done that then rerun SFC /scannow and after it has completed please zip up and share the complete CBS folder.

Thanks.
 
There was one more corruption identified but not able to be repaired:

Code: 
Checking System Update Readiness.

(p)    CSI Payload Corrupt            amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.14393.206_none_43639e5b651394af\dpx.dll
Repair failed: Missing replacement payload.

Summary:
Operation: Detect and Repair
Operation result: 0x8007000e
Last Successful Step: Entire operation completes.
Total Detected Corruption:    1
    CBS Manifest Corruption:    0
    CBS Metadata Corruption:    0
    CSI Manifest Corruption:    0
    CSI Metadata Corruption:    0
    CSI Payload Corruption:    1
Total Repaired Corruption:    0
    CBS Manifest Repaired:    0
    CSI Manifest Repaired:    0
    CSI Payload Repaired:    0
    CSI Store Metadata refreshed:    True

Please do the following to fix this:

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.
 

Attachments

There are no further errors showing. I guess now is the time to try a reboot.
 
Ok perfect i will try at the evening to reboot the server.
Thank you so much for your help
 
Hi
so it works, the only problem i have is the update KB5010359 when im installing this i have the same problem with the boot loop =/ so i went back to the snapshot where it was working 2 hours ago.
You have an idea what this could be ?
 
If it was the same problem as before one of the components in the update was not updating: see post #29

It is possible that you will get success by downloading the update from the Microsoft Catalogue and then installing it manually. Worth a try if you have the time and at least you know you can revert back to a working snapshot.
 
yes its the same problem.
I will try to do a snapshot now an then install it manually.
Other ideas or do you think this is the only solution ?
I do the window update service as disable cause it always try to install the Update
 
If the manual update fails I will have a think about others ways to install it and also search for any sign of problems emerging as others attempt this update.
 
Milkachillt13 said:
yes its the same problem.
I will try to do a snapshot now an then install it manually.
Other ideas or do you think this is the only solution ?
I do the window update service as disable cause it always try to install the Update
Click to expand...
Did you have any success with the manual install?
 
Hi Philc43,

sry my late answer i was off till toda.
I tried to do the update manual but i have the same problem =/
 
Please post the CBS logs again so that I can check to see if it is the same errors.
 
If its ok for you i will do that tomorrow evening. Icant boot in safe mode so i need to go back to the snapshot an install the update again so taht needs time ^^ but i will start it at 4 pm
 
Milkachillt13 said:
If its ok for you i will do that tomorrow evening. Icant boot in safe mode so i need to go back to the snapshot an install the update again so taht needs time ^^ but i will start it at 4 pm
Click to expand...
That's fine. Please try and do the manual update by the following method.

Install Update with DISM

  1. Copy the MSU file to a convenient location (such as C:\temp).
  2. Click on the Start button and in the search box, type Command Prompt
  3. When you see Command Prompt on the list, right-click on it and select Run as administrator
  4. When command prompt opens, copy and paste the following commands into it, press enter after each

    cd C:\temp
    replace C:\temp with your path if different

    expand windows10.0-kb5010359-x64_f0b427c713754e50609ad0fa7054607a5d404f37.msu -f:* C:\temp

    DISM.exe /Online /Add-Package /PackagePath:C:\temp\windows10.0-kb5010359-x64.cab
  5. You should receive the message:
    The operation completed successfully.
    Make sure to allow the computer to restart if prompted.
  6. If you receive any other message:
    Post a screenshot of the Command Prompt window.
    Zip and attach the file C:\Windows\Logs\CBS\CBS.log
 
Hi Philc43,

got the same Problem.
The Server went back to the status before the Update.
I Send you the whole CBS Folder in attach.
 

Attachments

Yes, it is the same three files that will not update:

Code: 
    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'

    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'

    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'

I have compared this to my Server 2016 installation where this update worked and I can see the following:

Code: 
    Old component: [l:188 ml:189]'Microsoft-Windows-Security-SPP-Component-SKU-csvlk-pack-License, Culture=neutral, Version=10.0.14393.4402, 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'

It seems to me that the jump from version 10.0.14393.2969 in your case is not working.
I am wondering if there is a missing update from much earlier on that Microsoft is expecting to be present for this CU to work.
Will continue to look into it for you.
 
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