D David86 Well-known member Joined Feb 12, 2020 Posts 129 Feb 1, 2023 #81 It is written that the operation was successfully completed, but there are no kb4499151 updates in the collection of updates (. Spoiler: cmd Microsoft Windows [Version 6.3.9600] (c) Корпорация Майкрософт (Microsoft Corporation), 2013. Все права защищены. C:\Windows\system32>DISM.exe /Online /Add-Package /PackagePath:C:\temp\windows8. 1-kb4499151-x64.cab Cистема DISM Версия: 6.3.9600.19408 Версия образа: 6.3.9600.19397 Обрабатывается 1 из 1 - Добавление пакета Package_for_RollupFix~31bf3856ad364e35 ~amd64~~9600.19356.1.9 [==========================100.0%========================= ] Операция успешно завершена. C:\Windows\system32>DISM.exe /Online /Add-Package /PackagePath:C:\temp\windows8. 1-kb4499151-x64.cab Cистема DISM Версия: 6.3.9600.19408 Версия образа: 6.3.9600.19397 Обрабатывается 1 из 1 - Добавление пакета Package_for_RollupFix~31bf3856ad364e35 ~amd64~~9600.19356.1.9 [==========================100.0%========================= ] Операция успешно завершена. Attachments Fixlog.txt 1.7 KB · Views: 2 CBS.zip 523.6 KB · Views: 1
It is written that the operation was successfully completed, but there are no kb4499151 updates in the collection of updates (. Spoiler: cmd Microsoft Windows [Version 6.3.9600] (c) Корпорация Майкрософт (Microsoft Corporation), 2013. Все права защищены. C:\Windows\system32>DISM.exe /Online /Add-Package /PackagePath:C:\temp\windows8. 1-kb4499151-x64.cab Cистема DISM Версия: 6.3.9600.19408 Версия образа: 6.3.9600.19397 Обрабатывается 1 из 1 - Добавление пакета Package_for_RollupFix~31bf3856ad364e35 ~amd64~~9600.19356.1.9 [==========================100.0%========================= ] Операция успешно завершена. C:\Windows\system32>DISM.exe /Online /Add-Package /PackagePath:C:\temp\windows8. 1-kb4499151-x64.cab Cистема DISM Версия: 6.3.9600.19408 Версия образа: 6.3.9600.19397 Обрабатывается 1 из 1 - Добавление пакета Package_for_RollupFix~31bf3856ad364e35 ~amd64~~9600.19356.1.9 [==========================100.0%========================= ] Операция успешно завершена.
P PeterJ Moderator, Windows Update Expert, Security Analyst Staff member Joined Dec 14, 2014 Posts 12,643 Feb 1, 2023 #82 The cbs.log looks good. Check Windows Update and report the result first.
D David86 Well-known member Joined Feb 12, 2020 Posts 129 Feb 2, 2023 #83 Thanks a lot!!! Update KB2919355 has been installed and the update center writes that no more updates are required. I was able to remove an unnecessary role from the server. The only dism check is still in error 1168. I don't understand why this is happening, but I don't think it's critical. Spoiler: cmd Microsoft Windows [Version 6.3.9600] (c) Корпорация Майкрософт (Microsoft Corporation), 2013. Все права защищены. C:\Windows\system32>sfc /scannow System scan started. This process may take some time. The beginning of the verification stage when scanning the system. Verification 100% completed. Windows Resource Protection found no integrity violations. C:\Windows\system32>dism /online /cleanup-image /restorehealth Cистема DISM Версия: 6.3.9600.19408 Версия образа: 6.3.9600.19397 [==========================100.0%==========================] Ошибка: 1168 Element not found The DISM log file is located at C:\Windows\Logs\DISM\dism.log C:\Windows\system32> Spoiler: pic Attachments Fixlog.txt 1.7 KB · Views: 1
Thanks a lot!!! Update KB2919355 has been installed and the update center writes that no more updates are required. I was able to remove an unnecessary role from the server. The only dism check is still in error 1168. I don't understand why this is happening, but I don't think it's critical. Spoiler: cmd Microsoft Windows [Version 6.3.9600] (c) Корпорация Майкрософт (Microsoft Corporation), 2013. Все права защищены. C:\Windows\system32>sfc /scannow System scan started. This process may take some time. The beginning of the verification stage when scanning the system. Verification 100% completed. Windows Resource Protection found no integrity violations. C:\Windows\system32>dism /online /cleanup-image /restorehealth Cистема DISM Версия: 6.3.9600.19408 Версия образа: 6.3.9600.19397 [==========================100.0%==========================] Ошибка: 1168 Element not found The DISM log file is located at C:\Windows\Logs\DISM\dism.log C:\Windows\system32> Spoiler: pic
P PeterJ Moderator, Windows Update Expert, Security Analyst Staff member Joined Dec 14, 2014 Posts 12,643 Feb 2, 2023 #84 Great. The main issue is solved. Please attach the files cbs.log and dism.log so we can have a look. If you prefer to stop here that is fine with me.
Great. The main issue is solved. Please attach the files cbs.log and dism.log so we can have a look. If you prefer to stop here that is fine with me.
D David86 Well-known member Joined Feb 12, 2020 Posts 129 Feb 2, 2023 #85 Аttached Attachments CBS.zip 8.4 MB · Views: 1 dism.zip 872.6 KB · Views: 1
P PeterJ Moderator, Windows Update Expert, Security Analyst Staff member Joined Dec 14, 2014 Posts 12,643 Feb 2, 2023 #86 Step 1: Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine. Download the attachment fixlist.txt and save it to your desktop. Right-click on FRST64.exe and select "Run as administrator". Press the Fix button. The tool will now process fixlist.txt. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from. Attach the logfile Fixlog.txt to your next reply. Step 2: Restart the machine. Run the command dism /online /cleanup-image /restorehealth again in an elevated commandprompt and report the result. Attachments fixlist.txt 42.8 KB · Views: 2
Step 1: Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine. Download the attachment fixlist.txt and save it to your desktop. Right-click on FRST64.exe and select "Run as administrator". Press the Fix button. The tool will now process fixlist.txt. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from. Attach the logfile Fixlog.txt to your next reply. Step 2: Restart the machine. Run the command dism /online /cleanup-image /restorehealth again in an elevated commandprompt and report the result.
D David86 Well-known member Joined Feb 12, 2020 Posts 129 Feb 3, 2023 #87 Unfortunately the error is still present Error: 1168 element not found. Spoiler: dism Microsoft Windows [version 6.3.9600] (c) 2013 Microsoft Corporation. All rights reserved. C:\Windows\system32>dism/online/cleanup-image/restorehealth DISM system Version: 6.3.9600.19408 Image version: 6.3.9600.19397 [=========================100.0%====================== ====] Error: 1168 Element not found. The DISM log file is located at C:\Windows\Logs\DISM\dism.log Attachments Fixlog.txt 89.8 KB · Views: 1 CBS.zip 84.5 KB · Views: 4 dism.zip 877.5 KB · Views: 1
Unfortunately the error is still present Error: 1168 element not found. Spoiler: dism Microsoft Windows [version 6.3.9600] (c) 2013 Microsoft Corporation. All rights reserved. C:\Windows\system32>dism/online/cleanup-image/restorehealth DISM system Version: 6.3.9600.19408 Image version: 6.3.9600.19397 [=========================100.0%====================== ====] Error: 1168 Element not found. The DISM log file is located at C:\Windows\Logs\DISM\dism.log
P PeterJ Moderator, Windows Update Expert, Security Analyst Staff member Joined Dec 14, 2014 Posts 12,643 Feb 3, 2023 #88 Unfortunately the cbs.log does not contain all faulty lines so we need to repeat this procedure several times. Step 1: Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine. Download the attachment fixlist.txt and save it to your desktop. Right-click on FRST64.exe and select "Run as administrator". Press the Fix button. The tool will now process fixlist.txt. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from. Attach the logfile Fixlog.txt to your next reply. Step 2: Restart the machine. Run the command dism /online /cleanup-image /restorehealth again in an elevated commandprompt and report the result. Attachments fixlist.txt 43.6 KB · Views: 1
Unfortunately the cbs.log does not contain all faulty lines so we need to repeat this procedure several times. Step 1: Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine. Download the attachment fixlist.txt and save it to your desktop. Right-click on FRST64.exe and select "Run as administrator". Press the Fix button. The tool will now process fixlist.txt. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from. Attach the logfile Fixlog.txt to your next reply. Step 2: Restart the machine. Run the command dism /online /cleanup-image /restorehealth again in an elevated commandprompt and report the result.
D David86 Well-known member Joined Feb 12, 2020 Posts 129 Feb 5, 2023 #89 After applying the fix and trying to restart the server, it could not boot correctly several times and had to be turned off and on again. Searches in the event log did not give anything except an error with the windows application store (the Desktop Experience component for the Disk Cleanup function was installed earlier). Removing this component didn't work 0x80073701. I suppose I have already tired you with the problems of this decrepit server. Spoiler: pic Attachments CBS.zip 12.9 MB · Views: 4 dism.zip 899.9 KB · Views: 1 Fixlog.txt 91.7 KB · Views: 1
After applying the fix and trying to restart the server, it could not boot correctly several times and had to be turned off and on again. Searches in the event log did not give anything except an error with the windows application store (the Desktop Experience component for the Disk Cleanup function was installed earlier). Removing this component didn't work 0x80073701. I suppose I have already tired you with the problems of this decrepit server. Spoiler: pic
P PeterJ Moderator, Windows Update Expert, Security Analyst Staff member Joined Dec 14, 2014 Posts 12,643 Feb 5, 2023 #90 Okay, the FRST log looks normal and removed all keys as expected. The log CBS.zip you attached is corrupt and cannot be opened. It's up to you if you want to continue this thread or not. Don't worry about my time. If you want to continue zip the cbs.log again and attach it to your next reply.
Okay, the FRST log looks normal and removed all keys as expected. The log CBS.zip you attached is corrupt and cannot be opened. It's up to you if you want to continue this thread or not. Don't worry about my time. If you want to continue zip the cbs.log again and attach it to your next reply.
D David86 Well-known member Joined Feb 12, 2020 Posts 129 Feb 5, 2023 #91 Аttached cbs.log. I repacked the logs and checked the unpacking several times. I think this time everything will be fine. Attachments CBS.zip 14.3 MB · Views: 2
Аttached cbs.log. I repacked the logs and checked the unpacking several times. I think this time everything will be fine.
P PeterJ Moderator, Windows Update Expert, Security Analyst Staff member Joined Dec 14, 2014 Posts 12,643 Feb 5, 2023 #92 Thank you. Found the reason for error 0x80073701. Step 1: Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine. Download the attachment fixlist.txt and save it to your desktop. Right-click on FRST64.exe and select "Run as administrator". Press the Fix button. The tool will now process fixlist.txt. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from. Attach the logfile Fixlog.txt to your next reply. Step 2: Restart the machine. Run the command dism /online /cleanup-image /restorehealth again in an elevated commandprompt and report the result. Attachments fixlist.txt 1.1 KB · Views: 1
Thank you. Found the reason for error 0x80073701. Step 1: Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine. Download the attachment fixlist.txt and save it to your desktop. Right-click on FRST64.exe and select "Run as administrator". Press the Fix button. The tool will now process fixlist.txt. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from. Attach the logfile Fixlog.txt to your next reply. Step 2: Restart the machine. Run the command dism /online /cleanup-image /restorehealth again in an elevated commandprompt and report the result.
D David86 Well-known member Joined Feb 12, 2020 Posts 129 Feb 6, 2023 #93 Unfortunately, both problems were not solved (. Spoiler: pic Attachments dism.log 831.7 KB · Views: 0 CBS.zip 15.2 MB · Views: 2
P PeterJ Moderator, Windows Update Expert, Security Analyst Staff member Joined Dec 14, 2014 Posts 12,643 Feb 6, 2023 #94 As I said earlier the cbs.log does not contain all faulty lines in one log so we need to repeat this procedure several times. According to the logs we are making progress. Step 1: Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine. Download the attachment fixlist.txt and save it to your desktop. Right-click on FRST64.exe and select "Run as administrator". Press the Fix button. The tool will now process fixlist.txt. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from. Attach the logfile Fixlog.txt to your next reply. Step 2: Restart the machine. Run the command dism /online /cleanup-image /restorehealth again in an elevated commandprompt and report the result. Attachments fixlist.txt 43.3 KB · Views: 1
As I said earlier the cbs.log does not contain all faulty lines in one log so we need to repeat this procedure several times. According to the logs we are making progress. Step 1: Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine. Download the attachment fixlist.txt and save it to your desktop. Right-click on FRST64.exe and select "Run as administrator". Press the Fix button. The tool will now process fixlist.txt. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from. Attach the logfile Fixlog.txt to your next reply. Step 2: Restart the machine. Run the command dism /online /cleanup-image /restorehealth again in an elevated commandprompt and report the result.
D David86 Well-known member Joined Feb 12, 2020 Posts 129 Feb 7, 2023 #95 All the same errors in Dism and component removal. Attachments Fixlog.txt 90.9 KB · Views: 1 CBS.zip 7.6 MB · Views: 2 dism.log 1.2 MB · Views: 0
P PeterJ Moderator, Windows Update Expert, Security Analyst Staff member Joined Dec 14, 2014 Posts 12,643 Feb 7, 2023 #96 We are making progress. Step 1: Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine. Download the attachment fixlist.txt and save it to your desktop. Right-click on FRST64.exe and select "Run as administrator". Press the Fix button. The tool will now process fixlist.txt. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from. Attach the logfile Fixlog.txt to your next reply. Step 2: Restart the machine. Run the command dism /online /cleanup-image /restorehealth again in an elevated commandprompt and report the result. Attachments fixlist.txt 42.9 KB · Views: 2
We are making progress. Step 1: Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine. Download the attachment fixlist.txt and save it to your desktop. Right-click on FRST64.exe and select "Run as administrator". Press the Fix button. The tool will now process fixlist.txt. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from. Attach the logfile Fixlog.txt to your next reply. Step 2: Restart the machine. Run the command dism /online /cleanup-image /restorehealth again in an elevated commandprompt and report the result.
D David86 Well-known member Joined Feb 12, 2020 Posts 129 Feb 8, 2023 #97 Nothing has changed. The CBS log is really too huge when you try to remove the server component. Attachments CBS.zip 7.6 MB · Views: 2 Fixlog.txt 90.1 KB · Views: 1 dism.log 215.4 KB · Views: 0
P PeterJ Moderator, Windows Update Expert, Security Analyst Staff member Joined Dec 14, 2014 Posts 12,643 Feb 8, 2023 #98 As I already said, we are making progress. Step 1: Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine. Download the attachment fixlist.txt and save it to your desktop. Right-click on FRST64.exe and select "Run as administrator". Press the Fix button. The tool will now process fixlist.txt. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from. Attach the logfile Fixlog.txt to your next reply. Step 2: Restart the machine. Run the command dism /online /cleanup-image /restorehealth again in an elevated commandprompt and report the result. Attachments fixlist.txt 42.8 KB · Views: 1
As I already said, we are making progress. Step 1: Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine. Download the attachment fixlist.txt and save it to your desktop. Right-click on FRST64.exe and select "Run as administrator". Press the Fix button. The tool will now process fixlist.txt. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from. Attach the logfile Fixlog.txt to your next reply. Step 2: Restart the machine. Run the command dism /online /cleanup-image /restorehealth again in an elevated commandprompt and report the result.
D David86 Well-known member Joined Feb 12, 2020 Posts 129 Feb 9, 2023 #99 The server again failed to boot correctly after restart (I'm looking for the reason). The Dism check gave the same error, the Desktop Experience role is also not removed 0x800f0831. Attachments dism.log 58.6 KB · Views: 0 CBS.zip 7.6 MB · Views: 2 Fixlog.txt 90 KB · Views: 1
The server again failed to boot correctly after restart (I'm looking for the reason). The Dism check gave the same error, the Desktop Experience role is also not removed 0x800f0831.
P PeterJ Moderator, Windows Update Expert, Security Analyst Staff member Joined Dec 14, 2014 Posts 12,643 Feb 9, 2023 #100 The server again failed to boot correctly after restart (I'm looking for the reason). Click to expand... Not sure but probably due to the partially fix. Unfortunately the only thing to do is to move on until the issues are solved. Step 1: Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine. Download the attachment fixlist.txt and save it to your desktop. Right-click on FRST64.exe and select "Run as administrator". Press the Fix button. The tool will now process fixlist.txt. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from. Attach the logfile Fixlog.txt to your next reply. Step 2: Restart the machine. Run the command dism /online /cleanup-image /restorehealth again in an elevated commandprompt and report the result. Attachments fixlist.txt 42.7 KB · Views: 1
The server again failed to boot correctly after restart (I'm looking for the reason). Click to expand... Not sure but probably due to the partially fix. Unfortunately the only thing to do is to move on until the issues are solved. Step 1: Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine. Download the attachment fixlist.txt and save it to your desktop. Right-click on FRST64.exe and select "Run as administrator". Press the Fix button. The tool will now process fixlist.txt. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from. Attach the logfile Fixlog.txt to your next reply. Step 2: Restart the machine. Run the command dism /online /cleanup-image /restorehealth again in an elevated commandprompt and report the result.