Raspberry Pi Forums

Hi,

I am struggling to flash ffu image on the sd card for the Raspberry Pi 2. I need help to resolve the issue. Please see the logs below for details:-




2016-01-01 23:22:10, Info DISM DISM.EXE: <----- Starting Dism.exe session ----->
2016-01-01 23:22:10, Info DISM DISM.EXE:
2016-01-01 23:22:10, Info DISM DISM.EXE: Host machine information: OS Version=10.0.10586, Running architecture=x86, Number of processors=2
2016-01-01 23:22:10, Info DISM DISM.EXE: Dism.exe version: 10.0.10586.0
2016-01-01 23:22:10, Info DISM DISM.EXE: Executing command line: dism.exe /Apply-Image /ImageFile:flash.ffu /ApplyDrive:\\.\PhysicalDrive1 /SkipPlatformCheck
2016-01-01 23:22:10, Info DISM DISM Provider Store: PID=9756 TID=264 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection
2016-01-01 23:22:10, Info DISM DISM Provider Store: PID=9756 TID=264 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2016-01-01 23:22:10, Info DISM DISM Provider Store: PID=9756 TID=264 Loading Provider from location C:\Program Files (x86)\Microsoft IoT\Dism\FolderProvider.dll - CDISMProviderStore::Internal_GetProvider
2016-01-01 23:22:10, Warning DISM DISM Provider Store: PID=9756 TID=264 Failed to Load the provider: C:\Program Files (x86)\Microsoft IoT\Dism\FolderProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2016-01-01 23:22:10, Info DISM DISM Provider Store: PID=9756 TID=264 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2016-01-01 23:22:10, Info DISM DISM Provider Store: PID=9756 TID=264 Loading Provider from location C:\Program Files (x86)\Microsoft IoT\Dism\WimProvider.dll - CDISMProviderStore::Internal_GetProvider
2016-01-01 23:22:10, Warning DISM DISM Provider Store: PID=9756 TID=264 Failed to Load the provider: C:\Program Files (x86)\Microsoft IoT\Dism\WimProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2016-01-01 23:22:10, Info DISM DISM Provider Store: PID=9756 TID=264 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2016-01-01 23:22:10, Info DISM DISM Provider Store: PID=9756 TID=264 Loading Provider from location C:\Program Files (x86)\Microsoft IoT\Dism\VHDProvider.dll - CDISMProviderStore::Internal_GetProvider
2016-01-01 23:22:10, Warning DISM DISM Provider Store: PID=9756 TID=264 Failed to Load the provider: C:\Program Files (x86)\Microsoft IoT\Dism\VHDProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2016-01-01 23:22:10, Info DISM DISM Provider Store: PID=9756 TID=264 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2016-01-01 23:22:10, Info DISM DISM Provider Store: PID=9756 TID=264 Loading Provider from location C:\Program Files (x86)\Microsoft IoT\Dism\ImagingProvider.dll - CDISMProviderStore::Internal_GetProvider
2016-01-01 23:22:10, Info DISM DISM Provider Store: PID=9756 TID=264 Connecting to the provider located at C:\Program Files (x86)\Microsoft IoT\Dism\ImagingProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2016-01-01 23:22:10, Info DISM DISM Provider Store: PID=9756 TID=264 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2016-01-01 23:22:10, Info DISM DISM Provider Store: PID=9756 TID=264 Loading Provider from location C:\Program Files (x86)\Microsoft IoT\Dism\CompatProvider.dll - CDISMProviderStore::Internal_GetProvider
2016-01-01 23:22:10, Warning DISM DISM Provider Store: PID=9756 TID=264 Failed to Load the provider: C:\Program Files (x86)\Microsoft IoT\Dism\CompatProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2016-01-01 23:22:10, Info DISM DISM Provider Store: PID=9756 TID=264 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2016-01-01 23:22:10, Info DISM DISM Provider Store: PID=9756 TID=264 Loading Provider from location C:\Program Files (x86)\Microsoft IoT\Dism\FfuProvider.dll - CDISMProviderStore::Internal_GetProvider
2016-01-01 23:22:10, Info DISM DISM Provider Store: PID=9756 TID=264 Connecting to the provider located at C:\Program Files (x86)\Microsoft IoT\Dism\FfuProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2016-01-01 23:22:10, Info DISM DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.
2016-01-01 23:22:10, Info DISM DISM.EXE: Attempting to add the commands from provider: DISM Log Provider
2016-01-01 23:22:10, Info DISM DISM.EXE: Attempting to add the commands from provider: GenericImagingManager
2016-01-01 23:22:10, Info DISM DISM.EXE: Succesfully registered commands for the provider: GenericImagingManager.
2016-01-01 23:22:10, Info DISM DISM.EXE: Attempting to add the commands from provider: FfuManager
2016-01-01 23:22:10, Warning DISM DISM.EXE: Failed to load WimManager. Try running from the Deployment Tools Command Prompt. If the issue persists, ensure that wimgapi.dll and wimserv.exe are up to date.
2016-01-01 23:22:10, Info DISM DISM Provider Store: PID=9756 TID=264 Getting Provider GenericImagingManager - CDISMProviderStore::GetProvider
2016-01-01 23:22:10, Info DISM DISM Provider Store: PID=9756 TID=264 Provider has previously been initialized. Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2016-01-01 23:22:10, Info DISM DISM Provider Store: PID=9756 TID=264 Getting Provider FfuManager - CDISMProviderStore::GetProvider
2016-01-01 23:22:10, Info DISM DISM Provider Store: PID=9756 TID=264 Provider has previously been initialized. Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2016-01-01 23:22:11, Error DISM FFU Provider: PID=9756 TID=264 Failed to create a new block flasher object. - CFfuManager::Apply(hr:0x80070057)
2016-01-01 23:22:11, Error DISM FFU Provider: PID=9756 TID=264 base\ntsetup\opktools\dism\providers\ffuprovider\dll\ffumanager.cpp:167 - CFfuManager::ApplyImage(hr:0x80070057)
2016-01-01 23:22:11, Error DISM DISM Imaging Provider: PID=9756 TID=264 base\ntsetup\opktools\dism\providers\imagingprovider\dll\genericimagingmanager.cpp:2546 - CGenericImagingManager::InternalCmdFFUApply(hr:0x80070057)
2016-01-01 23:22:11, Error DISM DISM Imaging Provider: PID=9756 TID=264 base\ntsetup\opktools\dism\providers\imagingprovider\dll\genericimagingmanager.cpp:535 - CGenericImagingManager::ExecuteCmdLine(hr:0x80070057)
2016-01-01 23:22:11, Info DISM DISM.EXE: Image session has been closed. Reboot required=no.
2016-01-01 23:22:11, Info DISM DISM.EXE:
2016-01-01 23:22:11, Info DISM DISM.EXE: <----- Ending Dism.exe session ----->
2016-01-01 23:22:11, Info DISM DISM.EXE:
2016-01-01 23:22:11, Info DISM DISM Provider Store: PID=9756 TID=264 Found the OSServices. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2016-01-01 23:22:11, Info DISM DISM Provider Store: PID=9756 TID=264 Disconnecting Provider: GenericImagingManager - CDISMProviderStore::Internal_DisconnectProvider
2016-01-01 23:22:11, Info DISM DISM Provider Store: PID=9756 TID=264 Disconnecting Provider: FfuManager - CDISMProviderStore::Internal_DisconnectProvider
2016-01-01 23:22:11, Info DISM DISM Provider Store: PID=9756 TID=264 Releasing the local reference to DISMLogger. Stop logging. - CDISMProviderStore::Internal_DisconnectProvider

