WDS & DISM: injecting updates into a captured image

Hello,
I have been working on this for a few days now. Finally, I found a good article on using 'dism' to inject windows updates into 'wim' file. The whole process seemed to have gone well until after I used the image to setup a new computer.
The original captured image has 183 updates installed. After running the prescribed 'dism' commands, I blasted the image onto a box, checked the number of installed updates, but the number stayed the same: 183.
I have a computer with all the recent updates based on the same captured image. That computer shows 300+ updates installed. I used its c:\windows\softwaredistribution\download folder with 'dism' to update the image.
So, the issue is: even though 'dism' says it did the job, the image is still not updated and only showing 183 updates.
Anyone else seen this before? Thank you.

Hi,
Which guide did you refer and how did you do?
Please do not use c:\windows\softwaredistribution\download folder directly to inject to image.
Please download the full Windows Update packages into a new folder and then follow the below guide to apply it:
Apply Updates to an Image Using DISM (Standard 7 SP1)
http://msdn.microsoft.com/en-us/library/ff794819.aspx
Applying Windows Updates to a base WIM using DISM and Powershell
http://blogs.technet.com/b/configmgrdogs/archive/2012/02/15/applying-windows-updates-to-a-base-wim-using-dism-and-powershell.aspx
Karen Hu
TechNet Community Support

Similar Messages

WDS - Server 2008 R2 Create an Capture Image Error

I'm trying to create a capture image, and when I do that I receive an error stating "The operation completed with errors. A required privilege is not held by the client".
I've logged in with multiple domain admins, I've "run as administrator" for WDS, I've uninstalled/reinstalled the role and reconfigured it. I cant find any group policies that would be affecting this in a negative way. This is installed on a DC
which does not have DHCP.
I'm pretty much at the end of my rope here, hopefully someone can point me in the right direction.
Thank you all in advance!
-J0N3S3D

Hi,
Add the user to local administrator group and try again.
If the issue persists, you can enable logging and tracing WDS component.
For more information you can refer to:
How to enable logging in Windows Deployment Services (WDS) in Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, and in Windows Server 2012
http://support.microsoft.com/kb/936625/en-us
This article contains information about how to modify the registry. Make sure that you back up the registry before you modify it. Make
sure that you know how to restore the registry if a problem occurs.

Deploying captured image of reference computer - WDS & MDT

Hi, yesterday I set up MDT 2012 Update 1 on Windows 7 computer and WDS on Windows Server 2008 R2. I completed the following tasks:
Create New Deployment Share
Import Operating System (Windows 7) into Deployment Share
Import network drivers for HP Compaq Pro 6300 Small Form Factor into Deployment Share
Create Sysprep and Capture Task Sequence for capturing image of reference computer
Update Deployment Share
Prepare reference computer for imaging - install OS, drivers, apps, patches . . .
Run Sysprep and Capture Task Sequence from reference computer
Import captured image of reference computer into Deployment Share
Create Standard Client Task Sequence for deploying captured image to bare-metal computer
Use Lite_Touch wim file as WDS boot image
Run PXE boot on bare-metal computer
Enter necessary information - computer name, domain name, time zone and so on
I took more than 2 hours to complete deployment of captured image to bare-metal computer. Everything worked well but after this process finished I noticed that computer name was not the one I entered in TS nor computer was joined to the domain. Time zone
was not set. It seems that computer name, workgroup membership, time zone can not be altered in TS - they remain the same as they were on sysprepped computer.

My doubts and yours Keith were right, sysprep was not performed well at all via Sysprep and Capture Task Sequence so I did
sysprep /generalize /oobe /shutdown on reference machine and then booted it into WinPE with ImageX tool (if I am right in newest ADK dism is main tool for capturing online images instead of ImageX which is deprecated). I captured
image of Windows 7 OS partition and copied it to MDT technician computer, imported it as operating system in MDT deployment share and selected it as .wim image to deploy to new bare metal machine via Standard Client Task Sequence. During deployment entered
values for computer name, time zone were applied successfully and computer was joined to a domain. After restart message was shown with info that built in local administator account was disabled with switch user option where I could choose local account that
existed on sysprepped machine or domain account.
Conclusion: Sysprep step in Sysprep and Capture TS in MDT does not work at all. I will try this on newest version of MDT (MDT 2013) since I am testing now on MDT 2012 Update 1 version. If sysprep does not work again MDT is useless for capturing images thus
I have to use sysprep manually and then dism for capturing sysprepped image.
Thank you very much for your time and patience.

