Dism windows server 2019 — Ваш верный помощник с OS Windows

In this tutorial you will learn how to repair Windows Server 2019 installation with DISM. If you’re experiencing problems with your Windows Server 2019 installation, using the DISM /restorehealth can help repair it. DISM is a command-line tool that can scan and fix issues with Windows images, including those used by the Server operating system. This process can be done by following a few simple steps such as opening an elevated command prompt, running the DISM tool, waiting for the process to complete, and restarting your system.

Remember to always have a backup. Or if it’s a virtual machine at least a snapshot.

1.Lets get started by Opening up CMD as administrator and running the following:

dism /online /cleanup-image /scanhealth

2. Once /scanhealth is complete, run the following.

dism /online /cleanup-image /checkhealth

3. Now lets mount your Windows Server 2019 ISO as a drive. Take note of your mounted drive letter because you may need to change it to reflect it within this next command. Start elevated command prompt.

dism /online /cleanup-image /restorehealth /source:WIM:d:\sources\install.wim:2 /limitaccess

4. Now run the following to find and repair additional corruption

5. Hopefully all has been repaired restart your server, then run some windows updates and you should be good to go.

I hope this article was helpful, if you have any questions, please feel free to contact me. If you would like to be notified of when I create a new post, you can subscribe to my blog alert.

Discover more from Patrick Domingues

Subscribe to get the latest posts sent to your email.

Источник

Для проверки целостности системных файлов и восстановления поврежденных файлов (библиотек) компонентов в Windows (Windows Server) можно использовать команды SFC и DISM. Эти две утилиты могут быть крайне полезными, если операционная система Windows работает нестабильно, появляются ошибки при запуске стандартных приложений или служб, после вирусного заражения и т.д.

В этой статье мы рассмотрим, как использовать команды
sfc /scannow
,
DISM /Online /Cleanup-Image /RestoreHealth
или
Repair-WindowsImage -Online -RestoreHealth
для восстановления образа и системных фалов в Windows 10/11 и Windows Server 2022/2019/2016.

Содержание:

SFC /scannow: восстановление системных файлов Windows
Проверка целостности хранилища компонентов Windows с помощью DISM
Восстановление образа Windows с помощью DISM /RestoreHealth
DISM /Source: восстановление образа Windows с установочного диска
Восстановление образа Windows с помощью PowerShell
DISM: восстановление поврежденного хранилища компонентов, если Windows не загружается

SFC /scannow: восстановление системных файлов Windows

Перед тем, как восстанавливать образ Windows с помощью DISM, рекомендуется сначала попробовать проверить целостность системных файлов с помощью утилиты SFC (System File Checker). Команда
sfc /scannow
позволяет проверить целостность системных файлов Windows. Если какие-то системные файлы отсутствуют или повреждены, утилита SFC попробует восстановить их оригинальные копии из хранилища системных компонентов Windows (каталог C:\Windows\WinSxS).

Утилита SFC записывает все свои действия в лог-файл
windir%\logs\cbs\cbs.log
. Для всех записей, оставленных SFC в файле CBS.log проставлен тег [SR]. Чтобы выбрать из лога только записи, относящиеся к SFC, выполните команду:

findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfc.txt"

Если команда sfc /scannow возвращает ошибку “
Программа защиты ресурсов Windows обнаружила повреждённые файлы, но не может восстановить некоторые из них / Windows Resource Protection found corrupt files but was unable to fix some of them
”, скорее всего утилита не смогла получить необходимые файла из хранилища компонентов (образа) Windows.

sfc /scannow Программа защиты ресурсов Windows обнаружила повреждённые файлы, но не может восстановить некоторые из них

В этом случае вам нужно попробовать восстановить хранилище компонентов вашего образа Windows с помощью DISM.

После восстановления образа вы можете повторно использовать утилиту SFC для восстановления системных файлов.

Проверка целостности хранилища компонентов Windows с помощью DISM

Утилита DISM (Deployment Image Servicing and Management) доступна во всех версиях Windows, начиная с Vista.

Для сканирования образа Windows на наличие ошибок и их исправления используется параметр DISM /Cleanup-image. Команды DISM нужно запускать из командной строки, с правами администратора.

Чтобы проверить наличие признака повреждения хранилища компонентов в образе Windows (флаг CBS), выполните команду (не применимо к Windows 7/Server 2008R2):

DISM /Online /Cleanup-Image /CheckHealth

