Win 10 DISM error 0x800f081f / Source opções

Navegue suas respostas
2

Eu notei esse problema quando encontrei 2502 e 2503 erros ao tentar instalar um SDK. Acredito que tenho recebido os 250 [2 | 3] erros desde a atualização do windows 8.1 para o windows 10.

Corri dism /Online /Cleanup-image /Scanhealth que respondeu The component store is repairable. , por isso corri dism /Online /Cleanup-image /Restorehealth , o que resultou no Error: 0x800f081f .

Esclarecimento 15/11/2015 6:45 MST

Alguém pode confirmar que esta sintaxe, se bem sucedida, está restaurando o arquivo quebrado em questão a partir de uma loja online na nuvem?

Não é a opção /Online que significa que o Windows está sendo executado a partir da unidade que está sendo testada.

Observe este post do funcionário da Microsoft, joscon, onde ele diz:

BOGUS! Não posso postar mais de 2 links! http: // blogs. technet. com /b/joscon/archive/2012/09/26/fixing-component-store-corruption-in-windows-8-and-windows-server-2012.aspx

/RestoreHealth: This checks for component store corruption, records the corruption to C:\Windows\Logs\CBS\CBS.log and FIXES the corruption using Windows Update. This operation takes ~10-15mins or more depending on the level of corruption.

Ele quis dizer que o Windows Update aqui significa o serviço na nuvem ms? Ou um cache no windows.

De qualquer forma, o título da minha pergunta agora deve ser "CSI Payload Corupt"

Esclarecimento final 15/11/2015 6:45 MST

Informações adicionais 15/11/2015 17:45 MST
Em outro tópico de suporte notei conselhos para executar chkdsk /r /f depois de executar chkdsk eu corri outro sfc /scannow

De cbs.log; 

0000561e [SR] Could not reproject corrupted file [ml:64{32},l:62{31}]"\??\C:\WINDOWS\SysWOW64\drivers"\[l:24{12}]"gmreadme.txt"; source file in store is also corrupted

De dism.log; 

(p) CSI Payload Corrupt         wow64_multimedia-generalmididata_31bf3856ad364e35_10.0.10240.16384_none_9b1267cc25712003\gmreadme.txt

Eu olhei para o arquivo. É 1kb aparentemente contendo apenas 'null's Posso deletar? Também encontrei na minha outra máquina. Substituiu-o em má máquina depois de ter permissões. Ainda tem corrupção do arquivo de origem.

Como posso saber quais dependências existem nessa carga? Arquivo. Se não houver nenhum, posso deletá-lo? Ou, de preferência, desinstalá-lo?

Fragmento cbs.log mais longo obtido após as mensagens chkdsk /r /f muitas Overlap: Duplicate ownership for directory e is not owned . 

2015-11-15 13:47:27, Info                  CSI    00004688 [DIRSD OWNER WARNING] Directory [ml:142{71},l:140{70}]"\??\C:\WINDOWS\SysWOW64\WindowsPowerShell\v1.0\Modules\Hyper-V.0.0.0" is not owned but specifies SDDL in component Microsoft.HyperV.PowerShell.Cmdlets.Misc, pA Host= amd64 Guest= x86, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}

2015-11-15 13:47:27, Info                  CSI    00004689@2015/11/15:20:47:27.647 Primitive installers committed for repair
2015-11-15 13:47:27, Info                  CSI    0000468a@2015/11/15:20:47:27.650 Primitive installers committed for repair
2015-11-15 13:47:27, Info                  CSI    0000468b Hashes for file member \SystemRoot\WinSxS\wow64_multimedia-generalmididata_31bf3856ad364e35_10.0.10240.16384_none_9b1267cc25712003\gmreadme.txt do not match actual file [l:24{12}]"gmreadme.txt" :
  Found: {l:32 b:TOu/P+8/JAcp+tWxG7JDl9tWiYdagd/TUHpCOPeWZO0=} Expected: {l:32 b:EL9uFcCMjH9dlrZYureK7YbR3iDwjnhx7vugk5rxGgI=}
