[SOLVED] Windows Server 2019 - All updates installs fail since being upgraded from Win2012

M

Mingle

Active member
Joined
Jul 24, 2022
Posts
39
This system was upgraded from Windows Server 2012 to Windows Server 2016 and Windows Server 2019 in one fell swoop. I am aware that an in-place upgrade is not recommended but this was one of dozens and it was not possible to build new due to time and resource constraints. The roles of this server are:
  • Windows Deployment Services
I have performed the following troubleshooting tasks
  • Renaming C:\Windows\SoftwareDistribution SoftwareDistribution
  • Dism.exe /online /Cleanup-Image /StartComponentCleanup
  • Dism.exe /online /Cleanup-Image /StartComponentCleanup /ResetBase
  • Dism.exe /online /Cleanup-Image /SPSuperseded
  • DISM /Online /Cleanup-Image /RestoreHealth
  • Ran “sfc /scannow"
  • Ran SCFix tool
  • Ran ComponentsScanner

After running the tasks above, I downloaded and ran the latest CU updates and it installs, reboots and eventually gives me the following:
1706219914284.png

I am out of ideas and attaching the CBS.zip and ComponentsScanner.txt, as instructed.
 

Attachments

Rich (BB code): 
2024-01-25 16:18:41, Error                 CSI    00000be4 (F) Installer: Task Scheduler    Binary Name: cmiadapter.dll    ErrorCode: 80070002    Phase: 38    Mode: Install (first install)    Component: Microsoft-OneCore-SecureBootEncodeUEFI-Task, Culture=neutral, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS[gle=0x80004005]
2024-01-25 16:18:41, Info                  CSI    00000be5 ==Error Summary End==
2024-01-25 16:18:41, Error                 CBS    Startup: Failed to process advanced operation queue, startupPhase: 0.  A rollback transaction will be created. [HRESULT = 0x800f0922 - CBS_E_INSTALLERS_FAILED]


Hi and welcome to Synative,

Please do the following to check if the "SecureBootEncodeUEFI" task exists under PI.
  • Open the start menu and type Task Scheduler and hit enter.
  • Navigate to Task Scheduler Library > Microsoft > Windows > PI
  • If the "SecureBootEncodeUEFI" task exists please post the Last Run Result info.
  • Or export the "SecureBootEncodeUEFI" task with a right click to an *.XML file and attach it to your next post.
 
I manually ran the job and then got the following error: "parameter is incorrect (0x80070057)"
 
There can be a couple of reasons why this error occurs, the most common issue is a (triggered) scheduled task date in the past. Or there's no next run time set.

Please check the following as well.
  • Open the start menu and type Task Scheduler and hit enter.
  • Navigate to Task Scheduler Library > Microsoft > Windows > PI
  • Open the "SecureBootEncodeUEFI" task and open the triggers tab.
  • Take a screenshot of this window and attach it to your next post.
 
Apologies, for some reason I mistook "SecureBootEncodeUEFI" for "Secure-Boot-Update". I have the latter but not the former.
1706711534582.png
 
I expected that this task was not present seen the error in the CBS log. Please do the following to re-add this task but first make a backup/snapshot of this server. Important!
  • Open the start menu and type Task Scheduler and hit enter.
  • Navigate to Task Scheduler Library > Microsoft > Windows > PI
  • In the menu of Task Sheduler click on Actions > Import Task.
  • Extract the attached ZIP-file and select the SecureBootEncodeUEFI.xml file.
Note: You can also compare the TASK settings with a similar server in your network and use a export of that system to use. This to be sure the Network Conditions are the same, otherwise you'll need to ammend them to avoid other issues.

Warning! The attached (SecureBootEncodeUEFI.xml) is a default file from a clean VM without specific settings.
 

Attachments

I imported the XML and got an error about a job of same name existing, even though I don't see one. I ended up successfully importing the XML and naming the job "SecureBootEncodeUEFI3". I then attempted to install the latest Cumulative Update and got the same "We couldn't complete the updates. Undoing changes." :-(
 
Mingle said:
(...) got an error about a job of same name existing, even though I don't see one.
Click to expand...

That's odd, could you please run the following tool which will also log tasks and/or ghost tasks.

Download the
577bf0efb8088-FRST.png
Farbar Recovery Scan Tool and save it to your Desktop:

