Восстановление не удалось код ошибки 11 dism

  • Remove From My Forums

  • Question

  • I have been running MS systems since you needed to 5-1/4′ floppies to boot them. I know the difference between 32-bit and 64-bit systems. This one has me a bit frazzled.

    When I run Dism.exe, I consistently get the following error:

    Deployment Image Servicing and Management tool
    Version: 6.3.9600.17031

    Error: 11

    You cannot service a running 64-bit operating system with a 32-bit version of DISM.
    Please use the version of DISM that corresponds to your computer’s architecture.

    The DISM log file can be found at C:WINDOWSLogsDISMdism.log

    It’s obvious that the command that’s loading is the 32-bit version. I scanned the hard drive and found several versions of DISM.exe. Each time I get the same error, regardless of which DISM.exe I execute. Each time I was in an «elevated» cmd environment.
    I even tried going into Powershell and running it. Same problem. I have checked the path, just to be sure. sysWOW64 appears before system32 in the path variable.  I have tried running dism.exe from each individual location on the drive, just to make sure
    the «local» command is/was being executed. Same error.

    The reason for this is that sfc /scannow found some corrupted files it could not repair. I wanted to run the DISM command, then rerun the sfc command.

    Where can I find the 64-bit version of dism.exe? It should be on the hard drive somewhere or at least you would think so.

    I also tried running Powershell and the Repair-WindowsImage -Online -RestoreHealth.  It failed with a similar error.

    Outside of these commands, I will likely have to restore Windows 8.1 and start over.

    What prompted all this was the laptop started doing some flaky things. For example, when you try to open a cmd environment, the system would just stall and restart explorer.exe after a few minutes. This happened repeatedly. I was finally able to get a cmd
    environment to open from the directory where the command is located. After that, it worked flawlessly. Similar things were happening trying to run other commands/features. This all started after installation of one of the MS security patches.

    At this point, wiping the system and starting with a clean slate may be the best option.

    Oh — system running Windows 8.1, latest patches. HP Laptop 750GB HD, 6GB RAM, i3 processor.

    Bob

    Bob C., OCP

Answers

  • Hi Bob,

    No, there is no way to edit the registry, since registry editor need administrator permission. However, according to your description, you have no administrator account. Like my last post, admin (especially built-in admin) have full permission to take
    ownership of folder and change any user account type.

    To confirm this, please run this command:

    From the output, we would check if it’s in Administrator group. Or post the output here let us help you.

    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    • Marked as answer by

      Thursday, April 2, 2015 7:45 PM

  • Okay folks… I have found a fix. It will take a while to iron out the kinks, but I back tracked the problem to the root drive, c: in this case.

    From the error, we all knew that it was a permissions thing. I got a software package that lists the access rights for all folders, including subfolders, on a drive. After looking deeper, I found that my account and the Administrator account still have full
    rights to the root drive. So, I logged out as myself; logged in as Administrator. Then, I proceeded to «take» ownership of the folders/subfolders on the drive from the root drive — c:.  I got errors on some of them, but for the most part I
    can now access and work with all the things I need to work with.

    To be candid, I have no idea how the access rights got changed. Maybe they were that way from day one. But, I never have had a virus, nor any malware/spyware. I have scanned the drive with Norton, Malwarebytes, and several other virus/malware products. They
    have found none. Of course, it could be something that none of these products can detect, but I feel that is a remote possibility.

    I know that security has really changed in Windows 8 & 8.1. It could be a quirk, but it seems odd that I am the only one who has had this issue. 

    I think the only user that had «Full Access» to all folders/sub-folders was the Trusted Installer. That in itself seems suspect. 

    All that said, I am still having to having some access issues with a few folders/sub-folders. But, I now know what to do get that access back to where it was.

    Bob C., OCP

    • Marked as answer by
      DBA_Guy
      Friday, April 3, 2015 1:36 AM

Источник

If when you run the built-in Windows 11/10 DISM tool, you receive error message codes like 87, 112, 11, 50, 3, 87,1726, 1392, 1393, 1910, etc, then these general troubleshooting suggestions may help you fix the problem. The error code may be accompanied by a message :

  • If the accompanying message is – The restore health option is not recognized in this context, or An error occurred while processing the command, it could indicate that the DISM command you uses is not supported by the operating system version.
  • If the accompanying message is – The add-package option is unknown, it could indicate that the option you use is not supported by the operating system version.

DISM error