2015-11-15 13:47:27, Info                  CSI    0000468c [SR] Cannot repair member file [l:24{12}]"gmreadme.txt" of Multimedia-GeneralMidiData, Version = 10.0.10240.16384, pA Host= amd64 Guest= x86, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2015-11-15 13:47:27, Info                  CSI    0000468d [SR] This component was referenced by [l:312{156}]"Microsoft-Windows-SKU-Foundation-Package-avcore-noindeo-Group-WOW64-avcore-Package~31bf3856ad364e35~amd64~~10.0.10240.16384.ba5b975ab9b4f73b13c1fb12d02ef8f3"
2015-11-15 13:47:27, Info                  CSI    0000468e Hashes for file member \??\C:\WINDOWS\SysWOW64\drivers\gmreadme.txt do not match actual file [l:24{12}]"gmreadme.txt" :
  Found: {l:32 b:TOu/P+8/JAcp+tWxG7JDl9tWiYdagd/TUHpCOPeWZO0=} Expected: {l:32 b:EL9uFcCMjH9dlrZYureK7YbR3iDwjnhx7vugk5rxGgI=}
2015-11-15 13:47:27, Info                  CSI    0000468f Hashes for file member \SystemRoot\WinSxS\wow64_multimedia-generalmididata_31bf3856ad364e35_10.0.10240.16384_none_9b1267cc25712003\gmreadme.txt do not match actual file [l:24{12}]"gmreadme.txt" :
  Found: {l:32 b:TOu/P+8/JAcp+tWxG7JDl9tWiYdagd/TUHpCOPeWZO0=} Expected: {l:32 b:EL9uFcCMjH9dlrZYureK7YbR3iDwjnhx7vugk5rxGgI=}
2015-11-15 13:47:27, Info                  CSI    00004690 [SR] Could not reproject corrupted file [ml:64{32},l:62{31}]"\??\C:\WINDOWS\SysWOW64\drivers"\[l:24{12}]"gmreadme.txt"; source file in store is also corrupted
2015-11-15 13:47:27, Info                  CSI    00004691@2015/11/15:20:47:27.703 Primitive installers committed for repair
2015-11-15 13:47:27, Info                  CSI    00004692@2015/11/15:20:47:27.715 Primitive installers committed for repair
2015-11-15 13:47:27, Info                  CSI    00004693@2015/11/15:20:47:27.727 Primitive installers committed for repair
2015-11-15 13:47:27, Info                  CSI    00004694@2015/11/15:20:47:27.742 Primitive installers committed for repair
2015-11-15 13:47:27, Info                  CSI    00004695 [DIRSD OWNER WARNING] Directory [ml:164{82},l:162{81}]"\??\C:\Program Files (x86)\WindowsPowerShell\Modules\PackageManagement.0.0.0\en" is not owned but specifies SDDL in component Microsoft.PackageManagement.resources, pA Host= amd64 Guest= x86, Culture = [l:10{5}]"en-US", nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}

2015-11-15 13:47:27, Info                  CSI    00004696 Warning - Overlap: Duplicate ownership for directory [l:162{81}]"\??\C:\Program Files (x86)\WindowsPowerShell\Modules\PackageManagement.0.0.0\en" in component Microsoft.PackageManagement.resources, Version = 10.0.10240.16384, pA Host= amd64 Guest= x86, Culture = [l:10{5}]"en-US", nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}

2015-11-15 13:47:27, Info                  CSI    00004697@2015/11/15:20:47:27.758 Primitive installers committed for repair
2015-11-15 13:47:27, Info                  CSI    00004698 [DIRSD OWNER WARNING] Directory [ml:246{123},l:244{122}]"\??\C:\WINDOWS\SysWOW64\WindowsPowerShell\v1.0\Modules\PSDesiredStateConfiguration\DSCResources\MSFT_PackageResource\en-US" is not owned but specifies SDDL in component Microsoft.PowerShell.DSCResources.Resources, pA Host= amd64 Guest= x86, Culture = [l:10{5}]"en-US", nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}

