"Failed to verify that the WIM file has a valid compression type. "

[carsontl]

Hey guys, recently stood up a 2012 environment with SCCM 2012 and MDT 2013.

I have successfully captured a win7 fully updated wim file in MDT's workbench off a Dell Lat 6420 and imported it into CM2012.

 

My issue is when I try to build the MDT boot image it gives this error:

Started processing.
Creating boot image.
Copying WIM file.
Mounting WIM file.
WIM file mounted.
Setting Windows PE system root.
Set Windows PE system root.
Set Windows PE scratch space.
Adding standard components.
Adding component: winpe-mdac
Adding extra content from: C:\Users\ADMINI~1\AppData\Local\Temp\1\rwiwfq0q.j4p
Unmounting WIM.
Copying WIM to the package source directory.
Creating boot image package.
Error while importing Microsoft Deployment Toolkit Task Sequence. 

Failed to verify that the WIM file has a valid compression type. 

Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryException: The SMS Provider reported an error. ---> System.Management.ManagementException: Generic failure 
   at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
   at System.Management.ManagementObject.Put(PutOptions options)
   at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.Put(ReportProgress progressReport)
   --- End of inner exception stack trace ---
   at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.Put(ReportProgress progressReport)
   at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.Put()
   at Microsoft.BDD.Wizards.SCCM_ImportTaskSequenceTask.DoWork(SmsPageData smspageData, Dictionary`2 data)

Could anyone please shed some light on what I can do?

 

Please and thank you!

[ccollins]

I am having this same problem.

 

Did you ever get this figured out?

 

Thanks

 

Chris

[Phylum]

I encountered this today after upgrading from:

• SCCM 2012 R2 SP1
• MDT 2013
• ADK 8.1

To:

• SCCM 2012 R2 SP1 + CU1 KB3074875 + Hotfix KB3084586
• MDT 2013 Update 1
• ADK 10

 

As crazy as this sounds, a reboot solved the issue. You see, after applying the SCCM updates, we bounced the box but didn't bounce it after installing the ADK and MDT.

We attempted to build several boot images but it always failed with:

Started processing.
Creating boot image.
Copying WIM file.
Mounting WIM file.
WIM file mounted.
Setting Windows PE system root.
Set Windows PE system root.
Set Windows PE scratch space.
Adding standard components.
Adding component: winpe-dismcmdlets
Adding component: winpe-mdac
Adding component: winpe-netfx
Adding component: winpe-powershell
Adding component: winpe-securebootcmdlets
Adding component: winpe-storagewmi
Adding component: dart8
Adding extra content from: C:\Users\USERNA~1\AppData\Local\Temp\2\a21hk3ml.g4n
Unmounting WIM.
Copying WIM to the package source directory.
Creating boot image package.
Error while importing Microsoft Deployment Toolkit Task Sequence. 

Failed to verify that the WIM file has a valid compression type. 

Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryException: The SMS Provider reported an error. ---> System.Management.ManagementException: Generic failure 
   at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
   at System.Management.ManagementObject.Put(PutOptions options)
   at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.Put(ReportProgress progressReport)
   --- End of inner exception stack trace ---
   at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.Put(ReportProgress progressReport)
   at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.Put()
   at Microsoft.BDD.Wizards.SCCM_ImportTaskSequenceTask.DoWork(SmsPageData smspageData, Dictionary`2 data)

Interestingly, a WIM was created but when we attempted to import the WIM, it complained that the WIM needed to be compressed. (Sorry, I lost the clip with the error text.)

Several permutations later, after ruling out the possibility of a share/permissions or networking issue, or an issue with our extra files and pre-start commands etc., we bounced the box.

It came up and worked fine.

 

Crazy that a restart solved the issue.