Ошибка unattend xml

I get ti error with answer file and don-t know what can be wrong, if someone can help me please.

setupact.log

_________________________

2011-12-14 11:38:22, Info                  CBS    Startup: Package: Server-Help-Package.ClientUltimate~31bf3856ad364e35~amd64~~6.1.7600.16385 completed startup
processing, new state: Absent, original: Staged, targeted: Absent.  hr = 0x0

2011-12-14 11:38:22, Info                  CBS    Setting ExecuteState key to: ExecuteStateNone

2011-12-14 11:38:22, Info                  CBS    Setting RollbackFailed flag to 0

2011-12-14 11:38:22, Info                  CBS    Clearing HangDetect value

2011-12-14 11:38:22, Info                  CBS    Saved last global progress. Current: 0, Limit: 1, ExecuteState: ExecuteStateNone

2011-12-14 11:38:22, Info                  CBS    Startup: Retry delayed by pending reboot; making sure we remain auto-start and don’t clean up the package store.

2011-12-14 11:38:22, Info                  CBS    Startup: Processing complete. [HRESULT = 0x80070bc2 — ERROR_SUCCESS_REBOOT_REQUIRED]

2011-12-14 11:38:22, Info                  CBS    Restored system sleep block state: 0x80000003

2011-12-14 11:38:22, Info                  CBS    Enabling LKG boot option

2011-12-14 11:38:22, Info                  CMI    Callback_CBS_Do_OnlineInstall:Calling startup processing succeeded but reboot is required 0x80070bc2

2011-12-14 11:38:23, Info                  CMI    Callback_CBS_Do_OnlineInstall:Calling startup processing succeeded

2011-12-14 11:38:23, Info                  CMI    CBS_Core_Finalize:Calling cbs core finalize

2011-12-14 11:38:23, Info                  CMI    CBS_Core_Finalize:Calling cbs core finalize complete

2011-12-14 11:38:23, Info                  CMI    Callback_CMI_ConfigInstall: CBS startup processing re-run complete.

2011-12-14 11:38:23, Info       [0x030023] CMI    Callback_CMI_ConfigInstall: Exit.

2011-12-14 11:38:23, Info                         [setup.exe] UnattendSearchExplicitPath: Found unattend file at [C:WindowsPantherunattend.xml];
examining for applicability.
2011-12-14 11:38:23, Info                         [setup.exe] UnattendSearchExplicitPath: Found usable unattend file for pass [specialize]
at [C:WindowsPantherunattend.xml].
2011-12-14 11:38:23, Info                  IBS    Callback_Unattend_InitEngine:Using unattend file found at [C:WindowsPantherunattend.xml].

2011-12-14 11:38:23, Info                         [setup.exe] ValidateSMIPass: serialized settings stream; status 0x00000000

2011-12-14 11:38:23, Info                         [setup.exe] ValidateSMIPass: construct settings context; status 0x00000000

2011-12-14 11:38:23, Error                 CSI    00000001 (F) 80220005 [Error,Facility=FACILITY_STATE_MANAGEMENT,Code=5] #82# from CWcmScalarInstanceCore::PutCurrentValue(options
= 0, value = { type: 8204 (0x0000200c), bytes ( 34 (0x00000022) ): 610064006d0069006e006900730074007200610074006f0072003100360031000000 })

[gle=0x80004005]
2011-12-14 11:38:23, Error                        [setup.exe] SMI data results dump: Source = Name: Microsoft-Windows-Shell-Setup, Language: neutral,
ProcessorArchitecture: amd64, PublicKeyToken: 31bf3856ad364e35, VersionScope: nonSxS, /settings/ComputerName

2011-12-14 11:38:23, Error                        [setup.exe] SMI data results dump: Description = Value is invalid.

2011-12-14 11:38:23, Info                         [setup.exe] ValidateSMIPass: load SMI settings; status 0x00000001

2011-12-14 11:38:23, Error      [0x060432] IBS    The provided unattend file is not valid; hrResult = 0x80220005

2011-12-14 11:38:23, Error      [0x060565] IBS    Callback_Unattend_InitEngine:The provided unattend file [C:WindowsPantherunattend.xml] is not a valid unattended Setup answer file; hr = 0x1, hrSearched = 0x1, hrDeserialized
= 0x0, hrImplicitCtx = 0x0, hrValidated = 0x1, hrResult = 0x80220005
2011-12-14 11:38:23, Info                  IBS    UnattendErrorFromResults: Hit an unattend error; dumping any info we have about the failure…

2011-12-14 11:38:23, Info                  IBS    UnattendDumpSetting: ——Unattend setting error / warning——

2011-12-14 11:38:23, Info                  IBS    UnattendDumpSetting: Error code = 0x80220005

2011-12-14 11:38:23, Info                  IBS    UnattendDumpSetting: Pass = specialize

2011-12-14 11:38:23, Info                  IBS    UnattendDumpSetting: ———————————————

2011-12-14 11:38:23, Info                  IBS    UnattendErrorFromResults: Error text = Windows ni mogel razčleniti ali obdelati nespremljane datoteke z odgovori
[C:WindowsPantherunattend.xml] za pregled [specialize]. Datoteka z odgovori ni veljavna.

2011-12-14 11:38:23, Error      [0x0600c2] IBS    Callback_Unattend_InitEngine:An error occurred while finding/loading the unattend file; hr = 0x1, hrResult = 0x80220005[gle=0x00000490]

2011-12-14 11:38:23, Info                  IBSLIB PublishCriticalError: Publishing blocked message [Windows ni mogel razčleniti ali obdelati nespremljane datoteke z odgovori
[C:WindowsPantherunattend.xml] za pregled [specialize]. Datoteka z odgovori ni veljavna.]

2011-12-14 11:38:23, Info                         This installation is blocked from completing due to compliance failures or invalid input;
this is not an internal error.

setuperr.log

__________________________

2011-12-14 11:38:23, Error                 CSI    00000001 (F) 80220005 [Error,Facility=FACILITY_STATE_MANAGEMENT,Code=5] #82# from CWcmScalarInstanceCore::PutCurrentValue(options
= 0, value = { type: 8204 (0x0000200c), bytes ( 34 (0x00000022) ): 610064006d0069006e006900730074007200610074006f0072003100360031000000 })