2015-11-15 13:47:27, Info                  CSI    00004699 [DIRSD OWNER WARNING] Directory [ml:246{123},l:244{122}]"\??\C:\WINDOWS\SysWOW64\WindowsPowerShell\v1.0\Modules\PSDesiredStateConfiguration\DSCResources\MSFT_ProcessResource\en-US" is not owned but specifies SDDL in component Microsoft.PowerShell.DSCResources.Resources, pA Host= amd64 Guest= x86, Culture = [l:10{5}]"en-US", nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}

Fim Informações adicionais 15/11/2015 17:45 MST

Informações adicionais 14/11/2015 22:20 MST

Olhando em volta de mais fóruns eu encontrei sugestões para executar chkdsk /r/f depois da inicialização Eu então corri sfc /scannow Eu tentei fazer um pastebin do cbs.log, acho que era grande. Aqui está um trecho que mostra o arquivo gmreadme.txt, bem como apenas alguns dos muitos erros encontrados pelo chkdsk em relação à propriedade duplicada e à não propriedade. Eu também reran dism /OnLine /Cleanup-image /Scanhealth , o que resultou no mesmo erro 0x800f081f . 

2015-11-14 21:38:16, Info                  CSI    00004706@2015/11/15:04:38:16.846 Primitive installers committed for repair
2015-11-14 21:38:16, Info                  CSI    00004707@2015/11/15:04:38:16.858 Primitive installers committed for repair
2015-11-14 21:38:16, Info                  CSI    00004708@2015/11/15:04:38:16.870 Primitive installers committed for repair
2015-11-14 21:38:16, Info                  CSI    00004709 [SR] Verify complete
2015-11-14 21:38:16, Info                  CSI    0000470a [SR] Verifying 100 (0x0000000000000064) components
2015-11-14 21:38:16, Info                  CSI    0000470b [SR] Beginning Verify and Repair transaction
2015-11-14 21:38:21, Info                  CSI    0000470c Hashes for file member \SystemRoot\WinSxS\wow64_multimedia-generalmididata_31bf3856ad364e35_10.0.10240.16384_none_9b1267cc25712003\gmreadme.txt do not match actual file [l:24{12}]"gmreadme.txt" :
  Found: {l:32 b:TOu/P+8/JAcp+tWxG7JDl9tWiYdagd/TUHpCOPeWZO0=} Expected: {l:32 b:EL9uFcCMjH9dlrZYureK7YbR3iDwjnhx7vugk5rxGgI=}
2015-11-14 21:38:21, Info                  CSI    0000470d [SR] Cannot repair member file [l:24{12}]"gmreadme.txt" of Multimedia-GeneralMidiData, Version = 10.0.10240.16384, pA Host= amd64 Guest= x86, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2015-11-14 21:38:23, Info                  CSI    0000470e [DIRSD OWNER WARNING] Directory [ml:174{87},l:172{86}]"\??\C:\WINDOWS\SysWOW64\WindowsPowerShell\v1.0\Modules\Microsoft.PowerShell.ODataUtils" is not owned but specifies SDDL in component Microsoft.PowerShell.ODataUtils, pA Host= amd64 Guest= x86, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}

2015-11-14 21:38:23, Info                  CSI    0000470f [DIRSD OWNER WARNING] Directory [ml:110{55},l:108{54}]"\??\C:\WINDOWS\SysWOW64\WindowsPowerShell\v1.0\Modules" is not owned but specifies SDDL in component Microsoft.PowerShell.ODataUtils, pA Host= amd64 Guest= x86, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}

2015-11-14 21:38:23, Info                  CSI    00004710 [DIRSD OWNER WARNING] Directory [ml:94{47},l:92{46}]"\??\C:\WINDOWS\SysWOW64\WindowsPowerShell\v1.0" is not owned but specifies SDDL in component Microsoft.PowerShell.ODataUtils, pA Host= amd64 Guest= x86, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}

