Mr_Smartepants

The clue would be in how the ISO is mastered at the end. Apparently, this is a known problem with ISO tools like PowerISO (UltraISO is unaffected) where the UEFI boot files are replaced by BIOS boot files as a default. I'm willing to bet that W7T is using Etfsboot.com as the default El Torito boot sector file for the ISO master which would make it non-bootable on UEFI systems. The AIK tool OSCDIMG is also unaffected, though requires designating the boot file. I use it in my tool with the following: REM (On UEFI: -bC:\winpe_x86\Efisys.bin) (On BIOS: -bC:\winpe_x86\Etfsboot.com)IF /I "%arch%"=="UEFI" (SET "bootfile=EFISYS.BIN") ELSE (SET "bootfile=ETFSBOOT.COM")IF /I EXIST "%src%\boot\%bootfile%" (SET "srcb=%src%\boot") ELSE (ECHO No valid boot file found to build ISO. & GOTO EXIT)"%OSCDIMG%" -b"%srcb%\%bootfile%" -u2 -h -m -l"%iso-name%" "%src%" "%outputDir%\%iso-name%.iso" Source: http://technet.microsoft.com/en-us/library/hh824847.aspx

Check your PM over at RyanVM's.

It didn't integrate because it's not a driver. A driver consists of a .inf file combined with a .sys and possibly .dll files. It's an Image Color Management (ICM) file used for color correction. http://en.wikipedia....olor_management

What you need to be careful of with the 2.5" Passport series is that they no longer stick a SATA-USB converter board in a case with a standard SATA drive. Their USB controller is soldered directly onto the drive itself, so you can't remove the drive and connect it directly to a PC via SATA anymore. If the drive fails, your data recovery bill just doubled because of that. Don't use it as your ONLY backup. I follow the 3-2-1 backup solution. 3 backups of critical data. 2 different backup media (HDD/Tape/Online/DVD/etc.) 1 of the backups is off-site (online/cloud/mom's house/ etc.)

Create a new folder with the name: GodMode.{ED7BA470-8E54-465E-825C-99712043E01C} That's it.

My point was that the 45MB language pack the OP selected will only integrate into the install.wim, NOT the boot.wim. The boot.wim language modifications need to come from (in his scenario) the following directory: As pointed out in the link I posted, certain other languages (not his) also require the winpe-fontsupport-xx-yy.cab in order to display the setup info in the right font. Also need to use the /gen-langini to recreate the correct language listings for setup. In the screenshots the OP posted, there is no indication that the language-specific WinPE packages were integrated. If these aren't integrated, then during setup the only available language to select would be "English". That's all I meant. :-)

Looks like you didn't integrate any of the PE Setup language packs. The boot.wim requires very special handling for language integration. Instructions: Walkthrough: Add Multilingual Support to Windows Setup (WAIK): http://technet.microsoft.com/en-us/library/dd799268(WS.10).aspx

For RVMI to use the addon the filename must contain the word "addon". So you must have downloaded from the first link (nlite only). The RVMI-compatible file is the second link. Verify MD5 hashes with the first post. Try integrating this pack with an update pack only (no other addons), then test. If it works, then move on to other addons.

Ignore my post. I just downloaded the current update .iso from http://support.microsoft.com/kb/913086 and it only contains the updates released in Aug. I thought it was a cumulative repository of all updates UP TO that month. Stupid M$! :ranting:

