Dism ошибка 1168 элемент не найден

ИНФОРМАЦИОННАЯ ПОДДЕРЖКА- CUSTOMER ADVISORY

Номер документа: c06424402

Версия: 1

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

Дата выпуска : 30-Jul-2019

Последнее обновление : 30-Jul-2019

ОПИСАНИЕ

При использовании Microsoft System Center Configuration Manager (SCCM) для настройки систем в области «ПРИМЕНЕНИЕ» появляется следующее сообщение об ошибке DISM:

Ошибка: 1168.

Элемент не найден.

Это может произойти, когда средство командной строки Microsoft Deployment Image Servicing and Management (DISM) выполняет команды для настройки драйвера Realtek HD Audio (SoftPaq SP95193). Проблема возникает из-за того, что драйвер содержит неправильно работающий компонент универсальной платформы Windows (UWP).

ПРИМЕНЕНИЕ

Информация в этом документе относится к следующему:

Компьютеры:

Ноутбук HP EliteBook 830 G5

Операционные системы:

Microsoft Windows 10 RS5 (версия 1809)

РЕШЕНИЕ

Ниже приведены действия, которые необходимо выполнить для установки данного компонента с SCCM.

  1. Разархивируйте SoftPaq

  2. Дополните командный файл для установки компонента UWP с DISM. Вот команда DISM, которую нужно вставить в командный файл:

    @echo ON dism.exe /image:%OSD_System% /add-Driver /Driver:%~dp0HSAcb68d18decd44cd44c94bec5cd2a2c354180.appxbundle /Region=»all» /LicensePath:%~dp0HSAcb68d18decd44cd44c94bec5cd2a2c354180_License1.xml /DependencyPackagePath:%~dp0HSA Micrsooft.VCLibs.140.00_14.0.26706.0_x64_8wekyb3d8bbwe.appx

    Примечание.

    Переменная
    %OSD_System%, используемая в приведенной выше команде, устанавливается предыдущим действием последовательности задач.

  3. Создайте пакет и добавьте действие командной строки, чтобы выполнить командный файл сразу после образа Windows и перед установкой параметров Windows.

  4. Разверните последовательность задач и используйте диспетчер устройств, чтобы убедиться в правильности установки драйвера Realtek Audio.

Hardware platforms affected :

HP EliteBook 830 G5 Notebook PC

Повережденные операционные системы : Не применимо

Поврежденное программное обеспечение : Не применимо

Идентификатор Перекрестной Ссылки Информационной Поддержки : IA06417547

© Copyright 2023 HP Development Company, L.P.

HP Inc. не несет ответственность за технические или редакторские ошибки или упущения, содержащиеся в данном документе. Предоставленная информация предоставляется «как есть» без каких-либо гарантий. В пределах, допускаемых законом, ни HP, ни ее аффилированные лица, субподрядчики или поставщики не будут нести ответственность за случайные, специальные или косвенные убытки, включая стоимость простоя; упущенную прибыль; убытки, связанные с приобретением товаров или услуг-заменителей; убытки за потерю данных или восстановление программного обеспечения. Информация в этом документе может быть изменена без предварительного уведомления. Компания HP Inc. и названия продуктов HP, упомянутые в данном документе, являются товарными знаками HP Inc. в США и других странах. Названия других продуктов и компаний, упомянутые здесь, могут являться товарными знаками соответствующих владельцев.

Источник
  • Remove From My Forums

locked

