Kullenen_Ask

i think you don't understand the subject. Have you got Sound and Flash on work in WinPE 3? yes. i had. this is end of your question. other sentences below is another thing.

they are not for winpe. they are from windows embedded standart 7 toolkit for to developers to build their own customized operating systems. what we try to do is grab reg entries and files to fit them for to give features to winpe.

it looks like a little foolish. of course Explorer.exe.mui is needed how can you get explorer work without it. i can GUESS some files \Windows\System32\en-US\hotplug.dll.mui ----- can be need for usb automount \Windows\System32\en-US\iccvid.dll.mui ----- from the name vid for video but can be for colour too. \Windows\System32\en-US\imageres.dll.mui ----- big but need for icons. icon database. use boot.wim one, 9mb install.wim one is 18mb i think. i didnt see much difference \Windows\System32\en-US\MFC40u.dll.mui ----- needed \Windows\System32\en-US\mshta.exe.mui ----- HTA support. like something like web page \Windows\System32\en-US\objsel.dll.mui ----- need for explorer to select a file or directory. \Windows\System32\en-US\photowiz.dll.mui ----- need for images can be the file you look for \Windows\System32\en-US\sti.dll.mui ----- for sti service colour and themes \Windows\System32\en-US\sti_ci.dll.mui ----- for sti service colour and themes \Windows\System32\Macromed\Flash\Flash10e.ocx ---- flash files for flash but ocx refuse to register manually if it can only 2 files will be enough for flash \Windows\System32\Macromed\Flash\FlashUtil10e.exe ------ flash files for flash but ocx refuse to register manually if it can only 2 files will be enough for flash \Windows\System32\Magnification.dll ------ need for photo for the images can be seen in desktop control panel if i don't remember false \Windows\System32\MediaMetadataHandler.dll ------ need for photo others auido,video and media player files. some service and other files. should be one of theese mentioned. Notice:dont understand wrong. if you will put a file put mui and the file same time. don't put \Windows\System32\en-US\MFC40u.dll.mui alone without \Windows\System32\MFC40u.dll. same for other files upside too. put \Windows\System32\themeservice.dll too. some users wants aero in your build. like the last post in your topic.

