none
Error 483 dism RRS feed

  • Question

  • Hello folks,

    i use dism to apply windows images on Embedded PCs (PCM3365). Because this takes some time i want to do this process simultaneously. So i have a network share which is accessd by the pcs via net use.

    But when they start at the same time there is appearing an error 483 and i cant find any information to this error .

    I use the following command: dism /apply-image /imagefile:F:\windows.wim /index:1 /ApplyDir:C:\

    Might it be a problem to access a WIM file with DISM simultaneously? I could observe that sometimes the apply-image process is very fast, but then the image is not working..

    Here is the dism logfile

    2017-09-08 14:59:46, Info                  DISM   DISM.EXE:
    2017-09-08 14:59:46, Info                  DISM   DISM.EXE: <----- Starting Dism.exe session ----->
    2017-09-08 14:59:46, Info                  DISM   DISM.EXE:
    2017-09-08 14:59:46, Info                  DISM   DISM.EXE: Host machine information: OS Version=10.0.15063, Running architecture=x86, Number of processors=2
    2017-09-08 14:59:46, Info                  DISM   DISM.EXE: Dism.exe version: 10.0.15063.0
    2017-09-08 14:59:46, Info                  DISM   DISM.EXE: Executing command line: "X:\Windows\System32\Dism.exe" /apply-image /imagefile:F:\Windows.wim /index:1 /ApplyDir:C:\ /CheckIntegrity /Verify
    2017-09-08 14:59:46, Info                  DISM   DISM Provider Store: PID=828 TID=836 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection
    2017-09-08 14:59:46, Info                  DISM   DISM Provider Store: PID=828 TID=836 Connecting to the provider located at X:\WINDOWS\System32\Dism\FolderProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2017-09-08 14:59:46, Info                  DISM   DISM Provider Store: PID=828 TID=836 Connecting to the provider located at X:\WINDOWS\System32\Dism\WimProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2017-09-08 14:59:46, Info                  DISM   DISM Provider Store: PID=828 TID=836 Connecting to the provider located at X:\WINDOWS\System32\Dism\VHDProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2017-09-08 14:59:46, Info                  DISM   DISM Provider Store: PID=828 TID=836 Connecting to the provider located at X:\WINDOWS\System32\Dism\ImagingProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2017-09-08 14:59:46, Info                  DISM   DISM Provider Store: PID=828 TID=836 Connecting to the provider located at X:\WINDOWS\System32\Dism\CompatProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2017-09-08 14:59:46, Info                  DISM   DISM Provider Store: PID=828 TID=836 Connecting to the provider located at X:\WINDOWS\System32\Dism\FfuProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2017-09-08 14:59:46, Warning               DISM   DISM Provider Store: PID=828 TID=836 Failed to Load the provider: X:\WINDOWS\System32\Dism\SiloedPackageProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
    2017-09-08 14:59:46, Warning               DISM   DISM Provider Store: PID=828 TID=836 Failed to Load the provider: X:\WINDOWS\System32\Dism\MetaDeployProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
    2017-09-08 14:59:46, Info                  DISM   DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.
    2017-09-08 14:59:46, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Log Provider
    2017-09-08 14:59:46, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: FolderManager
    2017-09-08 14:59:46, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: WimManager
    2017-09-08 14:59:46, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: WimManager.
    2017-09-08 14:59:46, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: VHDManager
    2017-09-08 14:59:46, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: GenericImagingManager
    2017-09-08 14:59:46, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: GenericImagingManager.
    2017-09-08 14:59:46, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: Compatibility Manager
    2017-09-08 14:59:46, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: Compatibility Manager.
    2017-09-08 14:59:46, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: FfuManager
    [828] [0x800701e3] WimCreateDirectory:(3112): The request failed due to a fatal device hardware error.
    [828] [0xc144012e]
    2017-09-08 15:00:36, Error                 DISM   DISM WIM Provider: PID=828 C:\Windows\WinSxS\amd64_netfx4-globalsansserifcf_b03f5f7f11d50a3a_4.0.10240.16384_none_8b2281a7d906294d (HRESULT=0x800701E3) - CWimManager::WimProviderMsgLogCallback
    [828] [0x800701e3] RestoreDirTree:(3380): The request failed due to a fatal device hardware error.
    [828] [0x800701e3] WIMApplyImageInternal:(706): The request failed due to a fatal device hardware error.
    2017-09-08 15:00:36, Error                 DISM   DISM WIM Provider: PID=828 TID=836 onecore\base\ntsetup\opktools\dism\providers\wimprovider\dll\wimmanager.cpp:1034 - CWimManager::Apply(hr:0x800701e3)
    2017-09-08 15:00:37, Error                 DISM   DISM Imaging Provider: PID=828 TID=836 onecore\base\ntsetup\opktools\dism\providers\imagingprovider\dll\genericimagingmanager.cpp:2535 - CGenericImagingManager::InternalCmdWimApply(hr:0x800701e3)
    2017-09-08 15:00:37, Error                 DISM   DISM Imaging Provider: PID=828 TID=836 onecore\base\ntsetup\opktools\dism\providers\imagingprovider\dll\genericimagingmanager.cpp:535 - CGenericImagingManager::ExecuteCmdLine(hr:0x800701e3)
    2017-09-08 15:00:37, Info                  DISM   DISM.EXE: Image session has been closed. Reboot required=no.
    2017-09-08 15:00:37, Info                  DISM   DISM.EXE:
    2017-09-08 15:00:37, Info                  DISM   DISM.EXE: <----- Ending Dism.exe session ----->
    2017-09-08 15:00:37, Info                  DISM   DISM.EXE:




    • Edited by pustekuchen Friday, September 8, 2017 1:07 PM added logs
    Friday, September 8, 2017 9:12 AM