Would it not be easier (legally) to just create a utility (batch script, vbs script, java script, .NET, or whatever) to extract the contents of a Win7.iso (w/SP1) to a working folder, then extract the Win7 updates from the other .iso (http://support.microsoft.com/kb/913086) and use DISM to integrate the updates into each image and effectively rebuild the original into an updated "vanilla" Win7.iso? I'm not talking about Win7Toolkit (which is infinitely more versatile!) but something super-simple that a user can download both .iso files, run the script, then 2 hours later be presented with a vanilla Win7 updated disc? I've already done something similar for a company (code protected by NDA or I'd release it here) and the entire codebase is less than 1000 lines. My early work from last year is here: http://forum.driverp...pic.php?id=5199 Just another line-of-attack to achieve the same result.

Yes, this is a known problem. I integrate it post-install with Add-to-iso\sources\$oem$\$$\Setup\scripts\setupcomplete.cmd @ECHO off & setlocal EnableDelayedExpansion SET "LOGFILE=%systemdrive%\install.log" for %%i in (C D E F G H I J K L M N O P Q R S T U V W X Y Z) do if exist %%i:\sources\install.wim set CDROM=%%i: ECHO>>"%LOGFILE%" 2>>&1 Found CD-Rom as drive %CDROM% :PROCESSOR :: Detect OS bit-ness on running system. Assumes 64-bit unless 64-bit components do not exist. SET "ARCH=64" IF NOT EXIST "%SystemRoot%\SysWOW64\cmd.exe" ( IF NOT DEFINED PROCESSOR_ARCHITEW6432 SET "ARCH=32" ) ECHO>>"%LOGFILE%" 2>>&1 System architecture is %ARCH% bit. ::Begin hotfix install :Hotfix-install ECHO>>"%LOGFILE%" ...................... ECHO>>"%LOGFILE%" 2>>&1 Installing required HotFix updates IF "%ARCH%"=="64" ( WUSA %CDROM%\updates\Windows6.1-KB2533552-x64.msu /quiet /norestart >>"%LOGFILE%" 2>>&1 ) ELSE ( WUSA %CDROM%\updates\Windows6.1-KB2533552-x86.msu /quiet /norestart >>"%LOGFILE%" 2>>&1 ) ::all processing finished, delete used files, and EXIT:: :CLEANUP IF EXIST %windir%\Setup\scripts RD /S /Q %windir%\Setup\scripts >nul endlocal DEL /F /Q %0% >nul

I downloaded the drivers again from the Logitech site and compared the files between the installer and the webcam driverpack. Yes, there are missing files. I'll see about fixing these over at driverpacks.net

Are you asking about the presence of the log entries themselves? Or are there actual errors (popups, install errors, etc.) associated with the log entries? Can you post a screenshot of the error?

No.Because "quite" is not "quiet". You need to use EITHER /quiet OR /passive, not both. Use /? to see ALL the switches.

For .NET 4.5 I use: dotnetfx45_full_x86_x64.exe /passive /norestart

Outstanding! Thank you.

Looks like ADK went final. Good catch.

The boot.wim only contains 2 images both are PE-mode framework: Install mode, Recovery mode. The install.wim contains the actual OS images that are extracted to the target HDD during Install mode.

For those that want to add the .NET installer and updates to their Win7 .iso, here's what I do. 1) Make the following folder structure on your .iso. You can use whatever folders you want, but you'll need to adjust the below code accordingly. %source_iso%\updates\NET45 %source_iso%\updates\NET45\32 %source_iso%\updates\NET45\64 (Where %source_iso% is the path to where your source files are kept.) 2) Put the dotnetfx45_full_x86_x64.exe file in the \NET45\ folder. Put any .NET 4.5 .exe updates (when released) into the appropriate \NET45\32 or \NET45\64 folders. 3) Add this code to your %source_iso%\sources\$oem$\$$\Setup\scripts\setupcomplete.cmd @ECHO off & setlocal EnableDelayedExpansion SET "LOGFILE=%systemdrive%\install.log" for %%i in (C D E F G H I J K L M N O P Q R S T U V W X Y Z) do if exist %%i:\sources\install.wim set CDROM=%%i: ECHO>>"%LOGFILE%" 2>>&1 Found CD-Rom as drive %CDROM% :PROCESSOR :: Detect OS bit-ness on running system. Assumes 64-bit unless 64-bit components do not exist. SET "ARCH=64" IF NOT EXIST "%SystemRoot%\SysWOW64\cmd.exe" ( IF NOT DEFINED PROCESSOR_ARCHITEW6432 SET "ARCH=32" ) ECHO>>"%LOGFILE%" 2>>&1 System architecture is %ARCH% bit. :NET-Framework-45 ECHO>>"%LOGFILE%" ...................... ECHO Installing .NET 4.5 Framework & ECHO>>"%LOGFILE%" 2>>&1 Installing .NET 4.5 Framework %CDROM%\updates\NET45\dotnetfx45_full_x86_x64.exe /passive /norestart >>"%LOGFILE%" 2>>&1 ECHO Installing .NET 4.5 updates & ECHO>>"%LOGFILE%" 2>>&1 Installing .NET 4.5 updates FOR %%X IN ("%CDROM%\updates\NET45\%ARCH%\*.exe") DO ( "%%X" /passive /norestart >>"%LOGFILE%" 2>>&1 ECHO>>"%LOGFILE%" 2>>&1 Executed %%X ) ::LAST entry! All processing finished, delete used files, and EXIT:: :CLEANUP IF EXIST %windir%\Setup\scripts RD /S /Q %windir%\Setup\scripts >nul endlocal DEL /F /Q %0% >nul In this way you can drag & drop .NET updates into your .iso whenever they're released and keep it up to date with minimal effort. This isn't as compact as Rick's repack, but you can keep it updated yourself as needed.

The only drivers that should be considered for integration into boot.wim are what M$ classifies as "boot-critical" drivers. Namely Mass-Storage and SOME Chipset drivers. Nothing else. More info: http://support.microsoft.com/kb/2686316

During the PE stage of Win7 install, after the install.wim has been extracted to the target drive, the OS is still in an "offline" state, so dpinst wouldn't be effective. I wonder if the first boot phase can be interrupted before the setupcomplete.cmd phase for driver injection into the now "online" OS? I'd be very interested to know how this can be achieved! *Edit This article has lots of driver-related info for both PE and OS loads. http://support.microsoft.com/kb/2686316

I accomplish this same goal by adding the call to my SAD2 script to the sources\$oem$\$$\Setup\scripts\setupcomplete.cmd @ECHO off & setlocal EnableDelayedExpansion SET "LOGFILE=%systemdrive%\install.log" for %%i in (C D E F G H I J K L M N O P Q R S T U V W X Y Z) do if exist %%i:\sources\install.wim set CDROM=%%i: ECHO>>"%LOGFILE%" 2>>&1 Found CD-Rom as drive %CDROM% REM :: Snip... :: :Drivers Start "" /max /separate %comspec% /c %CDROM%\SAD2\DP_Install_Tool.cmd /s ::all processing finished, delete used files, and EXIT:: :CLEANUP IF EXIST %windir%\Setup\scripts RD /S /Q %windir%\Setup\scripts >nul endlocal DEL /F /Q %0% >nul :EOF This process takes place after the main install is complete but prior to the first login.

That's surprising since I use RDP all the time to log into my Home Server from Win7 Home Premium. I don't remember doing anything special. It was just there.

OK, I tried it in VM on both 32 & 64 bit Win7 and your repack works fine. When using /ai there is zero feedback on install process (truly silent). Is there a different switch that provides a progress bar and updated definitions?

I have a clean install of Win7 x64 installing in VM now. I'll try it when it's done and report back.