Embedded packages. I installed embedded packages to embedded install.wim and backed up changes. Is it makes difference if they are same version number files and only kernel different? Can work for windows 7 updates to windows 7 install.wim or winpe updates to winpe.wim for to find changes. When a package installed using dism to an offline image it writes data to this hives. Windows/System32/config/SOFTWARE Windows/System32/config/SYSTEM Windows/System32/config/SECURITY Windows/System32/config/SAM Windows/System32/config/COMPONENTS Windows/System32/config/DEFAULT Users/default/ntuser.dat Windows/system32/smi/store/Machine/schema.dat It can be seen from dism.log. All changes to mentioned hives can be backed up and import manually to boot.wim (because packages doesn't let to install on boot.wim).i don't care to import everything and to have a closest wim, like really package imported. i want working features so only default,software and system will be mostly enough maybe sam and security too. yes. i had. ----------------------------------------------------------------------------------------------------------------- Topic: Usage of embeeded packages to add features to winpe I installed these packages i think enough for a winpe. Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-Application-UX.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-AppSupport-ComBase.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-AppSupport-ComPlus.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-AppSupport-Legacy.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-AV-Core.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-BootEnv.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-Branding-Embedded-Neutral-Package.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-DeviceFoundation.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-Diagnostics-Common.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-DirectoryServices-AD.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-DriverFoundation.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-File-Based-Write-Filter.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-File-Compression.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-Font-Western-Required.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-FS-Advanced.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-FS-Core.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-FS-RemoteClient.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-FS-SMB.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-Graphics-Platform.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-HelpEngine.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-IE-Core.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-IE-Explorer.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-IE-Foundation.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-acpipmi.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-adp94xx.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-adpahci.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-adpu320.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-amdsata.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-amdsbs.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-arc.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-arcsas.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-atiilhag.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-bthpan.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-bthspp.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-circlass.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-compositebus.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-djsvs.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-dot4.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-dot4prt.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-ehstorcertdrv.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-ehstorpwddrv.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-elxstor.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-gameport.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-hdaudio.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-hdaudss.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-hidbth.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-hidir.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-hpsamd.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-iastorv.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-igdlh.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-iirsp.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-image.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-iscsi.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-ks.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-kscaptur.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-ksfilter.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-lsi_fc.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-lsi_sas.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-lsi_sas2.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-lsi_scsi.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-mdmbtmdm.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-megasas.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-megasr.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-mf.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-msclmd.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-msdv.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-multiprt.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-net1k32.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-net1q32.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-net1y32.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-net8187bv32.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-net8187se86.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-netbc6.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-netgb6.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-netimm.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-netirda.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-netk57x.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-netl160x.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-netl1c86.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-netl1e86.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-netl260x.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-netmyk01.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-netnvmx.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-netr28.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-netr28u.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-netr73.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-nettun.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-netvfx86.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-netvg62.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-netvwifibus.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-netw5v32.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-netxe32.cab" *** Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-nfrd960.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-ntprint.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-nvraid.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-nv_lh.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-pcmcia.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-prnge001.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-qd3x86.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-ql2300.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-ql40xx.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-rawsilo.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-rndiscmp.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-scrawpdo.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-sdbus.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-sensorsalsdriver.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-sisraid2.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-sisraid4.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-stexstor.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-sti.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-tape.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-tpm.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-transfercable.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-tsprint.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-ts_generic.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-ts_wpdmtp.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-umpass.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-usbvideo.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-vhdmp.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-vsmraid.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-v_mscdsc.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-wave.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-wceisvista.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-wdmaudio.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-wdma_usb.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-windowssideshowenhanceddriver.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-winusb.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-wnetvsc.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-wpdcomp.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-wpdfs.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-wpdmtp.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-wpdmtphw.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-ws3cap.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-wsdprint.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-wstorflt.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-wstorvsc.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-wudfusbcciddriver.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-wvmbus.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-wvmbusvideo.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-INF-wvmic.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-Installers-MSI.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-Interface-Explorer.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-International.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-LogonDesktopBackground.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-Lpk-Setup.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-MDAC.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-Media-Support.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-MediaPlayer.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-NetFx20.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-NetFx20Client.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-Network-Security-Firewall.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-Networking-Base.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-Networking-Bluetooth.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-Networking-Devices.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-Networking-Diagnostics.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-Networking-EAP.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-Networking-Foundation.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-Networking-IAS.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-Networking-NAP.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-Networking-NASC.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-Networking-QoS.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-Networking-RAS.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-Networking-Services.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-Peer-To-Peer-Networking.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-Photos-Viewer.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-PowerManagement.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-PremiumCodecs-DOLBY-AC3-AudioEncoder.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-PremiumCodecs-MPEG2-Encoder.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-PremiumCodecs-MPEG3.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-PremiumCodecs-MPEG4.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-PremiumCodecs-WMV.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-Printing.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-Ramdisk-ROOTENUM.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-RegistryFilter.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-RPC.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-Security-Base.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-Security-Credentials.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-Security-EFS.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-Security-ForApplications.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-Security-RMClient-V1-API.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-Security-SecureStartUp.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-Security-TPM.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-Shell-Accessories.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-Shell-Basic.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-Shell-Core.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-Shell-Foundation.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-SystemControlPanel.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-SystemManagement-AdminTools.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-SystemManagement-GroupPolicy.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-SystemManagement-MMC.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-SystemManagement-Utilities.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-SystemManagement-WMI.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-TapiClient.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-TerminalServicesClient.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-usbboot.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-VSS-Foundation.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-VSS-Service.cab" Dism /image:C:\a /Add-Package /PackagePath:"C:\z\WinEmb-Wireless.cab" tracker home page http://www.evansprogramming.com/dloads/tr2623c.exe sample fix examples: *remove all HKEY_LOCAL_MACHINE\SOFTWARE\ HKEY_LOCAL_MACHINE\SYSTEM\ keys because they are my machines keys used when i backup but _00 prefixed ones are inside wim keys. *change all C:\ values to X:\ values * remove all runas interactive user keys *i don't know if embedded packages corresponds to windows 7 ones inside winsxs folder msil_iehost_b03f5f7f11d50a3a_6.1.7600.16385_none_52e0df7cc45bdbe4 ------>embedded msil_iehost_??????????????????????????????????????????????????? ------>win 7 *delete all HKEY_LOCAL_MACHINE\SOFTWARE_00\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageIndex\WinEmb-FS-Core~31bf3856ad364e35~x86~~0.0.0.0] such keys. Component Based Servicing keys not usefull for us. *i don't know if embedded packages corresponds to windows 7 ones inside winsxs folder HKEY_LOCAL_MACHINE\SOFTWARE_00\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-peertopeergraphing_31bf3856ad364e35_none_c6c7b5666ea7c729\6.1] ok???????? if they are same numbers everything will be perfect. if they are not we wont loose much. *HKEY_LOCAL_MACHINE\SOFTWARE_00\Microsoft\Windows\CurrentVersion\WINEVT\Publishers\ keys are important for functions but don't think anybody cared until now. i think we can use all. all until now is a 15 minutes operation to fix. and the most difficult part at services if we don't have related sys files. and a services doesn't works as we expected we wont boot any. we should compare with boot.wim and should make start values to on demand for our wim to boot as much as we can sample [HKEY_LOCAL_MACHINE\SYSTEM_00\ControlSet001\services\amdsbs] "Start"=dword:00000000 to [HKEY_LOCAL_MACHINE\SYSTEM_00\ControlSet001\services\amdsbs] "Start"=dword:00000003 we don't want it to give problem. thats all i can hope. if it works we should have all functions as we added like dism. i had a boot.wim 2 base wim imported this reg file when booted it boots without problem. i should be very very lucky i didnt checked any and at first attempt it boots perfect wowwww.

i found a very old software that doesn't developed anymore. name is "Tracker" http://www.evansprogramming.com/tracker.asp Of course will need modifications as changing D:\ values to X:\ values and such changes. Of course i can use dism to integrate packages. what you mean with it? HKEY_LOCAL_MACHINE\COMPONENTS means components.hiv root all will need manual fixes that will take 5 min only. can be seperated to different hives reg files. also all new file and folder structure can easly be copied with all files. how kind of errors you get? i used dism in windows 7 enterprise dvd sources folder to integrate package. not embedded. all hve changes can be backed up. i manually selected important hives in example not all of them but all can be backed up.

I found a way to keep tracking of dism package installation process with all regitry and file changes. It can give opportunity to have most of thing to get work in winpe environments. it is different from joakims pull registry entries from manifest files method. This method gives all changes when a package integrated with dism. good part it gives as reg files. I don't have time for test now but advanced users can try with given.

your usb power not enough to get your disk work properly.

Wooow. You listed all mutual problems that everybody wants to fix in such a short questionare. I want to explaine all i can from my side of vision. 1. How can I integrate the drivers necessary for video, lan, etc. (Specifically for Virtual PC)? - Previously i was integrating with dism. I saw that it creates some increasing number folder structure in windows folder and puts drivers in it (Maybe only for scsi drivers or maybe all type of drivers.) Probably adds drivers paths to registry for search for too. It's advantage is drivers will be different folders that you can see seperately. For me disadvantage is if you add many drivers folder number increase too many. Here is microsoft page explain how to add drivers to an offline wim. http://technet.microsoft.com/en-us/library/dd799289(WS.10).aspx If you search from internet you can find better explanations to use dism to inject drivers also with automized batch files. http://www.msfn.org/board/topic/113964-add-vmware-network-drivers-failed/ Now i don't use dism to integrate drivers. Just the time of writing also i am working on some wireless driver problems too. The way i use i manually put inf files to inf folder, sys files to sys folder, some dll stuff if it exist to system32 folder. For cat files you can put in inf folder or catroot folder. In Setupapi.dev.log it writes for catalog files that "Driver package does not contain a catalog file, but error is ignored in WinPE." i think it means no need for cat files. Setupapi.dev.log file is the main place for to check driver related problems. It is in inf folder after you boot in your Winpe. It will say you which files absent and can understand all driver load process. In winpe drivers can be in windows\inf,system32\drivers folder distributed AND Windows\System32\DriverStore\FileRepository folder in folder collected. Same drivers i think so will not take double space. Also in winsxs folder there are such driver folders but i belive they are not used in winpe. Driver loading secuence is it reads the inf file copies driver files to folders they should be and adds registry stuff from inf file. In our winpe all drivers will be in it's folders. Here is some code from my Setupapi.dev.log SourcePath - [X:\windows\TEMP\{15cd5da9-6090-4975-e04d-1b242890a82e}] flq: SourceFile - [netrasa.inf] flq: Flags - 0x00000000 flq: {_commit_copyfile} flq: CopyFile: 'X:\windows\TEMP\{15cd5da9-6090-4975-e04d-1b242890a82e}\netrasa.inf' flq: to: 'X:\windows\System32\DriverStore\Temp\{3a598889-617c-3343-4ec0-d046c162df77}\SET7722.tmp' flq: MoveFile: 'X:\windows\System32\DriverStore\Temp\{3a598889-617c-3343-4ec0-d046c162df77}\SET7722.tmp' flq: to: 'X:\windows\System32\DriverStore\Temp\{3a598889-617c-3343-4ec0-d046c162df77}\netrasa.inf' flq: {_commit_copyfile exit OK} flq: {_commit_copy_subqueue exit OK} flq: {_commit_file_queue exit OK} dvi: Set selected driver complete. dvi: {Plug and Play Service: Device Install for ROOT\MS_NDISWANBH\0000} ump: Creating Install Process: DrvInst.exe 15:47:53.564 ndv: Infpath=X:\windows\INF\oem0.inf ndv: DriverNodeName=netrasa.inf:Msft.NTx86:Ndi-Mp-Bh:6.1.7600.16385:ms_ndiswanbh ndv: DriverStorepath=X:\windows\System32\DriverStore\FileRepository\netrasa.inf_x86_neutral_096721844805d01f\netrasa.inf ndv: Building driver list from driver node strong name... From my very past experinces that years before from the time of pebuilder and windows xp i was using infcachebuild.exe to fix copy files sections. it removes all copy lines and temp folder don't get used also driver load process time decreases. From that time to now vista and windows 7 entered to our life and i don't know driver inf's chnaged and infcachebuild.exe works complately ok in windows 7 drivers. When used on all windows\inf folder "i think" not works fully ok with all inf's but doesn't give problem too. Also FileRepository folder infs should be changed with same infs. I couldn't get video drivers to load in winpe else then standart vga. I got Error: dispci.dll: OnInstallDevice: Not allowing install of video device. For other drivers i should say that i don't know the exact way of integrating drivers. also when you don't use the infcachebuild it doesn't effects to much. I also use vmware to test all and never get need to add vmware specific drivers in build. After i get more experience about wireless drivers on my friends 2 netbooks i can share my findings. As the wimb suggested in it's build to copy vwifibus.sys to inf folder i succesfully get work a broadcom wireless card to work after i copy a sys file to in inf folder. Strange part i fixed it's inf file with infcachebuild. It should't try to copy from inf folder to drivers folder but it wants. Maybe need more manual modification at inf file. At my real system tests wireless and hdaudio drivers wants to be in inf folder. other most of the other drivers loaded successfully. Need more real systems to test. Also i saw that battery icon in system tray work fully ok in netbook. Andddd. Infcache builder only puts ";" front of "copyfiles" sections. but when you look inside inf files there are [SourceDisksNames] 3426=windows cd [SourceDisksFiles] hdaudio.sys = 3426 when you comment them off with ";" or remove it,it doesn't want sys fle in inf folder and loads ok. 2. I have seen many posts (specifically on this site) saying that you have .NET 2.0 working, but with all the posts, I'm not sure what to do. I already have a working version using WinPE 2.0, but can't seem to figure out *exactly* what to do with WinPE 3.0 and Make_PE. -.Net is complately useless from my side and my experiences was only for to see if i can get it work or not. I manually copied related files and registry settings. Get related servives to work but i can not say it fully works. i didn't check with different kinds of software. Best way if you need it do as ludo did. Get msi service to work and install from setup in winpe. You will need a big strach space. I can't say anything about other scripts because i didn't used any of them 3. When I bring up Google using IE 8, it displays very weird and doesn't show images. Some other sites do display the images. -From my opinion it is because they use custom made classes.reg. i described many times how to make full classes.hiv manually exactly same of windows 7 classes registry key. shared my opinions about it with developers but i can't force anybody to use my way. Also developers wants to have multilanguage support. I think to have full classes not allow to get it multilanguage. I used same turkish classes on english build and didn't see a problem but maybe can be it is very big key. 4. How do I integrate Flash? -Install flash player inside of your winpe from offline installer. Backup your classes.hiv. Import offline. for 3 and 4 the main approach for them is to register needed dll files at boot time with commanline. "also for ie to register ieproxy.dll." it is very time consuming and the way i don't suggest ever. Boot process should be very clean that only should be explorer as shell and no more. also user shouldn't need to register any dll manually after boot. Should be a single classes.hiv that has every dll registered in it. 5. Using the "My Computer" desktop shortcut, when I format my attached virtual drive, and create it as a C:, it doesn't show. It only shows when I use the "Explorer" shortcuts. -It is the easiest to solve. if you have right HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer key it will always automatically mount also can use my computer icon for browse.

path C:\Make_PE3 boot.wim is copied for you if you select the Drive with Setup DVD as Source. maybe at cmd but not at gui. is it not possible if we select at gui setup dvd path. it mounts install.wim to a temporary location. copy needed files. unmounts. then it copy boot.wim from selected path. after mounts boot.wim again. add files.

it is not works with system user as far as we know for now. When you will boot your winpe it will be system user after boot. as i understand all sessions are terminal service sessions. maybe system user is not because log off button works in administrator user only. only working button in explorer start menu is change user button as system user. do you have a winpe that explorer enabled? my latest experiments i saw that you will need userenv.dll,logoncli.* and logonui.exe files in system32 folder for change user(not sure other need files but sure about theese). you need sessionenv, themes and seclogon(maybe not really need but prefered)service to work. also dwmcore.dll need for aero. registry keys for user profiles is below, you need to add it too. this keys will tell the system that there are administrator, guest ... users exist and their profile paths is ... I can advise a few more files to add too. UIAutomationCore.dll, themecpl.dll, themeservice.dll, themeui.dll, thumbcache.dll Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE_00\Microsoft\Windows NT\CurrentVersion\ProfileList] "ProfilesDirectory"=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,44,00,72,\ 00,69,00,76,00,65,00,25,00,5c,00,55,00,73,00,65,00,72,00,73,00,00,00 "Default"=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,44,00,72,00,69,00,\ 76,00,65,00,25,00,5c,00,55,00,73,00,65,00,72,00,73,00,5c,00,44,00,65,00,66,\ 00,61,00,75,00,6c,00,74,00,00,00 "Public"=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,44,00,72,00,69,00,76,\ 00,65,00,25,00,5c,00,55,00,73,00,65,00,72,00,73,00,5c,00,50,00,75,00,62,00,\ 6c,00,69,00,63,00,00,00 "ProgramData"=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,44,00,72,00,69,\ 00,76,00,65,00,25,00,5c,00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,00,44,00,\ 61,00,74,00,61,00,00,00 [HKEY_LOCAL_MACHINE\SOFTWARE_00\Microsoft\Windows NT\CurrentVersion\ProfileList\S-1-5-18] "Flags"=dword:0000000c "State"=dword:00000000 "RefCount"=dword:00000001 "Sid"=hex:01,01,00,00,00,00,00,05,12,00,00,00 "ProfileImagePath"=hex(2):25,00,73,00,79,00,73,00,74,00,65,00,6d,00,72,00,6f,\ 00,6f,00,74,00,25,00,5c,00,73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,\ 5c,00,63,00,6f,00,6e,00,66,00,69,00,67,00,5c,00,73,00,79,00,73,00,74,00,65,\ 00,6d,00,70,00,72,00,6f,00,66,00,69,00,6c,00,65,00,00,00 [HKEY_LOCAL_MACHINE\SOFTWARE_00\Microsoft\Windows NT\CurrentVersion\ProfileList\S-1-5-19] "ProfileImagePath"=hex(2):58,00,3a,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,77,\ 00,73,00,5c,00,53,00,65,00,72,00,76,00,69,00,63,00,65,00,50,00,72,00,6f,00,\ 66,00,69,00,6c,00,65,00,73,00,5c,00,4c,00,6f,00,63,00,61,00,6c,00,53,00,65,\ 00,72,00,76,00,69,00,63,00,65,00,00,00 "Flags"=dword:00000000 "State"=dword:00000000 [HKEY_LOCAL_MACHINE\SOFTWARE_00\Microsoft\Windows NT\CurrentVersion\ProfileList\S-1-5-20] "ProfileImagePath"=hex(2):58,00,3a,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,77,\ 00,73,00,5c,00,53,00,65,00,72,00,76,00,69,00,63,00,65,00,50,00,72,00,6f,00,\ 66,00,69,00,6c,00,65,00,73,00,5c,00,4e,00,65,00,74,00,77,00,6f,00,72,00,6b,\ 00,53,00,65,00,72,00,76,00,69,00,63,00,65,00,00,00 "Flags"=dword:00000000 "State"=dword:00000000 [HKEY_LOCAL_MACHINE\SOFTWARE_00\Microsoft\Windows NT\CurrentVersion\ProfileList\S-1-5-21-3149542145-3322839065-4058237693-500] "ProfileImagePath"=hex(2):58,00,3a,00,5c,00,55,00,73,00,65,00,72,00,73,00,5c,\ 00,41,00,64,00,6d,00,69,00,6e,00,69,00,73,00,74,00,72,00,61,00,74,00,6f,00,\ 72,00,00,00 "Flags"=dword:00000000 "State"=dword:00000304 "Sid"=hex:01,05,00,00,00,00,00,05,15,00,00,00,01,33,ba,bb,19,80,0e,c6,fd,ca,e3,\ f1,f4,01,00,00 "ProfileLoadTimeLow"=dword:00000000 "ProfileLoadTimeHigh"=dword:00000000 "RefCount"=dword:00000001 at my latest post i gave a link about whats going on at change user process. explore it and add files in there. Change user process log file in a winpe. It is very usefull for people who knows to use it. Can see which files and what keys used. Opening,closing session and login. Usage: Procmon.exe /OpenLog Logfile.PML http://hotfile.com/d...ogfile.rar.html Note: Make_pe3 was supporting change user at latest version. Only need to get themes service to work for get aero.

