MrJinje

You need to first extract the adobe flash .cab from a .wim that still has it. What's that ? You don't know how to extract packages from a .wim, try Bubbles Super Nasty SFX Extractor Tool. (written by myself and bubbles) The trick apparently is to do all this under the TrustedInstaller account so that things extract properly (don't worry, instructions included). It helps you create a package that can be re-inserted via DISM add-package command (or something similarly easy). http://forums.mydigitallife.info/threads/48325-VBScript-Aunty-Mel-s-Cheap-And-Nasty-SxS-Package-Extractor-%28Updated-2013-09-30%29/page2?p=848055&viewfull=1#post848055

What are you going to name it ?

Maybe a resource hack on spwizimg.dll bmp's 506-510

Does that prevent deletions from occurring on apps you paid for but are removed by vendors at a later date ?

Looking at the "recenv.exe.mui" en-us file on W7 winre.wim. I see this in DIALOG 107, maybe I would look in same dialog on new winre.wim. (resource hacker) 107 DIALOGEX 0, 0, 235, 120STYLE DS_SYSMODAL | DS_FIXEDSYS | DS_SETFOREGROUND | DS_CENTER | WS_POPUP | WS_VISIBLE | WS_CAPTION | WS_SYSMENUCAPTION "System Recovery Options"LANGUAGE LANG_ENGLISH, SUBLANG_ENGLISH_USFONT 8, "MS Shell Dlg"{ CONTROL "Select a language:", 236, STATIC, SS_LEFT | WS_CHILD | WS_VISIBLE | WS_GROUP, 10, 15, 215, 12 CONTROL "", 223, COMBOBOX, CBS_DROPDOWNLIST | WS_CHILD | WS_VISIBLE | WS_VSCROLL | WS_TABSTOP, 10, 30, 215, 15 CONTROL "Select a keyboard input method:", 237, STATIC, SS_LEFT | WS_CHILD | WS_VISIBLE | WS_GROUP, 10, 52, 215, 12 CONTROL "", 238, COMBOBOX, CBS_DROPDOWNLIST | CBS_SORT | WS_CHILD | WS_VISIBLE | WS_VSCROLL | WS_TABSTOP, 10, 65, 215, 15 CONTROL "&Next>", 1, BUTTON, BS_PUSHBUTTON | WS_CHILD | WS_VISIBLE | WS_GROUP | WS_TABSTOP, 121, 98, 50, 14 CONTROL "Cancel", 2, BUTTON, BS_PUSHBUTTON | WS_CHILD | WS_VISIBLE | WS_TABSTOP, 175, 98, 50, 14 }

Could use oscdimg.exe from the WAIK. http://technet.microsoft.com/en-us/library/dd799243%28v=ws.10%29.aspx Oscdimg -bC:\winpe_x86\Etfsboot.com -u2 -udfver102 C:\winpe_x86\ISO C:\winpe_x86\winpex86.isoor try the attached bootable.iso Windows_7_Bootable.7z

N/M what I posted don't work on vista LOL.

When you say 2GB do you mean decompressed size, if yes, that would translate to about 500-600MB saving on the capture.wim size.

My guess was that you had two different iso's and the x64 was volume media and the x86 was not. Not a problem, simple fix. FYI'd use the GVLK for installing/testing so that you don't waste your real activations until you are ready. Add it to your autounattend.xml http://technet.microsoft.com/en-us/library/jj612867.aspx

Not 100% sure, but last year when writing a shell extension to right click from taskbar I could not find a reg key for the mod. If taskbar is not registry based DLL injection might be the method needed, though I don't know where to start. (explorer.exe ??? - shell32 dll ??? or it's mui's ???)

Alternatively you could mount both images via dism and run the set-productkey. http://technet.microsoft.com/en-us/library/hh825157.aspx Dism /Image:C:\test\offlinex86 /Set-ProductKey:12345-67890-12345-67890-12345Dism /Image:C:\test\offlinex64 /Set-ProductKey:12345-67890-12345-67890-12345

First off let me state that I am not looking for how to call an external.vbs from a batch script, I know how to wscript/cscript. The question I am asking is how can we run native VBS code at the command line via cmd.exe arguments. For instance with powershell we have the -command "" parameter and can pass rather complex one-liners via cmd.exe. Windows Registry Editor Version 5.00[HKEY_CLASSES_ROOT\Directory\Background\shell\Open_Registry]"MUIVerb"="Open Registry""icon"="regedit.exe""Position"="Top""HasLUAShield"=""[HKEY_CLASSES_ROOT\Directory\Background\shell\Open_Registry\command]@="cmd /c start /wait /b powershell -command \"Clear-Host;$CLIPPY = PowerShell -NoProfile -STA -Command {[reflection.assembly]::loadwithpartialname('PresentationCore') | Out-Null;[Windows.Clipboard]::GetText()};$CLIPPY = $CLIPPY | Foreach-Object {$_ -replace 'HKCU', 'HKEY_CURRENT_USER'};$CLIPPY = $CLIPPY | Foreach-Object {$_ -replace 'HKLM', 'HKEY_LOCAL_MACHINE'};$CLIPPY = $CLIPPY | Foreach-Object {$_ -replace 'HKCR', 'HKEY_CLASSES_ROOT'};Set-ItemProperty -Path 'registry::HKEY_CURRENT_USER\\Software\\Microsoft\\Windows\\CurrentVersion\\Applets\\Regedit' -Name LastKey -Value $CLIPPY;regedit.exe /m;\"";Am looking for similar functionality in VBS, does such a thing exist. Is there any built-in command line vbs parser. cmd /c start /wait /b wscript -unknown "CreateObject("Wscript.Shell").Run """" & ".\DoSomething.ps1" & """", 0, False"I don't see any cscript/wscript switch to do that trick.

Nicko McBrain says: He is a big boy and understands the risk. I see no difference here than if he were to go randomly double clicking a folder full of .cmd or .vbs files which can do equal if not more damage. Anyone have the same setting for powershell.

in other words they used dism to set-productkey inside the iso (yes probably the same GVLK key). and fyi, using the generic key does not activate you. It merely allows you to bypass the prompt during installation, which I think was the point of your question. You will still be required to enter your real key later for activation. You can't. See above. Microsoft has removed that ability and now you must enter a GVLK or a real key just to install. Get used to it.

Put that GVLK key in your unattend.xml - see the example here on how to do it. <UserData> <AcceptEula>true</AcceptEula> <FullName>maxXPsoft</FullName> <Organization>Se7en_UA</Organization> <ProductKey> <Key>xxxxx-xxxxx-xxxxx-xxxxx-xxxxx</Key> <WillShowUI>OnError</WillShowUI> </ProductKey> </UserData>http://www.msfn.org/board/topic/139572-ask-your-seven-xml-here/ or you can mount your install.wim with DISM and use the set-productkey command (with the GVLK) so that it stops asking during installation. Dism /Image:C:\test\offline /Set-ProductKey:12345-67890-12345-67890-12345http://technet.microsoft.com/en-us/library/hh825157.aspx

Try a 'generic' volume license key to install. aka GVLK http://technet.microsoft.com/en-us/library/jj612867.aspx Then activate with slmgr with your regular key. slmgr.vbs -ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX

Not sure if relevant, but here a registry snip concerning UAC / Metro apps and the built-in admin account. http://forums.mydigitallife.info/threads/46105-Windows-8-1-Registry-Tweaks Windows Registry Editor Version 5.00 ; Enable Metro Apps to Work on In-Built Administrator Account with UAC Prompt Disabled (Requires Reboot) [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System] "EnableLUA"=dword:00000001 "FilterAdministratorToken"=dword:00000001 "ConsentPromptBehaviorAdmin"=dword:00000000 "ConsentPromptBehaviorUser"=dword:00000000 "PromptOnSecureDesktop"=dword:00000000

Good eye. I slapped that together pretty haphazardly. But then again, Max is entering them via a .reg file, so they will pre-exist, moot point. Was reading here, just some info for me on the appcompatflags you've been using. http://www.novell.com/support/kb/doc.php?id=7010269 Windows Registry Editor Version 5.00[HKEY_Current_User\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers]"c:\\windows\\system32\\cmd.exe"="RUNASADMIN"

Try this, it should pipe the (x86) path on x64 builds. Note: From powershell if the registry key does not exist it'll error on set-itemproperty, so we test-path beforehand to be safe. If ((Get-WmiObject -class Win32_OperatingSystem | Select-Object OSArchitecture).OSArchitecture -eq "64-bit") {$PROGS = "C:\Program Files (x86)"}else{$PROGS = "C:\Program Files"}$PROGSIf ( -Not (Test-Path 'registry::HKEY_CURRENT_USER\Software\Jinje')) {New-Item -Path 'registry::HKEY_CURRENT_USER\Software\' -Name Jinje -Force;}Set-ItemProperty -Path 'registry::HKEY_CURRENT_USER\Software\Jinje' -Name $PROGS -Value 1;#Unless I am mistaken and could have just used the new-itemproperty the whole time. Oh well getting late.Here I am using null "" variables to toggle ($OFF / $ON) for something, in case you ever wanted to switch from a mounted image to an online image. http://forums.mydigitallife.info/threads/48613-Aunty-Mel-s-Cheap-And-Nasty-SxS-File-Expander-(Updated-2013-09-29)?p=837143&viewfull=1#post837143 If ($radiobuttonOnline.Checked -eq $true){$On = " /online "}else{$On = ""} If ($radiobuttonOffline.Checked -eq $true){$Off = " /Image:" + $MountPath + "\Windows "}else{$Off = ""} and because they are toggled null, we can be lazy and send both variables into the command, knowing one of them would be blank. $labelParse.text = "cscript.exe " + $MOVE + "\sxsextract.vbs" + $DEB + $VIC + $RES + $On + $Off + $textbox1.text + " " + $textbox2.text

Hey Max, found a newer method to get feedback during scripts. Won't work in W7, but does work in W8 and above. Basically the Out-Gridview has a new parameter (-passthru) in Powershell 3.0/4.0 which adds an OK/Cancel to the window. Allows for multiple item selection and directs input back into the pipeline. Been around since last year, but I never used it 'til recently. Here is an example, it opens up a list of processes, allows you to choose a single or multiple processes, collects their names and loops through closing all the highlighted items. Probably be easy enough to drop the Get-WimInfo in place of the "Get-Process | Select-Object -Property Id,ProcessName" part of the command and the mounting bits later to generate a little GUI action. http://forums.mydigitallife.info/threads/50445-Windows-8-1-Task-Manager-Problem?p=843819&viewfull=1#post843819 $KILLPROCESS = (Get-Process | Select-Object -Property Id,ProcessName | Out-GridView -passthru -Title "Wise Guy Process Killer").ProcessName;Get-Process $KILLPROCESS | ForEach-Object -Process {Stop-Process -Id $_.ID}#

You need a new GVLK for 8.1http://technet.microsoft.com/en-us/library/jj612867.aspx Plus there is an update for your KMS host on Windows Update which should allow for 8.1 / 2012r2 activations

Here is how to do it manually. http://www.sevenforums.com/tutorials/888-quick-launch-enable-disable.html make a folder here. %userprofile%\AppData\Roaming\Microsoft\Internet Explorer\Quick Launchand create a toolbar on your taskbar.

Like trip said, it might be easier to just look at the log file and scroll to the bottom where it errors out. http://technet.microsoft.com/en-us/library/hh824819.aspx or if you have the ADK installed, you can open the WSIM and verify the XML against the install.wim

I'm sure he is busy coding, nothing to worry about. Not unless he forgets to eat and sleep, which is always a risk with coders.

In my house no part of the computer goes unused.