How to include a KB Update into a WIM in order to point to the WIM when using DISM (details inside)?

Hi, I was told in another of the forums that my issue
is best suited for the TechNet audience. Previously, I posted it here: http://answers.microsoft.com/en-us/windows/forum/windows8_1-system/how-to-include-a-kb-update-into-a-wim-in-order-to/e7015076-b4a9-4862-a73b-6c58b4c82461?tm=1409598696763
I've been struggling to fix a corrupted file.
Context: I feel that something is not right with the computer, so I started poking around.
I used "sfc /scannow" from an elevated command prompt and the result was:
Windows Resource Protection found corrupt files but was unable to fix some of them. Details are included in the CBS.Log <var style="border:0px;margin:0px;padding:0px;vertical-align:top;-webkit-font-smoothing:antialiased;">%WinDir%</var>\Logs\CBS\CBS.log.
I looked in the log. This message appears 4 times:
Cannot repair member file [l:36{18}]"Amd64\CNBJ2530.DPB" of prncacla.inf, Version = 6.3.9600.16384, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate",
TypeName neutral, PublicKey neutral in the store, hash mismatch
There is also the following message:
This component was referenced by [l:186{93}]"Microsoft-Windows-Printer-Drivers-Package~31bf3856ad364e35~amd64~~6.3.9600.16384.INF_prncacla"
I'm not positive what to do next, but I have been led to believe the problem is that Flash files in version 6.3.9600.16407 are corrupted, that I need to find which KB updates Flash to this version, download the file, add it to a new WIM, and point
to it when using DISM. I'm not positive this is correct, but it was suggested.
I downloaded the KB update: kb2889543, but I do not know how to add it to a new WIM or what the repercussions of doing so will be (e.g. Will I lose everything and have to restore my documents, etc from my external drive by doing this?).
So, the question is: How can I include a KB Update into a WIM and tell me what the result will be when once I do and point to it when using DISM?
Secondarily, if this is a bad way to move forward with the issue, would some kind soul offer sage advise on how to move forward with resolving the original issue?

Hi TTQSTTQS,
As you mentioned in the answers forum, when run the command DISM /Online /Cleanup-Image /RestoreHealth, we received the error message “The source files could not be downloaded. Use the "source" option to specify the
location of the files that are required to restore the feature”.
When run the command Dism /Online /Cleanup-Image /RestoreHealth /Source:c:\test\mount\windows /LimitAccess, we met the same error message.
I think there are some mistakes in the source setting, so we meet the same error messages.
As I mentioned in the last reply, we need a mounted image as a repair source, and then use this path.
We need to configure a Windows repair source. Please refer to the following article.
http://technet.microsoft.com/en-us/library/hh825020.aspx
Please refer to the following steps to set the source image.
1. Assign Drive Letters to Partitions by Windows PE.
2. Capture Partition Images using DISM
For more information, please refer to the following article.
http://technet.microsoft.com/en-us/library/hh825072.aspx
Then, we could try the command Dism /Online /Cleanup-Image /RestoreHealth /Source:c:\test\mount\windows /LimitAccess.
Best regards,
Fangzhou CHEN
Fangzhou CHEN
TechNet Community Support

Trouble booting to WDS server to deploy or capture image

Hello, we have an existing WDS server running Server 2008 R2 with SP1. I am having trouble getting a Surface Pro 3 to boot to the WDS (even after creating updated deploy and capture boot images). I can get the Surface to PXE boot, and I am
able to choose the Deploy or Capture boot image, but then I get the message that an error occurred obtaining an IP address from the DHCP server. During the PXE boot, the device does obtain an IP address in the correct range. I tried adding the
Surface ethernet adapter drivers to the boot wims but since they are not signed I get errors that they cannot be added. Any suggestions?

Added drivers to boot images using DISM with the /ForceUnsigned override.

WDS 2012 Black Screen when trying to capture image

I'm currently having an issue trying to capture windows 8.1 Enterprise image using Server 2012 R2 + WDS for deployment.
All the usual steps have been followed, images added from the install media used to set up the initial machine, DHCP configured and PXEBoot works fine for the deployment image (it loads, I get an ip, can access reminst share) but when I boot in the capture
image I get nothing but a black/blank screen.
Initially when I booted in to the capture image I was receiving an 0xC000000F error but by adding the network driver to the capture image it resolved that issue and it gives the blue windows logo and starts loading but then goes black. I've subsequently
tried to add all available drives for this machine from the HP site but made no difference.
WDS server is a hyper-v VM and the box to be capture is physical, both on the same vlan.
Any one experienced this?