SOLVED: Writing RPi2 image to SD Card: dism Error: 1168 — cannot find element

  • Question

  • Hello all,

    I have installed Windows 10 build 10074 (Dutch language) on a PC, no VM.

    I have downloaded and extracted Windows_IoT_Core_RPI2_BUILD.zip

    One of the files extracted is Flash.ffu

    I have established that my SD card is a class 10 and 16 GB

    I open an Administrator command prompt.

    I have established the SD card is seen as «Disk 1» 14 GB size

    I change directory to the directory containing Flash.ffu

    I execute the command:  «dism.exe /Apply-Image /ImageFile:flash.ffu /ApplyDrive:\.PhysicalDrive1 /SkipPlatformCheck»

    I receive follwing error:

    Deployment Image Servicing and Management tool
    Version: 10.0.10074.0

    Kan element niet vinden.

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

    > «Kan element niet vinden» translates as : «Cannot find element»

    I notice a difference in filename between the extracted «Flash.ffu» and the «flash.ffu» (capital F) so I retry the command as:

    «dism.exe /Apply-Image /ImageFile:Flash.ffu /ApplyDrive:\.PhysicalDrive1 /SkipPlatformCheck»

    but with same error 1168

    The DISM log entry follows below.

    Anyone encountering the same issue, and better still, have found a solution?

    Many thanks!

    Ralph

    DISM log file entry:

    2015-05-02 13:36:06, Info                  DISM   PID=4348 TID=4092 Scratch directory set to ‘C:UsersralphAppDataLocalTemp’. — CDISMManager::put_ScratchDir
    2015-05-02 13:36:06, Info                  DISM   PID=4348 TID=4092 DismCore.dll version: 10.0.10074.0 — CDISMManager::FinalConstruct
    2015-05-02 13:36:06, Info                  DISM   PID=4348 TID=4092 Successfully loaded the ImageSession at «C:WindowsSystem32Dism» — CDISMManager::LoadLocalImageSession
    2015-05-02 13:36:06, Info                  DISM   DISM Provider Store: PID=4348 TID=4092 Found and Initialized the DISM Logger. — CDISMProviderStore::Internal_InitializeLogger
    2015-05-02 13:36:06, Info                  DISM   DISM Provider Store: PID=4348 TID=4092 Failed to get and initialize the PE Provider.  Continuing by assuming
    that it is not a WinPE image. — CDISMProviderStore::Final_OnConnect
    2015-05-02 13:36:06, Info                  DISM   DISM Provider Store: PID=4348 TID=4092 Finished initializing the Provider Map. — CDISMProviderStore::Final_OnConnect
    2015-05-02 13:36:06, Info                  DISM   DISM Provider Store: PID=4348 TID=4092 Getting Provider DISMLogger — CDISMProviderStore::GetProvider
    2015-05-02 13:36:06, Info                  DISM   DISM Provider Store: PID=4348 TID=4092 Provider has previously been initialized.  Returning the existing instance.
    — CDISMProviderStore::Internal_GetProvider
    2015-05-02 13:36:06, Info                  DISM   DISM Provider Store: PID=4348 TID=4092 Getting Provider DISMLogger — CDISMProviderStore::GetProvider
    2015-05-02 13:36:06, Info                  DISM   DISM Provider Store: PID=4348 TID=4092 Provider has previously been initialized.  Returning the existing instance.
    — CDISMProviderStore::Internal_GetProvider
    2015-05-02 13:36:06, Info                  DISM   DISM Manager: PID=4348 TID=4092 Successfully created the local image session and provider store. — CDISMManager::CreateLocalImageSession
    2015-05-02 13:36:06, Info                  DISM   DISM Provider Store: PID=4348 TID=4092 Getting Provider DISMLogger — CDISMProviderStore::GetProvider
    2015-05-02 13:36:06, Info                  DISM   DISM Provider Store: PID=4348 TID=4092 Provider has previously been initialized.  Returning the existing instance.
    — CDISMProviderStore::Internal_GetProvider
    2015-05-02 13:36:06, Info                  DISM   DISM.EXE:

    2015-05-02 13:36:06, Info                  DISM   DISM.EXE: <—— Starting Dism.exe session ——>
    2015-05-02 13:36:06, Info                  DISM   DISM.EXE:

    2015-05-02 13:36:06, Info                  DISM   DISM.EXE: Host machine information: OS Version=10.0.10074, Running architecture=amd64, Number of processors=2
    2015-05-02 13:36:06, Info                  DISM   DISM.EXE: Dism.exe version: 10.0.10074.0
    2015-05-02 13:36:06, Info                  DISM   DISM.EXE: Executing command line: dism.exe  /Apply-Image /ImageFile:flash.ffu /ApplyDrive:\.PhysicalDrive1
    /SkipPlatformCheck
    2015-05-02 13:36:06, Info                  DISM   DISM Provider Store: PID=4348 TID=4092 Getting the collection of providers from a local provider store type. — CDISMProviderStore::GetProviderCollection
    2015-05-02 13:36:06, Info                  DISM   DISM Provider Store: PID=4348 TID=4092 Provider has not previously been encountered.  Attempting to initialize
    the provider. — CDISMProviderStore::Internal_GetProvider
    2015-05-02 13:36:06, Info                  DISM   DISM Provider Store: PID=4348 TID=4092 Loading Provider from location C:WindowsSystem32DismFolderProvider.dll
    — CDISMProviderStore::Internal_GetProvider
    2015-05-02 13:36:06, Info                  DISM   DISM Provider Store: PID=4348 TID=4092 Connecting to the provider located at C:WindowsSystem32DismFolderProvider.dll.
    — CDISMProviderStore::Internal_LoadProvider
    2015-05-02 13:36:06, Info                  DISM   DISM Provider Store: PID=4348 TID=4092 Provider has not previously been encountered.  Attempting to initialize
    the provider. — CDISMProviderStore::Internal_GetProvider
    2015-05-02 13:36:06, Info                  DISM   DISM Provider Store: PID=4348 TID=4092 Loading Provider from location C:WindowsSystem32DismWimProvider.dll —
    CDISMProviderStore::Internal_GetProvider
    2015-05-02 13:36:06, Info                  DISM   DISM Provider Store: PID=4348 TID=4092 Connecting to the provider located at C:WindowsSystem32DismWimProvider.dll.
    — CDISMProviderStore::Internal_LoadProvider
    2015-05-02 13:36:06, Info                  DISM   DISM Provider Store: PID=4348 TID=4092 Provider has not previously been encountered.  Attempting to initialize
    the provider. — CDISMProviderStore::Internal_GetProvider
    2015-05-02 13:36:06, Info                  DISM   DISM Provider Store: PID=4348 TID=4092 Loading Provider from location C:WindowsSystem32DismVHDProvider.dll —
    CDISMProviderStore::Internal_GetProvider
    2015-05-02 13:36:06, Info                  DISM   DISM Provider Store: PID=4348 TID=4092 Connecting to the provider located at C:WindowsSystem32DismVHDProvider.dll.
    — CDISMProviderStore::Internal_LoadProvider
    2015-05-02 13:36:06, Info                  DISM   DISM Provider Store: PID=4348 TID=4092 Provider has not previously been encountered.  Attempting to initialize
    the provider. — CDISMProviderStore::Internal_GetProvider
    2015-05-02 13:36:06, Info                  DISM   DISM Provider Store: PID=4348 TID=4092 Loading Provider from location C:WindowsSystem32DismImagingProvider.dll
    — CDISMProviderStore::Internal_GetProvider
    2015-05-02 13:36:06, Info                  DISM   DISM Provider Store: PID=4348 TID=4092 Connecting to the provider located at C:WindowsSystem32DismImagingProvider.dll.
    — CDISMProviderStore::Internal_LoadProvider
    2015-05-02 13:36:06, Info                  DISM   DISM Provider Store: PID=4348 TID=4092 Provider has not previously been encountered.  Attempting to initialize
    the provider. — CDISMProviderStore::Internal_GetProvider
    2015-05-02 13:36:06, Info                  DISM   DISM Provider Store: PID=4348 TID=4092 Loading Provider from location C:WindowsSystem32DismCompatProvider.dll
    — CDISMProviderStore::Internal_GetProvider
    2015-05-02 13:36:06, Info                  DISM   DISM Provider Store: PID=4348 TID=4092 Connecting to the provider located at C:WindowsSystem32DismCompatProvider.dll.
    — CDISMProviderStore::Internal_LoadProvider
    2015-05-02 13:36:06, Info                  DISM   DISM Provider Store: PID=4348 TID=4092 Provider has not previously been encountered.  Attempting to initialize
    the provider. — CDISMProviderStore::Internal_GetProvider
    2015-05-02 13:36:06, Info                  DISM   DISM Provider Store: PID=4348 TID=4092 Loading Provider from location C:WindowsSystem32DismFfuProvider.dll —
    CDISMProviderStore::Internal_GetProvider
    2015-05-02 13:36:06, Info                  DISM   DISM Provider Store: PID=4348 TID=4092 Connecting to the provider located at C:WindowsSystem32DismFfuProvider.dll.
    — CDISMProviderStore::Internal_LoadProvider
    2015-05-02 13:36:06, Info                  DISM   DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.
    2015-05-02 13:36:06, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Log Provider
    2015-05-02 13:36:06, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: FolderManager
    2015-05-02 13:36:06, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: WimManager
    2015-05-02 13:36:06, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: WimManager.
    2015-05-02 13:36:06, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: VHDManager
    2015-05-02 13:36:06, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: GenericImagingManager
    2015-05-02 13:36:06, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: GenericImagingManager.
    2015-05-02 13:36:06, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: Compatibility Manager
    2015-05-02 13:36:06, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: Compatibility Manager.
    2015-05-02 13:36:06, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: FfuManager
    2015-05-02 13:36:06, Info                  DISM   DISM Provider Store: PID=4348 TID=4092 Getting Provider GenericImagingManager — CDISMProviderStore::GetProvider
    2015-05-02 13:36:06, Info                  DISM   DISM Provider Store: PID=4348 TID=4092 Provider has previously been initialized.  Returning the existing instance.
    — CDISMProviderStore::Internal_GetProvider
    2015-05-02 13:36:06, Info                  DISM   DISM Provider Store: PID=4348 TID=4092 Getting Provider FfuManager — CDISMProviderStore::GetProvider
    2015-05-02 13:36:06, Info                  DISM   DISM Provider Store: PID=4348 TID=4092 Provider has previously been initialized.  Returning the existing instance.
    — CDISMProviderStore::Internal_GetProvider
    2015-05-02 13:36:06, Error                 DISM   DISM Imaging Provider: PID=4348 TID=4092 basentsetupopktoolsdismprovidersimagingproviderdllgenericimagingmanager.cpp:2546
    — CGenericImagingManager::InternalCmdFFUApply(hr:0x80070490)
    2015-05-02 13:36:06, Error                 DISM   DISM Imaging Provider: PID=4348 TID=4092 basentsetupopktoolsdismprovidersimagingproviderdllgenericimagingmanager.cpp:535
    — CGenericImagingManager::ExecuteCmdLine(hr:0x80070490)
    2015-05-02 13:36:06, Info                  DISM   DISM.EXE: Image session has been closed. Reboot required=no.
    2015-05-02 13:36:06, Info                  DISM   DISM.EXE:

    2015-05-02 13:36:06, Info                  DISM   DISM.EXE: <—— Ending Dism.exe session ——>
    2015-05-02 13:36:06, Info                  DISM   DISM.EXE:

    2015-05-02 13:36:06, Info                  DISM   DISM Provider Store: PID=4348 TID=4092 Found the OSServices.  Waiting to finalize it until all other providers
    are unloaded. — CDISMProviderStore::Final_OnDisconnect
    2015-05-02 13:36:06, Info                  DISM   DISM Provider Store: PID=4348 TID=4092 Disconnecting Provider: FolderManager — CDISMProviderStore::Internal_DisconnectProvider
    2015-05-02 13:36:06, Info                  DISM   DISM Provider Store: PID=4348 TID=4092 Disconnecting Provider: WimManager — CDISMProviderStore::Internal_DisconnectProvider
    2015-05-02 13:36:06, Info                  DISM   DISM Provider Store: PID=4348 TID=4092 Disconnecting Provider: VHDManager — CDISMProviderStore::Internal_DisconnectProvider
    2015-05-02 13:36:06, Info                  DISM   DISM Provider Store: PID=4348 TID=4092 Disconnecting Provider: GenericImagingManager — CDISMProviderStore::Internal_DisconnectProvider
    2015-05-02 13:36:06, Info                  DISM   DISM Provider Store: PID=4348 TID=4092 Disconnecting Provider: Compatibility Manager — CDISMProviderStore::Internal_DisconnectProvider
    2015-05-02 13:36:06, Info                  DISM   DISM Provider Store: PID=4348 TID=4092 Disconnecting Provider: FfuManager — CDISMProviderStore::Internal_DisconnectProvider
    2015-05-02 13:36:06, Info                  DISM   DISM Provider Store: PID=4348 TID=4092 Releasing the local reference to DISMLogger.  Stop logging. — CDISMProviderStore::Internal_DisconnectProvider

    • Edited by

      Thursday, May 14, 2015 6:16 PM

Answers

  • According to my research FfuProvider.dll checks this values and fails if one of them is empty.
    This is the only reason why dism fails with 1168 error on a Hyper-V virtual machine.

    You can patch x86 version of FfuProvider.dll with HEX editor.
    File offset 0x7312, replace B8 90 04 07 80 with B8 00 00 00 00 (valid for 10074 and 10075)

    Be sure you are patch and use an appropriate version of x86 dism:

    10074
    C:windowsSysWOW64Dism.exe
    C:windowsSysWOW64dismFfuProvider.dll
    To replace this file you have to become his owner and modify access rights.

    10075
    C:Program Files (x86)Windows Kits10Assessment and Deployment KitDeployment Toolsx86DISMdism.exe
    C:Program Files (x86)Windows Kits10Assessment and Deployment KitDeployment Toolsx86DISMffuprovider.dll

    Paths is for x64 windows system.

    Be careful: dism can rewrite any drive, including the system drive of running system if you specify its number in \.PhysicalDriveN

    • Edited by
      komarov.biz
      Thursday, May 14, 2015 9:20 AM
    • Marked as answer by
      PA1RB
      Thursday, May 14, 2015 6:14 PM

  • I’m very sorry to hear that you are still experiencing this issue.  Please know that we are looking into it and hope to have a solution or work-around available for you soon.

    The only other suggestion I can think of at the moment is if you could borrow a friends laptop that has a SD card reader built in you might get better results that way.

    Jonathan Tanner | Microsoft | Windows 10 IoT Core Insider Preview Support | This posting is provided ‘as is’ with no warranties and confers no rights.

    • Marked as answer by
      PA1RB
      Saturday, May 9, 2015 9:04 AM

  • OK, today I copied the Flash.ffu file to a Surface PRO 3 running Windows 10 build 10074.

    I have succesfully flashed two SD cards (SanDisk Ultra microSDHC UHS-1 cards with 8 GB, class 10) with the dism.exe on that Surface (dism version 10.0.10074.0).

    The first card I flashed using the build-in micro SD-card reader of the Surface. The second card I flashed using the exact same USB cardreader that does not work on my other computer (recognized by wmic as ChipBank SD/MM Reader USB Device).

    So the USB reader works on the Surface, but does not work on my other computer.

    The Windows 10 builds are both 10074, but the Surface runs the English language, the other computer runs the Dutch language.

    The computer on which the USB stick does not work is based on an ASUS P5LD2-VM motherboard (using the build in USB ports).

    So I will be off playing with the RPI-2 this weekend, but I will keep an eye out for the solution to the issue in this forum.

    Happy to provide more details if required by the engineers!

    • Proposed as answer by
      Jonathan TannerMicrosoft employee
      Friday, May 8, 2015 11:54 PM
    • Edited by
      PA1RB
      Saturday, May 9, 2015 9:02 AM
    • Marked as answer by
      PA1RB
      Saturday, May 9, 2015 9:04 AM

  • Hi,

    I had a similar problem with the above mentioned error. I tested all recomended methods/solutions with two USB card readers and three SD cards (class 10) but with no success. Now I installed Windows on the laptop that has SD card reader built
    in, as recomended above, and it works fine. Thanks for the tip!

    • Marked as answer by
      PA1RB
      Saturday, May 9, 2015 9:04 AM

  • Hello MiPiGamer,

    The page with instructions is here: http://ms-iot.github.io/content/win10/SetupRPI.htm

    The package including the image can be downloaded in step 3:
    Download the package «Windows 10 IoT Core Insider Preview Image for Raspberry Pi 2» from Microsoft Connect (you must be signed in to Microsoft Connect).

    Aside from the issue above writing the image, all went according to the description, and «Blinky» made the LED blink!

    • Marked as answer by
      PA1RB
      Sunday, May 10, 2015 8:49 PM

  • Wow — that did the trick allright:

    Deployment Image Servicing and Management tool
    Version: 10.0.10074.0

    Applying image
    [==========================100.0%==========================]
    The operation completed successfully.

    I confirm this patch absolutely fixed the issue, well done and many thanks indeed !!!

    Hope this finds its way into the next release of Windows 10.

    Ralph

    • Marked as answer by
      PA1RB
      Thursday, May 14, 2015 6:14 PM

