[SOLVED] Server 2016 Cumulative Updates Rolling Back

J

jaycee5585

Well-known member
Joined
Apr 27, 2022
Posts
52
I have a Server 2016 system that will not update itself. The updates install, but after reboot it reaches around 95% then changes to 'Rolling Back'. It seems to be only the Cumulative Updates that have issues. I have tried manually installing the latest SSU and CU *.msu packages to no avail. We do have a WSUS setup, but I have also tried having it download the updates directly from Microsoft with the same results. Any help would be appreciated, as I am at a loss on how to proceed with fixing this issue.

*****SFC*****
"Windows Resource Protection did not find any integrity violations"

*****DISM*****
"The operation completed successfully."

*****SFCFix*****
SFCFix version 3.0.2.1 by niemiro.
Start time: 2022-04-27 15:24:54.028
Microsoft Windows Server 10 Build 14393 - amd64
Not using a script file.




AutoAnalysis::
SUMMARY: No corruptions were detected.
AutoAnalysis:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2022-04-27 15:25:21.711
----------------------EOF-----------------------

*****ComponentsScanner*****
ComponentsScanner Version 1.3.0.0 by sysnative.com
Windows Version: Windows Server 2016 Standard x64 (10.0.14393.4825)
Start time: 4/27/2022 3:34:00 PM
Hive scanned: %windir%\System32\config\COMPONENTS
Number of keys: 171986
Number of values: 597267

==== Critical Errors ====
None

==== Corrupt Key Names ====
None

==== Corrupt Value Names ====
None

==== Corrupt Value Data Type ====
None

==== Corrupt Value Data ====
None

==== Repair Log ====
No possible repairs

Finish Time: 4/27/2022 3:34:35 PM. Corruption scan time: 5.0825297s
===========================EOF===========================

*****CBS Logs*****
CBS.zip
 
And... I seem to have posted under the wrong forum heading by mistake. My apologies. Feel free to move this or delete if needed.
 
Hi and welcome to Sysnative,

Open the following directory: "C:\Windows\System32\spp\tokens\skus" which folders are present here?
 
Last edited:
Thanks for the reply!

It's Windows Server 2016 Standard.
In the skus folder, we have the following folders: csvlk-pack, ServerStandard, and ServerStandardEval.
 
Hi,

Open an elevated command prompt and run the following command:
Code: 
slmgr /xpr
You now see the following message like this: please post the result of this.

6273dfb073b79-SLMGR.png
 
Hi,

Please run the following command in a elevated command prompt.
Code: 
ren "%SystemRoot%\System32\spp\tokens\skus\ServerStandardEval" ServerStandardEval.old
Reboot the server and try to update, if it fails attach a new copy of the CBS log.
 
The update downloaded, rebooted the server, setup got to 99% then failed. New CBS log attached.

updating.JPG
failed.JPG
 
Hi,

  • Open Windows Explorer and browse to the C:\Windows\INF folder.
  • Right-click on the file setupapi.dev and choose Send to > Compressed (zipped) folder.
  • Now the message will appear, "Windows cannot create the Compressed (zipped) Folder here. Do you want it to be placed on the desktop instead?"
  • Click on the Yes button here.
618e949e09fef-CBS-Folder.png

  • Attach the file setupapi.dev.zip in your next reply.
 
Please check if the following folder is renamed to "ServerStandardEval.old"

%SystemRoot%\System32\spp\tokens\skus\ServerStandardEval
 
Hi,

Step#1 - Capture Process Monitor BootLog
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Select the Options....Enable Boot Logging option. A Enable Boot Logging dialog will come up. Just click OK.
3. Create a folder on your desktop named BootLog.
4. Attempt to install the update just like you have in the past. Let the machine reboot and revert just like it has in the past.
5. After the machine has rebooted and come back up to the desktop, open Process Monitor again. A message box will come up telling you that a log of boot-time activity was created and ask if you wish to save it. Click Yes and save to the BootLog folder on your desktop.
6. This may take some time as it converts the boot-time data. Allow it to finish.
7. Zip up the entire BootLog folder on your desktop and upload to a file sharing service of your choice for my review. Examples of services to upload to are Dropbox or OneDrive or SendSpace
 
Hi,

I can't open the bootlog trace: The file 'C:\Users\User\Desktop\Bootlog.pml' was not closed cleanly during capture and is corrupt.

Please can you try it again to run Process Monitor with Boot Logging?

Which KB number has the problematic update?

Please run the following command in a elevated command prompt as well. Attach UpdateList.txt to your next post.
Code: 
wmic qfe list brief /format:texttablewsys > "%USERPROFILE%\Desktop\UpdateList.txt"
 
Last edited:
Any cumulative KB does it. Currently, KB5012596 is trying to install.

UpdateList.txt is attached.

New Bootlog.pml: BootLog.zip
(I verified myself that it could be opened this time.)
 

Attachments

Hi,

Do you have the ability to re-activate this server? If possible perform the following:
Open a elevated command prompt and run the following commands one at a time. (replace the alphabet characters with the productcode for this server)

Code: 
slmgr /ipk ABCDE FGHIJ KLMNO PQRST UVWXY
slmgr /ato

Let me know the result of both commands
 
Last edited:
In looking to reactivate it, I realized that the license key assigned to it was overused. I assigned an available key using slmgr /ipk, then ran slmgr /ato.

slmgr /ipk output: 'license successfully installed'
slmgr /ato output: 'activation successful'

I am trying the update again, and I will update you on the progress.
 
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