2015-11-14 21:38:23, Info                  CSI    00004711@2015/11/15:04:38:23.366 Primitive installers committed for repair
2015-11-14 21:38:23, Info                  CSI    00004712@2015/11/15:04:38:23.412 Primitive installers committed for repair
2015-11-14 21:38:23, Info                  CSI    00004713@2015/11/15:04:38:23.423 Primitive installers committed for repair
2015-11-14 21:38:23, Info                  CSI    00004714 [DIRSD OWNER WARNING] Directory [ml:178{89},l:176{88}]"\??\C:\WINDOWS\SysWOW64\WindowsPowerShell\v1.0\Modules\PSDesiredStateConfiguration\en-US" is not owned but specifies SDDL in component Microsoft.PowerShell.DSC.Resources, pA Host= amd64 Guest= x86, Culture = [l:10{5}]"en-US", nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}

2015-11-14 21:38:23, Info                  CSI    00004715 Warning - Overlap: Duplicate ownership for directory [l:176{88}]"\??\C:\WINDOWS\SysWOW64\WindowsPowerShell\v1.0\Modules\PSDesiredStateConfiguration\en-US" in component Microsoft.PowerShell.DSC.Resources, Version = 10.0.10240.16384, pA Host= amd64 Guest= x86, Culture = [l:10{5}]"en-US", nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}

2015-11-14 21:38:23, Info                  CSI    00004716@2015/11/15:04:38:23.542 Primitive installers committed for repair
2015-11-14 21:38:23, Info                  CSI    00004717 [DIRSD OWNER WARNING] Directory [ml:132{66},l:130{65}]"\??\C:\Program Files (x86)\WindowsPowerShell\Modules\Pester.3.5" is not owned but specifies SDDL in component Microsoft.PowerShell.Pester, pA Host= amd64 Guest= x86, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}

2015-11-14 21:38:23, Info                  CSI    00004718 [DIRSD OWNER WARNING] Directory [ml:174{87},l:172{86}]"\??\C:\Program Files (x86)\WindowsPowerShell\Modules\Pester.3.5\Functions\Assertions" is not owned but specifies SDDL in component Microsoft.PowerShell.Pester, pA Host= amd64 Guest= x86, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}

Fim da informação adicional 14/11/2015 22:20 MST

Informações adicionais 11/13/2015 7:15 am MST

Eu tenho outro computador com a mesma configuração. As duas máquinas relatam a versão da imagem: 10.0.10240.16384 quando eu executo o dism. Talvez o arquivo esteja disponível na máquina boa se assim for como posso obter o arquivo da máquina boa para a máquina quebrada ?

Parece que apliquei várias atualizações do Windows enquanto esse problema está em andamento. Pergunto por que eles não falham?

Talvez um arquivo de texto leia-me não seja tão importante. Talvez eu deva simplesmente deletar isso? Se sim, como?

Eu criei um .iso com a ferramenta de criação de mídia. Então eu corri dism /Online /Cleanup-image /Restorehealth /Source:esd:e:\sources\install.esd:1 /limitaccess eu tenho os mesmos resultados. Dessa vez, consegui entender um pouco mais os logs para perceber que o arquivo incorreto parece ser gmreadme.txt 

(p) CSI Payload Corrupt         wow64_multimedia-generalmididata_31bf3856ad364e35_10.0.10240.16384_none_9b1267cc25712003\gmreadme.txt
Repair failed: Missing replacement payload.

Parece que esse arquivo não está disponível on-line ou no .iso install.esd para corrigir esse erro. Alguma sugestão sobre o que tentar em seguida?

Aqui é um pastebin de dism.log e aqui é um pastebin de cbs.log

Termine a informação adicional de 11/13/2015 7:15 am MST 

C:\WINDOWS\system32>dism /Online /Cleanup-image /Scanhealth

Deployment Image Servicing and Management tool
Version: 10.0.10240.16384

Image Version: 10.0.10240.16384