[gle=0x80004005]
2011-12-14 11:38:23, Error                        [setup.exe] SMI data results dump: Source = Name: Microsoft-Windows-Shell-Setup, Language: neutral,
ProcessorArchitecture: amd64, PublicKeyToken: 31bf3856ad364e35, VersionScope: nonSxS, /settings/ComputerName

2011-12-14 11:38:23, Error                        [setup.exe] SMI data results dump: Description = Value is invalid.

2011-12-14 11:38:23, Error      [0x060432] IBS    The provided unattend file is not valid; hrResult = 0x80220005

2011-12-14 11:38:23, Error      [0x060565] IBS    Callback_Unattend_InitEngine:The provided unattend file [C:WindowsPantherunattend.xml] is not a valid unattended Setup answer file; hr = 0x1, hrSearched = 0x1, hrDeserialized
= 0x0, hrImplicitCtx = 0x0, hrValidated = 0x1, hrResult = 0x80220005
2011-12-14 11:38:23, Error      [0x0600c2] IBS    Callback_Unattend_InitEngine:An error occurred while finding/loading the unattend file; hr = 0x1, hrResult = 0x80220005[gle=0x00000490]

I never left an open problem….I search, dig and ask, until it’s solved….

Источник

Последнее обновление: 07/04/2022
[Среднее время чтения: 4,5 мин.]

Файлы XML, такие как unattend.xml, классифицируются как файлы XML (Extensible Markup Language). Как файл Extensible Markup Language он был создан для использования в VMWare Workstation Player 15.5.1 от компании VMware.

Файл unattend.xml изначально был выпущен с EaseUS Todo Backup 11.5 08/16/2018 для ОС Windows 10.

Самая последняя версия [версия 15.5.1] была представлена 09/19/2019 для VMWare Workstation Player 15.5.1.

Файл unattend.xml включен в VMWare Workstation Player 15.5.1, VMware Workstation 12.5.5 и EaseUS Partition Master Free Edition 13.5.

Ниже приведены подробные сведения, порядок устранения неполадок, возникших с файлом XML, и бесплатные загрузки различных версий файла unattend.xml.

Что такое сообщения об ошибках unattend.xml?

Общие ошибки выполнения unattend.xml

Ошибки файла unattend.xml часто возникают на этапе запуска VMWare Workstation Player, но также могут возникать во время работы программы.
Эти типы ошибок XML также известны как «ошибки выполнения», поскольку они возникают во время выполнения VMWare Workstation Player. К числу наиболее распространенных ошибок выполнения unattend.xml относятся:

  • Не удается найти unattend.xml.
  • unattend.xml — ошибка.
  • Не удалось загрузить unattend.xml.
  • Ошибка при загрузке unattend.xml.
  • Не удалось зарегистрировать unattend.xml / Не удается зарегистрировать unattend.xml.
  • Ошибка выполнения — unattend.xml.
  • Файл unattend.xml отсутствует или поврежден.

Библиотека времени выполнения Microsoft Visual C++

Ошибка выполнения!

Программа: C:Program Files (x86)VMwareVMware PlayerResourcesunattend.xml

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

В большинстве случаев причинами ошибок в XML являются отсутствующие или поврежденные файлы. Файл unattend.xml может отсутствовать из-за случайного удаления, быть удаленным другой программой как общий файл (общий с VMWare Workstation Player) или быть удаленным в результате заражения вредоносным программным обеспечением. Кроме того, повреждение файла unattend.xml может быть вызвано отключением питания при загрузке VMWare Workstation Player, сбоем системы при загрузке или сохранении unattend.xml, наличием плохих секторов на запоминающем устройстве (обычно это основной жесткий диск) или заражением вредоносным программным обеспечением. Таким образом, крайне важно, чтобы антивирус постоянно поддерживался в актуальном состоянии и регулярно проводил сканирование системы.

Как исправить ошибки unattend.xml — 3-шаговое руководство (время выполнения: ~5-15 мин.)

Если вы столкнулись с одним из вышеуказанных сообщений об ошибке, выполните следующие действия по устранению неполадок, чтобы решить проблему unattend.xml. Эти шаги по устранению неполадок перечислены в рекомендуемом порядке выполнения.

Шаг 1. Восстановите компьютер до последней точки восстановления, «моментального снимка» или образа резервной копии, которые предшествуют появлению ошибки.

Чтобы начать восстановление системы (Windows XP, Vista, 7, 8 и 10):

  1. Нажмите кнопку «Пуск» в Windows
  2. В поле поиска введите «Восстановление системы» и нажмите ENTER.
  3. В результатах поиска найдите и нажмите «Восстановление системы»
  4. Введите пароль администратора (при необходимости).
  5. Следуйте инструкциям мастера восстановления системы, чтобы выбрать соответствующую точку восстановления.
  6. Восстановите компьютер к этому образу резервной копии.

Если на этапе 1 не удается устранить ошибку unattend.xml, перейдите к шагу 2 ниже.

Шаг 2. Если вы недавно установили приложение VMWare Workstation Player (или схожее программное обеспечение), удалите его, затем попробуйте переустановить VMWare Workstation Player.

Чтобы удалить программное обеспечение VMWare Workstation Player, выполните следующие инструкции (Windows XP, Vista, 7, 8 и 10):

  1. Нажмите кнопку «Пуск» в Windows
  2. В поле поиска введите «Удалить» и нажмите ENTER.
  3. В результатах поиска найдите и нажмите «Установка и удаление программ»
  4. Найдите запись для VMWare Workstation Player 15.5.1 и нажмите «Удалить»
  5. Следуйте указаниям по удалению.

После полного удаления приложения следует перезагрузить ПК и заново установить VMWare Workstation Player.

Если на этапе 2 также не удается устранить ошибку unattend.xml, перейдите к шагу 3 ниже.

VMWare Workstation Player 15.5.1

VMware

Шаг 3. Выполните обновление Windows.

Когда первые два шага не устранили проблему, целесообразно запустить Центр обновления Windows. Во многих случаях возникновение сообщений об ошибках unattend.xml может быть вызвано устаревшей операционной системой Windows. Чтобы запустить Центр обновления Windows, выполните следующие простые шаги:

  1. Нажмите кнопку «Пуск» в Windows
  2. В поле поиска введите «Обновить» и нажмите ENTER.
  3. В диалоговом окне Центра обновления Windows нажмите «Проверить наличие обновлений» (или аналогичную кнопку в зависимости от версии Windows)
  4. Если обновления доступны для загрузки, нажмите «Установить обновления».
  5. После завершения обновления следует перезагрузить ПК.

