Patching of Embedded OS WIM Files

Hi Guys,
I currently have a System Centre Configuration Manager 2012 R2 installation and I have just added the wim file for our HP Thin Clients that run Windows Embedded Standard 7 (WES7).
When I tried to apply updates to this WIM, it would only pick up on Windows 7 updates and not the Embedded ones. I can see the Software Update groups for both and can see the patches that should be applied, but it looks like it is not seeing the wim as the
Embedded edition of the OS, but the full version instead.
Has anyone else had this issue or been able to get it to work?
When I do a dism /Get-WimInfo, the responses do indicate that it is Embedded for both the Edition and Installation. The only thing I can think of, is that when it looks for updates, it is only looking at the Version number and Architecture which is the same
between Embedded and Full.
Any help is appreciated.
Regards,
Byron

Hi,
Please refer to the link below:
Add Updates to an Image (Standard 7 SP1)
http://msdn.microsoft.com/en-US/library/ff794120(v=winembedded.60).aspx
Also, I suggest you ask it to Windows Embedded Standard forum.
http://social.msdn.microsoft.com/Forums/en-US/category/embeddedwindows/
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.

Similar Messages

Adding patches to an offline .WIM file

Hi guys
I am trying to update my companies Windows Server 2008 R2 x64 install.wim file with some patches I have downloaded from the Microsoft Catalogue.
So a little background, I have taken the install.wim file from the sources directory of our server image which is saved on our deployment server, and I have copied it locally to my PC. I am a domain admin and I am also a local admin on my PC.
I downloaded the latest ADK and ran the Deployment and Imaging Tools Environment tool as an administrator. I mounted the install.wim file to a mount folder with no problems.
When I try to inject a single patch using this command line DISM /image: <mount_directory> /Add-Package /Packagepath: <msu_file> (obviously replacing mount_directory and msu_file with the correct paths) I get the below error.
Image version: 6.17600.16385Processing 1 of 1 – adding package…………(package path details ect)
99.5%
An error occurred applying the Unattend.xml file from the .msu package.
For more information, review the log file.
Error: 0x80070005
Error: 5
Access is denied.
Edited copy of the log file:
2014-11-13 11:02:46, Error                 DISM   DISM Package Manager: PID=9880 Failed processing package changes - CDISMPackageManager::ProcessChanges(hr:0x80070005)
2014-11-13 11:02:46, Error                 DISM   DISM Package Manager: PID=9880 Failed to process package changes in unattend file. - CPackageManagerUnattendHandler::Apply(hr:0x80070005)
2014-11-13 11:02:46, Error                 DISM   DISM Package Manager: PID=9880 Failed to Apply the unattend. - CDISMPackageManager::Apply(hr:0x80070005)
2014-11-13 11:02:46, Error                 DISM   DISM Unattend Manager: PID=9880 d:\w7rtm\base\ntsetup\opktools\dism\providers\unattendprovider\dll\unattendmanager.cpp:400 - CUnattendManager::Apply(hr:0x80070005)
2014-11-13 11:02:46, Error                 DISM   DISM Package Manager: PID=9880 Failed applying the unattend file from the MSU package. - CMsuPackage::ApplyMsuUnattend(hr:0x80070005)
2014-11-13 11:02:46, Error                 DISM   DISM Package Manager: PID=9880 Failed to apply the MSU unattend file to the image. - CMsuPackage::Install(hr:0x80070005)
When looking at the Security tab under properties of the mount folder I can see that the account CREATOR OWNER has no permissions. When I tried to give it full control I get access is denied on the following folders:
C:\mount\program files
C:\mount\program files (x86)
C:\mount\windows
If I check the permissions for my account name, it does have full control of the mount folder.
I am wondering if anyone can help me get rid of this error?
Or even better still as I have 63 patches to inject into this .wim file, can anyone suggest an easier way, as I wouldn’t like to sit here all day doing one patch at a time?
Thanks in advance.
Dave