Download the 64 bit version: - Farbar Recovery Scan Tool Link
  • Note: Your antivirus program may report FRST incorrectly as an infection. If so, disable the real-time protection when downloading and running FRST.
  • Right-click to run the tool as administrator. When the tool opens click Yes to disclaimer.
  • Note: Ensure that the Addition.txt check box is checked at the bottom of the form within the Optional Scan area.
  • Press the Scan button.
  • Please wait for the tool to finish. It will produce two logfiles called FRST.txt and Addition.txt in the same directory the tool is run from (which should be the desktop)
  • Post the logfiles FRST.txt and Addition.txt as attachment in your next reply.
 
Please run the following commands in an elevated prompt and attach the file tasklist.txt to your next post.
Code: 
reg query "HKLM\Software\Microsoft\Windows NT\CurrentVersion\Schedule\Taskcache\Tasks" /s > "%userprofile%\desktop\tasklist.txt"
dir "%systemroot%\System32\Tasks\Microsoft\Windows\PI" /s >> "%userprofile%\desktop\tasklist.txt"
 
You're welcome, this is an interesting problem! Please do the following as well so I can load this hive export into the registry to compare some things.

Export registry key as hive file.
  • Open the Start menu of Windows and type CMD.
  • When you see Command Prompt on the list, select the option Run as administrator.
  • Copy and paste the following command into the command prompt and press enter.
Code: 
reg save "HKLM\Software\Microsoft\Windows NT\CurrentVersion\Schedule\Taskcache" "%userprofile%\Desktop\TaskList.hiv"
  • Once done, a file will appear on your desktop, called TaskList.hiv.
  • ZIP this file and attach it to your next reply.
 
Hi,

It seems the first task is corrupted, that might be the reason why it is not visible into Task Sheduler. I would suggest to create a new backup and then remove these three tasks, you can run the following commands in an elevated prompt to do that.

Afterwards re-add this task and check if the task is visible and this file: "C:\Windows\System32\Tasks\Microsoft\Windows\PI\SecureBootEncodeUEFI" is recreated.

Code: 
reg delete "HKLM\Software\Microsoft\Windows NT\CurrentVersion\Schedule\Taskcache\Tasks\{769AD357-4F17-493D-A6B4-79E823A3520F}" /f
reg delete "HKLM\Software\Microsoft\Windows NT\CurrentVersion\Schedule\Taskcache\Tasks\{E26B6A37-89FD-42D6-860B-8FB7E0A107E0}" /f
reg delete "HKLM\Software\Microsoft\Windows NT\CurrentVersion\Schedule\Taskcache\Tasks\{F91F045B-8394-49DF-B0E6-35E4D0A47A62}" /f
reg delete "HKLM\Software\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Tree\Microsoft\Windows\PI\SecureBootEncodeUEFI" /f
reg delete "HKLM\Software\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Tree\Microsoft\Windows\PI\SecureBootEncodeUEFI2" /f
reg delete "HKLM\Software\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Tree\Microsoft\Windows\PI\SecureBootEncodeUEFI3" /f

