[SOLVED] Windows 2012R2 can't full update

David86 · Feb 1, 2023

It is written that the operation was successfully completed, but there are no kb4499151 updates in the collection of updates (.

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%========================= ]
Операция успешно завершена.

PeterJ · Feb 1, 2023

The cbs.log looks good.
Check Windows Update and report the result first.

David86 · Feb 2, 2023

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.

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>

PeterJ · Feb 2, 2023

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.

David86 · Feb 2, 2023

Аttached

PeterJ · Feb 2, 2023

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.

David86 · Feb 3, 2023

Unfortunately the error is still present Error: 1168
element not found.

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

PeterJ · Feb 3, 2023

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.

David86 · Feb 5, 2023

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.

PeterJ · Feb 5, 2023

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.

David86 · Feb 5, 2023

Аttached cbs.log. I repacked the logs and checked the unpacking several times. I think this time everything will be fine.

PeterJ · Feb 5, 2023

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.

David86 · Feb 6, 2023

Unfortunately, both problems were not solved (.

PeterJ · Feb 6, 2023

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.

David86 · Feb 7, 2023

All the same errors in Dism and component removal.

PeterJ · Feb 7, 2023

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.

David86 · Feb 8, 2023

Nothing has changed. The CBS log is really too huge when you try to remove the server component.

PeterJ · Feb 8, 2023

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.

David86 · Feb 9, 2023

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.

PeterJ · Feb 9, 2023

The server again failed to boot correctly after restart (I'm looking for the reason).

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.

[SOLVED] Windows 2012R2 can't full update

Well-known member

Attachments

Moderator, Windows Update Expert, Security Analyst

Well-known member

Attachments

Moderator, Windows Update Expert, Security Analyst

Well-known member

Attachments

Moderator, Windows Update Expert, Security Analyst

Attachments

Well-known member

Attachments

Moderator, Windows Update Expert, Security Analyst

Attachments

Well-known member

Attachments

Moderator, Windows Update Expert, Security Analyst

Well-known member

Attachments

Moderator, Windows Update Expert, Security Analyst

Attachments

Well-known member

Attachments

Moderator, Windows Update Expert, Security Analyst

Attachments

Well-known member

Attachments

Moderator, Windows Update Expert, Security Analyst

Attachments

Well-known member

Attachments

Moderator, Windows Update Expert, Security Analyst

Attachments

Well-known member

Attachments

Moderator, Windows Update Expert, Security Analyst

Attachments