If a Windows image becomes unserviceable, you can use the Deployment Imaging and Servicing Management (DISM) tool to update the files and correct the problem. In the case of system inconsistencies and corruptions, corrupted Windows Update files, etc., you can run the DISM tool by using the Cleanup-Image functionality along with the available switches.

But if the effort fails, you may need to find out why this happened. Such errors are usually faced when you use the /restorehealth parameter – but could appear when you use other parameters as well.

What does DISM stand for?

DISM stands for Deployment Image Servicing and Management. It is a command-line tool that helps users service a Windows image or prepare a Windows Pre-installation Environment (Windows PE). The DISM tool is also helpful when the System File Checker stops working or the Windows image becomes unserviceable.

Fix DISM Error on Windows 11/10

1] Run offline ChkDsk scan

In an elevated CMD execute the following command:

chkdsk /offlinescanandfix

Restart Windows and proceed to the next action.

Read: System error 5 has occurred, Access is denied

2] Revert Pending Actions

Open an elevated command prompt window and execute the following command to refresh the DISM tool:

dism.exe /image:C: /cleanup-image /revertpendingactions

This will revert all pending tasks including Windows Updates. It is recommended that you boot offline and then run it a recovery command prompt.

Related: The WOF Driver encountered a corruption in the compressed file’s Resource Table – DISM error.

3] Start Component Cleanup

Next, execute the following command:

dism.exe /online /Cleanup-Image /StartComponentCleanup

This will clean up the component store so that everything can run properly again.

Read: DISM /Apply-Image command fails with Error Code 5

4] Restore Health

Restart and then Run sfc /scannow in Safe Mode.

Restart your system and see if you can run the following command now:

dism.exe /online /Cleanup-Image /RestoreHealth

How do you read DISM logs?

Windows saves the DISM logs inside the DISM folder on the C drive. The DISM folder is located at the following location:

c:windowslogsdism

On opening the DIS folder, you will see a text file with the name dism. Open this file to read the DISM logs.

This should help!

RELATED READS:

  1. Fix DISM Error 0x800f0906
  2. DISM Unable to access the Image Error 2
  3. Fix DISM Error 0x800f081f or 0x800f0906
  4. DISM Error 1009: The configuration registry database is corrupt
  5. Error 50, DISM does not support servicing Windows PE with the online option.
Источник

Hi.

I need help :)  

I’m looking into creating a WinRE and therefore I need to mount the install.wim and get it from there.

The info i got is from https://msdn.microsoft.com/en-us/library/windows/hardware/dn898523(v=vs.85).aspx

My PC is upgraded to win 10pro 32bit from Win 8.1

ADK is the newest and the Deployment and Imageing tools env. is 10.0.10240.16384

mouting other WIM with no problem.

I used the mediaCreationTool to download 32 and 64bit ISO on my langue language.

Used daemontools to open the ISO and copy the content to my HDD.

And they trying to mount with DISM. But I get this error. 

C:Program FilesWindows Kits10Assessment and Deployment KitDeployment Tools>
Dism /Mount-Image /ImageFile:C:windows10-32sourcesinstall.wim /Index:1 /Mount
Dir:C:mountwindows

Deployment Image Servicing and Management tool
Version: 10.0.10240.16384

Error: 11

Det blev forsøgt at indlæse et program med et forkert format.

The DISM log file can be found at C:WINDOWSLogsDISMdism.log

Here is the last info in the log