What image are you trying to load, and why are you using dism.exe?

The recommended process is here: https://www.raspberrypi.org/downloads/


Or if you want Windows 10 IoT try here: http://raspberrypihq.com/how-to-install ... pberry-pi/

I tried all the instructions and tools available on the Raspberry site as well as MS site. I am still getting the same error messages.

Windows 10 IoT Core SD Card creation can only be undertaken using Windows 10 Desktop Edition, there is no other supported method.

Only a Raspberry Pi 2B is compatible, any other model is not supported.

This has nothing to do with the Raspberry Pi Foundation and you should follow the Microsoft Instructions only:

https://ms-iot.github.io/content/en-US/GetStarted.htm

You will need a Class10 SD Card at least 8GB in size

Hi Jessie,
Thanks for your reply.. the followed all the directions listed on the link you posted above. Unfortunately, that's not working out for me. I am using 8GB class 10 SD card also.

pjsingh79 wrote:Hi Jessie,
Thanks for your reply.. the followed all the directions listed on the link you posted above. Unfortunately, that's not working out for me. I am using 8GB class 10 SD card also.

You have installed the Windows 10 IoT Dashboard on you PC ?

Followed the tutorial here: https://ms-iot.github.io/content/en-US/win10/RPI.htm

Is you Windows 10 Desktop PC fully up to date ?

Have you installed Visual Studio and updated ?

Do you have a Raspberry Pi 2B model ?

All the required items you listed have been updated to current version. I have Raspberry Pi 2 board.

You have installed the Windows 10 IoT Dashboard on you PC ?

Yes I installed Windows 10 ioT dashboard on my pc.

Followed the tutorial here: https://ms-iot.github.io/content/en-US/win10/RPI.htm

Yup followed instructions on github.

Is you Windows 10 Desktop PC fully up to date ?

Yes fully updated Windows 10

Have you installed Visual Studio and updated ?

Yup updated to latest all extensions included.


Do you have a Raspberry Pi 2B model ?

I have Raspberry Pi 2 model

Then one of the steps is not working for you.

you tried to run "WindowsIoTImageHelper" as administrator?
did you downloaded the most recent Win IoT Core for RPi2 are are you dealing with an outdated image? is wim uninstalled/disabled somehow on your system (group policies / other restrictions)

what you can try als well is, to boot from the windows 10 installation DVD/USB and go to the advanced troubleshooting options and then to the command console. from there you are able to runn the DISM command as well. but be carefully to do not wipe out your harddrive...