very close to a success build. tested under turkish xp with without waik and turkish mounted install.wim. gui used. *dism looks like it works fully ok. it works more slower then other builds it probably mean it using new dism. no problem. *looks like files copied in wim. didn't check every file but seems all there. but *again it opens setup as shell. *no winpeshl.ini inside wim and only wpeutil in startnet.cmd. *reg files didn't merged. i checked inside wim. classes not imported. in cmd: *it doesn't select setup dvd drive as source. it selects only mounted wim. it was selecting and try to build with setup dvd drive previous versions. again reg file errors and 2 dism errors. Error DISM DISM Manager: PID=1532 Failed to create unique image session lock name for DISM located at 'C:\Make_PE3\win7pe_x86\mount\Windows\System32\Dism\dismprov.dll'. - CDISMManager::CheckSessionAndLock(hr:0x8007013d) Error DISM DISM Manager: PID=1532 Failed to create the image session lock for location: C:\Make_PE3\win7pe_x86\mount\Windows\System32\Dism - CDISMManager::CreateImageSession(hr:0x8007013d) Error DISM DISM.EXE: Could not load the image session. HRESULT=8007013D Error DISM DISM.EXE: Unable to start the servicing process for the image at 'C:\Make_PE3\win7pe_x86\mount'. HRESULT=8007013D i think it works ok with C:\Make_PE3\AIK_Tools\x86\Dism\ folder but not with C:\Make_PE3\win7pe_x86\mount\Windows\System32\Dism\ can not you automize copying of boot.wim, bootmgr, boot folder to makepe3 folder? is it difficult to put a copy command in a batch file?