Эта команда не выполняет полное сканирование хранилища компонентов. Проверяются лишь записанные ранее маркеры повреждений и события в журнале Windows. Изменения в образ не вносятся. Команда проверит, не помечен ли ваш образ Windows как поврежденный и возможно ли исправить его.

DISM /CheckHealth - проверка повреждений в образе windows

В этом примере команда вернула, что с образом все хорошо:

No component store corruption detected.
The operation completed successfully.

Чтобы выполнить полное сканирование хранилища компонентов на наличие повреждений в хранилище компонентов Windows, запустите команду:

DISM /Online /Cleanup-Image /ScanHealth

Команда проверки образа Windows может выполняться довольно долго (от 10 до 30 минут). И вернет один из трех результатов:

No component store corruption detected – DISM не обнаружил повреждения в хранилище компонентов;
The component store is repairable – DISM обнаружил ошибки в хранилище компонентов и может исправить их;
The component store is not repairable – DISM не может исправить хранилище компонентов Windows (попробуйте использовать более новую версию DISM или вам придется восстанавливать образ Windows из резервной копии, сбрасывать или полностью переустанавливать вашу копию Windows.

DISM Cleanup-Image ScanHealth проверить хранилище компонентов Windows, хранилище компонентов можно исправить

В Windows 7 и Windows Server 2008 R2 для использования параметра DISM /ScanHealth нужно установить отдельное обновление KB2966583. Иначе при запуске DISM будет появляться “
Ошибка 87. Параметр ScanHealth не распознан в этом контексте
”.

Команда DISM /ScanHealth может вернуть ошибки:

Ошибка: 1726. Сбой при удалённом вызове процедуры;
Ошибка: 1910. Не найден указанный источник экспорта объекта.

Это однозначно говорит о том, что ваш образ Windows поврежден и его нужно восстановить.

Восстановление образа Windows с помощью DISM /RestoreHealth

Чтобы исправить повреждения в хранилище компонентов образа Windows нужно использовать опцию RestoreHealth команды DISM. Эта опция позволит исправить найденные в образе ошибки, автоматически скачать и заменить файлы повреждённых или отсутствующих компонентов эталонными версиями файлов из центра обновлений Windows (на компьютере должен быть доступ в Интернет). Выполните команду:

DISM /Online /Cleanup-Image /RestoreHealth

В Windows 7/2008 R2 эта команда выглядит по другому:
DISM.exe /Online /Cleanup-Image /ScanHealth

Процесс сканирования и восстановления компонентов может быть довольно длительным (30 минут или более). DISM автоматически загрузит недостающие или поврежденные файлы образа с серверов Windows Update.

Восстановление выполнено успешно. Операция успешно завершена.

The restore operation completed successfully.

DISM /Online /Cleanup-Image /RestoreHealth - восстановление образа windows 10

DISM /Source: восстановление образа Windows с установочного диска

Если на компьютере (сервере) отсутствует доступ в Интернет или отключена/повреждена служба Windows Update (как восстановить клиент Windows Update), то при восстановлении хранилища компонентов появятся ошибки:

0x800f0906 — Не удалось скачать исходные файлы. Укажите расположение файлов, необходимых для восстановления компонента, с помощью параметра Источник (0x800f0906 — The source files could not be downloaded. Use the source option to specify the location of the files that are required to restore the feature);
Ошибка: 0x800f0950 — Сбой DISM. Операция не выполнена (0x800f0950 — DISM failed. No operation was performed);
Ошибка:0x800F081F. Не удалось найти исходные файлы. Укажите расположение файлов, необходимых для восстановления компонента, с помощью параметра Источник (Error 0x800f081f, The source files could not be found. Use the «Source» option to specify the location of the files that are required to restore the feature).

DISM /RestoreHealth Error 0x800f081f, The source files could not be found

Во всех этих случаях вы можете использовать альтернативные средства получения оригинальных файлов хранилища компонентов. Это может быть:

Установочный диск/флешка/iso образ Windows
Смонтированный файл wim
Папка \sources\SxS с установочного диска
Файл install.wim с установочным образом Windows

Вы можете указать WIM или ESD файл с оригинальным установочным образом Windows, который нужно использовать в качестве источника для восстановления файлов системы. Предположим, вы смонтировали установочный ISO образ Windows 11 в виртуальный привод D:.

Примечание. Для восстановления поврежденных файлов в хранилище компонентов из локального источника версия и редакция Windows в образе должна полностью совпадать с вашей.

С помощью следующей PowerShell команды проверьте, какая версия Windows установлена на вашем компьютере:

Get-ComputerInfo |select WindowsProductName,WindowsEditionId,WindowsVersion, OSDisplayVersion

powershell Get-ComputerInfo получить номер билда и редакцию windows

Выведите список доступных версий Windows в установочном образе:

Get-WindowsImage -ImagePath "D:\sources\install.wim"

В нашем случае образ Windows 11 Pro в образе install.wim имеет
ImageIndex = 6
.

Для восстановления хранилища компонентов из локального WIM/ESD файла с блокированием доступа в интернет, выполните следующую команду (не забудьте указать ваш индекс версии Windows в файле):

DISM /online /cleanup-image /restorehealth /source:WIM:D:\sources\install.wim:6 /limitaccess

Или:
DISM /online /cleanup-image /restorehealth /source:ESD:D:\sources\install.esd:6 /limitaccess

dism restorehealth source: восстановить хранилище компонентов из оригинального образа Windows на установочном диске, ISO, WIM файле

Если при запуске появляется

Ошибка Error: 50: DISM does not support servicing Windows PE with the /Online option, значит ваша DISM считает, что вы используете WinPE образWindows. Чтобы исправить это, удалите ветку реестра HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\MiniNT.

Ошибка DISM Error 87: проверьте правильно написания команды, убедитесь что вы используете версию DISM для вашей версии Windows (обычно бывает при загрузке через WinPE/WinRE).

Утилита DISM пишет подробный журнал сканирования и восстановления системных файлов в файл
C:\Windows\Logs\DISM\dism.log
.

После восстановления хранилища компонентов вы можете запустить утилиту проверки системных файлов
sfc /scannow
. Скорее всего она успешно восстановит поврежденные файлы:

Программа защиты ресурсов Windows обнаружила поврежденные файлы и успешно их восстановила.

Windows Resource Protection found corrupt files and successfully repaired them.

sfc /scannow Программа защиты ресурсов Windows обнаружила поврежденные файлы и успешно их восстановила

Если все системные файлы целы, появится сообщение:

Windows Resource Protection did not find any integrity violations

Восстановление образа Windows с помощью PowerShell

В версии PowerShell в Windows 10/11 и Windows Server 2022/2019 есть аналоги рассмотренных выше команд DISM. Для сканирования хранилища компонентов и поиска повреждений в образе выполните:

Repair-WindowsImage -Online –ScanHealth

Если ошибок в хранилище компонентов не обнаружено, появится сообщение:

ImageHealth State: Healthy

Для запуска восстановления системных компонентов и файлов наберите:

Repair-WindowsImage -Online -RestoreHealth

При отсутствии доступа к интернету эта команда может зависнуть в процессе восстановления образа. Вы можете восстановить системные компоненты из локальной копии образа Windows в виде WIM/ESD файла, скопированного с установочного ISO образа Windows 10 (здесь также нужно указать индекс версии Windows в wim файле в качестве источника восстановления):

Repair-WindowsImage -Online -RestoreHealth -Source D:\sources\install.wim:5 –LimitAccess

DISM: восстановление поврежденного хранилища компонентов, если Windows не загружается

Если Windows не загружается корректно, вы можете выполнить проверку и исправление системных файлов в оффлайн режиме.

Для этого загрузите компьютер с установочного образа Windows (проще всего создать загрузочную USB флешку с Windows 10/11 с помощью Media Creation Tool) и на экране начала установки нажмите
Shift + F10
Чтобы разобраться с буквами дисков, назначенных в среде WinPE, выполните команду
diskpart
->
list vol
(в моем примере диску, на котором установлена Windows присвоена буква C:\, эту букву я буду использовать в следующих командах);

Картинка с сайта: winitpro.ru
Проверим системные файлы и исправим поврежденные файлы командой:
sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows

$sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows$

Картинка с сайта: winitpro.ru
Для исправления хранилища компонентов используйте следующую команду (в качестве источника для восстановления компонентов мы используем WIM файл с установочным образом Windows 10, с которого мы загрузили компьютер):
Dism /image:C:\ /Cleanup-Image /RestoreHealth /Source:WIM:D:\sources\install.wim:6

Картинка с сайта: winitpro.ru
Если на целевом диске недостаточно места, то для извлечения временных файлов нам понадобится отдельный диск достаточного размера, например F:\, на котором нужно создать пустой каталог:
mkdir f:\scratch
и запустить восстановление хранилища компонентов командой:
Dism /image:C:\ /Cleanup-Image /RestoreHealth /Source:D:\sources\install.wim /ScratchDir:F:\scratch

Совет. Другие полезные команды DISM, которые должен знать администратор:

DISM /Add-Package
– установка MSU/CAB файлов обновлений, интеграция обновлений в образ Windows;
DISM /Get-Drivers
– получение списка установленных драйверов;
DISM /Add-Driver
– добавление драйверов в образ;
DISM /Export-Driver
– экспорт установленных драйверов Windows;
DISM /Add-Capability
– установка дополнительных компонентов Windows через Features on Demand (например, RSAT, сервер OpenSSH или ssh клиент Windows;
DISM /Enable-Features
и
/Disable-Features
– включение и отключение компонентов Windows (например, протокола SMBv1),
DISM /online /Cleanup-Image /StartComponentCleanup
– очистка хранилища компонентов и удаление старых версий компонентов (папки WinSxS);
DISM /set-edition
– конвертирование ознакомительной редакции Windows на полную без переустановки.

Источник

- GitHub Copilot
  
  Write better code with AI
- GitHub Advanced Security
  
  Find and fix vulnerabilities
- Actions
  
  Automate any workflow
- Codespaces
  
  Instant dev environments
- Issues
  
  Plan and track work
- Code Review
  
  Manage code changes
- Discussions
  
  Collaborate outside of code
- Code Search
  
  Find more, search less
Explore
- Learning Pathways
- Events & Webinars
- Ebooks & Whitepapers
- Customer Stories
- Partners
- Executive Insights
- GitHub Sponsors
  
  Fund open source developers
- The ReadME Project
  
  GitHub community articles
- Enterprise platform
  
  AI-powered developer platform
Pricing

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Источник

You can use the SFC (System File Checker) and DISM (Deployment Image Servicing and Management) commands to check and repair the integrity of system files and Component Store of your Windows (Windows Server) image. These tools can be extremely useful if your Windows is unstable, won’t boot, errors appear when you try to run built-in apps or services, after a virus infection, etc.

In this article, we’ll take a look at how to use the SFC /ScanNow, DISM /Online /Cleanup-Image /RestoreHealth, or Repair-WindowsImage -Online -RestoreHealth commands to repair image and system files on Windows 10/11 and Windows Server 2022/2019/2016.

Contents:

SFC /ScanNow: Using System File Checker to Repair Windows System Files
Check Windows Component Store Health Using DISM
Repair Windows Image Using DISM /RestoreHealth
DISM /RestoreHealth: The Source Files Could Not Be Found
Repair-WindowsImage: Repairing Windows Image Component Store with PowerShell
Use DISM Offline to Repair Windows Image

SFC /ScanNow: Using System File Checker to Repair Windows System Files

It is recommended to use the DISM command to restore Windows after you have checked the integrity of your system files using the SFC tool. The sfc /scannow command scans protected system files and if they are missing or corrupted it tries to restore their original copies versions to the Windows Component Store (C:\Windows\WinSxS folder).

The SFC tool writes all its activities to the %windir%\logs\cbs\cbs.log . All SFC entries in the CBS.log file are tagged with [SR]. To select only SFC-related entries from the log, run the command:

findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfc.txt"

If sfc /scannow command returns the error “Windows Resource Protection found corrupt files but was unable to fix some of them“, it is likely that the tool could not get the necessary files from the Windows Component Store (see the image below).

sfc /scannow Windows Resource Protection found corrupt files but was unable to fix some of them

In this case, you can try to repair the Component Store of your Windows image using the DISM.exe command.

The DISM (Deployment Image Servicing and Management) tool is available in all versions of Windows starting from Vista.

After repairing the Windows image, you can try using SFC to restore your system files.

Check Windows Component Store Health Using DISM

The DISM /Cleanup-Image /CheckHealth switch is used to scan the Windows image for errors and fix them. DISM commands must be run from the elevated command prompt.

Run the following command to check if there are any flags of corruption in the Windows image Component Store (not applicable for Windows 7/Server 2008R2). This command checks the CBS flag set by one of the system maintenance processes.

DISM /Online /Cleanup-Image /CheckHealth

This command doesn’t perform a full scan of the Component Store. The command only checks if your Windows image is flagged as corrupted and if it is possible to fix it. No changes are made to the image.

DISM /Cleanup-Image /CheckHealth - check windows 10 image

In this example, the command has returned that the Windows 10 image has no corruptions:

No component store corruption detected.
The operation completed successfully.

To run a full scan of the Windows Component Store health, run the command:

DISM /Online /Cleanup-Image /ScanHealth

The command to check the Windows image can take quite a long time (10-30 minutes). And will return one of three results:

No component store corruption detected – DISM found no errors in the component store;
The component store is repairable – DISM has encountered errors in the Component Store and can fix them;
The component store is not repairable – DISM cannot fix the Windows Component Store (try using a newer version of DISM or you will have to restore a Windows image from a backup, reset or completely reinstall your Windows instance).

To use DISM /ScanHealth switch on Windowds 7 and Windows Server 2008, you have to install the KB2966583 update. Otherwise, you will see the message: “Error 87. The ScanHealth option is not recognized in this context”.

In some cases, the DISM /ScanHealth returns the following errors:

DISM Error 1726 – “The remote procedure call failed”;
DISM Error 1910 – “The object exporter specified was not found”.

It definitely means that your Windows image is corrupted and needs to be repaired.

Repair Windows Image Using DISM /RestoreHealth

To fix corruption in the Windows image Component Store, you must use the RestoreHealth option of the DISM command. This option will allow you to fix errors found in the Windows image, and automatically download and replace files of damaged or missing components with original versions of files from Windows Update (your computer must have direct Internet access). Run the command:

DISM /Online /Cleanup-Image /RestoreHealth

In Windows 7/2008 R2, this command looks different:
DISM.exe /Online /Cleanup-Image /ScanHealth

The process of scanning and repairing the Component Store may take quite a long time (30 minutes or more). DISM will automatically download and replace the files of corrupted or missing components with original file versions from Windows Update servers.

If the repair has been successful, the following message will appear:

The restore operation completed successfully.

DISM /Online /Cleanup-Image /RestoreHealth - The restore operation completed successfully

DISM /RestoreHealth: The Source Files Could Not Be Found

If your computer (server) has no direct Internet access (located behind a proxy, or have used internal WSUS to get security and build updates) or Windows Update service is disabled/damaged (how to repair Windows Update client), then the following errors appear when repairing the Component Store:

0x800f0906 – The source files could not be downloaded. Use the source option to specify the location of the files that are required to restore the feature;
0x800f0950 – DISM failed. No operation was performed;
0x800F081F – The source files could not be found. Use the “Source” option to specify the location of the files that are required to restore the feature.

dism error 0x800F081F - The source files could not be found. Use the “Source” option to specify the location of the files that are required to restore the feature

In all of these cases, you can use alternative ways to get the source Component Store files. It can be:

Installation disk/USB flash drive/ISO image;
Mounted wim/esd file;
Folder \sources\SxS from the installation disk;
The install.wim (esd) file with the Windows installation image.

You can specify a WIM or an ESD file with the original Windows installation image to be used as a source to repair the system files. Suppose, you have an installation Windows 11 ISO mounted to the virtual drive D:.

Check which version of Windows is installed on your computer using the following PowerShell command:

Get-ComputerInfo |select WindowsProductName,WindowsEditionId,WindowsVersion, OSDisplayVersion

powershell: get current windows edition and version

List the available Windows editions in the installation wim image:

Get-WindowsImage -ImagePath "D:\sources\install.wim"

In our case, the Windows 11 Pro image in the install.wim file has ImageIndex = 6.

To repair the Component Store from a local WIM/ESD file using the local source files (without using Windows Update online services), run the following command (remember to specify the Windows version index in the image file):

DISM /online /cleanup-image /restorehealth /source:WIM:D:\sources\install.wim:6 /limitaccess
or:
DISM /online /cleanup-image /restorehealth /source:ESD:D:\sources\install.esd:6 /limitaccess

dism /clenup-image /restorehealth command in windows 11

The following errors can appear when running the DISM /RestoreHealth command:

Error: 50: DISM does not support servicing Windows PE with the /Online option – this means your DISM thinks you are using a WinPE image. To fix this, remove the registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\MiniNT;
DISM Error 87: make sure the DISM command is written correctly, and make sure you are using the DISM version for your Windows version (usually when booting in WinPE/ WinRE).

You can find the DISM log of scanning and repair of the system files here: C:\Windows\Logs\CBS.log.

After the component store has been repaired, you can run the system file checker tool (sfc /scannow). It is likely that it will be able to restore the damaged or missing system files (Windows Resource Protection found corrupt files and successfully repaired them).

tool sfc /scannow - Windows Resource Protection found corrupt files and successfully repaired them

If the SFC.exe doesn’t detect any damage to the system files, a message will appear

Windows Resource Protection did not find any integrity violations.

Repair-WindowsImage: Repairing Windows Image Component Store with PowerShell

The version of PowerShell in Windows 10/11 and Windows Server 2016/2019/2022 has a cmdlet similar to the DISM commands discussed above. To scan the Windows component store and find any corruptions, run this command:

Repair-WindowsImage -Online –ScanHealth

If no errors are found in the Component Store, the following message appears:

ImageHealth State: Healthy

To repair Windows Component Store files, run:

Repair-WindowsImage -Online -RestoreHealth

If you don’t have direct Internet access, this command may hang during the image repairing process. You can restore the system components from the local Windows image file (install.wim/install.esd) copied from the Windows 10 installation ISO image. Here you also need to specify the Windows version index in the WIM file as the recovery source:

Repair-WindowsImage -Online -RestoreHealth -Source F:\sources\install.wim:5 -LimitAccess

Use DISM Offline to Repair Windows Image

If Windows doesn’t boot correctly, you can use DISM to check and repair system files of your Windows image offline.

Boot your device from the Windows installation image (you can use the Media Creation Tool to create a bootable Windows USB stick) and press Shift + F10 on the initial Windows install screen;
To check the drive letters assigned in WinPE, run the command diskpart -> list vol (in my example, the drive letter C:\ is assigned to the disk, on which Windows is installed, and I will use it in the next commands);

Картинка с сайта: woshub.com
Check the system files and repair the corrupted ones with the command: sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows

Картинка с сайта: woshub.com
To repair the offline Windows image, use the following command (I am using a WIM file with the Windows 10 installation image from which the computer is booted as a source to restore my offline Windows image):
Dism /image:C:\ /Cleanup-Image /RestoreHealth /Source:D:\sources\install.wim

Картинка с сайта: woshub.com
If there is not enough free space on the target disk, you will need a separate drive, for example, F:\, on which you will create an empty folder mkdir F:\scratch . Perform a repair of the component store using the scratch dir with the command: Dism /image:C:\ /Cleanup-Image /RestoreHealth /Source:D:\sources\install.wim /ScratchDir:F:\scratch

Tip. Here are some useful DISM parameters an administrator must know:

DISM /Add-Package –install MSU/CAB update files, integrate security updates into your Windows image;
DISM /Get-Drivers – get the list of installed drivers;
DISM /Add-Driver – inject drivers to Windows installation image;
DISM /Add-Capability – installing additional Windows features via Features on Demand (FoD). For example, RSAT, OpenSSH server, or Windows SSH client);
DISM /Enable-Features and /Disable-Features – enabling and disabling Windows components (for example, the SMBv1 protocol);
Dism.exe /StartComponentCleanup – cleanup the Component Store and remove old component versions (from the WinSxS folder);
Dism /set-edition – upgrading from the evaluation to the full Windows version without reinstalling.

Источник

Microsoft Support & Malware Removal
Windows Update

You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.

[SOLVED] Windows Server 2019 SFC/DISM corruption

Thread starter
Thread starter

talishka
Start date
Start date

Aug 23, 2019

Hi!

I’m having issues with one of my servers, i’ve already done chkdsk with no errors, sfc found issues a but cannot fix them.. I also tried with DISM command but it’s impossible (Online or Source), i need some help!

The issue started suddenly, the server stops responding everything but ping, so there’s not other walkaround but a hard reset..

I’ve attached my cbs and sfc reports.

Thanks in advance!

Attachments

DISM_and_CBS.ZIP

Joined: Oct 9, 2014

Posts: 741

Hi softwaremaniac! Long time!

I’ll work on it, and i’ll give you feedback asap.

Thanks!

No luck, i’ve updated my server, i have no updates left for install but the error keeps popin up.

The repairs doesn’t work at all. Have you fixed this issue yet?

My repairs fails:

PS C:\Windows\system32> DISM /Online /Cleanup-Image /RestoreHealth /Source:C:\Temp\Win2019\sources\install.wim

Deployment Image Servicing and Management tool
Version: 10.0.17763.1

Image Version: 10.0.17763.720

[==========================100.0%==========================]
Error: 0x800f081f

The source files could not be found.
Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see http://go.microsoft.com/fwlink/?LinkId=243077.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

PS C:\Windows\system32> DISM /Online /Cleanup-Image /RestoreHealth /Source:WIM:C:\Temp\Win2019\sources\install.wim

Deployment Image Servicing and Management tool
Version: 10.0.17763.1

Image Version: 10.0.17763.720


Error: 87

An error occurred while processing WIM:C:\Temp\Win2019\sources\install.wim. The specified path was not found.
Ensure that the argument is valid and that the path exists.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

Joined: Oct 9, 2014

Posts: 741

You are using wrong DISM parameters:

Step#1 — DISM /RestoreHealth Scan
Warning:this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

Right-click on the Start button and select Command Prompt (Admin)
When command prompt opens, Copy (Ctrl+C) and Paste (Right-click > Paste) the following command into it, then press Enter
Dism /Online /Cleanup-Image /RestoreHealth
Once it finishes, copy and paste the following into the command-prompt window and press Enter. If prompted to overwrite the existing file go ahead.
copy %windir%\logs\cbs\cbs.log «%userprofile%\Desktop\cbs.txt»
Once this has completed please go to your Desktop and you will find CBS.txt => Please zip/upload to this thread.
Please Note:: if the file is too big (over 7MB) to upload to your next post, please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link.

I was executing those commands because of this error:

PS C:\Windows\system32> Dism /Online /Cleanup-Image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 10.0.17763.1

Image Version: 10.0.17763.720

[==========================100.0%==========================]
Error: 0x800f081f

The source files could not be found.
Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see http://go.microsoft.com/fwlink/?LinkId=243077.

Joined: Oct 9, 2014

Posts: 741

Can I please see the new CBS.log?

Joined: Oct 9, 2014

Posts: 741

SFCFix Script

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

Download SFCFix.exe (by niemiro) and save this to your Desktop.
Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip — do not rename it.
Save any open documents and close all open windows.
On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
SFCFix will now process the script.
Upon completion, a file should be created on your Desktop: SFCFix.txt.
Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please — put [CODE][/CODE] tags around the log to break up the text.

Attachments

SFCFix.zip

SFCFix version 3.0.2.1 by niemiro.
Start time: 2019-08-27 08:16:18.470
Microsoft Windows Server 10 Build 17763 - amd64
Using .zip script file at C:\Users\administrator.AXOFT\Desktop\SFCFix.zip [0]




PowerCopy::
Successfully took permissions for file or folder C:\Windows\Winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.1_none_d48944eff97b9138\Defender.psd1
Successfully took permissions for file or folder C:\Windows\Winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.1_none_d48944eff97b9138\MSFT_MpComputerStatus.cdxml
Successfully took permissions for file or folder C:\Windows\Winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.1_none_d48944eff97b9138\MSFT_MpPreference.cdxml
Successfully took permissions for file or folder C:\Windows\Winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.1_none_d48944eff97b9138\MSFT_MpScan.cdxml
Successfully took permissions for file or folder C:\Windows\Winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.1_none_d48944eff97b9138\MSFT_MpSignature.cdxml
Successfully took permissions for file or folder C:\Windows\Winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.1_none_d48944eff97b9138\MSFT_MpThreat.cdxml
Successfully took permissions for file or folder C:\Windows\Winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.1_none_d48944eff97b9138\MSFT_MpThreatCatalog.cdxml
Successfully took permissions for file or folder C:\Windows\Winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.1_none_d48944eff97b9138\MSFT_MpThreatDetection.cdxml
Successfully took permissions for file or folder C:\Windows\Winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.1_none_d48944eff97b9138\MSFT_MpWDOScan.cdxml

Successfully copied file C:\Users\administrator.AXOFT\AppData\Local\niemiro\Archive\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.1_none_d48944eff97b9138\Defender.psd1 to C:\Windows\Winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.1_none_d48944eff97b9138\Defender.psd1.
Successfully copied file C:\Users\administrator.AXOFT\AppData\Local\niemiro\Archive\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.1_none_d48944eff97b9138\MSFT_MpComputerStatus.cdxml to C:\Windows\Winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.1_none_d48944eff97b9138\MSFT_MpComputerStatus.cdxml.
Successfully copied file C:\Users\administrator.AXOFT\AppData\Local\niemiro\Archive\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.1_none_d48944eff97b9138\MSFT_MpPreference.cdxml to C:\Windows\Winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.1_none_d48944eff97b9138\MSFT_MpPreference.cdxml.
Successfully copied file C:\Users\administrator.AXOFT\AppData\Local\niemiro\Archive\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.1_none_d48944eff97b9138\MSFT_MpScan.cdxml to C:\Windows\Winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.1_none_d48944eff97b9138\MSFT_MpScan.cdxml.
Successfully copied file C:\Users\administrator.AXOFT\AppData\Local\niemiro\Archive\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.1_none_d48944eff97b9138\MSFT_MpSignature.cdxml to C:\Windows\Winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.1_none_d48944eff97b9138\MSFT_MpSignature.cdxml.
Successfully copied file C:\Users\administrator.AXOFT\AppData\Local\niemiro\Archive\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.1_none_d48944eff97b9138\MSFT_MpThreat.cdxml to C:\Windows\Winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.1_none_d48944eff97b9138\MSFT_MpThreat.cdxml.
Successfully copied file C:\Users\administrator.AXOFT\AppData\Local\niemiro\Archive\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.1_none_d48944eff97b9138\MSFT_MpThreatCatalog.cdxml to C:\Windows\Winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.1_none_d48944eff97b9138\MSFT_MpThreatCatalog.cdxml.
Successfully copied file C:\Users\administrator.AXOFT\AppData\Local\niemiro\Archive\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.1_none_d48944eff97b9138\MSFT_MpThreatDetection.cdxml to C:\Windows\Winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.1_none_d48944eff97b9138\MSFT_MpThreatDetection.cdxml.
Successfully copied file C:\Users\administrator.AXOFT\AppData\Local\niemiro\Archive\WinSxS\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.1_none_d48944eff97b9138\MSFT_MpWDOScan.cdxml to C:\Windows\Winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.1_none_d48944eff97b9138\MSFT_MpWDOScan.cdxml.

Successfully restored ownership for C:\Windows\Winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.1_none_d48944eff97b9138\Defender.psd1
Successfully restored permissions on C:\Windows\Winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.1_none_d48944eff97b9138\Defender.psd1
Successfully restored ownership for C:\Windows\Winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.1_none_d48944eff97b9138\MSFT_MpComputerStatus.cdxml
Successfully restored permissions on C:\Windows\Winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.1_none_d48944eff97b9138\MSFT_MpComputerStatus.cdxml
Successfully restored ownership for C:\Windows\Winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.1_none_d48944eff97b9138\MSFT_MpPreference.cdxml
Successfully restored permissions on C:\Windows\Winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.1_none_d48944eff97b9138\MSFT_MpPreference.cdxml
Successfully restored ownership for C:\Windows\Winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.1_none_d48944eff97b9138\MSFT_MpScan.cdxml
Successfully restored permissions on C:\Windows\Winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.1_none_d48944eff97b9138\MSFT_MpScan.cdxml
Successfully restored ownership for C:\Windows\Winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.1_none_d48944eff97b9138\MSFT_MpSignature.cdxml
Successfully restored permissions on C:\Windows\Winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.1_none_d48944eff97b9138\MSFT_MpSignature.cdxml
Successfully restored ownership for C:\Windows\Winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.1_none_d48944eff97b9138\MSFT_MpThreat.cdxml
Successfully restored permissions on C:\Windows\Winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.1_none_d48944eff97b9138\MSFT_MpThreat.cdxml
Successfully restored ownership for C:\Windows\Winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.1_none_d48944eff97b9138\MSFT_MpThreatCatalog.cdxml
Successfully restored permissions on C:\Windows\Winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.1_none_d48944eff97b9138\MSFT_MpThreatCatalog.cdxml
Successfully restored ownership for C:\Windows\Winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.1_none_d48944eff97b9138\MSFT_MpThreatDetection.cdxml
Successfully restored permissions on C:\Windows\Winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.1_none_d48944eff97b9138\MSFT_MpThreatDetection.cdxml
Successfully restored ownership for C:\Windows\Winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.1_none_d48944eff97b9138\MSFT_MpWDOScan.cdxml
Successfully restored permissions on C:\Windows\Winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.1_none_d48944eff97b9138\MSFT_MpWDOScan.cdxml
PowerCopy:: directive completed successfully.




Successfully processed all directives.



Failed to generate a complete zip file. Upload aborted.


SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 9 datablocks.
Finish time: 2019-08-27 08:20:16.513
Script hash: oEeFBZVwMHUK7M5+45gMk/VW0AtM/Fz70q0oqCQQgNo=
----------------------EOF-----------------------

Joined: Oct 9, 2014

Posts: 741

It’s fixed!

As usual thank you very much for your help!

Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.

PS C:\Windows\system32> sfc /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.
PS C:\Windows\system32> DISM /Online /Cleanup-Image /ScanHealth

Deployment Image Servicing and Management tool
Version: 10.0.17763.1

Image Version: 10.0.17763.720

[==========================100.0%==========================] No component store corruption detected.
The operation completed successfully.

Joined: Oct 9, 2014

Posts: 741

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

Microsoft Support & Malware Removal
Windows Update

Источник