2015-08-06 13:32:08, Info                  DISM   DISM.EXE: Host machine information: OS Version=10.0.10240, Running architecture=x86, Number of processors=4
2015-08-06 13:32:08, Info                  DISM   DISM.EXE: Dism.exe version: 10.0.10240.16384
2015-08-06 13:32:08, Info                  DISM   DISM.EXE: Executing command line: Dism  /Mount-Image /ImageFile:C:windows10-32sourcesinstall.wim /Index:1 /MountDir:C:mountwindows
2015-08-06 13:32:08, Info                  DISM   DISM Provider Store: PID=2576 TID=2860 Getting the collection of providers from a local provider store type. — CDISMProviderStore::GetProviderCollection
2015-08-06 13:32:08, Info                  DISM   DISM Provider Store: PID=2576 TID=2860 Provider has not previously been encountered.  Attempting to initialize the provider. — CDISMProviderStore::Internal_GetProvider
2015-08-06 13:32:08, Info                  DISM   DISM Provider Store: PID=2576 TID=2860 Loading Provider from location C:Program FilesWindows Kits10Assessment and Deployment KitDeployment Toolsx86DISMFolderProvider.dll
— CDISMProviderStore::Internal_GetProvider
2015-08-06 13:32:08, Info                  DISM   DISM Provider Store: PID=2576 TID=2860 Connecting to the provider located at C:Program FilesWindows Kits10Assessment and Deployment KitDeployment Toolsx86DISMFolderProvider.dll.
— CDISMProviderStore::Internal_LoadProvider
2015-08-06 13:32:08, Info                  DISM   DISM Provider Store: PID=2576 TID=2860 Provider has not previously been encountered.  Attempting to initialize the provider. — CDISMProviderStore::Internal_GetProvider
2015-08-06 13:32:08, Info                  DISM   DISM Provider Store: PID=2576 TID=2860 Loading Provider from location C:Program FilesWindows Kits10Assessment and Deployment KitDeployment Toolsx86DISMWimProvider.dll
— CDISMProviderStore::Internal_GetProvider
2015-08-06 13:32:08, Info                  DISM   DISM Provider Store: PID=2576 TID=2860 Connecting to the provider located at C:Program FilesWindows Kits10Assessment and Deployment KitDeployment Toolsx86DISMWimProvider.dll.
— CDISMProviderStore::Internal_LoadProvider
2015-08-06 13:32:08, Info                  DISM   DISM Provider Store: PID=2576 TID=2860 Provider has not previously been encountered.  Attempting to initialize the provider. — CDISMProviderStore::Internal_GetProvider
2015-08-06 13:32:08, Info                  DISM   DISM Provider Store: PID=2576 TID=2860 Loading Provider from location C:Program FilesWindows Kits10Assessment and Deployment KitDeployment Toolsx86DISMVHDProvider.dll
— CDISMProviderStore::Internal_GetProvider
2015-08-06 13:32:08, Info                  DISM   DISM Provider Store: PID=2576 TID=2860 Connecting to the provider located at C:Program FilesWindows Kits10Assessment and Deployment KitDeployment Toolsx86DISMVHDProvider.dll.
— CDISMProviderStore::Internal_LoadProvider
2015-08-06 13:32:08, Info                  DISM   DISM Provider Store: PID=2576 TID=2860 Provider has not previously been encountered.  Attempting to initialize the provider. — CDISMProviderStore::Internal_GetProvider
2015-08-06 13:32:08, Info                  DISM   DISM Provider Store: PID=2576 TID=2860 Loading Provider from location C:Program FilesWindows Kits10Assessment and Deployment KitDeployment Toolsx86DISMImagingProvider.dll
— CDISMProviderStore::Internal_GetProvider
2015-08-06 13:32:08, Info                  DISM   DISM Provider Store: PID=2576 TID=2860 Connecting to the provider located at C:Program FilesWindows Kits10Assessment and Deployment KitDeployment Toolsx86DISMImagingProvider.dll.
— CDISMProviderStore::Internal_LoadProvider
2015-08-06 13:32:08, Info                  DISM   DISM Provider Store: PID=2576 TID=2860 Provider has not previously been encountered.  Attempting to initialize the provider. — CDISMProviderStore::Internal_GetProvider
2015-08-06 13:32:08, Info                  DISM   DISM Provider Store: PID=2576 TID=2860 Loading Provider from location C:Program FilesWindows Kits10Assessment and Deployment KitDeployment Toolsx86DISMCompatProvider.dll
— CDISMProviderStore::Internal_GetProvider
2015-08-06 13:32:08, Info                  DISM   DISM Provider Store: PID=2576 TID=2860 Connecting to the provider located at C:Program FilesWindows Kits10Assessment and Deployment KitDeployment Toolsx86DISMCompatProvider.dll.
— CDISMProviderStore::Internal_LoadProvider
2015-08-06 13:32:08, Info                  DISM   DISM Provider Store: PID=2576 TID=2860 Provider has not previously been encountered.  Attempting to initialize the provider. — CDISMProviderStore::Internal_GetProvider
2015-08-06 13:32:08, Info                  DISM   DISM Provider Store: PID=2576 TID=2860 Loading Provider from location C:Program FilesWindows Kits10Assessment and Deployment KitDeployment Toolsx86DISMFfuProvider.dll
— CDISMProviderStore::Internal_GetProvider
2015-08-06 13:32:08, Info                  DISM   DISM Provider Store: PID=2576 TID=2860 Connecting to the provider located at C:Program FilesWindows Kits10Assessment and Deployment KitDeployment Toolsx86DISMFfuProvider.dll.
— CDISMProviderStore::Internal_LoadProvider
2015-08-06 13:32:08, Info                  DISM   DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.
2015-08-06 13:32:08, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Log Provider
2015-08-06 13:32:08, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: FolderManager
2015-08-06 13:32:08, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: WimManager
2015-08-06 13:32:08, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: WimManager.
2015-08-06 13:32:08, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: VHDManager
2015-08-06 13:32:08, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: GenericImagingManager
2015-08-06 13:32:08, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: GenericImagingManager.
2015-08-06 13:32:08, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: Compatibility Manager
2015-08-06 13:32:08, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: Compatibility Manager.
2015-08-06 13:32:08, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: FfuManager
2015-08-06 13:32:08, Info                  DISM   DISM Provider Store: PID=2576 TID=2860 Getting Provider GenericImagingManager — CDISMProviderStore::GetProvider
2015-08-06 13:32:08, Info                  DISM   DISM Provider Store: PID=2576 TID=2860 Provider has previously been initialized.  Returning the existing instance. — CDISMProviderStore::Internal_GetProvider
2015-08-06 13:32:08, Info                  DISM   DISM Imaging Provider: PID=2576 TID=2860 WIM image specified — CGenericImagingManager::GetImageInfoCollection
2015-08-06 13:32:08, Info                  DISM   DISM Provider Store: PID=2576 TID=2860 Getting Provider WimManager — CDISMProviderStore::GetProvider
2015-08-06 13:32:08, Info                  DISM   DISM Provider Store: PID=2576 TID=2860 Provider has previously been initialized.  Returning the existing instance. — CDISMProviderStore::Internal_GetProvider
[2576] [0x8144012d] 
2015-08-06 13:32:08, Warning               DISM   DISM WIM Provider: PID=2576 [ReadWimHeader:(1723) -> version/header mismatch] C:windows10-32sourcesinstall.wim (HRESULT=0x8007000B) — CWimManager::WimProviderMsgLogCallback
[2576] [0xc144012e] 
2015-08-06 13:32:08, Error                 DISM   DISM WIM Provider: PID=2576 [WIMCreateFile:(425) -> Fail to read WIM header] C:windows10-32sourcesinstall.wim (HRESULT=0x8007000B) — CWimManager::WimProviderMsgLogCallback
2015-08-06 13:32:08, Error                 DISM   DISM WIM Provider: PID=2576 TID=2860 WIM open failed. — CWimImageInfo::Mount(hr:0x8007000b)
2015-08-06 13:32:08, Error                 DISM   DISM Imaging Provider: PID=2576 TID=2860 basentsetupopktoolsdismprovidersimagingproviderdllgenericimagingmanager.cpp:817 — CGenericImagingManager::InternalOpMount(hr:0x8007000b)
2015-08-06 13:32:08, Error                 DISM   DISM Imaging Provider: PID=2576 TID=2860 basentsetupopktoolsdismprovidersimagingproviderdllgenericimagingmanager.cpp:737 — CGenericImagingManager::InternalCmdMount(hr:0x8007000b)
2015-08-06 13:32:08, Error                 DISM   DISM Imaging Provider: PID=2576 TID=2860 basentsetupopktoolsdismprovidersimagingproviderdllgenericimagingmanager.cpp:535 — CGenericImagingManager::ExecuteCmdLine(hr:0x8007000b)
2015-08-06 13:32:08, Info                  DISM   DISM.EXE: Image session has been closed. Reboot required=no.
2015-08-06 13:32:08, Info                  DISM   DISM.EXE: 
2015-08-06 13:32:08, Info                  DISM   DISM.EXE: <—— Ending Dism.exe session ——>
2015-08-06 13:32:08, Info                  DISM   DISM.EXE: 