Если Центр обновления Windows не смог устранить сообщение об ошибке unattend.xml, перейдите к следующему шагу. Обратите внимание, что этот последний шаг рекомендуется только для продвинутых пользователей ПК.

Если эти шаги не принесут результата: скачайте и замените файл unattend.xml (внимание: для опытных пользователей)

Если ни один из предыдущих трех шагов по устранению неполадок не разрешил проблему, можно попробовать более агрессивный подход (примечание: не рекомендуется пользователям ПК начального уровня), загрузив и заменив соответствующую версию файла unattend.xml. Мы храним полную базу данных файлов unattend.xml со 100%-ной гарантией отсутствия вредоносного программного обеспечения для любой применимой версии VMWare Workstation Player . Чтобы загрузить и правильно заменить файл, выполните следующие действия:

  1. Найдите версию операционной системы Windows в нижеприведенном списке «Загрузить файлы unattend.xml».
  2. Нажмите соответствующую кнопку «Скачать», чтобы скачать версию файла Windows.
  3. Скопируйте этот файл в соответствующее расположение папки VMWare Workstation Player:

    Windows 10: C:Program Files (x86)EaseUSEaseUS Partition Master 13.5BUILDPEx86WindowsSystem32
    Windows 10: C:Program Files (x86)EaseUSTodo BackupBUILDPEx86Windowssystem32
    Windows 10: C:Program Files (x86)EaseUSDisk CopyBUILDPEx64Windowssystem32
    Windows 10: C:Program Files (x86)EaseUSDisk CopyBUILDPEx86Windowssystem32
    Windows 10: C:Program Files (x86)VMwareVMware WorkstationResources

    Показать на 3 каталогов больше +

    Windows 10: C:Program Files (x86)VMwareVMware PlayerResources
    Windows 10: C:Program Files (x86)EaseUSEaseUS Partition Master 13.5BUILDPEx64WindowsSystem32
    Windows 10: C:Program Files (x86)EaseUSTodo BackupBUILDPEx64Windowssystem32

  4. Перезагрузите компьютер.

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

СОВЕТ ОТ СПЕЦИАЛИСТА: Мы должны подчеркнуть, что переустановка Windows является достаточно длительной и сложной задачей для решения проблем, связанных с unattend.xml. Во избежание потери данных следует убедиться, что перед началом процесса вы создали резервные копии всех важных документов, изображений, установщиков программного обеспечения и других персональных данных. Если вы в настоящее время не создаете резервных копий своих данных, вам необходимо сделать это немедленно.

Скачать файлы unattend.xml (проверено на наличие вредоносного ПО — отсутствие 100 %)

ВНИМАНИЕ! Мы настоятельно не рекомендуем загружать и копировать unattend.xml в соответствующий системный каталог Windows. VMware, как правило, не выпускает файлы VMWare Workstation Player XML для загрузки, поскольку они входят в состав установщика программного обеспечения. Задача установщика заключается в том, чтобы обеспечить выполнение всех надлежащих проверок перед установкой и размещением unattend.xml и всех других файлов XML для VMWare Workstation Player. Неправильно установленный файл XML может нарушить стабильность работы системы и привести к тому, что программа или операционная система полностью перестанут работать. Действовать с осторожностью.

Файлы, относящиеся к unattend.xml

Файлы XML, относящиеся к unattend.xml

Имя файла Описание Программа (версия) Размер файла (байты) Расположение файла
update.xml Extensible Markup Language VMWare Workstation Player 15.5.1 993 C:UsersTesterAppDataLocalMicrosoftOneDriv…
appxmanifest.xml Extensible Markup Language VMWare Workstation Player 15.5.1 1266 C:Program FilesWindowsAppsMicrosoft.VCLibs.1…
appxmanifest.xml Extensible Markup Language VMWare Workstation Player 15.5.1 820 C:Program FilesWindowsAppsMicrosoft.GetHelp_…
ovftool-hw11-config-op… Extensible Markup Language VMWare Workstation Player 15.5.1 1030592 C:Program Files (x86)VMwareVMware PlayerOVF…
BuildInfo.xml Extensible Markup Language VMWare Workstation Player 15.5.1 372 C:Program FilesWindowsAppsMicrosoft.GetHelp_…

Другие файлы, связанные с unattend.xml

Имя файла Описание Программа (версия) Размер файла (байты) Расположение файла
setuperr.log Log VMware Workstation 12.5.5 11373 C:WindowsLogsDPX
setupact.log Log VMware Workstation 12.5.5 14252 C:WindowsSystem32SysprepPanther
SA.DAT Game Data VMware Workstation 12.5.5 6 C:WINDOWSTasks
netpacer.PNF Precompiled INF VMware Workstation 12.5.5 7484 C:WindowsSystem32DriverStoreFileRepository…
netserv.PNF Precompiled INF VMware Workstation 12.5.5 5348 C:WindowsSystem32DriverStoreFileRepository…

Вы скачиваете пробное программное обеспечение. Для разблокировки всех функций программного обеспечения требуется покупка годичной подписки, стоимость которой оставляет 39,95 долл. США. Подписка автоматически возобновляется в конце срока (Подробнее). Нажимая кнопку «Начать загрузку» и устанавливая «Программное обеспечение», я подтверждаю, что я прочитал (-а) и принимаю Лицензионное соглашение и Политику конфиденциальности компании Solvusoft.

Источник

When you’re deploying Windows 10 in a customized environment, you specify the selective settings in an answer file. For those, who are not familiar with an answer file, here is what it is. An answer file is an XML file, usually contains the customized settings that would be used by Windows Setup during the installation. Most of the IT professionals like to deploy custom settings in their workplace/organization and it raises the need of answer file. It is located as unattend.xml in Panther folder under windows directory (%windir% or C:Windows). Extended information on answer file is available in this documentation.

So if there are some incorrect entries in the answer file, Windows Setup won’t be able to process the file. In such a condition, following error will come into play:

Page Contents

Windows could not parse or process the unattend answer file for pass [specialize]. A component or setting specified in the answer file does not exist.