I did not find any help with this. I was able to get a native boot.wim and install.wim to work from the installation media (with driver injection - which I must say is way easier in W2K12). However the capture did not and will not work. VERY frustrating!
I wound up doing a WDS basic OS install then I had to manually touch 24 boxes to install the rest of the software (still not quite done after three solid days of work).
Also, I should point out: I am targeting Dell Optiplex 790s. I'm using the PE 5.0 drivers which work fine. i also downloaded the Dell Optiplex 790 driver set and injected those as well, even though they are targeted for Win 7, not Win 8.1.
Interestingly, if I updated the old system bios (A05) to the new (A18) the machine couldn't even contact the WDS server. It was working before at A05 and then completely stopped at A18, requiring me to do a complete full install from installation media.
Way to go Dell! This is why people are switching to Lenovo.
Best,
Bill

WDS Capture Image Failing to Load

Using the instructions posted here:http://social.technet.microsoft.com/wiki/contents/articles/11680.creating-a-capture-image-in-wds.aspx I created a capture image and then injected network drivers into the boot image. When trying to load the capture image
I get the error:
Status: 0x000000f Info: The boot selection failed because a required device is inaccessible.
Does anyone know what might cause this or how to resolve this issue?

Hi,
First test to add/remove any mass storage drivers when capture the image.
Also the error could relate to BCD corrupt. Check BCD entry to see if it is correct. You could try following 3 commands:
a. bcdedit /set {default} device partition=c:
b. bcdedit /set {default} osdevice partition=c:
c. bcdedit /set {bootmgr} device partition=c:
TechNet Subscriber Support in forum |If you have any feedback on our support, please contact [email protected]

WDS Capture Image Blank Screen with Cursor

Hey everyone, happy Friday and Happy Sysadmin Day!
Not super happy for myself unfortunately! I'm having a problem with a Capture Image in WDS. I have a Sysprepped Dell 6440 running Windows 7 x64.I've created a Capture Image in WDS from a boot image with drivers injected and without drivers injected, but every time I boot from PXE, it gets to the windows loading screen, and then it just shows a blank screen with a cursor.I'm using Microsoft's OpenLicense ISO as a base for the boot.wimI can't find any solution that works. I've tried mounting and unmounting the WIM, restarting WDS, etc. This is getting really frustrating as I'm so close to having these images ready.The blank screen won't do anything, won't open a cmd with Shift+
F10 or anything. I've also tried booting on a different machine and it does the same thing.Any suggestions are...
This topic first appeared in the Spiceworks Community

HI @Moonrod ,
Welcome to the HP Forums!
It is a super place to find answers and information!
For you to have the best experience in the HP forum I would like to direct your attention to the HP Forums Guide Learn How to Post and More
I grasp you were unable to do a refresh you PC as you received the message that the drive was locked.
Please refer to my post Re: Can't refresh or reset windows 8.1 because drive is locked
Here is a link from the windowsclub.com that may also be informative.
Fix: The drive where Windows is installed is locked.
Best of Luck!
Sparkles1
I work on behalf of HP
Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
Click the “Kudos, Thumbs Up" on the bottom right to say “Thanks” for helping!

WDS capture image on a Windows 2012 R2 server fails with a winload error

Hello,
I have been fighting with this problem for days now. I have to install
30 Win8.1 Pro PC's with WDS. The WDS service is running on a Win2012 R2
server. I added the Win 8.1 Pro boot and install images and created a capture image.
Now when I boot the reference computer I get a Boot Manager message saying that winload.exe is missing or corrupt. The original boot wim works
correctly.I removed and added the WDS role a couple of times, I tried the procedure with a 32 bit Win7 boot image, and that worked, But when I added the capture image created from the original Win8.1 boot.wim, that spoiled both capture images. I tried
the same thing with a Win2012 R2 Standard server after removing and adding the WDS role again, but the capture image generated the same error as above. .I see that since about mid-April many people has the same problem.Different solutions are suggested, but
none of them worked for me. One of them is to mount and unmount the capture image, that didn't help for me.
Any help is appreciated.
Thanks
Gabor

Do I understand correctly that if you deploy original wim file to your testPC1 it works all right, but if you deploy an image that you captured on buildPC to testPC1 then you get the winload.exe error ?
Are you formatting (deleting all the partitions) on testPC1 during the
deployment of captured image ? Can you check and confirm if the HDD seting for AHCI or IDE (yes, its still around) is the same option on both stations?

Capture image into a PDF form?