[==========================100.0%==========================]
The component store is repairable.
The operation completed successfully.

C:\WINDOWS\system32>dism /Online /Cleanup-image /Restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.10240.16384

Image Version: 10.0.10240.16384

[==========================100.0%==========================]

Error: 0x800f081f

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

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

C:\WINDOWS\system32>

Não sei como saber qual arquivo estava tentando restaurar?

Eu tenho outra máquina na minha LAN que tem a mesma imagem e relatórios No component store corruption detected Posso obter o arquivo fora desta máquina? Ou montá-lo como / Source para Dsim? 

C:\WINDOWS\system32>dism /online /cleanup-image /scanhealth

Deployment Image Servicing and Management tool
Version: 10.0.10240.16384

Image Version: 10.0.10240.16384

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

C:\WINDOWS\system32>

Informações adicionais 11/12/2015 A

Estas seis linhas no dsim.log foram marcadas como erro. Não estou claro em como interpretá-los. 

2015-11-12 02:55:56, Info                  DISM   DISM Provider Store: PID=175148 TID=175124 Getting Provider DISM Package Manager - CDISMProviderStore::GetProvider
2015-11-12 02:55:56, Info                  DISM   DISM Provider Store: PID=175148 TID=175124 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2015-11-12 02:55:56, Info                  DISM   DISM Package Manager: PID=175148 TID=175124 Processing the top level command token(cleanup-image). - CPackageManagerCLIHandler::Private_ValidateCmdLine
2015-11-12 02:55:56, Info                  DISM   DISM Package Manager: PID=175148 TID=175124 Attempting to route to appropriate command handler. - CPackageManagerCLIHandler::ExecuteCmdLine
2015-11-12 02:55:56, Info                  DISM   DISM Package Manager: PID=175148 TID=175124 Routing the command... - CPackageManagerCLIHandler::ExecuteCmdLine
2015-11-12 02:55:56, Info                  DISM   DISM Package Manager: PID=175148 TID=175124 CBS session options=0x48100! - CDISMPackageManager::Internal_Finalize
2015-11-12 03:07:14, Info                  DISM   DISM Package Manager: PID=175148 TID=175128  Error in operation: source for package or file not found, ResolveSource() unsuccessful. (CBS HRESULT=0x800f081f) - CCbsConUIHandler::Error
2015-11-12 03:07:14, Error                 DISM   DISM Package Manager: PID=175148 TID=175124 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x800f081f)
2015-11-12 03:07:14, Error                 DISM   DISM Package Manager: PID=175148 TID=175124 The source files could not be found; their location must be specified using the /source option to restore the feature. - GetCbsErrorMsg
2015-11-12 03:07:14, Error                 DISM   DISM Package Manager: PID=175148 TID=175124 Failed processing package changes with session option CbsSessionOptionRepairStoreCorruption - CDISMPackageManager::RestoreHealth(hr:0x800f081f)
2015-11-12 03:07:14, Error                 DISM   DISM Package Manager: PID=175148 TID=175124 The source files could not be found; their location must be specified using the /source option to restore the feature. - GetCbsErrorMsg
2015-11-12 03:07:14, Error                 DISM   DISM Package Manager: PID=175148 TID=175124 Failed to restore the image health. - CPackageManagerCLIHandler::ProcessCmdLine_CleanupImage(hr:0x800f081f)
2015-11-12 03:07:14, Error                 DISM   DISM Package Manager: PID=175148 TID=175124 Failed while processing command cleanup-image. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800f081f)
2015-11-12 03:07:14, Info                  DISM   DISM Package Manager: PID=175148 TID=175124 Further logs for online package and feature related operations can be found at %WINDIR%\logs\CBS\cbs.log - CPackageManagerCLIHandler::ExecuteCmdLine
2015-11-12 03:07:14, Info                  DISM   DISM Provider Store: PID=175148 TID=175124 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2015-11-12 03:07:14, Info                  DISM   DISM Provider Store: PID=175148 TID=175124 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2015-11-12 03:07:14, Info                  DISM   DISM Provider Store: PID=175148 TID=175124 Found the PE Provider.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2015-11-12 03:07:14, Info                  DISM   DISM Provider Store: PID=175148 TID=175124 Finalizing the servicing provider(DISM Package Manager) - CDISMProviderStore::Internal_DisconnectProvider
2015-11-12 03:07:14, Info                  DISM   DISM Package Manager: PID=175148 TID=175124 Finalizing CBS core. - CDISMPackageManager::Finalize