Windows Could Not Parse Or Process The Unattend Answer File For Windows 10

So if you’re facing this issue while deploying Windows 10, and if you know how to correct answer file errors, simply recheck the unattended.xml file and remove the extra code that is not applicable to your environment or causing the issue. Here, note the in some cases, Windows displays the components which is causing error so it would be easy for you to rectify the code. But if you’re an end user with not enough knowledge about modifying answer file and you incidentally started facing this problem, here is how to correct it.

FIX : Windows Could Not Parse Or Process The Unattend Answer File For Windows 10

Windows usually checks for unattend.xml file in %windir%/Panther. By following the steps mentioned below, you’ll be able to allow Windows to skip looking for unattend answer file. Once it skipped answer file verification, it would be able to boot without the above mentioned error. Here’s how to make this possible:

1. When this error appears, simply press Shift + F10 to bring Command Prompt.

2. Now in the Command Prompt window, type regedit.exe command to open Registry Editor. In the Registry Editor window, navigate to following key:

HKEY_LOCAL_MACHINESYSTEMSetupStatusChildCompletion

Windows Could Not Parse Or Process The Unattend Answer File For Windows 10

3. In the right pane of ChildCompletion folder, look for setup.exe named registry DWORD (REG_DWORD), the value for which might be corresponding to 1. Double click on that same DWORD and change its Value data to 3 (refer below screenshot). Click OK. Close Registry Editor and Continue to your existing operating system and reboot then.

Windows Could Not Parse Or Process The Unattend Answer File For Windows 10

After restarting your system, Windows will be able to skip checking for unattend answer file and you’ll be able to boot fine, without the error.

That’s it!

READ THESE ARTICLES NEXT

  • Fix: Getting Windows Ready Stuck in Windows 11/10
  • Fix: PC won’t boot after Windows 11 update
  • How to delete Windows.old Folder in Windows 11/10
  • How to boot into Safe Mode on Windows 11
  • How to downgrade from Windows 11 to Windows 10
  • How to reset Windows 11 without losing your data
  • Fix: Could not find the recovery environment in Windows 11/10
  • How to restore your Windows 11 to an earlier date
  • How to create a System Restore point in Windows 11
  • How To Downgrade Windows 10 After 10 Days
Источник

I am unable to apply offline updates to the Windows 10 IoT 1607 x86 fro

2018-07 Cumulative Update for Windows 10 Version 1607 for x86-based Systems (KB4346877) Windows 10,Windows 10 LTSB Updates 7/30/2018

Anything after this update i.e after 7/30/2018, I get the above mentioned error.

I have applied the servicing stack update which is: (KB4132216). I have checksummed and checked the image, it is a stock image that comes from Microsoft

An excerpt from the DISM log is as follows:

