Image Capture Boot Image Fails with 0xc000000f
I am trying to capture a Windows 8.1 Enterprise (with Update) x64 installation using WDS, but the Capture Image fails to load. I used the boot.wim from the Windows Server 2012 R2 (with Update) ISO to create a boot image in WDS and then a capture image from
it. After I press F12 and the progress bar finishes the following message appears:
This only happens when I boot the capture image - the original boot image that I imported in WDS boots normally. I also tried with the Windows 8.1 (with Update) boot.wim, but the issue reoccurs. This is a Hyper-V VM on Windows Server
2012. Is this a problem with the recent update?
-
Edited by
Yordan Yordanov
Friday, April 18, 2014 3:20 PM
April 18th, 2014 3:18pm
Hi,
Were currently experiencing exactly the same issue. Also a fully-updated Server 2012R2 (with the recent KB2919355 update) machine.
So far, I found two other posts with exactly the same issue:
1) http://wp.secretnest.info/?p=1474
2)
http://community.spiceworks.com/topic/472581-wds-capture-image-winload-exe-corrupt-or-missing
According to these posts it seems like the issue occurs after the first time a capture image based upon a Windows 8.1 or Server2012R2 boot.wim is created.
What Ive tried so far is removing the server role, deleting the WDS store, rebooting the server and start over with a Windows 7 boot.wim. The normal boot.wim starts ok, but the created capture image doesnt.
So the process of creating the capture boot image did something in a way the new boot.wim differences from the old boot.wim. To find out what, I first mounted the new .wim file to see if winload.exe is actually there it is both in
system32 as well as systen32\boot. So my second guess was that the Windows Boot Manager cannot find the windows loader, because of an incorrect declaration of disks in the BCD store.
I used BCDEDIT to show the differences between the working and non-working boot images:
Windows Boot Loader
-------------------
identifier {1d214c07-6892-401c-a762-04647ad38560}
device ramdisk=[boot]\Boot\x64\Images\boot.wim,{b321afc0-8a23-4
961-85dd-a10f3c46473f}
description Windows 7 Boot Image
osdevice ramdisk=[boot]\Boot\x64\Images\boot.wim,{68d9e51c-a129-4
ee1-9725-2ab00a957daf}
systemroot \WINDOWS
detecthal Yes
winpe Yes
Device options
--------------
identifier {b321afc0-8a23-4961-85dd-a10f3c46473f}
inherit {68d9e51c-a129-4ee1-9725-2ab00a957daf}
ramdiskmcenabled No
ramdiskmctftpfallback Yes
-- Second - Non Working disk --
Windows Boot Loader
-------------------
identifier {872352a0-0ad9-46f6-8612-1aed71ea8534}
device ramdisk=[boot]\Boot\x64\Images\boot-win7-capture.wim,{7a
b86a3a-3651-4f50-a748-34f3e784158c}
description Windows 7 Capture
osdevice ramdisk=[boot]\Boot\x64\Images\boot-win7-capture.wim,{68
d9e51c-a129-4ee1-9725-2ab00a957daf}
systemroot \WINDOWS
detecthal Yes
winpe Yes
Device options
--------------
identifier {7ab86a3a-3651-4f50-a748-34f3e784158c}
inherit {68d9e51c-a129-4ee1-9725-2ab00a957daf}
ramdiskmcenabled No
ramdiskmctftpfallback Yes
So the ID for the osdevice is the same, and only the device is different, but mentioned correctly under Device options (as far as my knowledge goes in this subject). I hope there will be a solution anytime soon.
-
Edited by
C-Laze
Saturday, April 19, 2014 10:44 PM
Added KB article
April 19th, 2014 10:43pm
Hi,
We are currently testing the same environment and will let you know once we got a result.
Meanwhile as you both mentioned that the issue occurs on a capture image of Windows 2012 R2 update1 system, will it work with a capture image of a Windows 2012 R2 system without update1?
April 22nd, 2014 1:47am
I can verify that i am having the exact same issue. I am in the process of redoing the server and testing with out update one installed.
April 22nd, 2014 9:21pm
Having the same issue here with Server 2012 R2 fully updated - even tried a full removal of the WDS role and a recreation of the remoteinstall folder with brand new boot images - this didn't resolve it.
I am trying a few things now, will update if I progress anywhere.
EDIT: Just tried rolling back
KB2919355 - tried the capture image again with no chances, didn't work.
Removed WDS Role, re-added and tried again - worked fine. Based on that, I'd say there's a good chance that the problem is due to the above update.
-
Edited by
Gavin Stone
Tuesday, April 22, 2014 10:00 PM
adding additional info
April 22nd, 2014 9:23pm
Okay guys, I think the problem is with every version of R2 server. I installed the "Windows 2012 Server (datacenter)" "Win_Svr_Std_and_DataCtr_2012_64Bit_English.iso" and created a capture image using the boot.wim of the same server I
Installed and then booted to Capture image and VOILA! Now i'm going to try to use the same capture image that windows 2012 server datacenter built for me and I'll put it in R2 WDS and see if that works. I'm sure it will but ill update if this technique works!!
- Copying good copy of Capture.wim to R2 server didn't work.
-
Edited by
Mike K Y
Tuesday, April 22, 2014 10:21 PM
April 22nd, 2014 9:47pm
I just experienced this same problem today when I attempted to create a Windows 8.1 Pro Capture image on a fully patched Windows 2012 R2 Datacenter server. No problems creating then Windows 8.1 Pro boot image. I need to deploy 500 Windows 8.1 Pro clients
by the middle of May. Really need an answer soon.
April 22nd, 2014 10:43pm
Only way I could get this working was to roll back KB2919355 and reinstall WDS
April 22nd, 2014 11:55pm
Ok so maybe this problem is not isolated to 2012 R2 Datacenter. We just checked another server running Windows Server 2012 Datacenter. Same problem. No KB2919355 on either server.
April 23rd, 2014 1:36am
Hi Yordan,
In our test, we use boot.wim from Windows 8.1 ISO (Enterprise version. also tried Windows Server 2012 R2 Datacenter ISO) and create capture image on a Windows Server 2012 R2 Update1 server - both created successfully.
I cannot find any difference between your steps and ours except you mentioned "used the boot.wim from the Windows Server 2012 R2 (with Update) ISO". Where comes the ISO with Update1? We would like to have a try on this and see if it is the
cause.
@Gavin: Your test seems directly related to KB2919355. What's the ISO you are using? Please have a try with boot.wim from a Windows Server 2012 R2 DataCenter ISO to see if you can get the same result as us.
@WillWally: It seems that your current situation is a little different as OP. If available please post a new thread and share your exact configuration so that we can discuss without confusion.
April 23rd, 2014 9:32am
I can verify that my issue is related to the update 1 of 2012 r2. I had a fresh install and updated all but update 1. My capture images worked with no issues. install update 1 and they then started becoming corrupt. I really hope that there is a hotfix
for this issue soon.
April 23rd, 2014 3:51pm
I've also experienced this issue, with a clean out of the box install of Server 2012 R2, with no updates. The trigger for it, is adding a boot image from the recently released ISO of Windows 8.1 with the Update 1 included (SW_DVD9_SA_Win_Ent_8.1_64BIT_English_2_MLF_X19_49847.iso).
The fix for me, adapted from the details on
http://wp.secretnest.info/?p=1474 was to remove the WDS role, reboot, delete the RemoteInstall\Boot folder, add the WDS role back, and add a different boot image. I used the boot.wim from the Server 2012 R2 iso (en_windows_server_2012_r2_x64_dvd_2707946.iso),
and was able to create a working capture image for my 8.1 Update clients.
April 23rd, 2014 9:28pm
Hi all,
Thank you for sharing the information.
With updating the boot.wim to update1, we could reproduce this issue as the screenshot posted by Yordan.
We have already report this issue and hope it could be fixed quickly.
April 24th, 2014 9:53am
Just wanted to update my situation with Windows server 2012 Datacenter. Same problem as reported here with Windows 2012 R2 with the exception of update 1. My Windows 2012 Datacenter server does not have Update 1. I was able to get a capture image to work
by first creating it in WDS 2008 R2. I then exported the image and imported it to my 2012 Datacenter server. Image boots successfully. For whatever reason, 2012 Datacenter corrupts the capture image when you try a create one.
-
Proposed as answer by
trelf
Tuesday, May 20, 2014 4:37 PM
April 24th, 2014 1:15pm
Totally legit....Creating the capture.wim file on server 2008 then copying to server 2012 worked for us as well.
-
Proposed as answer by
trelf
Tuesday, May 20, 2014 4:33 PM
-
Unproposed as answer by
trelf
Tuesday, May 20, 2014 4:37 PM
May 1st, 2014 7:53pm
experiencing the same issue here WDS server is windows server 2012. Havent been able to create a capture image.
May 2nd, 2014 2:30pm
I know this isn't a fix for this problem BUT if you really need to get deployments done - MDT 2013 is really a HUGELY better product than WDS. I am really surprised to see so many people using WDS - it is so massively limited compared to the Free MDT 2013.
It is very easy to set up.
May 14th, 2014 6:45pm
!
-, .
м м.
KB291935 , м Win Srv 2012
WDS, м.
м win- win- м, 2 , м WDS WIM .
, , CaptureImage winpeshl.ini
мм,
[LaunchApps]%SYSTEMROOT%\system32\wdscapture.exe
м CaptureImage
(http://technet.microsoft.com/en-us/library/cc730907%28v=ws.10%29.aspx#BKMK_custom)
м WDS.
мм Win8.1
м м DISM (DISM /?) index 2
м winpeshl.ini windows\system32\
м м, м .
м м WDS .
, !!!
, MS, :(
May 20th, 2014 5:08am
Had the same issue and was able to create a capture file from the Win 8.1 U1 media on a 2008 R2 WDS server, and it loaded and started working just fine on my 2012 R2 U1 WDS server.
May 20th, 2014 4:36pm
MS is being pretty silent on this issue. We don't have a software assurance contract, so no one will talk to us about this bug.
-
Proposed as answer by
Jan, IT
Tuesday, June 17, 2014 1:39 PM
-
Unproposed as answer by
Jan, IT
Tuesday, June 17, 2014 1:39 PM
May 30th, 2014 3:22pm
If you are looking for help - you need to use English.
May 30th, 2014 6:28pm
Hi all,
Thank you for sharing the information.
With updating the boot.wim to update1, we could reproduce this issue as the screenshot posted by Yordan.
We have already report this issue and hope it could be fixed quickly.
May 31st, 2014 5:12am
Also having this issue on Server 2012 R2 Update 1, waiting for fix?
June 5th, 2014 2:11am
One of the workarounds is to mount the capture.wim file using dism, do not make any changes. Unmount it with /commit switch.
-
Proposed as answer by
Saurabh.kMicrosoft employee
Thursday, July 03, 2014 5:47 PM
June 6th, 2014 12:51am
One of the workarounds is to mount the capture.wim file using dism, do not make any changes. Unmount it with /commit switch.
This worked perfectly; very simple and quick, thank you!!
-
Proposed as answer by
Saurabh.kMicrosoft employee
Thursday, July 03, 2014 5:47 PM
-
Unproposed as answer by
Saurabh.kMicrosoft employee
Thursday, July 03, 2014 5:47 PM
June 11th, 2014 4:16pm
Any actual Clear instructions for people on doing this?
June 12th, 2014 12:58pm
Any actual Clear instructions for people on doing
June 15th, 2014 7:59pm
One of the workarounds is to mount the capture.wim file using dism, do not make any changes. Unmount it with /commit switch.
That worked for me! Thanks! Its a Workaround, but i have not to deinstall any Updates.
June 17th, 2014 1:44pm
Thanks! This worked a treat for us on two new separate environments.
June 18th, 2014 8:21am
Aaah great, I was struggling with this and was thinking about installing an additional server with 2008 R2 just for WDS.....you saved me a lot of time, great find!
Keep it up!
Rob.
June 20th, 2014 12:12pm
I am also having this issue: Windows Server 2012 R2 Standard U1
June 29th, 2014 4:06pm
Try chris blakey's workaround.
Worked for me too. Only takes a minute.
Basically you create a folder to mount the image to temporarily, mount the image, then unmount it, and for some reason that probably makes sense to chris blakey this fixes the corruption. Then you have to re-create the 'Create' boot image in
WDS with the same one you mounted.
July 7th, 2014 2:18pm
I dont have update KB2919355. butt still O have this same error, did you how to solve this
issue
July 11th, 2014 9:01am
I want to point something out about this:
When you install Windows ADK for Windows 8.1 Update (Update 1), it installs a copy of DISM into the tools folder that is version 6.3.9600.17029. Just wanted to note that.
If you install a copy of Windows 8.1 with Update 1 from a Microsoft DVD, it can have build versions between 17029, 17030, and 17031, depending on whether the post-U1 version of Update 1 KB package is fully installed (it installs a second time after you install
a pre-"patched" version of a U1 Windows 8.1 install). The stock install AFAIK, always starts at 17029 though.
Now, when you patch an install of Windows 8.1 U1 with the post-U1 KB2912335 (I think that's the U1 KB number), the version of DISM in the system32 folder gets updated....HOWEVER, your installation of the ADK version of DISM *DOES NOT*.
In the example above, you'd be using the DISM from the Windows PATH, which would be the fully-patched U1 version of DISM, which you can see from the version number as being build 17031.
So the question is: are there conflicts with the builds in a stock Windows Setup U1 image (which would only ever be 17029), and a 17031 build of Windows Server 2012 R2 (or Windows 8.1)?
Has anyone here been able to patch a Windows Setup U1 image all the way to build 17031 by fully integrating the U1 KB, and then tried the WDS Capture build wizard? I'm assuming here that WDS uses DISM in the system32 folder on the native install of
Windows Server 2012 R2 U1, since it doesn't require the ADK. Just wanted to point out that the ADK version will always show 17029.
Also, I want to point out that if you have a non-U1 version of Windows Server 2012 R2 Essentials, your Client PC Restore images for WDS NEVER get updated to U1. If you want to update them, you have to patch them yourself. I've seen some problems
with using the build 16384 boot images for restoring PC's that had U1 installed.
July 19th, 2014 4:55pm
I just discovered another "bug" with DISM, just so people know about this:
I have had no luck mounting WIM files on a ReFS-formatted volume while trying the workaround explained by Chris. I get an Error 50: the request is not supported.
So just FYI: ONLY MOUNT WIM FILES ON NTFS VOLUMES.
Took me HOURS trying to figure out why I couldn't mount some images migrated from an old system to a new one....
Windows Server 2012 R2 Essentials on WinServer 2012 R2 Hyper-V with tiered storage. Separate VHDX's: 1 for OS, 1 for "ServerFolders" data folders formatted ReFS, 1 for WDS formatted NTFS, 1 for backup stored on an external hard drive.
The last setup I did was with 2012 before R2. No ReFS. Now, going with ReFS, noticing some limitations with it. Good for raw data, bad for anything vaguely related to file system access - and that includes WIM support.
Can someone from Microsoft please confirm that this is a known issue with ReFS, and comment? And where in the TechNet Library does it say that ReFS is not supported by WIM mount?
July 19th, 2014 7:10pm
Using Windows Server 2012 R2 Datacenter and experiencing the same thing.
I've tried the WIM mount/unmount trick but with no joy. Now in the processes of creating a 2008 R2 server for the purposes of image capture.
Where is the fix?
July 30th, 2014 7:10am
Any actual Clear instructions for people on doing this?
August 2nd, 2014 3:28pm
I encountered the same issue today trying to capture a image of Windows 8.1 w/Updates. Thank you all for you posts.
Paul - I did the additional steps witch helped but I also had to Replace Image using the same captureimage.wim file.
My steps:
- Create MountDir and Mount WIM then Unmount WIM, shown above.
- Deleted and recreated Capture Image
- Replaced Capture Image using same captureimage.wim file.
- Stop & Start WDS
Thanks again! Help me save a lot of time!!
August 6th, 2014 6:03pm
Thank you, worked perfectly!
August 22nd, 2014 12:29pm
Thanks to you all above, mounting, unmounting, deleting, adding, restarting did fix the issue booting the capture image.
Not so many thanks to Microsoft for it still being broken in September.
September 3rd, 2014 4:47am
The dism fix did not work for me for some reason. It would loads up fine, but it would come up with a blank screen instead of the capture wizard.
Regardless I have another fix for those lucky enough to have backup copy of their reminst folder from a non-update 1 installation. Even better if you already have the deploy and capture boot images in it already. Stop the WDS server and replace that backup
version in the folder. Don't install any boot images with update 1 after that. It should work.
Does anyone know any updates on this issue from Microsoft? We have workarounds, but this fundamentally feels broken.
September 3rd, 2014 6:15pm
I am trying to capture a Windows 8.1 Enterprise (with Update) x64 installation using WDS, but the Capture Image fails to load. I used the boot.wim from the Windows Server 2012 R2 (with Update) ISO to create a boot image in WDS and then a capture image from
it. After I press F12 and the progress bar finishes the following message appears:
This only happens when I boot the capture image - the original boot image that I imported in WDS boots normally. I also tried with the Windows 8.1 (with Update) boot.wim, but the issue reoccurs. This is a Hyper-V VM on Windows Server
2012. Is this a problem with the recent update?
I have been working with Microsoft Technical Support on this issue. Case 114072911658380
The case is now archived with Microsoft as they have escalated this to the relevant team. They have reproduced this bug and they are working on an official fix / workaround article. This may come in the form of a support article
or a patch, but a fix is being worked on.
I have done my best to pressure the product group to officially put up a "fash publish" support.microsoft.com article, but so far this has not happened. I am hopeful that this will however happen soon.
September 10th, 2014 1:47pm
Here are the exact steps I used to fix the x64 capture image on our production WDS, using Saurabh.k' DISM fix (I assume that you know how to locate the capture WIM on disk, if not it will normally be located in RemoteInstall\Boot\<architecture>\Images\).
- Log on to your WDS server and create an empty directory that you can mount the WIM in (I used C:\MountDir)
- Open a command line window with administrator privileges, you'll run the two DISM commands here
- Mount the WIM file with the command dism /mount-wim /wimfile:<path-to-wim-file> /mountdir:<your-mount-dir-of-choice> /index:1
- Unmount the WIM file, committing changes (even though you didn't make any) with the command
dism /unmount-wim /mountdir:<your-mount-dir-of-choice> /commit
Worked perfectly in my home lab and our production WDS at work. Both servers were running fully patched versions of Server 2012 R2. The capture image I had at home came from a Server 2012 R2 with Update ISO, while the one at work came from a Windows 8.1
with Update ISO. Neither worked before the fix.
Output from the successful fix at work:
C:\>dism /mount-wim /wimfile:C:\RemoteInstall\Boot\x64\Images\capture_x64.wim /mountdir:C:\MountDir /index:1
Deployment Image Servicing and Management tool
Version: 6.3.9600.17031
Mounting image
[==========================100.0%==========================]
The operation completed successfully.
C:\>dism /unmount-wim /mountdir:C:\MountDir /commit
Deployment Image Servicing and Management tool
Version: 6.3.9600.17031
Image File : C:\RemoteInstall\Boot\x64\Images\capture_x64.wim
Image Index : 1
Saving image
[==========================100.0%==========================]
Unmounting image
[==========================100.0%==========================]
The operation completed successfully.
These steps helped! Thanks Rolf! dammit Microsoft, this problem was reported in April, today is September 10 2014, still have the problem!
-
Proposed as answer by
Sten Lootens
Friday, October 10, 2014 12:12 PM
-
Unproposed as answer by
Sten Lootens
Friday, October 10, 2014 12:12 PM
-
Proposed as answer by
Sten Lootens
Monday, January 19, 2015 8:59 PM
September 10th, 2014 9:05pm
I just ran into this issue now while creating a capture image.
WDS Server is Windows Server 2012 R2 Standard; Capture image is based on a Windows 7 Professional boot.wim file. This workaround saved me oodles of time!
Thanks!!
September 25th, 2014 8:51am
Today is 25 September (in South East Asia, at least) and this hasn't been fixed yet... The mount / unmount workaround just saved me oodles of time.
September 25th, 2014 8:56am
This "mounting" and "unmounting" worked for me! Thx!
October 6th, 2014 3:32pm
Worked for me too.
Cheers
October 8th, 2014 2:06pm
dism /mount-wim /wimfile:C\RemoteInstall\Boot\x64\Images\capture.wim /mountdir:C\MountDir /index:1
dism /unmount-wim /mountdir:C:\MountDir /commit
Was the fastest solution as already stated by everyone, be aware thath his Problem was confirmed by me totday (10-10-2014) with the Official Windows Server 2012 R2 Evaluation ISO
October 10th, 2014 12:22pm
Just followed Gavin Stone's advice (Removed KB2919355, removed and added back WDS role) and it's working correctly now. Thank you so much for that post !
David Harris
-
Edited by
TessCompany
Wednesday, October 22, 2014 5:30 PM
October 22nd, 2014 5:29pm
This remains broken for 6 months now !!!
October 28th, 2014 10:53am
Thanks...
October 28th, 2014 10:58am
Thanks MannyManuel!
November 18th, 2014 2:37am
I still get the same error like the thread starter.
I have tried the mount think but still get the error.
I have even tried to reinstall windows server 2012 R2 and try with a boot.wim from a windows 7 disk but nothing works.
anyone have any idears what I am doing wrong?
November 20th, 2014 10:59am
ok now I found out that is was the wrong wim file i mounted.
but that only opens up for the next problem, where I get the windows loading logo and then black screen.
November 21st, 2014 8:12am
I get the same issue, have run through all the example resolution without any success. Have also updated the capture boot.wim image using the process outlined (http://technet.microsoft.com/en-us/library/dn622020.aspx) and
still have the bank screen after the initial boot sequence.
running windows server 2012R2 std. with all latest updates
Image Version: 6.3.9600.17031
Boot image is windows 8.1 direct for Microsoft volume licensing download.
I can boot fine from the original install, it's the capture disk that WDS creates that has the issue.
November 28th, 2014 3:16pm
I am experiencing the same thing. Did you happen to find a solution?
December 1st, 2014 2:30am
Hi
Here's the solution that worked for me:
Log on to your WDS server and create an empty directory that you can mount the WIM in (I used C:\MountDir)Open a command line window with administrator privileges, you'll run the two DISM commands here
Mount the WIM file with the command
dism /mount-wim /wimfile: /mountdir: /index:1
Unmount the WIM file, committing changes (even though you didn't make any) with the command
dism /unmount-wim /mountdir: /commit
Then add your Capture Image to WDS Boot Image Folder...
-
Proposed as answer by
MTorabi
Wednesday, December 03, 2014 2:17 PM
December 3rd, 2014 2:07pm
The mount, unmount thing only help on the 0xc000000f error.
The black screen error that some of us are getting now, is a new error.
I think it has somthing to do with the driver in the boot.wim but i am not sure yet.
-
Edited by
Jerslund
Friday, December 05, 2014 10:23 AM
December 5th, 2014 10:23am
Just wanted to update my situation with Windows server 2012 Datacenter. Same problem as reported here with Windows 2012 R2 with the exception of update 1. My Windows 2012 Datacenter server does not have Update 1. I was able to get a capture image
to work by first creating it in WDS 2008 R2. I then exported the image and imported it to my 2012 Datacenter server. Image boots successfully. For whatever reason, 2012 Datacenter corrupts the capture image when you try a create one.
Same problem, used a capture image from another server and it works fine.
December 11th, 2014 6:14pm
The wim files from server 2008 R2 works. Thanks a lot.
December 15th, 2014 8:05am
Dear : ALL
I faced this problem from 2 days and i spent many times try to fixing this problem and i solved it but you have common steps you should to do or sure its done :
im talking about WDS SERVER 2012 R2 : PROBLEM ( 0XC000000F )
Common Steps :
1- DHCP Server scope option
PXEClient = 060 add your WDS Server IP this you should add by manual in scope option
boot server host name = 066 add your WDS Server IP
Boot file Name = 067 add ( \boot\x86\wdsnbp.com )
Now your Done in DHCP SERVER
2- When you install Clean WDS Server ( win server 2012 R2 ) close Automatic Update For Windows and Remove
this Fucken Update ( KB2919355 ) cause you will find this update installed by default , Then Install your WDS Service ) and for configure server on any partition not in c:\ drive , and save all images and capture
you will add in RemoteInstall Folder
3- Ports Allowed
you should allow the following ports in your Firewall if you have and in your Antivirus server :
TCP = 135 , 5040
RPC= 137 , 139 ,
UDP = 67 , 69
DHCP= 4011 , 68
TFTP = 64001 : 65000
I Hope this can help >>>!!!!
December 28th, 2014 9:53am
i also had to stop and restart the WDS service through the WDS console however i have written a simple batch script to simplify the process of moving, mounting, unmounting and committing the images http://www.mediafire.com/view/ucauj2yahi4g0f8/WDStool.bat
December 29th, 2014 11:38am
hi
i just finished updating my Windows 8.1 Enterprise Master image (and do this in hyper-v on a windows 8.1 x64 client - fully patched) and the wsus is a Win 2012 r2 fully patched server also and get the same error when trying to capture now.
i was able to push the image into hyper-v and boot with a setup ok but am unable to capture now :\
i have recreated both setup and capture .wim files and restarted wds service in case the original files were corrupt - still no go.
any help would be much appreciated
thanks in advance : )
January 13th, 2015 11:39am
ok guys- here is what i did and what i found to be the problem -
i tried all the above and none of this worked so i ended up stopping my WDS server and built another WDS in hyper v on my file server - and voila! i imported my original boot wim's (capture and custom tools i have made on win pe) and everything works like
before.
i also tried copying winload.efi files from anotherwokring wds server (from another site) but that did not work also the files were exactly the same size hmm
must have been some corruption
my new server is fully patched also and one thing i have done is enabled system recovery, and made sure snapshots are taken before updates take place - so if something goes pear shaped - i can always go back
infact im gonna export this hyper v wds i built and bang it on the physical wds i used to have and turn that into a hyper v host instead.
hope this helps.
-
Proposed as answer by
MR. LONSKi
Wednesday, January 14, 2015 4:35 AM
January 14th, 2015 4:35am
Worked for me Thanks
I used Mount-WindowsImage/Dismount-WindowsImage
January 15th, 2015 1:22pm
I'm confused on which wim to use. Bear with me, I'm not incredibly smart with this stuff yet.
So I've captured my Windows 8.1 image to a wim file. Is that the file that I do the DISM patch on? Is there anything I have to change in the SCCM console afterward? I tried these steps, tried re-adding the OS image, tried creating a new task sequence, etc.
I'm using the default boot images.
February 20th, 2015 5:40pm
FYI:
Using a Capture Wim created on a Windows 2008 server solved the issue. Once created I right clicked my existing capture image on the Windows 2012 R2 server and selected replace.
-
Proposed as answer by
SeanB13
Tuesday, February 24, 2015 7:03 PM
February 24th, 2015 7:01pm
Can I ask does anyone know if the version of DISM makes any difference? I've mounted an image from the "Deployment Tools Command Prompt" but the version is way behind. 6.1.7600.16385.
I've yet to fully test but concerned by mounting using a old version will not fix the issue. Will update...
March 12th, 2015 11:22am
Hi,
I had this problem too.
Here is the way I solved it (I hope it will be useful):
(WDS and Dhcp are not on one server)
First remove my new and fully updated Win 2k12 R2 Then reinstall a 2K12 R2, this time I did not update the server and for boot image I imported the Win8.1 pro without update 1 , then make capture image.
Finally it work. I think there is something with latest update for 6.3 version of windows (Win 8.1 or Win Server)
thanks.
April 9th, 2015 2:31am