[SOLVED] Windows server 2016 cumulative updates install but rollback after reboot

Please run the following commands and post the result.
Code: 
reg delete "HKLM\Software\Microsoft\Windows NT\CurrentVersion\Schedule\Taskcache\Tasks\{D9D7C3E7-F174-43B3-9685-DAEB138995" /f
reg delete "HKLM\Software\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Tree\Microsoft\Windows\PI\SecureBootEncodeUEFI" /f
 
Maxstar said:
Please run the following commands and post the result.
Code: 
reg delete "HKLM\Software\Microsoft\Windows NT\CurrentVersion\Schedule\Taskcache\Tasks\{D9D7C3E7-F174-43B3-9685-DAEB138995" /f
reg delete "HKLM\Software\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Tree\Microsoft\Windows\PI\SecureBootEncodeUEFI" /f
Click to expand...
i think you missed the last part of the key, just to confirm

HKLM\Software\Microsoft\Windows NT\CurrentVersion\Schedule\Taskcache\Tasks\{D9D7C3E7-F174-43B3-9685-DAEB13899501 ?
 
Oops! Yes the last part is missing?

Code: 
reg delete "HKLM\Software\Microsoft\Windows NT\CurrentVersion\Schedule\Taskcache\Tasks\{D9D7C3E7-F174-43B3-9685-DAEB13899501}" /f
reg delete "HKLM\Software\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Tree\Microsoft\Windows\PI\SecureBootEncodeUEFI" /f
 
Please try the following.

Download
6530fbb0f4101-56f31e53c97da-SFCFix.PNG
SFCFix and save it to your desktop.

Warning: This fix was written specifically for this system. Do not run this fix on another system.
  • Save any work you have open, and close all programs.
  • Download the attachment SFCFixScript.txt and save it to your desktop.
  • Drag the SFCFixScript.txt file over the SFCFix.exe executable and release it.
650ef5dbdfd06-62151e1bebac4-SFCFix-Txt-Eng.gif

  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt.
  • Post the logfile (SFCFix.txt) as attachment in your next reply.
 

Attachments

Unfortunately the script failed, so let's try something else.

Please follow these instructions to run the
577bf0efb8088-FRST.png
Farbar Recovery Scan Tool with system privileges.

Download the 64 bit version: - Farbar Recovery Scan Tool Link

Warning: This script was written specifically for this system. Do not run this script on another system.
  • Download PsExec from Microsoft Sysinternals to your desktop.
  • Unzip PsTools.zip to its own directory on the system drive, for example: C:\Tools\PsTools
  • Navigate in an elevated command prompt to the PsTools directory: cd C:\Tools\PsTools.
  • Now copy and paste the following command into the command prompt and press enter. Click on the Agree button when the licence agreement of PsExec appears.
  • Note: Ensure that both FRST64.exe and the Fixlist.txt file are on your desktop! Otherwise you'll need to ammend the command to the right location.
    Code: 
    psexec -i -d -s "%userprofile%\desktop\FRST64.exe"
  • FRST will make a new backup of the registry first, please wait until this process is completed.
  • Ensure the provided Fixlist.txt is in the same location as FRST64.exe and then press the Fix button.
  • If for some reason the tool needs a restart, please make sure you let the system restart normally.
  • When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
  • Post the logfile Fixlog.txt as attachment in your next reply.
 

Attachments

it seems that the previous attempt deletaing the registry keys was successful... the two keys were not found
 

Attachments

Please run the following commands for a double check:
Code: 
reg query "HKLM\Software\Microsoft\Windows NT\CurrentVersion\Schedule\Taskcache\Tasks\{D9D7C3E7-F174-43B3-9685-DAEB13899501}"
reg query "HKLM\Software\Microsoft\Windows NT\CurrentVersion\Schedule\Taskcache\Tree\Microsoft\Windows\PI\SecureBootEncodeUEFI"
 
I really can't believe it.... it installed!!!

so only this F** keys were the problem??

so... I can run the sfcfix on the production server and try to install (is at this point disk space a player in this scenario?)
 
Yes, and I've seen similar issues on Server 2016/2019 which were upgraded from 2012R2.

And the disk space is also an issue, so I would extend the partition on the production server as well, also to avoid issues in the future.

Lybra77 said:
so... I can run the sfcfix on the production server and try to install
Click to expand...

When the {CLSID} is the same you can run the same fix to remove the keys. But you can also run the following commands again on the production server to check them.
Code: 
reg query "HKLM\Software\Microsoft\Windows NT\CurrentVersion\Schedule\Taskcache" /s > "%userprofile%\desktop\Tasklist.txt"
dir "%systemroot%\System32\Tasks\Microsoft\Windows\PI" /s >> "%userprofile%\desktop\Tasklist.txt"
 
ok, as this is a clone, CLSID are the same..

now.. I need to figure if it safe to delete those (old ) checkpoints preventing me from resizing disks as I did in the "clone".


I installed it on the production server after removing the two last keys and IT WORKED!!!

grabbing a full bottle of great wine and raise a toast to you...

I really had no more hope after one week of digging before contacting you and one week of digging with you...

What a save this was, I already started having nightmares on reinstalling SCCM on a new server and all the migration part!

Thanks a lot @Maxstar for your time !

L.
 
You're welcome. Glad to hear the production server was able to update as well after removing those keys. (y)

Lybra77 said:
I already started having nightmares on reinstalling SCCM on a new server and all the migration part!
Click to expand...

I can imagine that, but some maintaince in expanding the VHDx file may prevent you from other nightmares and/or issues in the future.

I would also take a look at the following tasks, they are just remnants too as it seems. Attached a Fixlist for FRST to remove those entry's.
The public guide for FRST can be found here: FRST Tutorial - How to use Farbar Recovery Scan Tool - FRST Tutorial

Rich (BB code): 
Task: {0A817E0C-5277-4E9E-B27C-B8EEE09913C4} - \Optimize Start Menu Cache Files-S-1-5-21-2507177388-3982217149-145561031-1516 -> No File <==== ATTENTION
Task: {0CB3FF1C-DB4D-4C0D-B1B3-59A29E45E352} - \Microsoft\Windows\Time Synchronization\SynchronizeTime -> No File <==== ATTENTION
Task: {0F0C5743-83DD-4742-9381-D5AB5E9FC3BA} - \Microsoft\Windows\Tcpip\IpAddressConflict1 -> No File <==== ATTENTION
Task: {146E453E-AE5F-4CFB-8BA4-73B014BB8543} - \BITS_CCM_Incoming_{6880FABF-5728-4872-B583-24F0910DCE2B} -> No File <==== ATTENTION
Task: {1878B7C9-D0E6-4C5A-9EBD-C76072EF0D99} - \Optimize Start Menu Cache Files-S-1-5-21-2507177388-3982217149-145561031-1132 -> No File <==== ATTENTION
Task: {348313AA-FAA4-4B4B-99EF-FCD19D9522B1} - \Microsoft\Windows\CertificateServicesClient\Notification\ReplaceOMCert -> No File <==== ATTENTION
Task: {3C4E2341-D2F0-4CD4-ACB2-EA7056CFEB0C} - \Microsoft\Windows\Workplace Join\Automatic-Workplace-Join -> No File <==== ATTENTION
Task: {3CB9BE78-1EF9-4C7F-A9DE-5FFFEC5FCF90} - \Microsoft\Configuration Manager\Configuration Manager Health Evaluation -> No File <==== ATTENTION
Task: {3F15F2A6-318E-47D4-94E8-10DDAA04D95F} - \Optimize Start Menu Cache Files-S-1-5-21-2507177388-3982217149-145561031-2437 -> No File <==== ATTENTION
Task: {5F4A93FF-2209-4F46-8FF1-B32050E32BFB} - \Microsoft\Windows\WindowsUpdate\AUFirmwareInstall -> No File <==== ATTENTION
Task: {607176C4-CA17-4B56-BAB6-FA062C8A7698} - \Microsoft\Windows\NetCfg\BindingWorkItemQueueHandler -> No File <==== ATTENTION
Task: {651FF2A7-84D4-4AE6-9231-BB0411D3A64F} - \Microsoft\Windows\Customer Experience Improvement Program\Server\ServerCeipAssistant -> No File <==== ATTENTION
Task: {69110D7B-41DC-4E9D-BDD3-C826C7DB613B} - \Microsoft\Windows\Customer Experience Improvement Program\Server\ServerRoleUsageCollector -> No File <==== ATTENTION
Task: {6CD9FD45-9DC4-43E6-B142-617D549F53EF} - \Optimize Start Menu Cache Files-S-1-5-21-2510075379-785543707-1353915232-500 -> No File <==== ATTENTION
Task: {6F13D7F0-5593-4DC6-A4FB-7FC8A56AF32A} - \Microsoft\Windows\WindowsUpdate\AUSessionConnect -> No File <==== ATTENTION
Task: {8D81349D-0385-4E2C-A5EA-86A7C5C176D2} - \Optimize Start Menu Cache Files-S-1-5-21-2507177388-3982217149-145561031-1521 -> No File <==== ATTENTION
Task: {8DDE4259-04B3-4200-B658-0841A4A93613} - \Optimize Start Menu Cache Files-S-1-5-21-2507177388-3982217149-145561031-1135 -> No File <==== ATTENTION
Task: {9FF7F184-DE35-4679-B342-B0951352218C} - \Microsoft\Windows\Tcpip\IpAddressConflict2 -> No File <==== ATTENTION
Task: {A14D7177-B746-41FE-8A03-8D4A996500FB} - \Microsoft\Windows\IME\SQM data sender -> No File <==== ATTENTION
Task: {AFECE848-8DA2-461B-B5E6-CBEF57A4DF7D} - \Microsoft\Windows\Customer Experience Improvement Program\Server\ServerRoleCollector -> No File <==== ATTENTION
Task: {B12A5945-7195-4348-AE1E-C960C5AC3E0E} - \Microsoft\Windows\WindowsUpdate\AUScheduledInstall -> No File <==== ATTENTION
Task: {D0576B2E-CB18-4F69-9C31-6771B5AE4F25} - \Microsoft\Windows\RAC\RacTask -> No File <==== ATTENTION
Task: {D34A472D-996A-4F20-9C90-910D0FFC8BDB} - \Microsoft\Configuration Manager\Content Usage -> No File <==== ATTENTION
Task: {D79E51A3-F5C8-4F70-99FE-C354C368410C} - \Optimize Start Menu Cache Files-S-1-5-21-2507177388-3982217149-145561031-1134 -> No File <==== ATTENTION
Task: {DC8D1441-AC6C-46E8-A5A7-6215162022C7} - \Optimize Start Menu Cache Files-S-1-5-21-2507177388-3982217149-145561031-1262 -> No File <==== ATTENTION
Task: {E411172D-4E3B-46A0-A748-4BBD923D93E7} - \Microsoft\Windows\WindowsUpdate\Scheduled Start With Network -> No File <==== ATTENTION
Task: {E5D55513-8BA6-41B6-82E2-16C2FDA4CE3B} - \Microsoft\Windows\Setup\WS2012R2EOSNotify -> No File <==== ATTENTION
 

Attachments

You must log in or register to reply here.
Back
Top