Answers

  • Hello folks,

    just some Feedback. The problem is that the onboard flash seems to have problems when the SATA Mode is set to AHCI. When it is set to IDE Mode, the dism process is successful.

    This seems to be some additional compatibility problems with WinPE (Win 10). With WinPE 6.3.9600 (Windows 8.1) there are no problems.

    Thanks for your time.


    MS Visual Web Developer 2010 Express MS Visual C# 2010 Express


    Tuesday, September 19, 2017 7:05 AM

All replies

  • Looks the issue has to deal with hardware "The request failed due to a fatal device hardware error." It might be a packet was dropped or connection issue occurred that cause the error. How many connections were running simultaneously?

    Sean Liming - Book Author: Starter Guide Windows 10 IoT Enterprise - www.annabooks.com / www.seanliming.com

    Friday, September 8, 2017 3:22 PM
    Moderator
  • Hello Sean,

    thanks for the reply. We've tried it with 1 to 3 devices at the same time.

    Our first tests used a mSATA SSD, but now we got the PC with eMMC Memory. This seems to lead to problems while applying the image to the flash memory.

    Have you any experience with this? Any workarounds?


    MS Visual Web Developer 2010 Express MS Visual C# 2010 Express


    • Edited by pustekuchen Monday, September 11, 2017 7:12 AM
    Monday, September 11, 2017 6:04 AM
  • Could also be a driver issue. Do you have special drivers for the eMMC? If yes, try to load them using drvload.exe utility.

    To be sure that it isn't a dism problem you might also try to deploy an image using another tool like Acronis etc., if you have.

    Monday, September 11, 2017 7:53 AM
  • Could also be a driver issue. Do you have special drivers for the eMMC? If yes, try to load them using drvload.exe utility.

    This would be very strange, because some devices were installed successfully with the same hardware + image.

    MS Visual Web Developer 2010 Express MS Visual C# 2010 Express


    • Edited by pustekuchen Monday, September 11, 2017 8:17 AM
    Monday, September 11, 2017 8:08 AM
  • eMMC - do you mean SD card?

    Sean Liming - Book Author: Starter Guide Windows 10 IoT Enterprise - www.annabooks.com / www.seanliming.com

    Monday, September 11, 2017 3:04 PM
    Moderator
  • Time to narrow down the suspects.

    1 - how many devices are we talking about here? DISM isn't really the tool for mass replication. You probably what clonezilla which can do multicast and thus rocks for doing N machines at a time.

    2 - are all devices identical? Other posts suggest otherwise.

    3 - does doing it with 1 device work every time? 

    Change one thing at a time until you can narrow down the suspect. My immediate idea would be to check your server for errors, not just your client.

     


    =^x^=

    Tuesday, September 12, 2017 2:27 AM
  • Hello Bunny, Hell Sean,

    thanks for helping.I had some misinformation about the memory. It is not eMMC. It is just an OnBoard SATA Flash Memory (will be recognized as 16GB NANDrive. read/write: 66/14 MB/s). I call this device "PC2".

    On our first sample(PC1) we got an 16GB SSD which was connected via mSATA/mini PCIe. But both use the same SATA Bus.

    1) It depends, but it could be up to 10 Devices at the same time.

    2) yes they are all identical

    3) with another device(PC1), which use the additional mSATA SSD, yes. But till now, i've got no sample of PC2 which works every time. I have to make some more tests.

    We are also in contact with our PC supplier.

    -- EDIT --

    I've done some more tests with both PCs.

    First I've copied the WIM-Image to a usb stick and used this as the source for dism. Another test was to copy the wim file on the Memory itself and use this as the source and destination.

    Both tests failed with PC2(OnBoardFlash). And Both tests were successful with PC1(mSATA SSD).

    So with this test i've excluded ethernet and other external factors!

    Here are some additional Logs:

    Image on OnBoard Flash:

    [520] [0x8144012d] 2017-09-12 14:39:18, Warning               DISM   DISM WIM Provider: PID=520 [UncompressFile:(1116) -> file corrupted in block at offset 060D26BE] C:\ProgramData\Microsoft\Windows Defender\Scans\mpcache-5E40E4BD434A7795691953D06E5AC9E64000EA26.bin.67 (HRESULT=0x80070570) - CWimManager::WimProviderMsgLogCallback
    [520] [0x80070570] ResExtract:(497): The file or directory is corrupted and unreadable.
    [520] [0x8144012d] 2017-09-12 14:39:18, Warning               DISM   DISM WIM Provider: PID=520 [ResExtract:(499) -> UncompressFile failed] C:\ProgramData\Microsoft\Windows Defender\Scans\mpcache-5E40E4BD434A7795691953D06E5AC9E64000EA26.bin.67 (HRESULT=0x80070570) - CWimManager::WimProviderMsgLogCallback [520] [0x81440133] [520] [0x8144012d]

    While using the usb stick the same errors as in my entry post appeard (The request failed due to a fatal device hardware error)


    MS Visual Web Developer 2010 Express MS Visual C# 2010 Express





    • Edited by pustekuchen Tuesday, September 12, 2017 2:04 PM
    Tuesday, September 12, 2017 7:10 AM
  • You might want to give P Bunny's suggestion about using Clonezilla or other cloning tool rather than DISM/WIM solution.

    http://www.annabooks.com/Articles/Articles_WE8S/Clonezilla-WE_Rev1.3.pdf - the article needs an update, but it provides the steps to use Clonezilla


    Sean Liming - Book Author: Starter Guide Windows 10 IoT Enterprise - www.annabooks.com / www.seanliming.com

    Tuesday, September 12, 2017 3:22 PM
    Moderator
  • Hello Sean,

    thanks for this advice and the link to the guide. At my first look i think clonezilla will not work for us. The reason is that i have developed a system, based on WinPE, which partition the drives, applies the image and copies some indiviual client data to the disk, without any user interaction on the client itself.

    There must be a possiblity to apply the image via CMD from WinPE


    MS Visual Web Developer 2010 Express MS Visual C# 2010 Express

    Wednesday, September 13, 2017 6:07 AM
  • Hello folks,

    just some Feedback. The problem is that the onboard flash seems to have problems when the SATA Mode is set to AHCI. When it is set to IDE Mode, the dism process is successful.

    This seems to be some additional compatibility problems with WinPE (Win 10). With WinPE 6.3.9600 (Windows 8.1) there are no problems.

    Thanks for your time.


    MS Visual Web Developer 2010 Express MS Visual C# 2010 Express


    Tuesday, September 19, 2017 7:05 AM