MrJinje

Sounds cool, will check it out later.

Paste the regedit command after all the other commands in whatever batch file you are using to automate your SFX installation. It might look something liek this. Install.cmd someapp.exe /S /V/QN regedit /s myreg.reg

Paste yur regedit command in the box "Run After Extraction" from section "Customize Basic Installer :" of this how to

question. What software are you using to create your SFX file ?

LOL, yes that's what that means and yes they will get deleted, but you do not need to do it manually (unless you really want to). Save the code as a text file and rename it something.reg and double click it.

I thought that was for XP ? Is that even supported on Windows 7 ?

regedit /s MYREG.reg pack the reg file right next to the cmd and when it expands in the temp folder it should run.

On first glance, if you are not pushing a product key, delete the <ProductKey></ProductKey> line entirely. I would assume a blank product key (in the XML) is considered "invalid".

After it does the registry stuff, start service and I think it is in RunRegistryDlls:Retrieved section name for this phase as Specialize. Starts out small screen and later goes bigger. Still the Powder puff Why had you found something else? It depends, not exactly sure what you mean by "powder puff", is that the background image with the stupid bird, which does not occur in my setup (anywhere). or is powder puff the little gif animation (firstuxres.wim) that actually isn't that bad ? (which does happen in my build on first boot). Here is a VMware movie of my install, the first reboot has just occurred and "Setup is updating Registry settings" followed by "Setup is starting services" (after a slight resize). I used to go blue image at about 30s into the video, but not sure what I changed to avoid that.

I assume cluberti meant for you to follow the link he provided. In post #7 he made this snip for XP forcing Details view.

What part are you missing. Only the background after the first reboot ?

This bright white background is killing my soul. LOL, sorry dude, disregard my post, that is some windows 7 advice, I'll have to dig a little deeper for XP

Try this No Sniffing hack and see if that doesn't work more to your liking. Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Classes\Local Settings\Software\Microsoft\Windows\Shell\Bags\AllFolders\shell] "FolderType"="NotSpecified" Better run the remove all bags as well. Further reading here turned up this.

I don't care about reducing the WIM size (that happened as well - 1.5GB), but I did remove enough to fit nicely on my 4GB DDR SSD. (install occupies 3.6GB). This was using vLite and I only removed the big/useless stuff (languages, natural language, speech, offline-help, media samples). The WIM only contains a single image if that makes a difference. That can be further reduced by using the Autounattend.xml "servicing" section to prevent installation of other items that vLite cannot remove properly. (not reducing WIM, but reducing install bloat). HINT: Use WSIM to create these settings, this is just a small sample of what it can do. <servicing> <package action="configure"> <assemblyIdentity name="Microsoft-Windows-Foundation-Package" version="6.1.7600.16385" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="" /> <selection name="MediaPlayback" state="false" /> <selection name="InboxGames" state="false" /> <selection name="WindowsGadgetPlatform" state="false" /> <selection name="TabletPCOC" state="false" /> <selection name="Internet-Explorer-Optional-x86" state="false" /> <selection name="MSRDC-Infrastructure" state="false" /> <selection name="SearchEngine-Client-Package" state="false" /> <selection name="Xps-Foundation-Xps-Viewer" state="false" /> <selection name="NetFx3" state="false" /> </package> <package action="configure"> <assemblyIdentity name="Microsoft-Windows-LocalPack-AU-Package" version="6.1.7600.16385" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="" /> <selection name="LocalPack-AU" state="false" /> </package> <package action="configure"> <assemblyIdentity name="Microsoft-Windows-LocalPack-CA-Package" version="6.1.7600.16385" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="" /> <selection name="LocalPack-CA" state="false" /> </package> <package action="configure"> <assemblyIdentity name="Microsoft-Windows-LocalPack-GB-Package" version="6.1.7600.16385" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="" /> <selection name="LocalPack-GB" state="false" /> </package> <package action="configure"> <assemblyIdentity name="Microsoft-Windows-LocalPack-ZA-Package" version="6.1.7600.16385" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="" /> <selection name="LocalPack-ZA" state="false" /> </package> <package action="configure"> <assemblyIdentity name="Microsoft-Windows-UltimateEdition" version="6.1.7600.16385" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="" /> <selection name="Microsoft-Hyper-V-Common-Drivers" state="false" /> <selection name="Microsoft-Hyper-V-Guest-Integration-Drivers" state="false" /> <selection name="Microsoft-Windows-Printing-XPSServices-Package" state="false" /> <selection name="OpticalMediaDisc" state="false" /> </package> </servicing>

Some stuff yes, other stuff no. You should check out the windows 7 keep list

Probably "C:\Windows\System32\lusrmgr.msc" but you might also want to look at. control userpasswords2 or Netplwiz.exe EDIT: Beat me to it...LOL

Attachment in post three is a multi-lingual right click shell extension version. Windows Registry Editor Version 5.00 [HKEY_CLASSES_ROOT\*\shell\runas] @="Take Ownership" "NoWorkingDirectory"="" [HKEY_CLASSES_ROOT\*\shell\runas\command] @="cmd.exe /c takeown /f \"%1\" && icacls \"%1\" /grant *S-1-5-32-544:F" "IsolatedCommand"="cmd.exe /c takeown /f \"%1\" && icacls \"%1\" /grant *S-1-5-32-544:F" [HKEY_CLASSES_ROOT\Directory\shell\runas] @="Take Ownership" "NoWorkingDirectory"="" [HKEY_CLASSES_ROOT\Directory\shell\runas\command] @="cmd.exe /c takeown /f \"%1\" /r /d y && icacls \"%1\" /grant *S-1-5-32-544:F /t" "IsolatedCommand"="cmd.exe /c takeown /f \"%1\" /r /d y && icacls \"%1\" /grant *S-1-5-32-544:F /t" S-1-5-32-544 is the well-known sid of the "Administrators" local group. So this should work as well. Dim Act : Set Act = CreateObject("Wscript.Shell") Dim Obj For Each Obj in Wscript.Arguments Act.Run("takeown /f " & Obj),0,True Act.Run("icacls " & Obj & " /grant *S-1-5-32-544:F"),0,True Next

It likely does not exist. See here at the Symantec site, they suggest using the Ghost 2003 boot disk. (or whatever version you used to create the .GHO)

MRTSTUB.EXE is not needed ? What does it do ?

I don't know about editing the .GHO files, but you can open/extract them with Norton GHO Explorer.

Known issue, see this thread.

Now I remember, it was, the EULA's. Gotta merge them inside the boot.wim before it will work. Not sure on the success ratio. More info Even more According to the second link, it will not work with Vista/2008 wim's for some reason W7/R2 do not play nice with the older wim format ???

Install WUD 2.50 then double click ULZ. want more details, read the stickies here. Afterwards, (once you've downloaded them all), you will need to integrate them (into your Install.wim) using DISM or DISM Tool™

Current WUD Windows 7 Updates lists: Here

Have you already tried imagex ? HINT: It is part of the Windows 7 AIK