2018-11-21 09:35:20, Error                 CBS    Failed to perform operation.  [HRESULT = 0x800f0922 — CBS_E_INSTALLERS_FAILED]
2018-11-21 09:35:20, Info                  CBS    Session: 6800_66313875 finalized. Reboot required: no [HRESULT = 0x800f0922 — CBS_E_INSTALLERS_FAILED]
2018-11-21 09:35:20, Error                 DISM   DISM Package Manager: PID=6800 TID=4748 Failed finalizing changes. — CDISMPackageManager::Internal_Finalize(hr:0x800f0922)
2018-11-21 09:35:22, Info                  CBS    Unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Mount/Windows/System32/config/SOFTWARE
2018-11-21 09:35:22, Info                  CBS    Failed to unload offline registry: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Mount/Windows/System32/config/SOFTWARE,
the client may still need it open. [HRESULT = 0x80070005 — E_ACCESSDENIED]
2018-11-21 09:35:22, Info                  CBS    Unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Mount/Windows/System32/config/SYSTEM
2018-11-21 09:35:22, Info                  CBS    Failed to unload offline registry: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Mount/Windows/System32/config/SYSTEM,
the client may still need it open. [HRESULT = 0x80070005 — E_ACCESSDENIED]
2018-11-21 09:35:22, Info                  CBS    Unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Mount/Windows/System32/config/SECURITY
2018-11-21 09:35:22, Info                  CBS    Failed to unload offline registry: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Mount/Windows/System32/config/SECURITY,
the client may still need it open. [HRESULT = 0x80070005 — E_ACCESSDENIED]
2018-11-21 09:35:22, Info                  CBS    Unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Mount/Windows/System32/config/SAM
2018-11-21 09:35:22, Info                  CBS    Failed to unload offline registry: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Mount/Windows/System32/config/SAM,
the client may still need it open. [HRESULT = 0x80070005 — E_ACCESSDENIED]
2018-11-21 09:35:22, Info                  CBS    Unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Mount/Windows/System32/config/COMPONENTS
2018-11-21 09:35:22, Info                  CBS    Failed to unload offline registry: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Mount/Windows/System32/config/COMPONENTS,
the client may still need it open. [HRESULT = 0x80070005 — E_ACCESSDENIED]
2018-11-21 09:35:22, Info                  CBS    Unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Mount/Windows/System32/config/DRIVERS
2018-11-21 09:35:22, Info                  CBS    Failed to unload offline registry: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Mount/Windows/System32/config/DRIVERS,
the client may still need it open. [HRESULT = 0x80070005 — E_ACCESSDENIED]
2018-11-21 09:35:22, Info                  CBS    Unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Mount/Windows/System32/config/DEFAULT
2018-11-21 09:35:22, Info                  CBS    Failed to unload offline registry: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Mount/Windows/System32/config/DEFAULT,
the client may still need it open. [HRESULT = 0x80070005 — E_ACCESSDENIED]
2018-11-21 09:35:22, Info                  CBS    Unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Mount/Users/Default/ntuser.dat
2018-11-21 09:35:22, Info                  CBS    Unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Mount/Windows/system32/smi/store/Machine/schema.dat
2018-11-21 09:35:23, Error                 DISM   DISM Package Manager: PID=6800 TID=4748 Failed processing package changes with session options — CDISMPackageManager::ProcessChangesWithOptions(hr:0x800f0922)
2018-11-21 09:35:23, Error                 DISM   DISM Package Manager: PID=6800 TID=4748 Failed to process package changes in unattend file. — CPackageManagerUnattendHandler::Internal_ProcessChanges(hr:0x800f0922)
2018-11-21 09:35:23, Error                 DISM   DISM Package Manager: PID=6800 TID=4748 Failed to process package changes. — CPackageManagerUnattendHandler::Apply(hr:0x800f0922)
2018-11-21 09:35:23, Error                 DISM   DISM Package Manager: PID=6800 TID=4748 Failed to Apply the unattend. — CDISMPackageManager::Apply(hr:0x800f0922)
2018-11-21 09:35:23, Error                 DISM   DISM Unattend Manager: PID=6800 TID=4748 «Error applying unattend for provider: DISM Package Manager» — CUnattendManager::Apply(hr:0x800f0922)
2018-11-21 09:35:23, Error                 DISM   DISM Package Manager: PID=6800 TID=4748 Failed applying the unattend file from the MSU package. — CMsuPackage::ApplyMsuUnattend(hr:0x800f0922)
2018-11-21 09:35:23, Error                 DISM   DISM Package Manager: PID=6800 TID=4748 Failed to apply the MSU unattend file to the image. — CMsuPackage::Install(hr:0x800f0922)
2018-11-21 09:35:23, Info                  DISM   DISM Package Manager: PID=6800 TID=4748 Loaded servicing stack for offline use only. — CDISMPackageManager::RefreshInstanceAndLock
2018-11-21 09:35:23, Info                  CBS    Offline image is writable
2018-11-21 09:35:23, Info                  CBS    Loading offline registry hive: SOFTWARE, into registry key ‘{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Mount/Windows/System32/config/SOFTWARE’
from path ‘\?C:MountWindowsSystem32configSOFTWARE’.
2018-11-21 09:35:23, Info                  CBS    Loading offline registry hive: SYSTEM, into registry key ‘{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Mount/Windows/System32/config/SYSTEM’
from path ‘\?C:MountWindowsSystem32configSYSTEM’.
2018-11-21 09:35:23, Info                  CBS    Loading offline registry hive: SECURITY, into registry key ‘{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Mount/Windows/System32/config/SECURITY’
from path ‘\?C:MountWindowsSystem32configSECURITY’.
2018-11-21 09:35:23, Info                  CBS    Loading offline registry hive: SAM, into registry key ‘{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Mount/Windows/System32/config/SAM’
from path ‘\?C:MountWindowsSystem32configSAM’.
2018-11-21 09:35:23, Info                  CBS    Loading offline registry hive: COMPONENTS, into registry key ‘{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Mount/Windows/System32/config/COMPONENTS’
from path ‘\?C:MountWindowsSystem32configCOMPONENTS’.
2018-11-21 09:35:23, Info                  CBS    Loading offline registry hive: DRIVERS, into registry key ‘{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Mount/Windows/System32/config/DRIVERS’
from path ‘\?C:MountWindowsSystem32configDRIVERS’.
2018-11-21 09:35:23, Info                  CBS    Loading offline registry hive: DEFAULT, into registry key ‘{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Mount/Windows/System32/config/DEFAULT’
from path ‘\?C:MountWindowsSystem32configDEFAULT’.
2018-11-21 09:35:23, Info                  CBS    Loading offline registry hive: ntuser.dat, into registry key ‘{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Mount/Users/Default/ntuser.dat’
from path ‘\?C:MountUsersDefaultntuser.dat’.
2018-11-21 09:35:23, Info                  CBS    Loading offline registry hive: schema.dat, into registry key ‘{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Mount/Windows/system32/smi/store/Machine/schema.dat’
from path ‘\?C:MountWindowssystem32smistoreMachineschema.dat’.
2018-11-21 09:35:23, Info                  CSI    00001913 CSI Store 205369904 initialized
2018-11-21 09:35:23, Info                  CBS    Session: 6800_66858718 initialized by client DISM Package Manager Provider, external staging directory: (null),
external registry directory: (null
2018-11-21 09:35:23, Info                  DISM   DISM Package Manager: PID=6800 TID=4748 Loaded servicing stack for offline use only. — CDISMPackageManager::RefreshInstanceAndLock
2018-11-21 09:35:23, Info                  DISM   DISM Package Manager: PID=6800 TID=4748 Loaded servicing stack for online use only. — CDISMPackageManager::RefreshInstanceAndLock
2018-11-21 09:35:23, Error                 DISM   DISM Package Manager: PID=6800 TID=4748 Failed while processing command add-package. — CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800f0922)
2018-11-21 09:35:23, Error                 DISM   DISM.EXE: DISM Package Manager processed the command line but failed. HRESULT=800F0922
2018-11-21 09:35:23, Info                  DISM   DISM Provider Store: PID=6800 TID=4748 Found the OSServices.  Waiting to finalize it until all other providers
are unloaded. — CDISMProviderStore::Final_OnDisconnect
2018-11-21 09:35:23, Info                  DISM   DISM Provider Store: PID=6800 TID=4748 Found the OSServices.  Waiting to finalize it until all other providers
are unloaded. — CDISMProviderStore::Final_OnDisconnect
2018-11-21 09:35:23, Info                  DISM   DISM Provider Store: PID=6800 TID=4748 Found the PE Provider.  Waiting to finalize it until all other providers
are unloaded. — CDISMProviderStore::Final_OnDisconnect
2018-11-21 09:35:23, Info                  DISM   DISM Provider Store: PID=6800 TID=4748 Finalizing the servicing provider(DISM Package Manager) — CDISMProviderStore::Internal_DisconnectProvider
2018-11-21 09:35:23, Info                  CBS    Unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Mount/Windows/System32/config/SOFTWARE
2018-11-21 09:35:23, Info                  CBS    Failed to unload offline registry: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Mount/Windows/System32/config/SOFTWARE,
the client may still need it open. [HRESULT = 0x80070005 — E_ACCESSDENIED]
2018-11-21 09:35:23, Info                  CBS    Unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Mount/Windows/System32/config/SYSTEM
2018-11-21 09:35:23, Info                  CBS    Failed to unload offline registry: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Mount/Windows/System32/config/SYSTEM,
the client may still need it open. [HRESULT = 0x80070005 — E_ACCESSDENIED]
2018-11-21 09:35:23, Info                  CBS    Unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Mount/Windows/System32/config/SECURITY
2018-11-21 09:35:23, Info                  CBS    Failed to unload offline registry: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Mount/Windows/System32/config/SECURITY,
the client may still need it open. [HRESULT = 0x80070005 — E_ACCESSDENIED]
2018-11-21 09:35:23, Info                  CBS    Unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Mount/Windows/System32/config/SAM
2018-11-21 09:35:23, Info                  CBS    Failed to unload offline registry: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Mount/Windows/System32/config/SAM,
the client may still need it open. [HRESULT = 0x80070005 — E_ACCESSDENIED]
2018-11-21 09:35:23, Info                  CBS    Unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Mount/Windows/System32/config/COMPONENTS
2018-11-21 09:35:23, Info                  CBS    Failed to unload offline registry: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Mount/Windows/System32/config/COMPONENTS,
the client may still need it open. [HRESULT = 0x80070005 — E_ACCESSDENIED]
2018-11-21 09:35:23, Info                  CBS    Unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Mount/Windows/System32/config/DRIVERS
2018-11-21 09:35:23, Info                  CBS    Failed to unload offline registry: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Mount/Windows/System32/config/DRIVERS,
the client may still need it open. [HRESULT = 0x80070005 — E_ACCESSDENIED]
2018-11-21 09:35:23, Info                  CBS    Unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Mount/Windows/System32/config/DEFAULT
2018-11-21 09:35:23, Info                  CBS    Failed to unload offline registry: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Mount/Windows/System32/config/DEFAULT,
the client may still need it open. [HRESULT = 0x80070005 — E_ACCESSDENIED]
2018-11-21 09:35:23, Info                  CBS    Unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Mount/Users/Default/ntuser.dat
2018-11-21 09:35:23, Info                  CBS    Unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Mount/Windows/system32/smi/store/Machine/schema.dat
2018-11-21 09:35:23, Info                  DISM   DISM Package Manager: PID=6800 TID=4748 Finalizing CBS core. — CDISMPackageManager::Finalize
2018-11-21 09:35:23, Info                  CBS    CbsCoreFinalize: ManifestCacheFinalize
2018-11-21 09:35:23, Info                  CBS    CbsCoreFinalize: ExecutionEngineFinalize
2018-11-21 09:35:23, Info                  CBS    CbsCoreFinalize: ComponentAnalyzerFinalize
2018-11-21 09:35:23, Info                  CBS    CbsCoreFinalize: PackageTrackerFinalize
2018-11-21 09:35:23, Info                  CBS    CbsCoreFinalize: CoreResourcesUnload
2018-11-21 09:35:23, Info                  CBS    CbsCoreFinalize: SessionManagerFinalize
2018-11-21 09:35:23, Info                  CBS    CbsCoreFinalize: CapabilityManagerFinalize
2018-11-21 09:35:23, Info                  CBS    CbsCoreFinalize: GetPublicObjectMonitor::Audit
2018-11-21 09:35:23, Info                  CBS    CbsCoreFinalize: PublicObjectMonitorFinalize
2018-11-21 09:35:23, Info                  CBS    CbsCoreFinalize: Enter vCoreInitializeLock
2018-11-21 09:35:23, Info                  CBS    CbsCoreFinalize: WcpUnload
2018-11-21 09:35:23, Info                  CBS    CbsCoreFinalize: DrupUnload
2018-11-21 09:35:23, Info                  CBS    CbsCoreFinalize: CfgMgr32Unload
2018-11-21 09:35:23, Info                  CBS    CbsCoreFinalize: DpxUnload
2018-11-21 09:35:23, Info                  CBS    CbsCoreFinalize: SrUnload
2018-11-21 09:35:23, Info                  CBS    CbsCoreFinalize: CbsEsdUnload
2018-11-21 09:35:23, Info                  CBS    CbsCoreFinalize: CbsTraceInfoUninitialize
2018-11-21 09:35:23, Info                  CBS    CbsCoreFinalize: CbsEventUnregister
2018-11-21 09:35:23, Info                  CBS    CbsCoreFinalize: AppContainerUnload
2018-11-21 09:35:23, Info                  CBS    CbsCoreFinalize: WdsUnload, logging from cbscore will end.
2018-11-21 09:35:23, Info                  DISM   DISM Provider Store: PID=6800 TID=4748 Disconnecting Provider: DISM Package Manager — CDISMProviderStore::Internal_DisconnectProvider
2018-11-21 09:35:41, Info                  DISM   DISM Provider Store: PID=6800 TID=4748 Finalizing the servicing provider(MsiManager) — CDISMProviderStore::Internal_DisconnectProvider
2018-11-21 09:35:41, Info                  DISM   DISM Provider Store: PID=6800 TID=4748 Disconnecting Provider: MsiManager — CDISMProviderStore::Internal_DisconnectProvider
2018-11-21 09:35:41, Info                  DISM   DISM Provider Store: PID=6800 TID=4748 Finalizing the servicing provider(IntlManager) — CDISMProviderStore::Internal_DisconnectProvider
2018-11-21 09:35:41, Info                  DISM   DISM Provider Store: PID=6800 TID=4748 Disconnecting Provider: IntlManager — CDISMProviderStore::Internal_DisconnectProvider
2018-11-21 09:35:41, Info                  DISM   DISM Provider Store: PID=6800 TID=4748 Finalizing the servicing provider(IBSManager) — CDISMProviderStore::Internal_DisconnectProvider
2018-11-21 09:35:41, Info                  DISM   DISM Provider Store: PID=6800 TID=4748 Disconnecting Provider: IBSManager — CDISMProviderStore::Internal_DisconnectProvider
2018-11-21 09:35:41, Info                  DISM   DISM Provider Store: PID=6800 TID=4748 Finalizing the servicing provider(DriverManager) — CDISMProviderStore::Internal_DisconnectProvider
2018-11-21 09:35:41, Info                  DISM   DISM Provider Store: PID=6800 TID=4748 Disconnecting Provider: DriverManager — CDISMProviderStore::Internal_DisconnectProvider
2018-11-21 09:35:41, Info                  DISM   DISM Provider Store: PID=6800 TID=4748 Finalizing the servicing provider(DISM Unattend Manager) — CDISMProviderStore::Internal_DisconnectProvider
2018-11-21 09:35:41, Info                  DISM   DISM Provider Store: PID=6800 TID=4748 Disconnecting Provider: DISM Unattend Manager — CDISMProviderStore::Internal_DisconnectProvider
2018-11-21 09:35:41, Info                  DISM   DISM Provider Store: PID=6800 TID=4748 Finalizing the servicing provider(SmiManager) — CDISMProviderStore::Internal_DisconnectProvider
2018-11-21 09:35:41, Info                  DISM   DISM Provider Store: PID=6800 TID=4748 Disconnecting Provider: SmiManager — CDISMProviderStore::Internal_DisconnectProvider
2018-11-21 09:35:41, Info                  DISM   DISM Provider Store: PID=6800 TID=4748 Finalizing the servicing provider(AppxManager) — CDISMProviderStore::Internal_DisconnectProvider
2018-11-21 09:35:41, Info                  DISM   DISM Provider Store: PID=6800 TID=4748 Disconnecting Provider: AppxManager — CDISMProviderStore::Internal_DisconnectProvider
2018-11-21 09:35:41, Info                  DISM   DISM Provider Store: PID=6800 TID=4748 Finalizing the servicing provider(ProvManager) — CDISMProviderStore::Internal_DisconnectProvider
2018-11-21 09:35:41, Info                  DISM   DISM Provider Store: PID=6800 TID=4748 Disconnecting Provider: ProvManager — CDISMProviderStore::Internal_DisconnectProvider
2018-11-21 09:35:41, Info                  DISM   DISM Provider Store: PID=6800 TID=4748 Finalizing the servicing provider(AssocManager) — CDISMProviderStore::Internal_DisconnectProvider
2018-11-21 09:35:41, Info                  DISM   DISM Provider Store: PID=6800 TID=4748 Disconnecting Provider: AssocManager — CDISMProviderStore::Internal_DisconnectProvider
2018-11-21 09:35:41, Info                  DISM   DISM Provider Store: PID=6800 TID=4748 Finalizing the servicing provider(GenericManager) — CDISMProviderStore::Internal_DisconnectProvider
2018-11-21 09:35:41, Info                  DISM   DISM Provider Store: PID=6800 TID=4748 Disconnecting Provider: GenericManager — CDISMProviderStore::Internal_DisconnectProvider
2018-11-21 09:35:41, Info                  DISM   DISM Provider Store: PID=6800 TID=4748 Finalizing the servicing provider(OfflineSetupManager) — CDISMProviderStore::Internal_DisconnectProvider
2018-11-21 09:35:41, Info                  DISM   DISM Provider Store: PID=6800 TID=4748 Disconnecting Provider: OfflineSetupManager — CDISMProviderStore::Internal_DisconnectProvider
2018-11-21 09:35:41, Info                  DISM   DISM Provider Store: PID=6800 TID=4748 Finalizing the servicing provider(Edition Manager) — CDISMProviderStore::Internal_DisconnectProvider
2018-11-21 09:35:41, Info                  DISM   DISM Provider Store: PID=6800 TID=4748 Disconnecting Provider: Edition Manager — CDISMProviderStore::Internal_DisconnectProvider
2018-11-21 09:35:41, Info                  DISM   DISM Provider Store: PID=6800 TID=4748 Releasing the local reference to OSServices. — CDISMProviderStore::Internal_DisconnectProvider
2018-11-21 09:35:41, Info                  DISM   DISM Provider Store: PID=6800 TID=4748 Disconnecting Provider: OSServices — CDISMProviderStore::Internal_DisconnectProvider
2018-11-21 09:35:41, Info                  DISM   DISM OS Provider: PID=6800 TID=4748 Successfully unloaded all registry hives. — CDISMOSServiceManager::Final_OnDisconnect
2018-11-21 09:35:41, Info                  DISM   DISM Provider Store: PID=6800 TID=4748 Releasing the local reference to DISMLogger.  Stop logging. — CDISMProviderStore::Internal_DisconnectProvider
2018-11-21 09:35:41, Info                  DISM   DISM Manager: PID=2684 TID=6064 Closing session event handle 0x2bc — CDISMManager::CloseImageSession
2018-11-21 09:35:41, Info                  DISM   DISM.EXE: Image session has been closed. Reboot required=no.
2018-11-21 09:35:41, Info                  DISM   DISM.EXE:

2018-11-21 09:35:41, Info                  DISM   DISM.EXE: <—— Ending Dism.exe session ——>
2018-11-21 09:35:41, Info                  DISM   DISM.EXE:

2018-11-21 09:35:41, Info                  DISM   DISM Provider Store: PID=2684 TID=6064 Found the OSServices.  Waiting to finalize it until all other providers
are unloaded. — CDISMProviderStore::Final_OnDisconnect
2018-11-21 09:35:41, Info                  DISM   DISM Provider Store: PID=2684 TID=6064 Disconnecting Provider: FolderManager — CDISMProviderStore::Internal_DisconnectProvider
2018-11-21 09:35:41, Info                  DISM   DISM Provider Store: PID=2684 TID=6064 Disconnecting Provider: WimManager — CDISMProviderStore::Internal_DisconnectProvider
2018-11-21 09:35:41, Info                  DISM   DISM Provider Store: PID=2684 TID=6064 Disconnecting Provider: VHDManager — CDISMProviderStore::Internal_DisconnectProvider
2018-11-21 09:35:41, Info                  DISM   DISM Provider Store: PID=2684 TID=6064 Disconnecting Provider: GenericImagingManager — CDISMProviderStore::Internal_DisconnectProvider
2018-11-21 09:35:41, Info                  DISM   DISM Provider Store: PID=2684 TID=6064 Disconnecting Provider: Compatibility Manager — CDISMProviderStore::Internal_DisconnectProvider
2018-11-21 09:35:41, Info                  DISM   DISM Provider Store: PID=2684 TID=6064 Disconnecting Provider: FfuManager — CDISMProviderStore::Internal_DisconnectProvider
2018-11-21 09:35:41, Info                  DISM   DISM Provider Store: PID=2684 TID=6064 Disconnecting Provider: SiloedPackageManager — CDISMProviderStore::Internal_DisconnectProvider
2018-11-21 09:35:41, Info                  DISM   DISM Provider Store: PID=2684 TID=6064 Releasing the local reference to DISMLogger.  Stop logging. — CDISMProviderStore::Internal_DisconnectProvider

Источник

I’m trying to set up automated installations of Windows Server 2008 x64.

I have it working using a DVD and autounattend.xml on a USB key, but now I want to make it work over PXE so I don’t have to put the DVD in the drive on some overseas servers.

I’m trying this method Walkthrough: Deploy an Image by using PXE, which boots WinPE over PXE, except at the last stage I’m using pxeboot.com rather than wdsnbp.com because I don’t have a Windows Deployment Server. That part is working fine.

The problem I’m having is trying to get WinPE to start an installation. Wpeinit Command-Line Options documentation says I can do wpeinit /unattend=pathtounattend.xml, but that fails without printing anything to the console, and there’s no obvious error messages in the log file either.

  • unattend.xml lives on a network share.
  • I’ve tried both wpeinit -unattend:\servershareunattend.xml and net use u: \servershare followed by wpeinit -unattend:u:unattend.xml, but neither works, neither does copying it to a local drive (e.g. X:) and using that path instead.
  • WinPE-XML-Package and WinPE-HTA-Package were both added to the winpe.wim file that’s being served over TFTP. I’m not sure if they are required, but one tutorial suggested adding them, so I did.
  • The wpeinit logs (below) mention it found HTA but not XML for some reason. Should I expect to see it too?
  • Networking is up, but I had to run wpeutil InitializeNetwork to make it work.
  • WinPE can see my C:, which is a previous Server 2008 install.
  • I haven’t customized winpeshl.ini or startnet.cmd.
  • My test system is a Dell Optiplex 755 with Intel Core2 Duo and an Intel 82566DM network card.
  • The difference between my working USB key autounattend.xml and my SMB unattend.xml is the added Windows-Setup|ImageInstall|OSImage|InstallFrom=\server IPshareinstall.wim, which I believe is needed if I want it to work without the Server 2008 DVD.
  • The SMB server is a Linux Samba that will allow anonymous access without a password. No credentials have been specified in unattend.xml.

Any ideas what I’m doing wrong?

Thanks

wpeinit.log after automatic wpeinit’s first pass

Info      No unattend file was found; WPEINIT is using default settings to initialize WinPE
Info      Spent 6115ms initializing removable media before unattend search
Info      ==== Initializing Display Settings ====
Info      No display settings specified
Info      STATUS: SUCCESS (0x00000001)
Info      ==== Initializing Computer Name ====
Info      Generating a random computer name
Info      STATUS: SUCCESS (0x00000000)
Info      ==== Initializing Virtual Memory Paging File ====
Info      No WinPE page file setting specified
Info      STATUS: SUCCESS (0x00000001)
Info      ==== Initializing Optional Components ====
Info      WinPE optional component 'Microsoft-WinPE-HTA' is present
Info      STATUS: SUCCESS (0x00000000)
Info      ==== Initializing Network Access and Applying Configuration ====
Info      No EnableNetwork unattend setting was specified; the default action for this context is to enable networking support.
Info      Service dhcp stop: 0x00000000
Info      Service lmhosts stop: 0x00000000
Info      Service bfe stop: 0x00000000
Info      Service ikeext stop: 0x00000000
Info      Service mpssvc stop: 0x00000000
Info      Spent 125ms initializing security templates; status 0x00000000
Info      Install MS_MSCLIENT: 0x0004a020
Info      Install MS_NETBIOS: 0x0004a020
Info      Install MS_SMB: 0x0004a020
Info      Install MS_TCPIP6: 0x0004a020
Info      Install MS_TCPIP: 0x0004a020
Info      Spent 5288ms installing network components
Info      iSCSI: iBFT ACPI Table is not available on this system
Info      Installing device pciven_8086&dev_10bd X:WindowsINFnete1e3e.inf succeeded
Info      Spent 1295ms installing network drivers
Info      QueryAdapterStatus: no adapters operational.
Info      Spent 0ms confirming network initialization; status 0x003d0001
Info      STATUS: SUCCESS (0x003d0001)
Info      ==== Applying Firewall Settings ====
Info      STATUS: SUCCESS (0x00000001)
Info      ==== Executing Synchronous User-Provided Commands ====
Info      STATUS: SUCCESS (0x00000001)
Info      ==== Executing Asynchronous User-Provided Commands ====
Info      STATUS: SUCCESS (0x00000001)
Info      ==== Applying Shutdown Settings ====
Info      No shutdown setting was specified
Info      STATUS: SUCCESS (0x00000001)

lines added to wpeinit.log after running wpeinit /unattend=u:unattend.xml

Info      WPEINIT is processing the unattend file [u:unattend.xml]
Info      ==== Initializing Display Settings ====
Info      No display settings specified
Info      STATUS: SUCCESS (0x00000001)
Info      ==== Initializing Computer Name ====
Info      Generating a random computer name
Info      STATUS: SUCCESS (0x00000000)
Info      ==== Initializing Virtual Memory Paging File ====
Info      No WinPE page file setting specified
Info      STATUS: SUCCESS (0x00000001)
Info      ==== Initializing Optional Components ====
Info      WinPE optional component 'Microsoft-WinPE-HTA' is present
Info      STATUS: SUCCESS (0x00000000)
Info      ==== Initializing Network Access and Applying Configuration ====
Info      No EnableNetwork unattend setting was specified; the default action for this context is to enable networking support.
Info      Found an smb connection.
Info      Networking is currently in use and will not be restarted.
Info      QueryAdapterStatus: found operational adapter with DHCP address assigned.
Info      Spent 0ms confirming network initialization; status 0x00000000
Info      STATUS: SUCCESS (0x00000000)
Info      ==== Applying Firewall Settings ====
Info      STATUS: SUCCESS (0x00000001)
Info      ==== Executing Synchronous User-Provided Commands ====
Info      STATUS: SUCCESS (0x00000001)
Info      ==== Executing Asynchronous User-Provided Commands ====
Info      STATUS: SUCCESS (0x00000001)
Info      ==== Applying Shutdown Settings ====
Info      No shutdown setting was specified
Info      STATUS: SUCCESS (0x00000001)
Источник

Понравилась статья? Поделить с друзьями:

Не пропустите эти материалы по теме:

  • Яндекс еда ошибка привязки карты
  • Ошибка unknown software exception 0xc0000094
  • Ошибка unarc isdone dll 100
  • Ошибка unexpected store extension
  • Ошибка unknown software exception 0x40000015

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

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