Источник

Если при запуске встроенного средства DISM в Windows 10 вы получаете коды сообщений об ошибках, такие как 87, 112, 11, 50, 2, 3, 87,1726, 1393, 1910, 0x800f081f, то эти общие рекомендации по устранению неполадок могут помочь вам решить проблему. Код ошибки может сопровождаться сообщением:

  • Если сопровождающее сообщение – Параметр восстановления работоспособности не распознается в этом контексте или Произошла ошибка при обработке команды , это может указывать на то, что используемая вами команда DISM имеет вид не поддерживается версией операционной системы.
  • Если сопровождающее сообщение – Опция add-package неизвестна , это может означать, что используемая опция не поддерживается версией операционной системы.

Если образ Windows становится неработоспособным, вы можете использовать средство управления развертыванием образов и обслуживанием (DISM) для обновления файлов и устранения проблемы. В случае системных несоответствий и повреждений, поврежденных файлов Центра обновления Windows и т. Д. Вы можете запустить инструмент DISM, используя функциональность Cleanup-Image вместе с доступными переключателями. Но если усилия не увенчаются успехом, вам может понадобиться выяснить, почему это произошло. Такие ошибки обычно возникают при использовании параметра /restorehealth , но могут появляться и при использовании других параметров.

Исправить ошибку DISM

