Windows 7 embedded 64 repair CD creation. Cannot find path specified.

Well I've made some progress with this... I've managed to extract the boot.wim from a windows 7 64 pro repair cd that I created from another pc, and am using dism.exe to inject the RAID driver.
It's not working for whatever reason, but I do have the repair CD at least working to the point where I can click "add driver" and manually add the driver from a usb stick. I'd really like to incorporate this on the repair cd but for whatever reason the dism driver injection isn't working.

Alright I figured it out! I had to change an option in using dism and it worked like a charm.
So if anyone cares, or would like to know here is what I did:

Windows 7 Embedded 64 - Wanted to create a repair CD with RAID drivers preloaded in order to avoid the necessity of an additional diskette or usb stick/drive.
Problems: Windows 7 repair cd creation does not auto-include 3rd party drivers. Windows 7 embedded cannot properly create repair CD.

Solution:

• Create a windows 7 repair CD on a windows 7 64 professional environment. Might be able to download this as well since the files should be the same.
• Once the CD is created, view the contents and copy them to a folder like c:\windows repair cd
• Install Windows WAIK
• Under the windows repair cd there is a folder named sources. Inside is a file named boot.wim. Copy this file to c:\Temp
• Create a folder c:\temp\mount and c:\temp\drivers
• Copy your driver .inf file to c:\temp\drivers - locating the driver you need can be tricky, refer to your manufacturer for help locating it.
• Open Deployment and Imaging Tools Environment.
• Use the following DISM commands: dism.exe /mount-wim /wimfile:C:\temp\customboot.wim /index:2 /mountdir:C:\temp\mount
• dism /image:"C:\Temp\mount" /add-driver /driver:"C:\temp\drivers\[YOUR DRIVER FILENAME HERE]"
• dism /unmount-wim /Mountdir:C:\Temp\mount /commit
• Once it is finished unmounting you now have an updated boot.wim file in c:\temp. Simply replace boot.wim in your c:\repair cd folder and burn a new repair cd with the updated file

The burning of the CD may be tricky, I don't know as I host the entire CD on an internal drive fit my custom setup. I'm able to boot from it by modifying the BCD. This isn't 100% fail safe since it's hosted on the drive, if the drive fails you need to use an external cd. I do this more for convenience than for hard drive failure, in case PC os installation is completely wrecked but the HD is in tact I can restore to the factory installation without any additional media required.

SIW2 said:

I have been doing that for years.

Full size pe maker here:

Win 7 winpemaker

You need a client x64sp1 dvd, so your PRO dvd will be fine.

Simple pemaker here, also for client versions, x64 or x86 no dvd required.

new versions of simple winpe maker

I'm not sure I understand how this relates to creating a windows 7 repair cd with custom drivers. It seems like it creates a bootable iso that boots into a custom WinPE environment that supports third party imaging software, and other useful tools, and automatically includes needed drivers if you create it on the target machine. This is really freaking cool actually, thanks for sharing. I'll definitely check it out for internal use.

But I just want the simple windows repair cd for the purpose of restoring an image and nothing more so I can avoid using third party software at all. Mission was accomplished as I listed above.

I dont' know why you couldn't create your System Repair Disk but you can also use the installation media for your version to repair. Both allow you to inject drivers on either of these screens in the very rare case that a storage controller driver is not in the disk:

gregrocker said:

I dont' know why you couldn't create your System Repair Disk but you can also use the installation media for your version to repair. Both allow you to inject drivers on either of these screens in the very rare case that a storage controller driver is not in the disk:

Don't know why, Windows Embedded would fail to create a repair disk every time. And they do allow you to inject drivers on that screen but you need additional hardware to load the driver like a floppy or a usb stick. The way I did it injected with DISM eliminates the need for this.

Essentially I made my own recovery partition but it wasn't working for my RAID setups. Now they do and all is well, plus it was fun to learn about wim files.

Well the driver needs to be supplied somehow so stick or disk are best. Floppies are outmoded and as useless and inadvisable for Win7 as RAID.