i am trying to solve reboot-shutdown issues in winpe3 environment. start menu butons doesn't work. After i read your topic i thought maybe it can be usefull to solve shutdown issues in winpe with explorer enabled shell too. it is not a real system. because of it is live environment there is not a possibility to take the data after reboot. i could only take theese. can it be possible to find missing files only with that data? i have related topic in winpe section.

Can somebody give a look to my etl files and tell whats going on. Startmenu shutdown buttun doesn't work http://hotfile.com/dl/53213899/9f4d508/Test.rar.html http://rapidshare.com/files/405495929/Test.rar mirror

what is the connection of licensing issues and video functionality? if it be possible to use this to create a thin client for use in a corporate environment it will be illegal and need to be removed. looks more that you search for a way to block the content because of licensing issues sorry if we understand your question wrong? maybe you should ask in a different way.

i think it means it is forbidden to share this program here. i don't know who decide what can be shared or not and in which criteriums that is decided. there is lots of same software around and they live for years. what should he wrote in his readme? it is for educations purposes only? it is same lie for every software. i don't know anybody care it. if anybody wants to use it commercial nothing can stop him. it is same for every software. crack tools writers write same too. if you have knife you can use it for to cut bread or to kill a person. it will be possible if the users conscience open license terms allow him to use also an internet explorer, a paint, a calculator will enough for his commercial desires. maybe we should stop developing that we are in the limit. i am already stopped

