issues adding feature on Server 2016 standard has led CBS errors with KB4598243

Hi,

That's not a problem, and you can upload files up to 2GB at WeTransfer..
 
Hi,

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.
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.

Afterwards rebot the server and try to uninstall the backup future with Process Monitor running. Attach this trace with the latest CBS log to your next post.
 

Attachments

This script failed. I tried a few ways and restarted just in case something was locked. No Luck.
 

Attachments

Hi,

Please do the following to check the permissions of the PackageIndex key.

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

  • Download the attachment fixlist.txt and save it to your desktop.
  • Right-click on FRST.exe and select "Run as administrator".
  • 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

Alright, I tried that and it seemed successful. However, the SFCFix failed with the same error. I checked the registry with regedit and the permissions were read only for Administrator and it would not let me change them (with my domain admin account). I logged into the local admin account and re-ran the Farbar fix again and the SFCFix again and both seemed to have worked. I am including both log files.

Since I was logged in as the local admin I went ahead and tried removing the Backup feature and it failed with the same error. I am including the CBS logs again as well. I cannot reboot the server currently but I can this evening.
 

Attachments

I logged into the local admin account and re-ran the Farbar fix again and the SFCFix again and both seemed to have worked.
Could you please try to uninstall the backup future again with Process Monitor running under this local admin account.
Afterwards attach the PML trace as well as a new copy of the CBS logs.
 
Rich (BB code):
4:40:02.8692866 PM	TiWorker.exe	11520	RegOpenKey	HKLM\Software\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-spp-main_31bf3856ad364e35_none_9797ae0ef4e5697b	NAME NOT FOUND	Desired Access: Read
4:40:02.8693252 PM	TiWorker.exe	11520	RegOpenKey	HKLM\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-spp-main_31bf3856ad364e35_10.0.14393.4169_none_5a090d33076c5120	SUCCESS	Desired Access: Read

Hi,

Here's the next fix to replace the missing winners key.

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.
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.

Afterwards reboot the server and try to uninstall the backup future with Process Monitor running. Attach this trace with the latest CBS log to your next post.
 

Attachments

Hi,

Do you have also the trace of Process Monitor after running the last steps?
 
Rich (BB code):
5:47:30.8862061 PM    TiWorker.exe    12204    RegOpenKey    HKLM\Software\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-blb-wsbapp-proxy-main_31bf3856ad364e35_none_60ae9010611bb62b    NAME NOT FOUND    Desired Access: Read
5:47:30.8862721 PM    TiWorker.exe    12204    RegOpenKey    HKLM\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-blb-wsbapp-proxy-main_31bf3856ad364e35_10.0.14393.2515_none_2077cab839a82f2f    SUCCESS    Desired Access: Read

Here's the next fix.

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.
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.

Afterwards reboot the server and try to uninstall the backup future with Process Monitor running. Attach this trace with the latest CBS log to your next post.
 

Attachments

Rich (BB code):
7:19:32.1029043 PM    TiWorker.exe    11736    RegOpenKey    HKLM\Software\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-blb-cli-main_31bf3856ad364e35_none_e55f65a3866f16c7    NAME NOT FOUND    Desired Access: Read
7:19:32.1029498 PM    TiWorker.exe    11736    RegOpenKey    HKLM\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-blb-cli-main_31bf3856ad364e35_10.0.14393.4169_none_c116f391e9953974    SUCCESS    Desired Access: Read

Hi,

Here's the next fix.

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.
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.

Afterwards reboot the server and try to uninstall the backup future with Process Monitor running. Attach this trace with the latest CBS log to your next post.
 

Attachments

Rich (BB code):
6:25:17.7753449 AM    TiWorker.exe    9284    RegOpenKey    HKLM\Software\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-blb-srv-main_31bf3856ad364e35_none_d259502694f83050    NAME NOT FOUND    Desired Access: Read
6:25:17.7754002 AM    TiWorker.exe    9284    RegOpenKey    HKLM\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-blb-srv-main_31bf3856ad364e35_10.0.14393.4169_none_895fe80866c353a3    SUCCESS    Desired Access: Read

Hi,

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.
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.

Afterwards reboot the server and try to uninstall the backup future with Process Monitor running. Attach this trace with the latest CBS log to your next post.
 

Attachments

Hi,

Please perform the following steps to uninstall KB4048953 (Nov 2017).


Step 1. Try to uninstall the following update:
Code:
wusa /uninstall /KB:40489532
When you get the message: The update KB******* is not installed on this computer, then perform step 2.


Step 2.
1. Open a elevated command prompt and run the following command (to be sure that the COMPONENTS hive is loaded).
Code:
reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS
2. Open FRST64.exe as administrator and perform a registry search for:
Code:
KB40489532
3. Attach SearchReg.txt in your next reply.
 
I am not sure why I did not think about this before, but at some point I had issues with this server receiving updates from our WSUS server. It was about a year ago. No matter what I did, it would only pull updates directly from Microsoft. I had to reset Windows Update a few times before I finally got it to start pulling from WSUS again. I'm not sure if that information helps or not. I wish I could remember what I had to do to get it to work again.

I have attached the search results.
 

Attachments

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top