Hi David Smale,
From your current description and base on my experience, it usually caused by the WIM file corrupt, please try to copy a new Wim file then try to patch again, if it not work,
please post your DISM error log, you can refer the following KB to get the DISM log.
This error also can caused by the Mcafee AV.
DISM.exe generates an Error: 5 or Access Denied when VSE 8.8 Access Protection is enabled
https://kc.mcafee.com/corporate/index?page=content&id=KB76867&locale=zh_CN
I’m glad to be of help to you!
*** This response contains a reference to a third party World Wide Web site. Microsoft is providing this information as a convenience to you. Microsoft does not control
these sites and has not tested any software or information found on these sites; therefore, Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. There are inherent dangers in the
use of any software found on the Internet, and Microsoft cautions you to make sure that you completely understand the risk before retrieving any software from the Internet. ***
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.

Adding custom WIM files to a bootable thumb drive

Hi, I have setup an WDS 2008 that works fine for deploying and capturing images over my network. I am trying to find a solution to create a bootable thumb, that would contain those custom images captured with WDS. So what I did until I got stuck:
Created a bootable thumb drive from an Windows 7 Pro installation disk, using Se7en Lite. Mounted the custom image in a folder and used "imagex" to append it to the "install.wim" file on the thumb drive. Checked with "imagex /info"
and indeed the custom image showed with index 5 and description "Windows7_x64_patched". Booted a PC off the thumb drive and got to the screen that asks which version of Windows I would like to install. Here, only one option shows up "Professional",
which would be the untouched Windows 7 Pro version. So no Basic, Premium or Patched version would show up, even though I can see them and their indexes with "imagex /info".
Questions:1) Is there an easier/faster way of creating a bootable thumb with multiple custom WIMs?
2) If "imagex /append" is a good solution and I'm on the right track, then what I should do so that the appended image would show as an option when installing off the thumb drive?
Thanks!