Источник

Здравствуйте, Владимир! У меня целая эпопея с восстановлением хранилища оригинальных компонентов Windows 10. Нужен Ваш совет, думаю я Вас пойму, так как считаю себя опытным пользователем. Установленная на моём ноутбуке Windows 10 работает со значительными ошибками. Решил проверить целостность системных файлов с помощью средства sfc /scannow, но вышла ошибка «Программа защиты ресурсов Windows обнаружила повреждённые файлы, но не может восстановить некоторые из них». Как я понял, ошибка эта обозначает, что нарушена целостность самого хранилища системных компонентов Win 10 (папка WinSxS). Тогда решил проверить целостность этого самого хранилища командой Dism /Online /Cleanup-Image /ScanHealth, вышло сообщение «Хранилище компонентов подлежит восстановлению». Соответственно восстанавливаю хранилище командой Dism /Online /Cleanup-Image /RestoreHealth, данная команда восстанавливает хранилище компонентов с помощью Центра обновлений Windows, и у меня опять выходит ошибка «Не удалось скачать исходные файлы. Укажите расположение файлов, необходимых для восстановления компонента, с помощью параметра «Источник»». 

Непонятно, почему вылезла ошибка в этот раз, ведь интернет у меня есть. Ладно думаю, буду использовать для восстановления хранилища компонентов средство PowerShell и ISO-образ Windows 10, скачал дистрибутив Windows 10 и подсоединил его к виртуальному дисководу, запустил PowerShell и ввёл команду: Repair-WindowsImage -Online -RestoreHealth -Source F:sourcesinstall.wim:1 (где буква «F» соответствует букве подключенного образа с Win 10, а цифра «1» — индексу издания в образе Win 10 PRO (именно она у меня установлена), но и в очередной раз я потерпел неудачу — «Ошибка: 0x800f081. Сбой восстановления. Не найден источник восстановления, или хранилище компонентов восстановить невозможно». 

На одном известном форуме подсказали, что не нужно подсоединять ISO-образ Windows 10 к виртуальному дисководу, а нужно смонтировать ISO-образ с файлами Win 10 в папку с помощью команды: Dism /Mount-Wim /WimFile:F:sourcesinstall.wim /index:1 /MountDir:C:WIM /ReadOnly (где WIM, это пустая папка на диске C:, в которую монтируется ISO-образ, а F:sourcesinstall.wim — местонахождение файла-образа install.wim), но у меня и здесь уже при монтировании вышел промах «Ошибка: 11. Была сделана попытка загрузить программу, имеющую неверный формат».

Короче я сдался и не знаю, почему у меня ничего не получается. 

Автор — Владимир

Привет, друзья. Цель данной статьи рассказать начинающим пользователям в подробностях, как производить восстановление повреждённого хранилища компонентов Windows 10 в различных критических ситуациях. Если вы хотите проверить целостность системных файлов в своей операционной системе, то поможет вам в этом встроенная утилита «sfc /scannow», но если она выдаст ошибку: «Программа защиты ресурсов Windows обнаружила повреждённые файлы, но не может восстановить некоторые из них», 

то значит в вашей OS нарушена целостность самого хранилища системных компонентов (содержимое папки WinSxS). В этом случае нужно проверить целостность хранилища компонентов командой «Dism /Online /Cleanup-Image /ScanHealth», если при данной проверке тоже будут выходить различные ошибки, например, «Хранилище компонентов подлежит восстановлению», «Ошибка: 1910 Не найден указанный источник экспорта объекта», «Ошибка: 1726 Сбой при удалённом вызове процедуры», 

 

то в этом случае нужно сначала восстановить хранилище компонентов, а уже затем восстанавливать целостность системных файлов с помощью «sfc /scannow», вот здесь начинается самое интересное, так как имеется очень много нюансов, давайте разберём их все.

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

Dism /Online /Cleanup-Image /RestoreHealth

Данная команда восстанавливает хранилище компонентов с помощью Центра обновлений Windows (у вас должен работать Интернет), отсутствующие компоненты будут скачаны на серверах Майкрософт и восстановлены в вашей системе. В итоге должны получить сообщение «Восстановление выполнено успешно».

Но если данная команда выдаст ошибку 0x800f0906 «Не удалось скачать исходные файлы. Укажите расположение файлов, необходимых для восстановления компонента, с помощью параметра «Источник»» или 

выйдет другая ошибка 0x800f081f «Не удалось найти исходные файлы. Укажите расположение файлов, необходимых для восстановления компонента, с помощью параметра «Источник»»,

то нужно использовать для восстановления хранилища ISO-образ Windows 10. Скачиваем дистрибутив Windows 10 на сайте Майкрософт и подсоединяем его к виртуальному дисководу (в моём случае (G:)), затем заходим в папку sources и смотрим какое сжатие у файла-образа Windows 10,

 

обычно бывает install.esd, запоминаем это, пригодится при вводе последующих команд (если в вашем случае попадётся файл install.wim, то читайте информацию в конце статьи).

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

Dism /Online /Cleanup-Image /RestoreHealth /Source:G:Install.esd /limitaccess

где G: — буква виртуального дисковода с Windows 10,

Install.esd — файл-образ Win 10,

/limitaccess  — параметр, закрывающий доступ к центру обновлений (ведь мы используем для восстановления дистрибутив Win 10)

В итоге получаем сообщение «Восстановление выполнено успешно. Операция успешно завершена».

Вот таким способом мы с вами восстановили повреждённое хранилище компонентов Windows 10.

Хранилище компонентов восстановлено, теперь восстанавливаем целостность системных файлов Windows 10 командой «sfc /scannow». Получаем сообщение «Программа защиты ресурсов Windows обнаружила повреждённые файлы и успешно их восстановила». Целостность системных файлов Windows 10 восстановлена.

Ещё один способ восстановления хранилища компонентов с помощью файла виртуального жёсткого диска VHD

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

Dism /Online /Cleanup-Image /RestoreHealth /Source:G:Install.esd /limitaccess

вы опять получите ошибку, к примеру, «Ошибка: 1726 Сбой при удалённом вызове процедуры».

В этом случае нужно поступить так. Создать виртуальный жёсткий диск и распаковать на него содержимое файла-образа install.esd, после этого запустить команду:

Dism /Online /Cleanup-Image /RestoreHealth /Source:D:Windows /limitaccess

Где D: — буква подсоединённого виртуального диска VHD с развёрнутыми файлами Windows 10.

в результате будет произведено восстановление хранилища компонентов за счёт распакованных на виртуальный диск VHD файлов операционной системы.

Идём в Управлении дисками и создаём виртуальный диск VHD. «Действие»—>«Создать виртуальный жёсткий диск»

Отмечаем пункт «Динамический расширяемый». Размер виртуального жёсткого диска — 20 Гб. Жмём на кнопку «Обзор».

Выбираем в проводнике место сохранения виртуального жёсткого диска. Я выберу диск (F:). Присваиваю имя виртуальному диску — «Win10» и жму кнопку «Сохранить».

«ОК»

Созданный виртуальный диск представляет из себя в Управлении дисками нераспределённое пространство (Диск 1) размером 20 Гб.

Щёлкаем на Диске 1 правой мышью и выбираем «Инициализировать диск»

По большему счёту всё равно какой пункт отмечать — MBR или GPT. Я отмечу пункт «Таблица с GUID разделов (GPT)» и жму «ОК»

После инициализации диска создаём на нераспределённом пространстве простой том.

Новый том (G:) создан.

Архивы операционной системы — install.esd или install.wim могут содержать в себе несколько других архивов (релизов) операционных систем (Про, Домашняя и т.д.) и этим образам присваиваются индексы 1, 2, 3, 4. Чтобы узнать, какие образы находятся внутри нашего файла install.esd, вводим команду:

Dism /Get-WimInfo /WimFile:G:\sourcesinstall.esd

Где G: буква виртуального дисковода с Windows 10,

sourcesinstall.esd — адрес файла-образа install.esd в дистрибутиве Win 10.

На моём компьютере установлена Windows 10 PRO и именно её я хочу восстановить. Нужный мне образ Win 10 PRO имеет индекс 1.

Вводим команду:

Dism /apply-image /imagefile:G:\sourcesinstall.esd /index:1 /ApplyDir:D:\

Где G:sources — адрес расположения файла install.esd, 

index:1 — индекс Windows 10 PRO,

D: — подключенный виртуальный диск VHD (раздел D:).

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

Файл install.esd (Win 10 PRO) развёрнут на виртуальный диск VHD (раздел D:).

 

Ну и теперь восстанавливаем хранилище компонентов за счёт распакованных на виртуальный диск VHD (раздел D:) файлов операционной

системы Win 10, командой:

Dism /Online /Cleanup-Image /RestoreHealth /Source:D:Windows /limitaccess

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

Вот таким ещё способом мы с вами восстановили повреждённое хранилище компонентов Windows 10! Теперь восстанавливаем целостность системных файлов Windows 10 командой «sfc /scannow».  

 

В конце статьи вам пригодится такая информация. Если в ISO-образе Windows 10, в папке sourses, вам попадётся вместо файла install.esd файл install.wim, то команда восстановления немного изменится:

Dism /Online /Cleanup-Image /RestoreHealth /Source:G:install.wim /limitaccess

Это команда восстановления хранилища компонентов.

Источник
  • Remove From My Forums

locked

SOLVED: Writing RPi2 image to SD Card: dism Error: 1168 — cannot find element

  • Question

  • Hello all,

    I have installed Windows 10 build 10074 (Dutch language) on a PC, no VM.

    I have downloaded and extracted Windows_IoT_Core_RPI2_BUILD.zip

    One of the files extracted is Flash.ffu

    I have established that my SD card is a class 10 and 16 GB

    I open an Administrator command prompt.

    I have established the SD card is seen as «Disk 1» 14 GB size

    I change directory to the directory containing Flash.ffu

    I execute the command:  «dism.exe /Apply-Image /ImageFile:flash.ffu /ApplyDrive:.PhysicalDrive1 /SkipPlatformCheck»

    I receive follwing error:

    Deployment Image Servicing and Management tool
    Version: 10.0.10074.0

    Kan element niet vinden.

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

    > «Kan element niet vinden» translates as : «Cannot find element»

    I notice a difference in filename between the extracted «Flash.ffu» and the «flash.ffu» (capital F) so I retry the command as:

    «dism.exe /Apply-Image /ImageFile:Flash.ffu /ApplyDrive:.PhysicalDrive1 /SkipPlatformCheck»

    but with same error 1168

    The DISM log entry follows below.

    Anyone encountering the same issue, and better still, have found a solution?

    Many thanks!

    Ralph

    DISM log file entry:

    2015-05-02 13:36:06, Info                  DISM   PID=4348 TID=4092 Scratch directory set to ‘C:UsersralphAppDataLocalTemp’. — CDISMManager::put_ScratchDir
    2015-05-02 13:36:06, Info                  DISM   PID=4348 TID=4092 DismCore.dll version: 10.0.10074.0 — CDISMManager::FinalConstruct
    2015-05-02 13:36:06, Info                  DISM   PID=4348 TID=4092 Successfully loaded the ImageSession at «C:WindowsSystem32Dism» — CDISMManager::LoadLocalImageSession
    2015-05-02 13:36:06, Info                  DISM   DISM Provider Store: PID=4348 TID=4092 Found and Initialized the DISM Logger. — CDISMProviderStore::Internal_InitializeLogger
    2015-05-02 13:36:06, Info                  DISM   DISM Provider Store: PID=4348 TID=4092 Failed to get and initialize the PE Provider.  Continuing by assuming
    that it is not a WinPE image. — CDISMProviderStore::Final_OnConnect
    2015-05-02 13:36:06, Info                  DISM   DISM Provider Store: PID=4348 TID=4092 Finished initializing the Provider Map. — CDISMProviderStore::Final_OnConnect
    2015-05-02 13:36:06, Info                  DISM   DISM Provider Store: PID=4348 TID=4092 Getting Provider DISMLogger — CDISMProviderStore::GetProvider
    2015-05-02 13:36:06, Info                  DISM   DISM Provider Store: PID=4348 TID=4092 Provider has previously been initialized.  Returning the existing instance.
    — CDISMProviderStore::Internal_GetProvider
    2015-05-02 13:36:06, Info                  DISM   DISM Provider Store: PID=4348 TID=4092 Getting Provider DISMLogger — CDISMProviderStore::GetProvider
    2015-05-02 13:36:06, Info                  DISM   DISM Provider Store: PID=4348 TID=4092 Provider has previously been initialized.  Returning the existing instance.
    — CDISMProviderStore::Internal_GetProvider
    2015-05-02 13:36:06, Info                  DISM   DISM Manager: PID=4348 TID=4092 Successfully created the local image session and provider store. — CDISMManager::CreateLocalImageSession
    2015-05-02 13:36:06, Info                  DISM   DISM Provider Store: PID=4348 TID=4092 Getting Provider DISMLogger — CDISMProviderStore::GetProvider
    2015-05-02 13:36:06, Info                  DISM   DISM Provider Store: PID=4348 TID=4092 Provider has previously been initialized.  Returning the existing instance.
    — CDISMProviderStore::Internal_GetProvider
    2015-05-02 13:36:06, Info                  DISM   DISM.EXE:

    2015-05-02 13:36:06, Info                  DISM   DISM.EXE: <—— Starting Dism.exe session ——>
    2015-05-02 13:36:06, Info                  DISM   DISM.EXE:

    2015-05-02 13:36:06, Info                  DISM   DISM.EXE: Host machine information: OS Version=10.0.10074, Running architecture=amd64, Number of processors=2
    2015-05-02 13:36:06, Info                  DISM   DISM.EXE: Dism.exe version: 10.0.10074.0
    2015-05-02 13:36:06, Info                  DISM   DISM.EXE: Executing command line: dism.exe  /Apply-Image /ImageFile:flash.ffu /ApplyDrive:.PhysicalDrive1
    /SkipPlatformCheck
    2015-05-02 13:36:06, Info                  DISM   DISM Provider Store: PID=4348 TID=4092 Getting the collection of providers from a local provider store type. — CDISMProviderStore::GetProviderCollection
    2015-05-02 13:36:06, Info                  DISM   DISM Provider Store: PID=4348 TID=4092 Provider has not previously been encountered.  Attempting to initialize
    the provider. — CDISMProviderStore::Internal_GetProvider
    2015-05-02 13:36:06, Info                  DISM   DISM Provider Store: PID=4348 TID=4092 Loading Provider from location C:WindowsSystem32DismFolderProvider.dll
    — CDISMProviderStore::Internal_GetProvider
    2015-05-02 13:36:06, Info                  DISM   DISM Provider Store: PID=4348 TID=4092 Connecting to the provider located at C:WindowsSystem32DismFolderProvider.dll.
    — CDISMProviderStore::Internal_LoadProvider
    2015-05-02 13:36:06, Info                  DISM   DISM Provider Store: PID=4348 TID=4092 Provider has not previously been encountered.  Attempting to initialize
    the provider. — CDISMProviderStore::Internal_GetProvider
    2015-05-02 13:36:06, Info                  DISM   DISM Provider Store: PID=4348 TID=4092 Loading Provider from location C:WindowsSystem32DismWimProvider.dll —
    CDISMProviderStore::Internal_GetProvider
    2015-05-02 13:36:06, Info                  DISM   DISM Provider Store: PID=4348 TID=4092 Connecting to the provider located at C:WindowsSystem32DismWimProvider.dll.
    — CDISMProviderStore::Internal_LoadProvider
    2015-05-02 13:36:06, Info                  DISM   DISM Provider Store: PID=4348 TID=4092 Provider has not previously been encountered.  Attempting to initialize
    the provider. — CDISMProviderStore::Internal_GetProvider
    2015-05-02 13:36:06, Info                  DISM   DISM Provider Store: PID=4348 TID=4092 Loading Provider from location C:WindowsSystem32DismVHDProvider.dll —
    CDISMProviderStore::Internal_GetProvider
    2015-05-02 13:36:06, Info                  DISM   DISM Provider Store: PID=4348 TID=4092 Connecting to the provider located at C:WindowsSystem32DismVHDProvider.dll.
    — CDISMProviderStore::Internal_LoadProvider
    2015-05-02 13:36:06, Info                  DISM   DISM Provider Store: PID=4348 TID=4092 Provider has not previously been encountered.  Attempting to initialize
    the provider. — CDISMProviderStore::Internal_GetProvider
    2015-05-02 13:36:06, Info                  DISM   DISM Provider Store: PID=4348 TID=4092 Loading Provider from location C:WindowsSystem32DismImagingProvider.dll
    — CDISMProviderStore::Internal_GetProvider
    2015-05-02 13:36:06, Info                  DISM   DISM Provider Store: PID=4348 TID=4092 Connecting to the provider located at C:WindowsSystem32DismImagingProvider.dll.
    — CDISMProviderStore::Internal_LoadProvider
    2015-05-02 13:36:06, Info                  DISM   DISM Provider Store: PID=4348 TID=4092 Provider has not previously been encountered.  Attempting to initialize
    the provider. — CDISMProviderStore::Internal_GetProvider
    2015-05-02 13:36:06, Info                  DISM   DISM Provider Store: PID=4348 TID=4092 Loading Provider from location C:WindowsSystem32DismCompatProvider.dll
    — CDISMProviderStore::Internal_GetProvider
    2015-05-02 13:36:06, Info                  DISM   DISM Provider Store: PID=4348 TID=4092 Connecting to the provider located at C:WindowsSystem32DismCompatProvider.dll.
    — CDISMProviderStore::Internal_LoadProvider
    2015-05-02 13:36:06, Info                  DISM   DISM Provider Store: PID=4348 TID=4092 Provider has not previously been encountered.  Attempting to initialize
    the provider. — CDISMProviderStore::Internal_GetProvider
    2015-05-02 13:36:06, Info                  DISM   DISM Provider Store: PID=4348 TID=4092 Loading Provider from location C:WindowsSystem32DismFfuProvider.dll —
    CDISMProviderStore::Internal_GetProvider
    2015-05-02 13:36:06, Info                  DISM   DISM Provider Store: PID=4348 TID=4092 Connecting to the provider located at C:WindowsSystem32DismFfuProvider.dll.
    — CDISMProviderStore::Internal_LoadProvider
    2015-05-02 13:36:06, Info                  DISM   DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.
    2015-05-02 13:36:06, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Log Provider
    2015-05-02 13:36:06, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: FolderManager
    2015-05-02 13:36:06, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: WimManager
    2015-05-02 13:36:06, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: WimManager.
    2015-05-02 13:36:06, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: VHDManager
    2015-05-02 13:36:06, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: GenericImagingManager
    2015-05-02 13:36:06, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: GenericImagingManager.
    2015-05-02 13:36:06, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: Compatibility Manager
    2015-05-02 13:36:06, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: Compatibility Manager.
    2015-05-02 13:36:06, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: FfuManager
    2015-05-02 13:36:06, Info                  DISM   DISM Provider Store: PID=4348 TID=4092 Getting Provider GenericImagingManager — CDISMProviderStore::GetProvider
    2015-05-02 13:36:06, Info                  DISM   DISM Provider Store: PID=4348 TID=4092 Provider has previously been initialized.  Returning the existing instance.
    — CDISMProviderStore::Internal_GetProvider
    2015-05-02 13:36:06, Info                  DISM   DISM Provider Store: PID=4348 TID=4092 Getting Provider FfuManager — CDISMProviderStore::GetProvider
    2015-05-02 13:36:06, Info                  DISM   DISM Provider Store: PID=4348 TID=4092 Provider has previously been initialized.  Returning the existing instance.
    — CDISMProviderStore::Internal_GetProvider
    2015-05-02 13:36:06, Error                 DISM   DISM Imaging Provider: PID=4348 TID=4092 basentsetupopktoolsdismprovidersimagingproviderdllgenericimagingmanager.cpp:2546
    — CGenericImagingManager::InternalCmdFFUApply(hr:0x80070490)
    2015-05-02 13:36:06, Error                 DISM   DISM Imaging Provider: PID=4348 TID=4092 basentsetupopktoolsdismprovidersimagingproviderdllgenericimagingmanager.cpp:535
    — CGenericImagingManager::ExecuteCmdLine(hr:0x80070490)
    2015-05-02 13:36:06, Info                  DISM   DISM.EXE: Image session has been closed. Reboot required=no.
    2015-05-02 13:36:06, Info                  DISM   DISM.EXE:

    2015-05-02 13:36:06, Info                  DISM   DISM.EXE: <—— Ending Dism.exe session ——>
    2015-05-02 13:36:06, Info                  DISM   DISM.EXE:

    2015-05-02 13:36:06, Info                  DISM   DISM Provider Store: PID=4348 TID=4092 Found the OSServices.  Waiting to finalize it until all other providers
    are unloaded. — CDISMProviderStore::Final_OnDisconnect
    2015-05-02 13:36:06, Info                  DISM   DISM Provider Store: PID=4348 TID=4092 Disconnecting Provider: FolderManager — CDISMProviderStore::Internal_DisconnectProvider
    2015-05-02 13:36:06, Info                  DISM   DISM Provider Store: PID=4348 TID=4092 Disconnecting Provider: WimManager — CDISMProviderStore::Internal_DisconnectProvider
    2015-05-02 13:36:06, Info                  DISM   DISM Provider Store: PID=4348 TID=4092 Disconnecting Provider: VHDManager — CDISMProviderStore::Internal_DisconnectProvider
    2015-05-02 13:36:06, Info                  DISM   DISM Provider Store: PID=4348 TID=4092 Disconnecting Provider: GenericImagingManager — CDISMProviderStore::Internal_DisconnectProvider
    2015-05-02 13:36:06, Info                  DISM   DISM Provider Store: PID=4348 TID=4092 Disconnecting Provider: Compatibility Manager — CDISMProviderStore::Internal_DisconnectProvider
    2015-05-02 13:36:06, Info                  DISM   DISM Provider Store: PID=4348 TID=4092 Disconnecting Provider: FfuManager — CDISMProviderStore::Internal_DisconnectProvider
    2015-05-02 13:36:06, Info                  DISM   DISM Provider Store: PID=4348 TID=4092 Releasing the local reference to DISMLogger.  Stop logging. — CDISMProviderStore::Internal_DisconnectProvider

    • Edited by

      Thursday, May 14, 2015 6:16 PM

Answers

  • According to my research FfuProvider.dll checks this values and fails if one of them is empty.
    This is the only reason why dism fails with 1168 error on a Hyper-V virtual machine.

    You can patch x86 version of FfuProvider.dll with HEX editor.
    File offset 0x7312, replace B8 90 04 07 80 with B8 00 00 00 00 (valid for 10074 and 10075)

    Be sure you are patch and use an appropriate version of x86 dism:

    10074
    C:windowsSysWOW64Dism.exe
    C:windowsSysWOW64dismFfuProvider.dll
    To replace this file you have to become his owner and modify access rights.

    10075
    C:Program Files (x86)Windows Kits10Assessment and Deployment KitDeployment Toolsx86DISMdism.exe
    C:Program Files (x86)Windows Kits10Assessment and Deployment KitDeployment Toolsx86DISMffuprovider.dll

    Paths is for x64 windows system.

    Be careful: dism can rewrite any drive, including the system drive of running system if you specify its number in .PhysicalDriveN

    • Edited by
      komarov.biz
      Thursday, May 14, 2015 9:20 AM
    • Marked as answer by
      PA1RB
      Thursday, May 14, 2015 6:14 PM

  • I’m very sorry to hear that you are still experiencing this issue.  Please know that we are looking into it and hope to have a solution or work-around available for you soon.

    The only other suggestion I can think of at the moment is if you could borrow a friends laptop that has a SD card reader built in you might get better results that way.

    Jonathan Tanner | Microsoft | Windows 10 IoT Core Insider Preview Support | This posting is provided ‘as is’ with no warranties and confers no rights.

    • Marked as answer by
      PA1RB
      Saturday, May 9, 2015 9:04 AM

  • OK, today I copied the Flash.ffu file to a Surface PRO 3 running Windows 10 build 10074.

    I have succesfully flashed two SD cards (SanDisk Ultra microSDHC UHS-1 cards with 8 GB, class 10) with the dism.exe on that Surface (dism version 10.0.10074.0).

    The first card I flashed using the build-in micro SD-card reader of the Surface. The second card I flashed using the exact same USB cardreader that does not work on my other computer (recognized by wmic as ChipBank SD/MM Reader USB Device).

    So the USB reader works on the Surface, but does not work on my other computer.

    The Windows 10 builds are both 10074, but the Surface runs the English language, the other computer runs the Dutch language.

    The computer on which the USB stick does not work is based on an ASUS P5LD2-VM motherboard (using the build in USB ports).

    So I will be off playing with the RPI-2 this weekend, but I will keep an eye out for the solution to the issue in this forum.

    Happy to provide more details if required by the engineers!

    • Proposed as answer by
      Jonathan TannerMicrosoft employee
      Friday, May 8, 2015 11:54 PM
    • Edited by
      PA1RB
      Saturday, May 9, 2015 9:02 AM
    • Marked as answer by
      PA1RB
      Saturday, May 9, 2015 9:04 AM

  • Hi,

    I had a similar problem with the above mentioned error. I tested all recomended methods/solutions with two USB card readers and three SD cards (class 10) but with no success. Now I installed Windows on the laptop that has SD card reader built
    in, as recomended above, and it works fine. Thanks for the tip!

    • Marked as answer by
      PA1RB
      Saturday, May 9, 2015 9:04 AM

  • Hello MiPiGamer,

    The page with instructions is here: http://ms-iot.github.io/content/win10/SetupRPI.htm

    The package including the image can be downloaded in step 3:
    Download the package «Windows 10 IoT Core Insider Preview Image for Raspberry Pi 2» from Microsoft Connect (you must be signed in to Microsoft Connect).

    Aside from the issue above writing the image, all went according to the description, and «Blinky» made the LED blink!

    • Marked as answer by
      PA1RB
      Sunday, May 10, 2015 8:49 PM

  • Wow — that did the trick allright:

    Deployment Image Servicing and Management tool
    Version: 10.0.10074.0

    Applying image
    [==========================100.0%==========================]
    The operation completed successfully.

    I confirm this patch absolutely fixed the issue, well done and many thanks indeed !!!

    Hope this finds its way into the next release of Windows 10.

    Ralph

    • Marked as answer by
      PA1RB
      Thursday, May 14, 2015 6:14 PM

Have you ever tried to use your VPN app only to be slapped by an error message saying error 1168 element not found? It is not only annoying but frustrating.

As an avid VPN user, it is normal to encounter one of these errors because VPNs are not as fail-proof as one might think.

But you are in the right place if you have experienced this error, so read till the end to know how to clear VPN error 1168 element not found for good.

What is the element not found error?

The element not found error is usually a network connection problem that appears on Windows versions 7 and 8.

Oftentimes, this error message pops up when launching your VPN app.

However, it can also happen with apps like File Explorer, Microsoft Edge, Command Prompt, or even the Settings app in Windows.

It usually appears either as a result of a bad Windows update, corrupt drivers, or interference from third-party applications.

Below are some fixes you can try:

  1. Install pending Windows updates
  2. Reload Explorer.exe
  3. Uninstall any recently installed apps
  4. Run the DSM tool
  5. Reset your PC
  6. Use a modern VPN

1. Install pending updates

This error may occur if one of your computer’s software components is outdated.

Therefore, ensure that you update your software to the latest version. Follow the steps below to achieve this:

  1. Open Windows settings.
  2. Click Update and Security.

vpn error 1168 element not found

  1. Click Check for updates.

windows updates

Your PC will search the internet for any relevant updates. Click the Update button to download and install any available updates.

2. Reload Explorer.exe

If you get the element not found error whenever you start up your VPN, you may need to reload your File Explorer. Here is how to do that:

  1. Press the Ctrl + Shift + Esc keys on your keyboard to launch the Task Manager.
  2. Click on the Details tab.
  3. Right-click Explorer.exe and select End Task. This will close all Windows Explorer processes so you can reload it.

task manager

  1. Click on File and select Create new task.

run new task

  1. Type explorer.exe into the text box.

refresh windows explorer

  1. Tick the Create this task with administrative privileges box and click OK.

Doing this refreshes your computer so that the Windows Explorer process can start afresh.

3. Uninstall any recently installed apps

If you started getting the error message after installing an app, then it’s only logical to uninstall it and check if it fixes the issue.

This is because the new app may have installed a driver that doesn’t support the VPN application. This has worked in many cases, so you should try it if you have any recently installed apps.

To uninstall apps on your computer, follow these steps:

  1. Press the Windows + R keys on your keyboard.
  2. Type Control Panel and press Enter to launch the Control Panel.

run dontrol panel

  1. Click on Programs.

programs

  1. Click on Uninstall a program.

uninstall

  1. Search for the recently installed app, right-click on it, and click Uninstall.

uninstall adobe air

Now check to see if your VPN works properly.

Alternatively, some windows updates can cause this error to happen. Therefore, you may need to uninstall recent updates. The process is similar to the one above. However, instead of clicking on Uninstall a program,

  1. Click on View installed updates.

view installed updates

  1. Then right-click on the affected updates and click Uninstall.

uninstall updates

Check back to see if the error message is now clear.

4. Run the DISM tool

Running the Deployment Image Servicing and Management tool is another fix for the element not found error.

The purpose of the tool is to scan your PC for problems that can lead to errors and repair them for you.

To run this tool:

  1. Search for Command Prompt from your Start Menu.
  2. Right-click on its icon and select Run as administrator. After this, a black rectangular window will pop up, asking for a command.

    command prompt

  3. Type in the following command: DISM.exe /Online /Cleanup-image /Scanhealth and press the Enter key.

    cmd

  4. After the scan is complete, type this second command: DISM.exe /Online /Cleanup-image /Restorehealth and press Enter to run it.

    cmd

This fix requires a little bit of patience if there are serious or multiple issues with your configuration.

The good news is that it can get rid of a lot of errors and there’s not a lot of work on your end, you just have to make sure you enter the correct commands.

5. Reset Your PC

Resetting your PC should be the last fix to try if you have tried fixes 1- 4 and none worked. Although intense, performing a full reset on your PC is definitely going to clear this error from your computer.

Follow these steps to reset your PC:

  1. Open Computer Settings and click Update and Security.
  2. Click Recovery.
  3. Then click on Get Started below the Reset PC menu.

  1. Select an option from the menu that appears and follow the instructions to reset your PC.

Resetting your PC returns the Windows OS to its original condition – as it was when you first installed it without all the installed programs so it is important to back up your personal files.

6. Use a modern VPN

This element not found error is most pronounced on VPNs with old tunneling protocols, especially L2TP and PPTP.

Therefore, switching to a provider with modern protocols such as OpenVPN and Wireguard is a sure way to fix the issue permanently.

If you want an error-free experience and very fast connections, consider ExpressVPN.

The tool is frequently updated to avoid errors. On top of that, as you can see in the screenshot, it gives you the possibility to pick from multiple VPN protocols.

We must also mention that the VPN has a large network of 3000+ servers located in 94 countries. This is great for anyone who uses VPNs for a better connection or to bypass geo-blocking.

ExpressVPN

ExpressVPN

Use this up-to-date VPN to prevent any errors and enjoy all the benefits of private browsing!

Conclusion

We tested all the fixes in this article. Therefore, we hope that one of them works for you and helps you get rid of the VPN error 1168 element not found on your PC.

by Teodor Nechita

Eager to help those in need, Teodor writes articles daily on subjects regarding Windows, Xbox, and all things tech-related. When not working, you may usually find him either… read more


Updated on December 14, 2021

XINSTALL BY CLICKING THE DOWNLOAD FILE

To fix various PC problems, we recommend DriverFix:
This software will keep your drivers up and running, thus keeping you safe from common computer errors and hardware failure. Check all your drivers now in 3 easy steps:

  1. Download DriverFix (verified download file).
  2. Click Start Scan to find all problematic drivers.
  3. Click Update Drivers to get new versions and avoid system malfunctionings.
  • DriverFix has been downloaded by 0 readers this month.

Several users have been reporting on the official Microsoft forums that they are having issues with the XPS printer:

I was unable to print from software using the XPS writer.  I attempted to reinstall the printer but the installation fails reporting “printer driver not installed.  Element not found”

Apparently, they are getting an error 1168: Element not found can have a wide variety of causes.

This article will guide you step-by-step on how to fix this error with the XPS printer.

How do you fix a generic error 1168?

1. Update your drivers

  1. Click on the Start button, then go to Settings
  2. Select Update & Security
  3. Click on Check for updates
  4. Allow Windows Update to download and install the updated driver

Follow these steps to install the latest printer drivers using Windows Update.

Alternatively, you can use a professional third-party tool that performs this process automatically and aims to keep your printer drivers updated and healthy.

More so, by choosing this automated method of managing drivers you also stay secure from potential damages caused by devices incompatibility.

Thus if you need reliable support to install or update any driver, the following software will accomplish this mission with no exception.

⇒ Get DriverFix

2. Try reinstalling the Windows XPS feature

  1. Press Windows
  2. Click on Settings (the cogwheel-shaped button)
  3. Select Apps
  4. Go to Apps & features
  5. Click Optional features
  6. Look for XPS feature if it is present
  7. If it is, right-click it and select uninstall
  8. Restart your PC
  9. After the restart or if your PC didn’t have the feature, go to the Manage optional features screen, and select Add a new feature
  10. When on the Add a new feature screen, select the XPS Viewer
  11. Restart your PC

Add a new feature XPS

3. Manually search for the location of your XPS Writer

Depending on which version of Windows 10 you have installed, the location of the XPS Writer may vary.

As such, if the solution listed above didn’t work, try this:

  1. Press Windows + R
  2. Type in control.exe
  3. Click Programs
  4. Select Programs and Features
  5. Click Turn Windows features on or off
  6. See if XPS Services and XPS Viewer are listed
    • If the services are marked in their checkbox, unmark them and restart the PC
    • If the services are unmarked in their checkbox, mark them and restart the PC
  7. Press Windows + R
  8. Type in control.exe
  9. Go to Hardware and Sound 
  10. Click Devices and Printers
  11. See if Microsoft XPS Document Writer is installed as a printer.
  12. If it is, right-click it and choose Remove device
  13. Restart your PC
  14. Go back to Devices and Printers and select Add a printer
  15. Select The printer that I want isn’t listed
  16. Click Add a local printer or network printer with manual setting
  17. In the Choose a printer port screen, select Use an existing port and PORTPROMPT: (Local Port)
  18. In the Install a printer driver screen, select Microsoft on the left pane and Microsoft XPS Document Writer on the right
  19. When asked Which version of the driver do you want to use? select Use the driver that is currently installed (recommended)

XPS printer remove device

If these particular steps didn’t help, you could also try to:

  • Uninstall Recent Windows Updates
  • Reset Your PC

newsletter icon

Newsletter

SUPPORT COMMUNICATION- CUSTOMER ADVISORY

Document ID: c06417547

Version: 1

Notice: The information in this document, including products and software versions, is current as of the release date.The document is subject to change without notice.

Release date : 22-Jul-2019

Last updated : 22-Jul-2019

DESCRIPTION

When using Microsoft System Center Configuration Manager (SCCM) to configure systems in the SCOPE, the following DISM error occurs:

Error: 1168.

Element Not Found.

This occurs when the Microsoft Deployment Image Servicing and Management (DISM) command tool executes commands to configure the Realtek HD Audio driver (SoftPaq SP95193). The issue occurs because the driver includes a Universal Windows Platform (UWP) component that is not being handled properly.

SCOPE

Information in this document applies to the following:

Computers:

HP EliteBook 830 G5 Notebook PC

Operating Systems:

Microsoft Windows 10 RS5 (Version 1809)

RESOLUTION

Below are the steps necessary to install this component with SCCM.

  1. Extract SoftPaq .

  2. Add a batch file to install the UWP component with DISM. Here is the DISM command to insert into the batch file:

    @echo ON dism.exe /image:%OSD_System% /add-Driver /Driver:%~dp0HSAcb68d18decd44cd44c94bec5cd2a2c354180.appxbundle /Region=»all» /LicensePath:%~dp0HSAcb68d18decd44cd44c94bec5cd2a2c354180_License1.xml /DependencyPackagePath:%~dp0HSA Micrsooft.VCLibs.140.00_14.0.26706.0_x64_8wekyb3d8bbwe.appx

    note:

    The variable
    %OSD_System%, used in the command above, is set by the partitioning step previous in the task sequence.

  3. Create a package and add a command line step to execute the batch file right after windows image, and before Apply Windows Settings.

  4. Deploy the task sequence and use Device Manager to verify that the Realtek Audio driver is installed.

Hardware platforms affected :

HP EliteBook 830 G5 Notebook PC

Operating systems affected : Not applicable

Software affected : Not applicable

Support Communication Cross Reference ID : IA06417547

© Copyright 2023 HP Development Company, L.P.

HP Inc. shall not be liable for technical or editorial errors or omissions contained herein. The information provided is provided «as is» without warranty of any kind. To the extent permitted by law, neither HP or its affiliates, subcontractors or suppliers will be liable for incidental, special or consequential damages including downtime cost; lost profits; damages relating to the procurement of substitute products or services; or damages for loss of data, or software restoration. The information in this document is subject to change without notice. HP Inc. and the names of HP products referenced herein are trademarks of HP Inc. in the United States and other countries. Other product and company names mentioned herein may be trademarks of their respective owners.

  • Remove From My Forums

  • Question

  • I am trying to install printer drivers on two Windows 2012R2 servers and I am getting  the error: Printer driver was not installed  ‘Element not found’.  In the setupapi.dev.log file it shows ‘

    Class installer: failed(0x00000490)!

    Error 1168: Element not found

    I have tried using the pnputil to add the driver, but nothing has worked.

Answers

  • This sounds like the print drivers are not package aware print drivers.

    I assume other printer drivers install without any issue, just some drivers that you have not mentioned where they were obtained.

    If the print driver does install on one 2012R2 machine, use the print backup utility c:windowssystem32spooltoolsprintbrm.exe to backup the driver and then restore the driver to the machine with the issue adding the driver to the driverstore.

    printbrm -b -f backup.printerexport

    printbrm -r -s printserver -f backup.printerexport

    Alan Morris formerly with Windows Printing Team

    • Proposed as answer by

      Wednesday, June 17, 2015 9:36 AM

    • Marked as answer by
      Vivian_Wang
      Monday, June 22, 2015 5:19 AM

After you upgrade to Windows 10 or install a Windows 10 Feature update, you’ll be able to go back to your previous version of Windows within a limited time of 10 days. This can be done by opening Settings → Update & Security → Recovery → Go back to the previous version of Windows 10.

windows 10 go back uninstall days

(If you have upgraded from Windows 7, you’ll see Go back to Windows 7 instead.)

Rolling back to the previous version using this method keeps your personal files, but it’ll remove your customizations, apps, and drivers installed after the upgrade. By default, you have ten days, before which you can roll back to the previous version of Windows.

Uninstalling the current version and going back to the previous version of Windows also frees up gigabytes of data on your hard disk, as the Windows.old folder is deleted.

After the 10-day window, the previous Windows installation files under the Windows.old directory would be automatically erased (maybe using Disk Cleanup) by the Operating System. The Get started button would then be grayed out.

free disk space after windows upgrade

In Windows 10 versions before the Anniversary Update (v1607), the rollback timeframe was 30 days. Since the Anniversary Update, Microsoft has reduced the uninstall window to 10 days. As per Microsoft, it was a data-driven decision (based on telemetry) to change the rollback timeframe from 30 to just 10 days. Quoting the source:

Based on our user research, we noticed most users who choose to go back to a previous version of Windows do it within the first several days. As such, we changed the setting to 10 days to free storage space used by previous copies.

Evaluating an Operating System may need more time for end-users, and a 10-day window is insufficient for most people. The good news is that you can increase the Go back to the previous version of Windows to a maximum of 60 days manually.

This article tells you how to extend the 10-day rollback window on your Windows 10 computer.

Using the DISM utility, you can do the following:

  • Find out how many days after an upgrade that an OS can be uninstalled.
  • Initiate an uninstall or roll back to the previous OS or version.
  • Remove the ability to uninstall a Windows upgrade.
  • Set the number of days that a user has to uninstall a Windows upgrade.

(Reference: DISM Operating System uninstall Command-Line Options.)

Find the rollback timeframe (number of days)

To determine the uninstall window timeframe (days) of your existing Windows installation, run this command from admin Command Prompt:

DISM /Online /Get-OSUninstallWindow

You’ll see the following output:

Deployment Image Servicing and Management tool
Version: 10.0.19041.572

Image Version: 10.0.19042.661

Uninstall Window : 10
The operation completed successfully.

Increase the rollback timeframe (number of days)

Run this command to set the number of days after an upgrade that an uninstall can be initiated.

Syntax:

DISM /Online /Set-OSUninstallWindow /Value:<days>

The value (i.e., number of days) must be in the range of 2 to 60. If the value you input doesn’t fall in that range, the default value of 10 will be set.

Example:

DISM /Online /Set-OSUninstallWindow /Value:30

You should see the message “The operation completed successfully” in the output.

The above command-line sets the rollback window to 30 days. Windows won’t erase the Windows.old folder before 30 days.

Set the Rollback timeframe via the Registry

You can set the rollback window timeframe by editing the registry, as well.

  1. Start the Registry Editor, and go to the following branch: 
    HKEY_LOCAL_MACHINESYSTEMSetup
  2. Create a new DWORD value named UninstallWindow if it doesn’t already exist.
  3. Double-click UninstallWindow, select Decimal, and type in the desired value (>2 to <60), and click OK.
    windows 10 go back uninstall days
    Note that if the above registry value doesn’t exist, “10” days will be the default threshold limit used by Windows.
  4. Exit the Registry Editor.

After the registry modification, it’s better that you restart Windows, though the DISM Get-OSUninstallWindow command would reflect the registry change even if you don’t reboot.

Additional Tip

There are two more DISM switches namely, Initiate-OSUninstall and Remove-OSUninstall that you may like to know about. The former is to initiate a rollback using command-line, and the latter is to remove the ability to rollback by users.

The Remove-OSUninstall switch would gray out the Get Started button under the Go back to the previous… section. The command deletes the following registry values from the abovesaid branch. It may also remove the corresponding BCD data and the Windows Recovery Environment entry named “Go back to the previous build.”

Registry values:

  • UninstallActive
  • UninstallGUID
  • UninstallMark
  • UninstallScenario

Error: 1168 – Element not found

In some cases, the error 1168 (‘element not found’) may occur when running the DISM Get-OSUninstallWindow or Set-OSUninstallWindow command.

Deployment Image Servicing and Management tool
Version: 10.0.19041.572

Image Version: 

Error: 1168

Element not found.

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

The DISM.log file would show the following entries:

Error pGetUninstallInterfaceCommon: Failed loading the setupplatform, hr = 0x80070490 [gle=0x00000003]
Error DISM DISM SetupPlatform Provider: PID=3944 TID=9192 Failed getting UninstallInterface Online. - CSetupPlatformManager::GetUninstallWindow(hr:0x80070490)
Error DISM DISM SetupPlatform Provider: PID=3944 TID=9192 Failed to get the uninstall window. - CSetupPlatformManager::ProcessCmdLine_GetUninstallWindow(hr:0x80070490)
Error DISM DISM SetupPlatform Provider: PID=3944 TID=9192 Failed while processing command get-osuninstallwindow. - CSetupPlatformManager::ExecuteCmdLine(hr:0x80070490)

Error 1168 (0x80070490), which denotes “Element not found”, occurs if the Windows.old folder (especially the subfolder $WINDOWS.~BT) has been deleted by Windows after the rollback window has expired.

It’s also possible that you’ve manually cleared the “Previous Windows installation(s)” files using Disk Cleanup or Storage settings to recover the disk space.free disk space after windows upgrade

windows 10 go back uninstall days

The DISM DISM Get-OSUninstallWindow and Set-OSUninstallWindow commands would need the following files in order to work correctly:

C:windows.old$WINDOWS.~BTSourcesapi-ms-win-core-kernel32-legacy-l1-1-0.dll
C:windows.old$WINDOWS.~BTSourcesfltLib.dll
C:windows.old$WINDOWS.~BTSourcesmpr.dll
C:windows.old$WINDOWS.~BTSourcessetupplatform.dll
C:windows.old$WINDOWS.~BTSourcessspicli.dll
C:windows.old$WINDOWS.~BTSourcesunbcl.dll
C:windows.old$WINDOWS.~BTSourcesvirtdisk.dll
C:windows.old$WINDOWS.~BTSourceswinhttp.dll
C:windows.old$WINDOWS.~BTSourceswtsapi32.dll

windows 10 go back uninstall days

If Windows.old or its subfolder $WINDOWS.~BT is missing, or if some of the DLLs are missing in that location, you’ll get one of the following errors:

Error: 1168

Element not found.

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

The specified module could not be found.

The DISM log file can be found at C:WINDOWSLogsDISMdism.log
Error 3: The system cannot find the path specified

hand point iconDespite this, you should be able to set the uninstall threshold or timeframe using the registry method described above.

Closing words

It’s unclear whether the uninstall window you set using DISM or the registry will the preserved or not if you install an update (Feature Update) in the future.

Of course, the ultimate trick of renaming C:Windows.old and C:$Windows~BT would prevent Windows 10 from erasing them automatically. By renaming the folders, you get unlimited time to go back to the chosen version.

One small request: If you liked this post, please share this?

One «tiny» share from you would seriously help a lot with the growth of this blog.
Some great suggestions:

  • Pin it!
  • Share it to your favorite blog + Facebook, Reddit
  • Tweet it!

So thank you so much for your support. It won’t take more than 10 seconds of your time. The share buttons are right below. :)

