Solution: Boot images may be missing or unable to be imported through the ConfigMgr 2007 admin console

Solution: Boot images may be missing or unable to be imported through the ConfigMgr 2007 admin console

  • Comments 3
  • Likes

image Here's an interesting issue I've run into a couple times and since I didn't see it documented anywhere I thought I'd give everyone a heads up here.

When using System Center Configuration Manager 2007 you may find that you have missing default boot images and that you're unable to import boot images through the administrator's console.  When you try to import a boot image you get the following error:

System Events -
“{Registry Hive Recovered} Registry hive (file): '\??\C:\Windows\TEMP\BootImages\{6488069C-63E9-44AA-8C47-BB2A3EDD6B75}\mount\Windows\system32\config\SYSTEM' was corrupted and it has been recovered. Some data might have been lost.”

You may also see these errors in the DISM.log:

<date-time>, Error CBS Failed to load offline store from boot directory: '\\?\C:\Windows\TEMP\BootImages\{3401126F-CE34-476A-9C70-535FC749FCEA}\mount\' and windows directory: '\\?\C:\Windows\TEMP\BootImages\{3401126F-CE34-476A-9C70-535FC749FCEA}\mount\Windows\' [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
<date-time>, Error CBS Failed to initialize store parameters with boot drive: C:\Windows\TEMP\BootImages\{3401126F-CE34-476A-9C70-535FC749FCEA}\mount and windows directory: C:\Windows\TEMP\BootImages\{3401126F-CE34-476A-9C70-535FC749FCEA}\mount\Windows [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
<date-time>, Error DISM DISM Package Manager: PID=14568 Failed initializing the session - CDISMPackageManager::RefreshInstanceAndLock(hr:0x80070002)
<date-time>, Error DISM DISM Package Manager: PID=14568 Failed doing internal initialization - CDISMPackageManager::Initialize(hr:0x80070002)
<date-time>, Warning DISM DISM Provider Store: PID=14568 Failed to call Initialize method on IDismServicingProvider Interface - CDISMProviderStore::Internal_LoadProvider(hr:0x80070002)
<date-time>, Warning DISM DISM Provider Store: PID=14568 Failed to Load the provider: C:\Windows\TEMP\3CE573A0-8E9B-4337-A1F1-4AF0E74A5E5F\CbsProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x80070002)

and

<date-time>, Error DISM DISM OS Provider: PID=14568 Failed to open the key Microsoft\Windows NT\CurrentVersion. - CDISMOSServiceManager::DetermineBootDrive(hr:0x80070002)
<date-time>, Error DISM DISM Driver Manager: PID=14568 Failed to getting the boot drive from the os services provider. - CDriverManager::Initialize(hr:0x80070002)
<date-time>, Warning DISM DISM Provider Store: PID=14568 Failed to call Initialize method on IDismServicingProvider Interface - CDISMProviderStore::Internal_LoadProvider(hr:0x80070002)
<date-time>, Warning DISM DISM Provider Store: PID=14568 Failed to Load the provider: C:\Windows\TEMP\3CE573A0-8E9B-4337-A1F1-4AF0E74A5E5F\DmiProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x80070002)
<date-time>, Warning DISM DISM Provider Store: PID=14568 Failed to Load the provider: C:\Windows\TEMP\3CE573A0-8E9B-4337-A1F1-4AF0E74A5E5F\TransmogProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
<date-time>, Error DISM DISM.EXE: No providers were found that support the command(add-package). HRESULT=0dsim cbs

So what was the cause?  What we ultimately found was that if there's a disk management or maintenance service such as IntelliWrite by Diskeeper running on the disk then it can cause this type of issue.

In my case, we temporarily disabled the Diskeeper service and once we did that we were able to import the default boot images after manually copying the WIMS from a working server to the following folders:

C:\Program Files (x86)\Microsoft Configuration Manager\OSD\boot\x86

and

C:\Program Files (x86)\Microsoft Configuration Manager\OSD\boot\x64

So if you're running into an issue like the one I describe above, take a look and see what disk related services you have installed.  There's a chance that simply disabling those services temporarily will let you import the images successfully.

Hope this helps,

Clifton Hughes | Senior Support Engineer

clip_image001 clip_image002

Bookmark and Share

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • I'm the Product Manager with Diskeeper Corporation. Very sorry to see that you potentially experienced some form of conflict or issue with the software.

    When you have an opportunity, would you please report this to our Tech Support, so that we can look into this and fix any issues we discover? To do so, send an email to service@diskeeper.com

  • I had the same problem.  searched for two days ntil i came across this post.  i disabled diskeeper.  then i was able to run DISM without error.

    Thank you.

  • Hi, I'm getting the "DISM...Failed to load provider ...PEProvider.dll hr:0x8007007e" error where windows update is attempting to apply a NET 3.5 patch. 1. It's on a win8 laptop - is there a disk service on laptops too? 2. Does it require copying a folder from "another win 8 installation" as above on the server O/S? thx