Thank you for your reply! So I edited the ei.cfg file (deleted "Professional" from [EditionID]. Now it shows me the four untouched versions "Basic", "Home Premium", "Professional" and "Ultimate" but not the custom one. I can still scroll down one more
row, so there is something without a description available seems. But if i scroll down to the 5th row and press enter, then I get the error: "Windows could not display the image available for installation". Referring to the first question and answer now, if
I replace the original "install.wim" on the thumb with my custom WIM, then I only have one image, as the WIM container would only have my captured image. So what I was asking is there an easier way to stick MORE THAN ONE installation image on the same bootable
device, without using the huge time consuming "imagex /append" command?
Here's a copy of my "imagex /info" on the modified "install.wim" from thumb:
WIM Information:
Path: e:\sources\install.wim
GUID: {65caf905-5e50-4a42-900b-5e14084871e9}
Image Count: 5
Compression: LZX
Part Number: 1/1
Attributes: 0x8
Relative path junction
Available Image Choices:
<WIM>
<TOTALBYTES>5643506813</TOTALBYTES>
<IMAGE INDEX="1">
<DIRCOUNT>13365</DIRCOUNT>
<FILECOUNT>64285</FILECOUNT>
<TOTALBYTES>11710161360</TOTALBYTES>
<CREATIONTIME>
<HIGHPART>0x01CB8936</HIGHPART>
<LOWPART>0x131F339A</LOWPART>
</CREATIONTIME>
<LASTMODIFICATIONTIME>
<HIGHPART>0x01CBF8F0</HIGHPART>
<LOWPART>0x0027D0DC</LOWPART>
</LASTMODIFICATIONTIME>
<WINDOWS>
<ARCH>9</ARCH>
<PRODUCTNAME>Microsoft® Windows® Operating System</PRODUCTNAME>
<EDITIONID>HomeBasic</EDITIONID>
<INSTALLATIONTYPE>Client</INSTALLATIONTYPE>
<HAL>acpiapic</HAL>
<PRODUCTTYPE>WinNT</PRODUCTTYPE>
<PRODUCTSUITE>Terminal Server</PRODUCTSUITE>
<LANGUAGES>
<LANGUAGE>en-US</LANGUAGE>
<DEFAULT>en-US</DEFAULT>
</LANGUAGES>
<VERSION>
<MAJOR>6</MAJOR>
<MINOR>1</MINOR>
<BUILD>7601</BUILD>
<SPBUILD>17514</SPBUILD>
<SPLEVEL>1</SPLEVEL>
</VERSION>
<SYSTEMROOT>WINDOWS</SYSTEMROOT>
</WINDOWS>
<NAME>Windows 7 HOMEBASIC</NAME>
<DESCRIPTION>Windows 7 HOMEBASIC</DESCRIPTION>
<FLAGS>HomeBasic</FLAGS>
<HARDLINKBYTES>4497873056</HARDLINKBYTES>
<DISPLAYNAME>Windows 7 Home Basic</DISPLAYNAME>
<DISPLAYDESCRIPTION>Windows 7 Home Basic</DISPLAYDESCRIPTION>
</IMAGE>
<IMAGE INDEX="2">
<DIRCOUNT>13614</DIRCOUNT>
<FILECOUNT>65339</FILECOUNT>
<TOTALBYTES>12222587449</TOTALBYTES>
<CREATIONTIME>
<HIGHPART>0x01CB8936</HIGHPART>
<LOWPART>0x131F339A</LOWPART>
</CREATIONTIME>
<LASTMODIFICATIONTIME>
<HIGHPART>0x01CBF8F0</HIGHPART>
<LOWPART>0x236D21C7</LOWPART>
</LASTMODIFICATIONTIME>
<WINDOWS>
<ARCH>9</ARCH>
<PRODUCTNAME>Microsoft® Windows® Operating System</PRODUCTNAME>
<EDITIONID>HomePremium</EDITIONID>
<INSTALLATIONTYPE>Client</INSTALLATIONTYPE>
<HAL>acpiapic</HAL>
<PRODUCTTYPE>WinNT</PRODUCTTYPE>
<PRODUCTSUITE>Terminal Server</PRODUCTSUITE>
<LANGUAGES>
<LANGUAGE>en-US</LANGUAGE>
<DEFAULT>en-US</DEFAULT>
</LANGUAGES>
<VERSION>
<MAJOR>6</MAJOR>
<MINOR>1</MINOR>
<BUILD>7601</BUILD>
<SPBUILD>17514</SPBUILD>
<SPLEVEL>1</SPLEVEL>
</VERSION>
<SYSTEMROOT>WINDOWS</SYSTEMROOT>
</WINDOWS>
<NAME>Windows 7 HOMEPREMIUM</NAME>
<DESCRIPTION>Windows 7 HOMEPREMIUM</DESCRIPTION>
<FLAGS>HomePremium</FLAGS>
<HARDLINKBYTES>4912986404</HARDLINKBYTES>
<DISPLAYNAME>Windows 7 Home Premium</DISPLAYNAME>
<DISPLAYDESCRIPTION>Windows 7 Home Premium</DISPLAYDESCRIPTION>
</IMAGE>
<IMAGE INDEX="3">
<DIRCOUNT>13701</DIRCOUNT>
<FILECOUNT>65851</FILECOUNT>
<TOTALBYTES>12122886417</TOTALBYTES>
<CREATIONTIME>
<HIGHPART>0x01CB8936</HIGHPART>
<LOWPART>0x131F339A</LOWPART>
</CREATIONTIME>
<LASTMODIFICATIONTIME>
<HIGHPART>0x01CE98EE</HIGHPART>
<LOWPART>0xCA54650A</LOWPART>
</LASTMODIFICATIONTIME>
<WINDOWS>
<ARCH>9</ARCH>
<PRODUCTNAME>Microsoft® Windows® Operating System</PRODUCTNAME>
<EDITIONID>Professional</EDITIONID>
<INSTALLATIONTYPE>Client</INSTALLATIONTYPE>
<HAL>acpiapic</HAL>
<PRODUCTTYPE>WinNT</PRODUCTTYPE>
<PRODUCTSUITE>Terminal Server</PRODUCTSUITE>
<LANGUAGES>
<LANGUAGE>en-US</LANGUAGE>
<DEFAULT>en-US</DEFAULT>
</LANGUAGES>
<VERSION>
<MAJOR>6</MAJOR>
<MINOR>1</MINOR>
<BUILD>7601</BUILD>
<SPBUILD>17514</SPBUILD>
<SPLEVEL>1</SPLEVEL>
</VERSION>
<SYSTEMROOT>WINDOWS</SYSTEMROOT>
</WINDOWS>
<NAME>Windows 7 PROFESSIONAL</NAME>
<DESCRIPTION>Windows 7 PROFESSIONAL</DESCRIPTION>
<FLAGS>Professional</FLAGS>
<HARDLINKBYTES>4786527097</HARDLINKBYTES>
<DISPLAYNAME>Windows 7 Professional</DISPLAYNAME>
<DISPLAYDESCRIPTION>Windows 7 Professional</DISPLAYDESCRIPTION>
</IMAGE>
<IMAGE INDEX="4">
<DIRCOUNT>13737</DIRCOUNT>
<FILECOUNT>66029</FILECOUNT>
<TOTALBYTES>12285492779</TOTALBYTES>
<CREATIONTIME>
<HIGHPART>0x01CB8936</HIGHPART>
<LOWPART>0x131F339A</LOWPART>
</CREATIONTIME>
<LASTMODIFICATIONTIME>
<HIGHPART>0x01CBF8F0</HIGHPART>
<LOWPART>0x6D7F6938</LOWPART>
</LASTMODIFICATIONTIME>
<WINDOWS>
<ARCH>9</ARCH>
<PRODUCTNAME>Microsoft® Windows® Operating System</PRODUCTNAME>
<EDITIONID>Ultimate</EDITIONID>
<INSTALLATIONTYPE>Client</INSTALLATIONTYPE>
<HAL>acpiapic</HAL>
<PRODUCTTYPE>WinNT</PRODUCTTYPE>
<PRODUCTSUITE>Terminal Server</PRODUCTSUITE>
<LANGUAGES>
<LANGUAGE>en-US</LANGUAGE>
<DEFAULT>en-US</DEFAULT>
</LANGUAGES>
<VERSION>
<MAJOR>6</MAJOR>
<MINOR>1</MINOR>
<BUILD>7601</BUILD>
<SPBUILD>17514</SPBUILD>
<SPLEVEL>1</SPLEVEL>
</VERSION>
<SYSTEMROOT>WINDOWS</SYSTEMROOT>
</WINDOWS>
<NAME>Windows 7 ULTIMATE</NAME>
<DESCRIPTION>Windows 7 ULTIMATE</DESCRIPTION>
<FLAGS>Ultimate</FLAGS>
<HARDLINKBYTES>4947144081</HARDLINKBYTES>
<DISPLAYNAME>Windows 7 Ultimate</DISPLAYNAME>
<DISPLAYDESCRIPTION>Windows 7 Ultimate</DISPLAYDESCRIPTION>
</IMAGE>
<IMAGE INDEX="5">
<DIRCOUNT>16853</DIRCOUNT>
<FILECOUNT>80207</FILECOUNT>
<TOTALBYTES>17942171343</TOTALBYTES>
<HARDLINKBYTES>4936766950</HARDLINKBYTES>
<CREATIONTIME>
<HIGHPART>0x01CE9935</HIGHPART>
<LOWPART>0x5B788A49</LOWPART>
</CREATIONTIME>
<LASTMODIFICATIONTIME>
<HIGHPART>0x01CE9935</HIGHPART>
<LOWPART>0x6D5A05EC</LOWPART>
</LASTMODIFICATIONTIME>
<WINDOWS>
<ARCH>9</ARCH>
<PRODUCTNAME>Microsoft® Windows® Operating System</PRODUCTNAME>
<EDITIONID>Professional</EDITIONID>
<INSTALLATIONTYPE>Client</INSTALLATIONTYPE>
<HAL>acpiapic</HAL>
<PRODUCTTYPE>WinNT</PRODUCTTYPE>
<PRODUCTSUITE>Terminal Server</PRODUCTSUITE>
<LANGUAGES>
<LANGUAGE>en-US</LANGUAGE>
<DEFAULT>en-US</DEFAULT>
</LANGUAGES>
<VERSION>
<MAJOR>6</MAJOR>
<MINOR>1</MINOR>
<BUILD>7601</BUILD>
<SPBUILD>18015</SPBUILD>
<SPLEVEL>1</SPLEVEL>
</VERSION>
<SYSTEMROOT>WINDOWS</SYSTEMROOT>
</WINDOWS>
<NAME>Win7Pro_x64_patched_nod</NAME>
</IMAGE>
</WIM>

DISM Command to retrieve updates from software distribution and apply to wim file

I'm following
this guide about slipstreaming updates into a wim file. What im attempting to is what the author outlines in step 2, namely pulling updates from the software distribution folder on a pc that has had the image applied to it and then patched to current. The
trouble I'm running into is around the command. namely this section DISM
/image:C:\Mount
/add-package /packagepath:”%U” Running this command produces a invalid path message. What should be happening is the previous commands
are telling it to pull in any files name .cab from all of the directories, but this doesn't seem to be working. I can't define this as a static path as there are tons of sub-folders in this directory with the cab files. Am I just doing something wrong? how
can I accomplish this?

I'm still having trouble with this. For some reason, it is stripping the % sign. So I am seeing this when I run my batch file:
/add-package /packagepath:"u"
or
/add-package /packagepath:"f"
Any ideas?

How do I use copyprofile, image manager and create a wim file to Sysprep a reference Windows 8 computer.

Im trying to deploy a reference machine (configured) to other machines (exact or close image) with different hardware.
I have successfully used sysprep in out of the box, generalise, shutdown mode although i havent tried to deploy this to another device. Unfortunately it doesnt copy the profile to default.
I understand that I have to create an answer file using image manager based on that image, save it to a usb drive and attach this in the sysprep command line when sysprepping it.
My problem is I dont know how to easily capture an image of windows 8 into a wim file so that i can add this into image manager to create a answer file. Im also not sure what I have to do in image manager, is it a simple matter of creating and saving
the answer file or do i have to configure it to copy the profile specifically (theres only one account anyhow).
I also want to know if i have to attach the drivers or are all the standard drivers put into the sysprep image as standard. I would like the machine to be an exactly replica, same as doing a clone (but with the drivers for the new machine installed
so it will boot) same as doing a clone and then repair? If thats possible.
Any specific instructions on this would be helpful. I have read the microsft links but they are somewhat confusing.

I know this is a very late response but I thought I'd post for others who search.
The easiest way to create the .wim file is via WinPE, this guy's two YouTube videos explain the entire process in detail -
Windows 8 ADK Part 1: Capture an OS image - https://www.youtube.com/watch?v=XJ8zKX_8E9w
Windows 8 ADK Part 2: Windows Image Deployment - https://www.youtube.com/watch?v=HHIvoqSw_FI
Here's a quick rundown from my notes:
WINPE
Create WinPE via imaging tools command prompt
copype amd64 c:\winpe
makewinpemedia /iso "c:\winpe" "c:\winpe\winpe64.iso"
UNATTEND
Open Windows System Image Manager
Configure unattend.xml
Save unattend.xml to sysprep folder
Create script and save it to sysprep folder to launch sysprep with unattend
@echo off
cd C:\Windows\System32\sysprep
Sysprep /oob /generalize /unattend:C:\Windows\System32\sysprep\unattend.xml
SYSPREP
C:\Windows\System32\Sysprep
Run as administrator
OOBE/Generalize
Shutdown
CONFIGURATION of WINPE
Set IP - netsh int ip set address "Local Area Connection" static 192.168.1.2 255.255.255.0 192.168.1.1
Set DNS - netsh int ip set dns name = "Local Area Connection" source = static addr = 192.168.1.4 validate = no
Map Network Name - net use z:
\\WindowsADK\reflex\images password /USER:domain.local\username
DISKPART
diskpart
list disk
select disk zero
list partition
select partition 2 (OS partition #)
Assign letter=S (assigns drive letter to partition)
Exit
DISM
dism /capture-image /imagefile:z:\image.wim /capturedir:s:\ /name:"Windows 8.1 Custom"
Verify image is saved in the image share (z:)
http://www.microsoftfanboys.com

How to edit a captured custom .wim file?

Hi folks,
I am in process of gaining experience with capturing and deploying Windows 7 SP1 from our WDS server using unattend file.
Everything is working, since we installed our applications, ran sysprep, and captured a custom .wim file.
Now we deploy it using unattend file and everything works.
I am trying to figure out if there is a best practice here for adding applications to this new custom .wim file?
I've tried deploying this new image to a unit, installed app, and run sysprep but fails with this error:
A fatal error occurred while trying to sysprep the machine.
I am thinking this has to do with multiple syspreps or something?
I am trying to avoid having to use a default install.wim and app install automation with MDT or something like that. We are strict to WDS only right now.
Appreciate any comments,
Thanks! romatlo

Offline servicing allows for adding/removing drivers and updates in MSU/CAB files.
I do not use MDT either. If you want to "install" a new application to an image that is "out of arms" then you will need to install it after deployment. If your image has an answer file, you can mount your image. Then copy the installation files to it or
you can keep it on a network share. Then in the answer file, you can put in the commands to install it using FirstLogonCommands.
I typically like to reference a .cmd file in my unattend that I can add/remove commands to finalized images. So if a client wants to install a new program but doesn't want to recreate the image, then I can have it installed that way.
<FirstLogonCommands>
<SynchronousCommand wcm:action="add">
<Order>1</Order>
<Description>Set up Service Account</Description>
<CommandLine>cmd /C start /wait c:\folder\FirstLog.cmd</CommandLine>
</SynchronousCommand>
</FirstLogonCommands>

Temporary wim-files for multicast transmissions still needed for WDS installation in Server 2012 R2?

Acording to
https://technet.microsoft.com/en-us/library/dn281955.aspx one of the new features for WDS in Server 2012 R2 for multicast is:
Improved multicast deployment by eliminating the need for making a local copy of the install.wim file. You can apply the install.wim file while it is being downloaded without significant impact to the application process.
However, this doesn't seem to be activated by default and I still get the following error when installing one or more machines using multicast:
"Windows Setup cannot locate a valid hard drive to store temporary installation files." However, once I remove Multicast from this install image, it installs without any problems at all.
I have also noticed that while multicasting, the installation will use the "Copying Windows files" phase, while downloading and copying the install.wim (or whatever name it is) locally on the hard drive first, so this will require lots of space.
So the question is, how do you enable this new feature that should be a part of WDS in Server 2012 R2???

Full version:
Following steps could help enable the feature:
1. Mount the boot image using dism.
e.g.
>dism /mount-wim /wimfile:c:\remoteinstall\boot\x64\images\boot.wim /index:2 /mountdir:c:\mount
2. Create a metadata file if no existing one. The metadata file should be in mountdir from the first step under mountdir\sources. And the file name should be: WdsClientMetadata.txt
3. Add entry to the metadata file: WDS.Client.Multicast.WIM.Streaming.Enabled=true
4. Save changes and unmount the boot image
e.g.
>dism /unmounts-wim /mountdir:c:\mount /commit
Sorry for the late reply, but I had to test this thoroughly since I didn't get it working right away. I tried both the regedit you first mentioned, and later also creating a textfile in the "/index:2 boot.wim", both without any success. I noticed
that creating the sources\WdsClientMetadata.txt with the data "WDS.Client.Multicast.WIM.Streaming.Enabled=true" gives me an error upon booting into WDS as follows (EUFI/IPv6-boot):
Same happens if I boot using IPv4 (an non-UEFI boot), except that there would be a plain IPv4-address instead in the error msg. Just for troubleshooting I tried writing WDS.Client.Multicast.WIM.Streaming.Enabled=false in the file instead, and WDS would throw
me the exact same error message. Once I delete the file sources\WdsClientMetadata.txt from the WDS/Boot image, the client boots ok, both for IPv4/IPv6. Disabling the firewall on the WDS didn't help, so something in the configuration is still missing? I'm getting
to a dead end here, and I suppose you're all out of advice on this one?
Thank you Shaon Shan for your great effort so far.

ImageX and appending .wim files VERY WEIRD Discovery!

I have a PC with two hard drives. I used ImageX to image each drive to a .wim file independently.
The first image was of the C:\ drive
The second image was of the D:\ drive.
I then used the following command to append the 2nd hard disk WIM file to the first hard disk WIM file.
C:>Program Files\Windows AIK\Tools\PETools>imagex /append /boot C:\1stdrive C:\Users\MyUserName\Documents\zTestFolder\Prec690_HDisk2Install.wim "Win7"
My thinking was that I could then deploy the image as 1 WIM file. But when I get to the familiar 'Install Now' screen, once I click 'Next', I immediately get the following message.
'The product key entered does not match any of the Windows images available for installation. Enter a different product key.'
So, for fun I decide to try something else.
I use my 'Deploy' UFD and only put in the C_Drive install.wim in the proper default location.
I then successfully install the O/S and it boots into Windows no problem!!!
But, HERE is WHERE IT GETS WEIRD
I do the Diskpart portion so disk 1 can now have an image applied to it.
Then, I apply the HardDisk2.wim file and it is successful...ie it doesn't throw any errors. The command I used was imageX /apply F:\HardDisk2.wim 1 D:\
But when I reboot, now the system no longer boots into Windows.
Instead it provides error of: No boot device available!

Hello,
The Windows Desktop Perfmon and Diagnostic tools forum is to discuss performance monitor (perfmon), resource monitor (resmon), and task manager, focusing on HOW-TO, Errors/Problems, and usage scenarios.
As the question is off topic here, I am moving it to the
Where is the Forum... forum.
Karl
When you see answers and helpful posts, please click Vote As Helpful, Propose As Answer, and/or Mark As Answer.
My Blog: Unlock PowerShell
My Book:
Windows PowerShell 2.0 Bible
My E-mail: -join ('6F6C646B61726C406F75746C6F6F6B2E636F6D'-split'(?<=\G.{2})'|%{if($_){[char][int]"0x$_"}})

How do I restore my backup (.wim files) after running HP System recovery on a G62 with windows 7

I had to do a system restore after getting a blue screen and I backed up the files on my external drive. after restoring the system I tried to restore my files from my external with Recovery manager but it didn't see my external so I couldn't restore. I copied and pasted the backup folder on my g62 desktop and tried again with no results. As far as I can tell the restore was done because my free space on the g 62 decreased by the same size as the backup, but when I open the c:\ drive I can't see the transfer. these are .wim files and I even tried to call tech service (my warranty juse expired) and they were trying to sell me extended warranty for the next year to help me. the problem exist with HP if they had good programs that follow up what it was meant to do maybe Today I wouldn't be here looking for help. when I restored the system, recovery told me the it would install my backup, but nothing happened leaving me hanging.NEED HELP!!!!!!!!!!!!!!

If you call AppleCare they will be more than willing to help you. Use the appropriate phone number on this page. Tell them you need a support related fulfillment - replacement disks. As shldr says there will be a small charge, but you will be able to install your system again.
Best of luck.

How do I open .wim files on my macbook pro?

When my hard drive crashed for the second time on my HP computer, I knew it was time for a change. The HP help menue gave me the option to backup everything onto an external hard drive. I did this and now when I try to open the files inside, they are all "#.wim" files. The #s go from 0.wim-53.wim. How do I open these files? Some might be microsoft word or powerpoint files but I have not got Microsoft word for mac yet. I understand that this will probably prevent me from opening some of the files but wouldnt I be able to open the others? If you know anything about ".wim" files, please help me.

https://en.wikipedia.org/wiki/Windows_Imaging_Format
http://www.eigenlogik.com/entropy/

The specified UNC path does not contain a valid WIM file or you do not have permission to access it. please specify a valid path

I loaded 4 captured images into SCCM via the Add Operating System Image Wizard 2 months ago.
I have since captured another image to the same location (which is the SCCM site server) and tried to add it to the server.
I am getting error
the specified UNC path does not contain a valid WIM file or you do not have permission to access it. please specify a valid path
nothing has changed on the site server that i can think of.
i am domain admin and permissions have not changed.
anyone got any answers?
please help i am baffled

I am having similer issues.
Win 2003 SP2 - SCCM2007 SP2 R2 single site with MDT2010 intergrated but can not get a MDT2010 TS Captured WIM to import into SCCM OS Images "Invalid WIM". allso i tried to mount the MDT WIM image without luck (Invalid Image). however a SCCM TS
will Capture and I can Import it into OS Images. it seems like something is amiss with MDT or WAIK possibly.

Variable .wim file (BackupFile) using %TaskSequence% not working for reference image

Hello,
I am trying to make a semi-automated solution for building reference image. The goal is to just select a task sequence and based on only that input create a reference image and store it on the MDT server as a unique named .wim file. I'm doing almost exactly
the same as all the pro's (Johan, Mikael, etc.). What I do is in the CustomSettings.ini I specify BackupFile to be %TaskSequenceID%.wim. My goal with that is to get a .wim file that is called REFWIN81CORENLX64.wim. Instead of that I get %TaskSequenceID%.wim.
I'm banging my head against the wall all day now and I have even build another environment to see if the problem occurs there too. It does..
I'm hoping that someone can tell me what Ido wrong.
Mathijs

Short Answer:
You have programmed a race condition into your system.
Long answer:
MDT will fill out the TaskSequenceID variable during the MDT LiteTouch Wizard.
You put the BackupShare variable in your CS.ini file:
BackupShare=\\MDT02\MDTBuildLab$\%TaskSequenceID%
However, the CS.ini was ALREADY processed *BEFORE* the MDT LiteTouch Wizard. and since TaskSequenceID was set to <BLANK> then Backupshare becomes the value above. ANy attempt to re-parse the cs.ini file will not process BackupShare because ZTIGather.wsf
will only pick up the value the first time.
Instead you should set the BackupShare variable *AFTER* the MDT Litetouch Wizard, if you want to leave it in your CS.ini file, then use Johan's method to re-parse the CS.ini file during the Task Sequence.
http://www.deployvista.com/tabid/36/EntryID/139/language/en-US/Default.aspx
-k
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com

Embedding a SWF file with an iFrame

I wanted to embed an assessment in to one of my PDFs. I know I can't do it directly so I tried to create a small little Flex app that shows an iFrame (see here for the example). I then tried to insert this (as a SWF) in to my PDF file. I have a problem where when selected in the PDF it displays the SWF file, but not the linked URLs for the iFrames. Any ideas? how I might be able to get around this. Here is an example of what I was working on.
Any help would be much appreciated.
Noel

hat do you mean with embedding a SWF file into another?
you can embedd a SWF file in a HTML file. you can load a SWF
file in another SWF file.
but to embedd a SWF into another is not possible.

The source folder must contain a valid boot.wim file

Hi.
I have the following problem
I have downloaded MDOP2014 (en_microsoft_desktop_optimization_pack_2014_x86_x64_dvd_4130158)
I have installed the Windows Assessment and Deployment Kit (Windows ADK) for Windows 8.1 Update
And then installed MSDaRT81.exe on a Windows 8.1 (with Update) machine
I have also copied the boot.wim from the "Sources" folder from the Win8.1 ISO file.
But when I start the DaRT Recovery Image Wizard an try to point to the folder with the boot.wim file, it gives me:
"The source folder must contain a valid boot.wim file"
I have tried boot.wim files from 8.1 ent, 8.1 ent with update, server 2012 R2, server 2012 R2 with update...no go
I am using boot.wim of win 7.
Any ideas????

Hi,
I found that if you point to the root directory (not the sources folder), then it finds the correct boot.wim. Specifically, I downloaded the 8.1 Enterprise evaluation ISO, then mounted the ISO (F:). When pointing to the sources folder, it gave the same error,
but when I pointed only to F:, it worked fine.
Additionally, both in the wizard and in the article 'Creating the DaRT 8.0 Recovery Image', it states:
Specify the root path of the Windows 8 <64-bit or 32-bit> install media
Hope this helps,
David
MDOP on the Springboard Series on TechNet

What HTML code do I need to get Adobe Flash to play an embedded MP4 video file (8 MB)?

What HTML code do I need to get Adobe Flash to play an embedded MP4 video file (8 MB)?
Thanks
Mark

Here are a couple of ways, one using the Netstream class and the other using the FLVPlayback component.
For the NetStream approach, the following in the timeline code will play/loop the intended mp4 file...
     var video:Video;
     var connect_nc:NetConnection = new NetConnection();
     connect_nc.connect(null);
     var stream_ns:NetStream = new NetStream(connect_nc);
     stream_ns.client = this;
     function netStatusHandler(p_evt:NetStatusEvent):void {
         if (p_evt.info.code == "NetStream.Play.Stop") {
             stream_ns.seek(0); // to loop the video
     stream_ns.addEventListener(NetStatusEvent.NET_STATUS, netStatusHandler);
     video = new Video();
     addChild(video);
     video.attachNetStream(stream_ns);
     stream_ns.play("path_to/your.mp4");
For the FLVPlayback component, add it to the stage, give it an instance name ("fp" used below), assign your mp4 file ("path_to/your.mp4") as the source property in the Properties panel, and select the option to autoplay as well. Place the following code in the timeline...
     fp.addEventListener(Event.COMPLETE, playAgain);
     function playAgain(evt:Event):void {
         fp.play();
To put the Flash swf file in an html page, in the Publish Settings set it to publish an swf and an html page. Publish the file an the html page will be created for you.

Patching of Embedded OS WIM Files

Similar Messages

Maybe you are looking for