Informações adicionais 11/12/2015 B 

Checking System Update Readiness.

(p) CSI Payload Corrupt         wow64_multimedia-generalmididata_31bf3856ad364e35_10.0.10240.16384_none_9b1267cc25712003\gmreadme.txt

Summary:
Operation: Detect only 
Operation result: 0x0
Last Successful Step: CSI store detection completes.
Total Detected Corruption:  1
    CBS Manifest Corruption:    0
    CBS Metadata Corruption:    0
    CSI Manifest Corruption:    0
    CSI Metadata Corruption:    0
    CSI Payload Corruption: 1
Total Repaired Corruption:  0
    CBS Manifest Repaired:  0
    CSI Manifest Repaired:  0
    CSI Payload Repaired:   0
    CSI Store Metadata refreshed:   True

Total Operation Time: 702 seconds.
 - CDISMPackageManager::Internal_Finalize
2015-11-12 02:54:14, Info                  DISM   DISM Package Manager: PID=141616 TID=41384  - CDISMPackageManager::Internal_Finalize
2015-11-12 02:54:14, Info                  DISM   DISM Package Manager: PID=141616 TID=41384 <----- Ending corruption detect/repair info -----> - CDISMPackageManager::Internal_Finalize
2015-11-12 02:54:14, Info                  DISM   DISM Package Manager: PID=141616 TID=41384  - CDISMPackageManager::Internal_Finalize
2015-11-12 02:54:14, Info                  DISM   DISM Package Manager: PID=141616 TID=41384 DISM has detected a DISM component change. Requesting a shutdown. - CDISMPackageManager::Internal_Finalize
2015-11-12 02:54:14, Info                  DISM   DISM Image Session: PID=141616 TID=41384 The image session needs to be closed and re-opened before any servicing operations can be performed. - CDISMImageSession::put_ImageState
2015-11-12 02:54:14, Info                  DISM   DISM Package Manager: PID=141616 TID=41384 Loaded servicing stack for online use only. - CDISMPackageManager::RefreshInstanceAndLock
2015-11-12 02:54:14, Info                  DISM   DISM Provider Store: PID=141616 TID=41384 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2015-11-12 02:54:14, Info                  DISM   DISM Provider Store: PID=141616 TID=41384 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2015-11-12 02:54:14, Info                  DISM   DISM Provider Store: PID=141616 TID=41384 Found the PE Provider.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2015-11-12 02:54:14, Info                  DISM   DISM Provider Store: PID=141616 TID=41384 Finalizing the servicing provider(DISM Package Manager) - CDISMProviderStore::Internal_DisconnectProvider
2015-11-12 02:54:14, Info                  DISM   DISM Package Manager: PID=141616 TID=41384 Finalizing CBS core. - CDISMPackageManager::Finalize
2015-11-12 02:54:14, Info                  DISM   DISM Provider Store: PID=141616 TID=41384 Disconnecting Provider: DISM Package Manager - CDISMProviderStore::Internal_DisconnectProvider
2015-11-12 02:54:14, Info                  DISM   DISM Provider Store: PID=141616 TID=41384 Finalizing the servicing provider(MsiManager) - CDISMProviderStore::Internal_DisconnectProvider
2015-11-12 02:54:14, Info                  DISM   DISM Provider Store: PID=141616 TID=41384 Disconnecting Provider: MsiManager - CDISMProviderStore::Internal_DisconnectProvider
2015-11-12 02:54:14, Info                  DISM   DISM Provider Store: PID=141616 TID=41384 Finalizing the servicing provider(IntlManager) - CDISMProviderStore::Internal_DisconnectProvider
2015-11-12 02:54:14, Info                  DISM   DISM Provider Store: PID=141616 TID=41384 Disconnecting Provider: IntlManager - CDISMProviderStore::Internal_DisconnectProvider
2015-11-12 02:54:14, Info                  DISM   DISM Provider Store: PID=141616 TID=41384 Finalizing the servicing provider(IBSManager) - CDISMProviderStore::Internal_DisconnectProvider
2015-11-12 02:54:14, Info                  DISM   DISM Provider Store: PID=141616 TID=41384 Disconnecting Provider: IBSManager - CDISMProviderStore::Internal_DisconnectProvider
2015-11-12 02:54:14, Info                  DISM   DISM Provider Store: PID=141616 TID=41384 Finalizing the servicing provider(DriverManager) - CDISMProviderStore::Internal_DisconnectProvider
2015-11-12 02:54:14, Info                  DISM   DISM Provider Store: PID=141616 TID=41384 Disconnecting Provider: DriverManager - CDISMProviderStore::Internal_DisconnectProvider
2015-11-12 02:54:14, Info                  DISM   DISM Provider Store: PID=141616 TID=41384 Finalizing the servicing provider(DISM Unattend Manager) - CDISMProviderStore::Internal_DisconnectProvider
2015-11-12 02:54:14, Info                  DISM   DISM Provider Store: PID=141616 TID=41384 Disconnecting Provider: DISM Unattend Manager - CDISMProviderStore::Internal_DisconnectProvider
2015-11-12 02:54:14, Info                  DISM   DISM Provider Store: PID=141616 TID=41384 Finalizing the servicing provider(SmiManager) - CDISMProviderStore::Internal_DisconnectProvider
2015-11-12 02:54:14, Info                  DISM   DISM Provider Store: PID=141616 TID=41384 Disconnecting Provider: SmiManager - CDISMProviderStore::Internal_DisconnectProvider
2015-11-12 02:54:14, Info                  DISM   DISM Provider Store: PID=141616 TID=41384 Finalizing the servicing provider(AppxManager) - CDISMProviderStore::Internal_DisconnectProvider
2015-11-12 02:54:14, Info                  DISM   DISM Provider Store: PID=141616 TID=41384 Disconnecting Provider: AppxManager - CDISMProviderStore::Internal_DisconnectProvider
2015-11-12 02:54:14, Info                  DISM   DISM Provider Store: PID=141616 TID=41384 Finalizing the servicing provider(ProvManager) - CDISMProviderStore::Internal_DisconnectProvider
2015-11-12 02:54:14, Info                  DISM   DISM Provider Store: PID=141616 TID=41384 Disconnecting Provider: ProvManager - CDISMProviderStore::Internal_DisconnectProvider
2015-11-12 02:54:14, Info                  DISM   DISM Provider Store: PID=141616 TID=41384 Finalizing the servicing provider(AssocManager) - CDISMProviderStore::Internal_DisconnectProvider
2015-11-12 02:54:14, Info                  DISM   DISM Provider Store: PID=141616 TID=41384 Disconnecting Provider: AssocManager - CDISMProviderStore::Internal_DisconnectProvider
2015-11-12 02:54:14, Info                  DISM   DISM Provider Store: PID=141616 TID=41384 Finalizing the servicing provider(GenericManager) - CDISMProviderStore::Internal_DisconnectProvider
2015-11-12 02:54:14, Info                  DISM   DISM Provider Store: PID=141616 TID=41384 Disconnecting Provider: GenericManager - CDISMProviderStore::Internal_DisconnectProvider
2015-11-12 02:54:14, Info                  DISM   DISM Provider Store: PID=141616 TID=41384 Finalizing the servicing provider(OfflineSetupManager) - CDISMProviderStore::Internal_DisconnectProvider
2015-11-12 02:54:14, Info                  DISM   DISM Provider Store: PID=141616 TID=41384 Disconnecting Provider: OfflineSetupManager - CDISMProviderStore::Internal_DisconnectProvider
2015-11-12 02:54:14, Info                  DISM   DISM Provider Store: PID=141616 TID=41384 Finalizing the servicing provider(Edition Manager) - CDISMProviderStore::Internal_DisconnectProvider
2015-11-12 02:54:14, Info                  DISM   DISM Provider Store: PID=141616 TID=41384 Disconnecting Provider: Edition Manager - CDISMProviderStore::Internal_DisconnectProvider
2015-11-12 02:54:14, Info                  DISM   DISM Provider Store: PID=141616 TID=41384 Releasing the local reference to OSServices. - CDISMProviderStore::Internal_DisconnectProvider
2015-11-12 02:54:14, Info                  DISM   DISM Provider Store: PID=141616 TID=41384 Disconnecting Provider: OSServices - CDISMProviderStore::Internal_DisconnectProvider
2015-11-12 02:54:14, Info                  DISM   DISM Provider Store: PID=141616 TID=41384 Releasing the local reference to DISMLogger.  Stop logging. - CDISMProviderStore::Internal_DisconnectProvider
2015-11-12 02:54:14, Info                  DISM   DISM Manager: PID=165808 TID=184312 Closing session event handle 0x1a0 - CDISMManager::CloseImageSession
2015-11-12 02:54:14, Info                  DISM   DISM.EXE: Image session has been closed. Reboot required=no.
2015-11-12 02:54:14, Info                  DISM   DISM.EXE: 
2015-11-12 02:54:14, Info                  DISM   DISM.EXE: <----- Ending Dism.exe session ----->
    