Rich (BB code): 
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Schedule\Taskcache\Tasks\{769AD357-4F17-493D-A6B4-79E823A3520F}
    Path    REG_SZ    \Microsoft\Windows\PI\SecureBootEncodeUEFI
    Hash    REG_BINARY    52A0A80B67A9DAE7DD1B88951D022C5867E1DF5F0205A9B3AB2742AE226BBFED
    SecurityDescriptor    REG_SZ    D:P(A;;FA;;;BA)(A;;FA;;;SY)(A;;FR;;;AU)(A;;FRFX;;;LS)
    URI    REG_SZ    Microsoft\Windows\PI\SecureBootEncodeUEFI
    Triggers    REG_BINARY    150000000000000000D5703813000000000000000000000000D5703813000000FFFFFFFFFFFFFFFFC0A1404348484848C9C0648B484848480048484848484848004848484848484804000000484848481000000048484848010200000000000520000000200200000000000048484848580000004848484800000000FFFFFFFF3C000000FFFFFFFF0700000000000000000000000000000000000000000000000000000061006E0000000000000000000000000000001400000000000000000000000000190000000000000000000000888800000000000000D5703813000000000000000000000000D5703813000000FFFFFFFFFFFFFFFF00000000FFFFFFFF0000000000000000000000000000000001000000000000000000000000000000
    Actions    REG_BINARY    0100666600000000540000002500570049004E0044004900520025005C00730079007300740065006D00330032005C0053006500630075007200650042006F006F00740045006E0063006F006400650055004500460049002E006500780065000000000000000000
    DynamicInfo    REG_BINARY    030000007B24EBB9EDABD901000000000000000000000000000000000000000000000000

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Schedule\Taskcache\Tasks\{E26B6A37-89FD-42D6-860B-8FB7E0A107E0}
    Path    REG_SZ    \Microsoft\Windows\PI\SecureBootEncodeUEFI2
    Hash    REG_BINARY    ECC03BAE6566D4CBA7BF890C23B0BB745897772A5DD0E5122DDF6DD428541838
    Schema    REG_DWORD    0x10004
    Date    REG_SZ    2024-01-31T09:50:37.2096643
    Author    REG_SZ    MAGNT\*******
    URI    REG_SZ    \Microsoft\Windows\PI\SecureBootEncodeUEFI2
    Triggers    REG_BINARY    17000000000000000045C0E5FE7F000000000000000000000045C0E5FE7F0000FFFFFFFFFFFFFFFFE821024248484848A1C239E3484848480E0000004848484841007500740068006F0072000000484800000000484848480048484848484848004848484848484805000000484848480C000000484848480101000000000005120000004848484800000000484848482C0000004848484800000000FFFFFFFF80F40300FFFFFFFF0700000000000000000000000000000000000000000000000000000048484848FFFF0000000000000045C0E5FE7F000000000000000000000045C0E5FE7F0000FFFFFFFFFFFFFFFF00000000FFFFFFFF00000000000000000000000000000000010000000000000000000000000000000000000048484848
    Actions    REG_BINARY    03000C00000041007500740068006F007200666600000000540000002500570049004E0044004900520025005C00730079007300740065006D00330032005C0053006500630075007200650042006F006F00740045006E0063006F006400650055004500460049002E0065007800650000000000000000000000
    DynamicInfo    REG_BINARY    030000001368E8E95454DA018690C4825654DA0100000000020007800000000000000000

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Schedule\Taskcache\Tasks\{F91F045B-8394-49DF-B0E6-35E4D0A47A62}
    Path    REG_SZ    \Microsoft\Windows\PI\SecureBootEncodeUEFI3
    Hash    REG_BINARY    8F8BA3B98C55F90DD98F714F3F2999A1372514D9FB3D0BFFC7B4E9205C250767
    Schema    REG_DWORD    0x10006
    Date    REG_SZ    2024-01-31T10:09:25.3795455
    SecurityDescriptor    REG_SZ    D:P(A;;FA;;;BA)(A;;FA;;;SY)(A;;FR;;;AU)(A;;FRFX;;;LS)
    Author    REG_SZ    CLONE_MAGSSCCMD\Actifio_Backup
    URI    REG_SZ    \Microsoft\Windows\PI\SecureBootEncodeUEFI3
    Triggers    REG_BINARY    17000000000000000045081DFE7F0000000000000000000000070C0000001F00FFFFFFFFFFFFFFFFC021424248484848DABEB63C4848484818000000484848484C006F00630061006C00530079007300740065006D00000000000000484848480048484848484848004848484848484805000000484848480C000000484848480101000000000005120000004848484800000000484848482C0000004848484800000000FFFFFFFF0A000000FFFFFFFF0700000000000000000000000000000000000000000000000000000048484848FFFF0000000000000045081DFE7F0000000000000000000001070C0000001F0000204CFD4C7ADC012C010000FFFFFFFF00000000000000000000000000000000010000000000000000000000000000000000000048484848DDDD00000000000001070C0000001F0000204CFD4C7ADC0100000000000000000000000000000000000000000000000000000000000000000000000000000000FFFFFFFF0300000001400000FF0F00000001AC1C0100000000000000110200000000000048484848
    Actions    REG_BINARY    0300160000004C006F00630061006C00530079007300740065006D00666600000000540000002500570049004E0044004900520025005C00730079007300740065006D00330032005C0053006500630075007200650042006F006F00740045006E0063006F006400650055004500460049002E0065007800650000000000000000000000
    DynamicInfo    REG_BINARY    03000000C8740F855754DA01770C2B216654DA0100000000020007800000000000000000
 
Last edited:
I would say, this looks good! But is the .NET Framework update also installed?
 
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