Источник

Using the latest version of DISM (Version: 10.0.14393.0) I mounted the Install.wim for W10 1607 and injected the five roll-up updates (KB3193494, KB3176938, KB3176934, KB3176495, KB3176929.)  I got no errors during the installs, but afterward I got
the 1168 error and the message that the image was no longer serviceable.

I first tried this on my host system running W10 1511, then my Hyper-V VM running W10 1607 (with SecureBoot enabled).  The error is the same on both.  Injecting only one KB gave no error.

The roll-up updates were DLed from Microsoft Update Catalog and the hash codes confirmed.

Below is the DISM log (LogLevel:1).

Thanks and enjoy, John.

[6632] Caller did not request sparse mount
[6632] Mounting new image.
Wim:         [\tsclientWW10-FXsourcesinstall.wim]
Image Index: [1]
Mount Path:  [C:FastMount]
[6632] Wimserv process started for guid 577426ba-4a55-4981-9d32-ba6794ce4ab8.  Id is 1920
[1920] ImageUnmarshallHandle: Reconstituting wim at \tsclientWW10-FXsourcesinstall.wim.
[1920] Mounted image at C:FastMount.
[696] ImageUnmarshallHandle: Reconstituting wim at \tsclientWW10-FXsourcesinstall.wim.
[696] ImageUnmarshallHandle: Reconstituting wim at \tsclientWW10-FXsourcesinstall.wim.
2016-09-26 12:47:39, Error                 DISM   DISM Package Manager: PID=5736 TID=2476 Incorrect parameter E:W10-ComponentsBuild-ComponentsUpdates — path not found
— CDISMPackageManager::Internal_CreatePackageByPath(hr:0x80070003)
2016-09-26 12:47:39, Error                 DISM   DISM Package Manager: PID=5736 TID=2476 Failed to get the underlying CBS package. — CDISMPackageManager::OpenPackageByPath(hr:0x80070003)
2016-09-26 12:47:39, Error                 DISM   DISM Package Manager: PID=5736 TID=2476 Failed to open the package at location: «E:W10-ComponentsBuild-ComponentsUpdates»
— CPackageManagerCLIHandler::ProcessPackagePath(hr:0x80070003)
2016-09-26 12:47:39, Error                 DISM   DISM Package Manager: PID=5736 TID=2476 Failed while processing command add-package. — CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x80070003)
[4944] ImageUnmarshallHandle: Reconstituting wim at \tsclientWW10-FXsourcesinstall.wim.
[4944] ImageUnmarshallHandle: Reconstituting wim at \tsclientWW10-FXsourcesinstall.wim.
[1920] ReadWriteDataInternal:(135)
[1920] ResExtract:(558)
[1920] [ResExtract:(559) -> WIMCopyFileEx failed] C:FastMountWindowsWinSxSamd64_microsoft-windows-ui-search_31bf3856ad364e35_10.0.14393.0_none_2285a4ae39b49b48logo.scale-80.png (Error = 59)