por Jeff Albrecht 13.11.2015 / 03:18

1 resposta

1

Me deparei com essa postagem que continha a sintaxe para montar boas janelas 10 da mesma versão Eu estava na minha LAN.

Eu compartilhei temporariamente a unidade c: \ da máquina boa e a montei como y: na máquina ruim.

Eu corri o dism, então o sfc. Isso funcionou! Infelizmente, ele não corrigiu todos os meus problemas com os erros 2502 e 2503 com instaladores msi. Como essa questão é sobre as opções de Source para o dism, e eu respondi, levarei as perguntas 2502/3 para uma nova pergunta.

  • No entanto, para o aprendizado , eu gostaria de saber como ter resolvido isso se eu não tivesse uma boa instalação do Windows 10 da mesma compilação disponível para uso como um fonte para dism.

  • Ao trabalhar com esse problema, notei muitas mensagens Duplicate ownership e is not owned em cbs.log. Eu chequei uma máquina windows 8.1 que tinha cerca de 90% de muitos erros. Eu estou supondo que não é para se preocupar, mas me pergunto o que outras pessoas experimentam é em suas instalações.

(executei um bash shell porque estou mais confortável com o grep do que com o findstr.) 

bash-3.1$ grep 2015-11-16 cbs.log | grep  "Overlap: Duplicate ownership for directory" | wc
    927   27111  299889
bash-3.1$ grep 2015-11-16 cbs.log | grep  "is not owned but specifies SDDL in component" | wc
    910   26119  297824
bash-3.1$

Aqui estão os resultados bem sucedidos para o dism e o sfc. 

C:\Windows\System32>Dism /Online /Cleanup-Image /RestoreHealth /Source:y:\windows /LimitAccess

Deployment Image Servicing and Management tool
Version: 10.0.10240.16384

Image Version: 10.0.10240.16384

[==========================100.0%==========================]
The restore operation completed successfully.
The operation completed successfully.

C:\Windows\System32>sfc /scannow

Beginning system scan.  This process will take some time.

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

Windows Resource Protection did not find any integrity violations.

C:\Windows\System32>
    
por 17.11.2015 / 03:00

Tags

Não é possível inicializar sem disco rígido inútil conectado Tempo limite em determinados URLs