And can you test with DVD or Win7 drive as source instead of your mounted install.wim how will it be? i don't see such option. i am used to foreign language issues. you always say it will detect language and copy right files but i never get it work without modify changing en-us values to tr-tr values inside txt files. If you can help me one time me to built it in xp without waik without problem. i will give you are prize and will work on a feature you want to integrate to your build with files and registry settings i cant work on a built that i cant build. testing cmd. first select 1 and selected source after selected 2 it takes very long time with cmd. had C:\Make_PE3\PE3_mod\WIN7_add\x86\Windows\System32\wlansvc.dll Not Found error. selected continue to build. base is turkish setup dvd. Error: Unknown Return Code 317 PE3-SOFTWARE_CUSTOM.reg added to HKLM\PE3-SOFTWARE and lots of from that 317 return codes. Error DISM DISM Manager: PID=2184 Failed to create unique image session lock name for DISM located at 'C:\Make_PE3\win7pe_x86\mount\Windows\System32\Dism\dismprov.dll'. - CDISMManager::CheckSessionAndLock(hr:0x8007013d) Error DISM DISM Manager: PID=2184 Failed to create the image session lock for location: C:\Make_PE3\win7pe_x86\mount\Windows\System32\Dism - CDISMManager::CreateImageSession(hr:0x8007013d) Error DISM DISM.EXE: Could not load the image session. HRESULT=8007013D Error DISM DISM.EXE: Unable to start the servicing process for the image at 'C:\Make_PE3\win7pe_x86\mount'. HRESULT=8007013D Warning DISM DISM Provider Store: PID=536 Failed to Load the provider: J:\sources\WimProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