[1920]
2016-09-26 13:16:37, Error                 CBS    Doqe: Failed processing queue [HRESULT = 0x80070490 — ERROR_NOT_FOUND]
2016-09-26 13:16:37, Error                 CBS    Doqe: Failed while processing driver operations queue. [HRESULT = 0x80070490 — ERROR_NOT_FOUND]
2016-09-26 13:16:37, Error                 CBS    Failed to process single phase execution. [HRESULT = 0x80070490 — ERROR_NOT_FOUND]
2016-09-26 13:16:38, Error                 CBS    Failed to perform operation.  [HRESULT = 0x80070490 — ERROR_NOT_FOUND]
2016-09-26 13:16:38, Error                 DISM   DISM Package Manager: PID=1352 TID=4416 Failed finalizing changes. — CDISMPackageManager::Internal_Finalize(hr:0x80070490)
2016-09-26 13:16:42, Error                 DISM   DISM Package Manager: PID=1352 TID=4416 Failed processing package changes — CDISMPackageManager::ProcessChanges(hr:0x80070490)
2016-09-26 13:16:42, Error                 DISM   DISM Package Manager: PID=1352 TID=4416 Failed to process package changes in unattend file. — CPackageManagerUnattendHandler::Internal_ProcessChanges(hr:0x80070490)
2016-09-26 13:16:42, Error                 DISM   DISM Package Manager: PID=1352 TID=4416 Failed to process package changes. — CPackageManagerUnattendHandler::Apply(hr:0x80070490)
2016-09-26 13:16:42, Error                 DISM   DISM Package Manager: PID=1352 TID=4416 Failed to Apply the unattend. — CDISMPackageManager::Apply(hr:0x80070490)
2016-09-26 13:16:42, Error                 DISM   DISM Unattend Manager: PID=1352 TID=4416 «Error applying unattend for provider: DISM Package Manager» — CUnattendManager::Apply(hr:0x80070490)
2016-09-26 13:16:42, Error                 DISM   DISM Package Manager: PID=1352 TID=4416 Failed applying the unattend file from the MSU package. — CMsuPackage::ApplyMsuUnattend(hr:0x80070490)
2016-09-26 13:16:42, Error                 DISM   DISM Package Manager: PID=1352 TID=4416 Failed to apply the MSU unattend file to the image. — CMsuPackage::Install(hr:0x80070490)
2016-09-26 13:16:43, Error                 DISM   DISM Package Manager: PID=1352 TID=4416 Discard this Windows image and try the operation again on a new Windows image.
— GetCbsErrorMsg
2016-09-26 13:16:43, Error                 DISM   DISM Package Manager: PID=1352 TID=4416 The specified image is no longer serviceable. Unmount the image and discard your
changes.  Mount the original image to try the operation again. — CPackageManagerCLIHandler::ReportFailedPackage
2016-09-26 13:17:27, Error                 CBS    The image has been damaged by an offline servicing failure and no further servicing is allowed. [HRESULT = 0x800f0830
— CBS_E_IMAGE_UNSERVICEABLE]
2016-09-26 13:17:27, Error                 CBS    Failed to perform operation.  [HRESULT = 0x800f0830 — CBS_E_IMAGE_UNSERVICEABLE]
2016-09-26 13:17:27, Error                 DISM   DISM Package Manager: PID=1352 TID=4416 Failed finalizing changes. — CDISMPackageManager::Internal_Finalize(hr:0x800f0830)
2016-09-26 13:17:27, Error                 DISM   DISM Package Manager: PID=1352 TID=4416 Discard this Windows image and try the operation again on a new Windows image.
— GetCbsErrorMsg
2016-09-26 13:17:27, Error                 DISM   DISM Package Manager: PID=1352 TID=4416 Failed processing package changes — CDISMPackageManager::ProcessChanges(hr:0x800f0830)
2016-09-26 13:17:27, Error                 DISM   DISM Package Manager: PID=1352 TID=4416 Discard this Windows image and try the operation again on a new Windows image.
— GetCbsErrorMsg
2016-09-26 13:17:27, Error                 DISM   DISM Package Manager: PID=1352 TID=4416 Failed to process package changes in unattend file. — CPackageManagerUnattendHandler::Internal_ProcessChanges(hr:0x800f0830)
2016-09-26 13:17:27, Error                 DISM   DISM Package Manager: PID=1352 TID=4416 Failed to process package changes. — CPackageManagerUnattendHandler::Apply(hr:0x800f0830)
2016-09-26 13:17:27, Error                 DISM   DISM Package Manager: PID=1352 TID=4416 Failed to Apply the unattend. — CDISMPackageManager::Apply(hr:0x800f0830)
2016-09-26 13:17:27, Error                 DISM   DISM Unattend Manager: PID=1352 TID=4416 «Error applying unattend for provider: DISM Package Manager» — CUnattendManager::Apply(hr:0x800f0830)
2016-09-26 13:17:27, Error                 DISM   DISM Package Manager: PID=1352 TID=4416 Failed applying the unattend file from the MSU package. — CMsuPackage::ApplyMsuUnattend(hr:0x800f0830)
2016-09-26 13:17:27, Error                 DISM   DISM Package Manager: PID=1352 TID=4416 Failed to apply the MSU unattend file to the image. — CMsuPackage::Install(hr:0x800f0830)
2016-09-26 13:17:27, Error                 DISM   DISM Package Manager: PID=1352 TID=4416 Failed while processing command add-package. — CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x80070490)

Источник

  • Dism ошибка 1 неверная функция windows 10
  • Dism ошибка 0x8024402c windows 10
  • Dism ошибка 0x800f081f не удалось найти исходные файлы
  • Dism код ошибки 193
  • Dism windows 10 ошибка 0x800f0906