Maxstar Windows Update Moderator, Security Analyst Staff member Joined Aug 16, 2015 Posts 10,383 Location The Netherlands May 13, 2022 #41 Hi, Thanks for the additional info, please try to remove KB5013952 again with the following command. Code: wusa /uninstall /KB:5013952 If it fails, perform the steps in post #31 again and post and attach the new SearchReg.txt to your next reply.
Hi, Thanks for the additional info, please try to remove KB5013952 again with the following command. Code: wusa /uninstall /KB:5013952 If it fails, perform the steps in post #31 again and post and attach the new SearchReg.txt to your next reply.
J jaycee5585 Well-known member Joined Apr 27, 2022 Posts 52 May 13, 2022 #42 The command failed. New searchreg.txt below. Attachments SearchReg.txt 13 MB · Views: 3
Maxstar Windows Update Moderator, Security Analyst Staff member Joined Aug 16, 2015 Posts 10,383 Location The Netherlands May 13, 2022 #43 Step 1. Start the Farbar Recovery Scan Tool again. Warning: This script was written specifically for this system. Do not run this script on another system. 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. Step 2. Open a elevated command prompt and run the following commands once at a time. Code: lodctr.exe /R winmgmt.exe /RESYNCPERF Dism /Online /Cleanup-Image /RestoreHealth Please let me know the result with a screenshot or a copy/paste after running this three commands. Step 3. Reboot the server and try Windows Update again. * * If it fails I think we should remove all the failed updates first. Attachments fixlist.txt 9.8 MB · Views: 3
Step 1. Start the Farbar Recovery Scan Tool again. Warning: This script was written specifically for this system. Do not run this script on another system. 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. Step 2. Open a elevated command prompt and run the following commands once at a time. Code: lodctr.exe /R winmgmt.exe /RESYNCPERF Dism /Online /Cleanup-Image /RestoreHealth Please let me know the result with a screenshot or a copy/paste after running this three commands. Step 3. Reboot the server and try Windows Update again. * * If it fails I think we should remove all the failed updates first.
J jaycee5585 Well-known member Joined Apr 27, 2022 Posts 52 May 13, 2022 #44 STEP 1 Fixlog.txt is attached. STEP 2 STEP 3 Server has been rebooted, however - it is too late in the day for me to attempt updating this server now. I will try the updates on Monday. Attachments Fixlog.txt 20.1 MB · Views: 3
STEP 1 Fixlog.txt is attached. STEP 2 STEP 3 Server has been rebooted, however - it is too late in the day for me to attempt updating this server now. I will try the updates on Monday.
J jaycee5585 Well-known member Joined Apr 27, 2022 Posts 52 May 17, 2022 #45 I just attempted to update, and it failed.
Maxstar Windows Update Moderator, Security Analyst Staff member Joined Aug 16, 2015 Posts 10,383 Location The Netherlands May 17, 2022 #46 Hi, Please post the following logs. %systemdrive%\$Windows.~BT\Sources\Rollback\setupact.log %systemdrive%\$Windows.~BT\Sources\Rollback\setuperr.log %systemdrive%\Windows\Logs\CBS\cbs.log If there is an memory dump in the following folder as well - please zip it and upload it to WeTransfer and post the downloadlink. %systemdrive%\$Windows.~BT\Sources\Rollback\setupmem.dmp
Hi, Please post the following logs. %systemdrive%\$Windows.~BT\Sources\Rollback\setupact.log %systemdrive%\$Windows.~BT\Sources\Rollback\setuperr.log %systemdrive%\Windows\Logs\CBS\cbs.log If there is an memory dump in the following folder as well - please zip it and upload it to WeTransfer and post the downloadlink. %systemdrive%\$Windows.~BT\Sources\Rollback\setupmem.dmp
J jaycee5585 Well-known member Joined Apr 27, 2022 Posts 52 May 17, 2022 #47 The folder C:\$Windows.~BT does not exist on this system. Attached is the current CBS.log . Attachments CBS.log 9.7 MB · Views: 3
Maxstar Windows Update Moderator, Security Analyst Staff member Joined Aug 16, 2015 Posts 10,383 Location The Netherlands May 17, 2022 #48 jaycee5585 said: The folder C:\$Windows.~BT does not exist on this system. Click to expand... That's odd, can you please run the following tool from Microsoft. Download and run SetupDiag from Microsoft Download SetupDiag to your desktop. Right-click on SetupDiag.exe and select Run as administrator. When completed the following files are created: "Logs.zip, SetupDiag.exe.config and SetupDiagResults.log" Attach SetupDiagResults.log and Logs.zip to your next reply.
jaycee5585 said: The folder C:\$Windows.~BT does not exist on this system. Click to expand... That's odd, can you please run the following tool from Microsoft. Download and run SetupDiag from Microsoft Download SetupDiag to your desktop. Right-click on SetupDiag.exe and select Run as administrator. When completed the following files are created: "Logs.zip, SetupDiag.exe.config and SetupDiagResults.log" Attach SetupDiagResults.log and Logs.zip to your next reply.
J jaycee5585 Well-known member Joined Apr 27, 2022 Posts 52 May 17, 2022 #49 I ran the tool. It only took about 2 seconds to run. When finished, it did not generate a zip file. The log file generated was empty (0 bytes).
I ran the tool. It only took about 2 seconds to run. When finished, it did not generate a zip file. The log file generated was empty (0 bytes).
Maxstar Windows Update Moderator, Security Analyst Staff member Joined Aug 16, 2015 Posts 10,383 Location The Netherlands May 17, 2022 #50 Hmm, strange. I suppose that the update this time also resulted in a rollback?
J jaycee5585 Well-known member Joined Apr 27, 2022 Posts 52 May 17, 2022 #51 I did find files with the same names in C:\Windows\Panther\UnattendGC which were updated today. setuperr.log was empty. setupact.log is attached. Attachments setupact.log 75.9 KB · Views: 5
I did find files with the same names in C:\Windows\Panther\UnattendGC which were updated today. setuperr.log was empty. setupact.log is attached.
Maxstar Windows Update Moderator, Security Analyst Staff member Joined Aug 16, 2015 Posts 10,383 Location The Netherlands May 17, 2022 #53 Thank you very much! This is quite interesting, I'll need to figure out some things.
J jaycee5585 Well-known member Joined Apr 27, 2022 Posts 52 May 17, 2022 #54 Maxstar said: Step 3. Reboot the server and try Windows Update again. * * If it fails I think we should remove all the failed updates first. Click to expand... Do you still think this is a valid plan?
Maxstar said: Step 3. Reboot the server and try Windows Update again. * * If it fails I think we should remove all the failed updates first. Click to expand... Do you still think this is a valid plan?
Maxstar Windows Update Moderator, Security Analyst Staff member Joined Aug 16, 2015 Posts 10,383 Location The Netherlands May 17, 2022 #55 Maybe, but first I'm going to consult one of the experts here.
Maxstar Windows Update Moderator, Security Analyst Staff member Joined Aug 16, 2015 Posts 10,383 Location The Netherlands May 18, 2022 #56 jaycee5585 said: Do you still think this is a valid plan? Click to expand... Yes, let's start with KB5013952 again. 1. Open a elevated command prompt and run the following command Code: reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS 2. Open FRST64.exe as administrator and perform a registry search for: Code: KB5013952 3. Attach SearchReg.txt in your next reply.
jaycee5585 said: Do you still think this is a valid plan? Click to expand... Yes, let's start with KB5013952 again. 1. Open a elevated command prompt and run the following command Code: reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS 2. Open FRST64.exe as administrator and perform a registry search for: Code: KB5013952 3. Attach SearchReg.txt in your next reply.
J jaycee5585 Well-known member Joined Apr 27, 2022 Posts 52 May 18, 2022 #57 Done. Attachments SearchReg.txt 13 MB · Views: 5
Maxstar Windows Update Moderator, Security Analyst Staff member Joined Aug 16, 2015 Posts 10,383 Location The Netherlands May 18, 2022 #58 Step 1. Start the Farbar Recovery Scan Tool again. Warning: This script was written specifically for this system. Do not run this script on another system. 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. Step 2. Try to uninstall KB5012596 with the following command: Code: wusa /uninstall /KB:5012596 When you get the message: The update KB..... is not installed on this computer, then perform step 3. Step 3. FRST REG Search. 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: KB5012596 3. Attach SearchReg.txt in your next reply. Attachments fixlist.txt 9.8 MB · Views: 3
Step 1. Start the Farbar Recovery Scan Tool again. Warning: This script was written specifically for this system. Do not run this script on another system. 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. Step 2. Try to uninstall KB5012596 with the following command: Code: wusa /uninstall /KB:5012596 When you get the message: The update KB..... is not installed on this computer, then perform step 3. Step 3. FRST REG Search. 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: KB5012596 3. Attach SearchReg.txt in your next reply.
J jaycee5585 Well-known member Joined Apr 27, 2022 Posts 52 May 18, 2022 #59 As requested. All commands completed. Attachments Fixlog.txt 20.1 MB · Views: 5 SearchReg.txt 624.3 KB · Views: 7
Maxstar Windows Update Moderator, Security Analyst Staff member Joined Aug 16, 2015 Posts 10,383 Location The Netherlands May 19, 2022 #60 Hi, Start the Farbar Recovery Scan Tool again. Warning: This script was written specifically for this system. Do not run this script on another system. 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 fixlist.txt 474.8 KB · Views: 6
Hi, Start the Farbar Recovery Scan Tool again. Warning: This script was written specifically for this system. Do not run this script on another system. 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.