1] Откройте окно командной строки с повышенными правами и выполните следующую команду, чтобы обновить инструмент DISM: 

 dism.exe/image: C:/cleanup-image/revertpendingactions

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

2] Затем выполните следующую команду: 

 dism.exe/online/Cleanup-Image/StartComponentCleanup

Это очистит хранилище компонентов, чтобы все снова могло нормально работать.

3] Перезапустите, а затем запустите sfc/scannow в безопасном режиме.

Перезагрузите систему и посмотрите, можете ли вы сейчас запустить следующую команду: 

 dism.exe/online/Cleanup-Image/RestoreHealth

Это должно помочь!

СВЯЗАННЫЕ ЧИТАНИЯ:

  1. Исправьте ошибку DISM 0x800f0906.
  2. Сбой DISM в Windows 10. Исходные файлы не найдены.
Источник

Если при запуске встроенного инструмента DISM в Windows 10 вы получаете коды сообщений об ошибках, например 87, 112, 11, 50, 2, 3, 87,1726, 1392, 1393, 1910, 0x800f081f, то эти общие предложения по устранению неполадок могут помочь. вы устраняете проблему. Код ошибки может сопровождаться сообщением:

  • Если сопроводительное сообщение — Параметр восстановления работоспособности не распознается в этом контексте, или же Произошла ошибка при обработке команды, это может означать, что используемая вами команда DISM не поддерживается версией операционной системы.
  • Если сопроводительное сообщение — Опция add-package неизвестна, это может означать, что используемый вами параметр не поддерживается версией операционной системы.

Ошибка DISM

Если образ Windows становится неработоспособным, вы можете использовать средство управления развертыванием образов и обслуживанием (DISM) для обновления файлов и устранения проблемы. В случае системных несоответствий и повреждений, поврежденных файлов Центра обновления Windows и т. Д. Вы можете запустить инструмент DISM, используя функцию Cleanup-Image вместе с доступными переключателями.

Но если усилия не увенчаются успехом, возможно, вам потребуется выяснить, почему это произошло. С такими ошибками обычно сталкиваются при использовании /restorehealth параметр — но может появиться и при использовании других параметров.

1]Запустить автономное сканирование ChkDsk

В CMD с повышенными привилегиями выполните следующую команду:

chkdsk /offlinescanandfix

Перезагрузите Windows 10 и перейдите к следующему действию.

2]Отменить ожидающие действия

Откройте окно командной строки с повышенными привилегиями и выполните следующую команду, чтобы обновить инструмент DISM:

dism.exe /image:C: /cleanup-image /revertpendingactions

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

3]Запустить очистку компонентов

Затем выполните следующую команду:

dism.exe /online /Cleanup-Image /StartComponentCleanup

Это очистит хранилище компонентов, чтобы все снова могло работать правильно.

4]Восстановить здоровье

Перезагрузите, а затем запустите sfc / scannow в безопасном режиме.

Перезагрузите систему и посмотрите, сможете ли вы сейчас выполнить следующую команду:

dism.exe /online /Cleanup-Image /RestoreHealth

Это должно помочь!

СВЯЗАННЫЕ ЧТЕНИЯ:

  1. Исправить ошибку DISM 0x800f0906
  2. Ошибка DISM 1009: база данных реестра конфигурации повреждена
  3. Ошибка 50, DISM не поддерживает обслуживание Windows PE в интерактивном режиме.
  4. DISM не работает в Windows 10, исходные файлы не могут быть найдены.

Источник

Возможно, вам также будет интересно:

  • Восстановление и обновление айфон через айтюнс ошибка
  • Восстановление жесткого диска поиск ошибок
  • Восстановление жесткого диска ошибка ввода вывода
  • Восстановление жесткого диска на ошибки windows 10
  • Восстановление диска после проверки на ошибки

    • Понравилась статья? Поделить с друзьями:
    0 0 голоса
    Рейтинг статьи
    Подписаться
    Уведомить о
    guest

    0 комментариев
    Старые
    Новые Популярные
    Межтекстовые Отзывы
    Посмотреть все комментарии