Edit: This one seems to work at dism part. i think i found the problem. when i put boot.wim from directly setup dvd it works at dism part builts ok. but when i test iso and wim size ok but no shell inside wim and other files. starts setup. maybe same language fixes need in add_files.txt to change en-us to tr-tr. will try that. there is C:\Make_PE3\PE3_mod\WIN7_add\x86\Windows\explorer.exe. it collects ok. but not explorer.exe inside boot.wim when i export boot.wim 2 with boot flag only one image inside wim it gives same error.

Please check version of used Dism.exe and wimgapi.dll in folder Make_PE3\AIK_Tools\x86\Dism it copy by itself. wrong copy? it is not. i checked C:\Make_PE3\AIK_Tools\x86\Dism\wimgapi.dll 6.1.7600.16385 C:\Make_PE3\AIK_Tools\x86\Dism\Dism.exe 6.1.7600.16385 why it complain about C:\windows\system32\wimgapi.dll in error if it uses C:\Make_PE3\AIK_Tools\x86\Dism\wimgapi.dll ?

standalone Make_PE3.exe 17.898.950 bayt not works yet (latest) can we return to version post #124. i think i am the only man on the earth that use this on a xp base system and i can copy bootmgr and boot.wim at least want dism to work and build it. why don't you have a previous builds on your ftp? don't they give you a enough space. maybe you can put them as Make_PE3_010810.exe Make_PE3_220710.exe with time date for to easy access prvious builds. it was working like this until now. it try to use c:\windows\system32\wimgapi.dll.