Hi,
Is it somehow possible to capture an image from a digital camera/scanner etc. (over WIA) into a PDF form?

Hi,
Designer ES doesnt have possibility to capture image from digital camera. You can create form from already existing PDF file with image.
To create this PDF you can use Adobe Acrobe 9 which has possibility to create pdf from Scanner.
BR,
Paul Butenko

When capturing images from a Nikon D600, they show in Bridge, but when clicked to load into CS6,an error message says that it is the wrong type of document, even jpeg files. This is a NEW frustration.

When capturing images from a Nikon D600, they show in Bridge, but when clicked to load into CS6,an error message says that it is the wrong type of document, evne jpeg files. This is a NEW frustration.

Nikon raw files would open up in Adobe Camera Raw and so should jpegs.
If you select one in Bridge and give the command "Ctrl r" (Windows), what happens?
Also what is the version of ACR in the title bar?
Gene
Note: unmark your question as "answered". the green balloon next to the subject shows it as "solved".

Since I downloaded the latest PSE12 update, when I download images from my camera into Organizer on my iMac, the application freezes.

Since I installed the latest PSE12 update, when I download images from my camera into Organizer on my iMac, the application freezes. If I "force quit" then it seems to download them, but will do nothing else, including verifying and deleting the images from my camera. It worked fine prior to the update.

Dear Steve--
You are the man--a true Apple genius. Your suggestion worked.
Thanks you so much.
Charlie Jarowski

Can't inject drivers into boot images as they don't appear

Hello,
I have a problem trying to inject some drivers into the boot image using SCCM 2012.
I right click on the specific driver, I choose Edit > Boot image and there no boot images show up! The list is empty.
We do have 2 boot images (x32 and x64) and they are working just fine!
Does anybody have a clue what is going wrong here?
Thanks.

What version of ConfigMgr (RTM, SP1, or R2) are you using and what version are the boot images?
Each version of ConfigMgr can only directly manage (including driver injection) specific boot image versions.
RTM -> WinPE 3.1
SP1 -> WinPE 4.0
R2 -> WinPE 5.0
Thus, you are most likely trying to edit downlevel (or maybe uplevel) boot images.
Jason | http://blog.configmgrftw.com

Windows Server 2012r2 WDS capture image hangs at black screen

Ok so i upgraded my server to 2012r2 and i am using the boot.wim from windows8.1 pro iso. I create a deploy image and it boots up on my fujitsu stylistic machine. It also boots on my lenovo thinkpad yoga.
I go and create a capture image and at first fails so i added the usb3.0 lenovo dongle driver. It then shows me the windows logo and just hangs at black screen. I have downloaded the entire sccm driver package off lenovo site and nothing has
helped. It also does not load on the fujitsu machine either.
I have been going nuts any help is much appreciated
thanks
Dave

Hello,
Where did you get the original image? If you download it from MSDN or technet, can you provide the link?
And is update 1 integrated with the original image or you install it manually after installation?
In order to address the issue, we need collect some more informaiton.
Thank you.

Windows 7 Professional PC hangs at "Loading files" when trying to boot with custom capture image on Windows Deployment Services.

I have created a custom capture image in WDS. Now when I try to boot my reference PC into this image the PC hangs at "Loading files". The reference PC is running Windows 7 and I am using Windows Server 2012 Standard on my server.
I have followed the instructions on how to create the custom capture image on the server to a fault. I PXE boot the PC and it shows the capture images after I hit F12. The problem is that it starts to boot and then hangs about 2/3 way through the progress
bar.
Any help would be appreciated.

Hi Derrick Logan,
We need know the detail phases your client hang, if it is irregular status, please collect the WDS log then post it. You can refer the following similar thread solution first.
How to enable logging in Windows Deployment Services (WDS) in Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, and in Windows Server 2012
http://support.microsoft.com/kb/936625/en-us
Windows is loading files... Hangs on WDS
https://social.technet.microsoft.com/Forums/windowsserver/en-US/baacadc4-830d-43e1-ace8-3292e886958e/windows-is-loading-files-hangs-on-wds?forum=winserversetup
WDS hangs at "Windows is loading files..." on a LAM jhl91 laptop
https://social.technet.microsoft.com/Forums/windowsserver/en-US/3ebb6e0b-9f05-4fee-b3c0-129c34bb879d/wds-hangs-at-windows-is-loading-files-on-a-lam-jhl91-laptop?forum=winserversetup
I’m glad to be of help to you!
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

WDS & DISM: injecting updates into a captured image

Similar Messages

Maybe you are looking for