i am mounting install.wim to a folder with gimagex using vista imagex and apis. it works 10 times faster then dism. did everything about bootmgr and boot.wim no problem there. when it start build it gives dism errors. previous versions works. i select option one from gui as always. pe3 or 7pe different things??? possible reason dism should work from its working directory. probably your batches calls it from a different directory.

sorry but it gets worse then ever with my every comment i dont understand why. maybe better to be calm. i use imagex vista version and it was working until now without problem. now it complain for new version dism and dism errors. trizet your batches also doesnt support xp as base operating system isnt it?

i use full setup files inspite of reduced number of boot files. as all the same files will be optimized it will not get iso bigger, only file number will be big. did you put winnt.sif file to the ROOT\W03A\i386 folder too? maybe help

@Kullenen_Ask when you said it doesn't copy file "bootmgr" do you mean you build using Wimb's Make_PE3 or using My_7PE.cmd? because you replying to wimb's post but quoting my readme file, it is confusing me i use Wimb's Make_PE3. because he used your cmd files as base thats why i quote your read me. if something wrong at yours can be wrong at his too. isn't it? all i want to learn that why both of you don't use setupdvd boot.wim as option to copy wim. because xp users will not have hidden boot partition to copy wim.

do you use oem custom build notebook? they modify windows setup files. i don't know what to say. is it a clean install from a retail dvd? then i am false. sorry. my operating system is xp. i investigated that long time before and i remember like that. didnt test short time before. it is stupid to have setup packages in winre that you can not install windows from system boot hidden partition. why the boot.wim 1 is for then? it should be copied to system boot partition at install as a winre. you install windows 7 from its own dvd from inside winpe. not from the setup packages integrated in winre.??? not from x:\windows\setup.exe or x:\sources\setup.exe should be from dvddrive\setup.exe when you boot in winre. open cmd prompt. write "setup.exe" and installed windows? where will it search for install.wim. probably in x:\sources\install.wim that doesnt exist in 1gb partition. if we think the windows setup exports wims at install. why it should exports boot.wim 2 modify files and change shell from setup to recovery inside wim (mount,change shell,dismount,export) if it can only export boot.wim 1 without changing shell as recovery(export and bootflag)?

With default settings, My_7PE will look for Winre file on Recovery folder then it will look for bootmgr files from local computer. If you have bootmgr in System Reserved partition, it will temporary assign drive letter to copy necessary files. Optionally you can use Winre/bootmgr files from system repair cd or Windows installation DVD. from your read me explains why there is no bootmgr in my build.