simurqq

Hi there, I will appreciate if you can help me find correct registry entries that would help (i) to tweak "Folder Options" and (ii) apply tweaks to all folders ("Apply to Folders") and users on computer. I've tried googling and found some tweaks (see: excerpt below) which allegedly would serve for the purpose but none of them work. [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Advanced\Folder] "Type"="group" "Text"="@shell32.dll,-30498" "Bitmap"=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,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,73,00,\ 68,00,65,00,6c,00,6c,00,33,00,32,00,2e,00,64,00,6c,00,6c,00,2c,00,34,00,00,\ 00 "HelpID"="shell.hlp#51140" [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Advanced\Folder\AlwaysShowMenus] "Type"="checkbox" "Text"="@shell32.dll,-30557" "HKeyRoot"=dword:80000001 "RegPath"="Software\\Microsoft\\Windows\\CurrentVersion\\Explorer\\Advanced" "ValueName"="AlwaysShowMenus" "CheckedValue"=dword:00000001 "UncheckedValue"=dword:00000000 "DefaultValue"=dword:00000000 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Advanced\Folder\AlwaysShowMenus\Policy] [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Advanced\Folder\AlwaysShowMenus\Policy\AlwaysShowClassicMenu] [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Advanced\Folder\AutoCheckSelect] "Type"="checkbox" "Text"="@shell32.dll,-30522" "HKeyRoot"=dword:80000001 "RegPath"="Software\\Microsoft\\Windows\\CurrentVersion\\Explorer\\Advanced" "ValueName"="AutoCheckSelect" "CheckedValue"=dword:00000001 "UncheckedValue"=dword:00000000 "DefaultValue"=dword:00000000 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Advanced\Folder\DesktopProcess] "Type"="checkbox" "Text"="@shell32.dll,-30507" "HKeyRoot"=dword:80000001 "RegPath"="Software\\Microsoft\\Windows\\CurrentVersion\\Explorer\\Advanced" "ValueName"="SeparateProcess" "CheckedValue"=dword:00000001 "UncheckedValue"=dword:00000000 "DefaultValue"=dword:00000000 "HelpID"="shell.hlp#51079" [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Advanced\Folder\DesktopProcess\Policy] [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Advanced\Folder\DesktopProcess\Policy\SeparateProcess] They don't work because there is no difference between default Win7 install (on Virtual PC) and the one that I use on my rig - values, keys are the same... So no effect at all!!! Thank you very much in advance!!!

Back in days I used to use nLite, Winaddons.com was one of my favourites. Since I moved to Se7en, I wonder whether it's possible to use the same addons for Win7 (SVCPACK method)?!? The other question is: What do you guys recommend for Win7 addons - methodology, links, guides?!? Thank you!

Hi there, Can you guide me to more info on this topic, i.e. pre-installing addons and image capturing? Also, do I need to do this at Audit stage of unattended install? Thank you!!!

Yeah, same for me... I ain't pro but I think <InputLocale> under WindowsPE is different and serves for the purpose of setting initial setup environment for Windows install while <InputLocale> under oobeSystem is to kinda "please" user experience - hence initializes and sets up things as user wants to see on the screen on the very final stage of setup... Just my 2 cents BUT I would be very grateful to hear more about differences of SAME settings and their functions at different passes... E.g., OEM info can be used at several locations throughout setup - the same values BUT under different passes. Can anybody enlighten me WHY it's designed as such?!?

I got it working for the cmd to stay open but it does not show any text for it. Still trying to figure this part out. I will post back when I get closer to working it out. Hi gotenks98, Any success with displaying text in cmd window? Also, I'm not much comfortable with batch files yet but I use a slightly modified version of your SetupComplete.cmd in the first post as follows: @echo off setlocal enableextensions disabledelayedexpansion (set CDROM=) 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:\Autounattend.xml set "CDROM=%%i:") if not defined CDROM goto :eof start /wait cmd /c wusa.exe %CDROM%\Updates\IE9-win7.msu /quiet /norestart /log:ie9logfile.txt start /wait cmd /c wusa.exe %CDROM%\Updates\IE9-Windows6.1-KB2586448-x64.msu /quiet /norestart /nobackup start /wait cmd /c wusa.exe %CDROM%\Updates\IE9-Windows6.1-KB2624899-x64.msu /quiet /norestart /nobackup start /wait cmd /c wusa.exe %CDROM%\Updates\Windows6.1-KB2533552-x64.msu /quiet /norestart /nobackup start /wait cmd /c %CDROM%\Updates\Silverlight.exe /q del %0 It works OK (sort of...) and installs KB2533552, Silverlight and IE9 but without cumulative update KB2586448 and hotfix KB2624899. I can see empty CMD windows upon initialization of SetupComplete.cmd but since there is no text/progress bar, it's difficult to judge which app or update is being installed. My update history shows that installation of KB2624899 was cancelled (see: logfile attached). However, "About Internet Explorer" page looks as below. So, here are my guesses: (i) Update KB2586448 is already inserted into IE9 since I use the latest "IE9-win7.msu" and update agent doesn't bother with installing it on top of already-installed package; (ii) Update agent refuses to install hotfix KB2624899 because it's applied on special cases only. However, support article states that: .Now, I'm really confused!!! Since, as the image shows, I have it installed already... And the last question: Is it possible to somehow suppress WUSA.exe information window during "Setupcomplete" ?!? Thank you! WindowsUpdate.zip

Thank you, maxXPsoft! Your link helped a lot... I noticed that I actually had defined <InputLocale> in 2 passes - "specialize" and "oobeSystem". As <InputLocale>0409:00000409</InputLocale> in "specialize", and as <InputLocale>0409:00000409; 042c:0000042c; 0419:00000419</InputLocale> under "oobeSystem". I think that was the problem... So, I have removed the following section from "specialize" and left <InputLocale> values under "oobeSystem" only and this solved the problem! <component name="Microsoft-Windows-International-Core" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <InputLocale>0409:00000409</InputLocale> <SystemLocale>ru-RU</SystemLocale> <UILanguage>en-US</UILanguage> <UserLocale>en-US</UserLocale> </component>

Thank you both!!! I guess I somehow managed to solve the problem by: (i) completely removing packages from Autounattend.xml (ii) dropping Autounattend.xml onto a separate USB stick. After that unattended setup completed successfully! Dunno why but whatever I do, setup refuses to read Autounattend.xml directly from the root of installation DVD. Actually, it reads it and follows instructions partially (judging from "skipped" windows during setup) but pops up with the above message at some point after expansion of Windows files. Anyway, I'll stick to the above scheme for now, and will share future problems/achievements with you here... Now, let me ask a completely different question which occurred during the last successful installation... I cannot implement different keyboard input languages. As you can see from Autounattend.xml (see: my previous post above), the XML contains the following: <settings pass="oobeSystem"> <component name="Microsoft-Windows-International-Core" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <InputLocale>0409:00000409; 042c:0000042c; 0419:00000419</InputLocale> <SystemLocale>ru-RU</SystemLocale> <UILanguage>en-US</UILanguage> <UserLocale>en-US</UserLocale> </component> But in fact, on first logon to Desktop I cannot see English, Azeri & Russian set as keyboard input locales on the language bar. Checked it on Regional settings page - the same thing, only en-US is defined. System locale (Russian) is OK though... Input locales - no changes! Any advice?!? Maybe I need to apply these settings at different pass? Thank you!

I'm posting my question {problem} here since I found the topic most suitable for asking answer file questions and am trying to avoid bloating the forum space. Sorry if it's the wrong place... Below is my AutoUnattend.xml. It's a slightly modified version of the file posted by "Rick Steele". I've only hushed up the product key and my name in it, plus removed or added sections I use often. Win7 SP1 (x64) image - which I use for testing on VirtualBox - recognizes it OK in the root of DVD and all goes fine until expansion of files is complete. After that the setup pops up with the following message: "Windows could not apply settings during pass [offlineServicing]". I've rearranged the order of passes, removed pass [offlineServicing] completely, re-checked the sections which I modified in original XML... tens of times - to no avail yet!!! Googling didn't help either - I found only this article but the symptoms described there are not applicable to my file since both Setup.exe and "Microsoft-Windows-Foundation-Package" under "servicing" are the same version, i.e. 6.1.7601.17514... Any help is much appreciated!!! Autounattend.xml

Thank you guys for your prompt replies!!! @Tripredacus: Technet articles instruct to include "unattend.xml" containing setup instructions for a package or a driver into the WIM image. But is it possible NOT to include XML into the image and simply put "autounattend.xml" into the root of setup DVD? This would be very useful since (i) mounting/unmounting INSTALL.WIM takes too long; and (ii) I would be able to regularly update my update package and drivers offline untouching "install.wim". Also, Technet recommends to apply updates at offlineServicing pass but I think "setupcomplete.cmd" activates at oobeSystem. Right? And one more question: what do you mean by this: @gotenks98: Can you advise how to turn off system restore in "Autounattend.xml"? Or, turn it off using a registry tweak just before running "setupcomplete.cmd"? Thank you!

Still learning unattended W7 setup... So far I have created "autounattend.xml" which runs ok on my VM. Now, in order to move to the next step I need your recommendations on installation of Windows updates (hotfixes), drivers and my favourite applications AFTER basic W7 setup is complete. Btw, I don't intend to use any R7Lite-kind of apps to manipulate install.wim, etc. - only Windows AIK tools for now... So, I guess one of the options to achieve this is through a so-called "setupcomplete.cmd" looking just as below (code snippet taken from another thread): @echo off setlocal enableextensions disabledelayedexpansion (set CDROM=) 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:") if not defined CDROM goto :eof start /wait %CDROM%\Updates\IE9-Windows7-x64-enu.exe /passive /norestart /update-no start /wait wusa.exe %CDROM%\Updates\AMD64-all-ie9-windows6.1-kb2530548-x64.msu /quiet /norestart /nobackup start /wait wusa.exe %CDROM%\Updates\AMD64-all-ie9-windows6.1-kb2559049-x64.msu /quiet /nobackup /norestart start /wait wusa.exe %CDROM%\Updates\AMD64-all-windows6.1-kb2533552.msu /quiet /norestart /nobackup start /wait %CDROM%\Updates\AMD64_X86-all-silverlight.exe /q del %0 Now the questions are: (1) Shall I prefer "setupcomplete.cmd" to insertion of files through "WSIM // Packages" option into "Autounattend.xml"? (2) How to successfully install drivers in unattended W7 setup environment? Any methods or guides available?!? (3) I got more than 200 hotfixes (.MSU) for W7 SP1 (from SoLoR's update pack) stored on my USB drive. Considering the number of files, HOW do I know (i) which switch (/quiet, /norestart, etc.) must be used in "setupcomplete.cmd" with a particular KBxxxxxx.exe and (ii) whether I need to restart Windows after a specific hotfix is installed? Thank you very much in advance!!!

Thanks a lot for prompt reply! Sorry for being a PITA but if I understand you right, e.g., if I integrate the following two files into Win7 ISO (using either RT7Lite or Onepiece's Integrator): IE9-Windows6.1-KB2559049-x64.msu (hotfix for IE9) Windows6.1-KB982861-x64.msu ("top level" installer for IE9) Windows will chose the installer first and only then the hotfix regardless of the order the files are listed? In other words, (i) Windows will NOT make a mistake in choosing the "right" file for installation; and (ii) there is NO need to worry about hotfix listing in either of the above integration tools?

Thanks!!! What you say is true about superseding updates (e.g., KBxxxxxx-v2.exe vs. KBxxxxxx-v3.exe) but I am more interested to know about the dependencies between hotfixes. Is there any rule of thumb?

Sorry, I couldn't find the answer in forums but I always wondered IF the install order of Windows 7 updates matter when compiling Win7 ISO using RT7Lite or Onepiece's Integrator?!? I want to use one of these tools - they both provide an option to move CAB files up and down in the list but not sure whether moving them up or down will change anything during Windows installation? The other reason to ask this question is when I use Windows' native updater, it installs updates in order different from the listed items which means there IS a background rationale for installing Windows updates and usually it does NOT depend on KB number (the higher number = the latest release). Thank you!!!

You need to use Rt Se7en Lite Beta 2.6.0 64-bit: http://www.rt7lite.com/downloads.html But is it possible to use Rt Se7en Lite Beta 2.6.0 64-bit on Win7 with SP1 MSDN edition? I don't want to slipstream SP1 since it's already done by MS... Thanks!

I remember, there was a topic full of XP registry tweaks for Explorer and IE. Any chance for Windows 7 regtweaks? Thank you for help!!! Rustam

Thank you very much, maxXPsoft - both for your reply and sticky! I'm in there Will check back soon, if got smth to ask - if you don't mind, guys! Cheers and all the best from Baku!

Hi all, Thanks to these forums I've been very successful with Windows XP SP3 unattended installation. The time changed and now I'm face to face with Windows 7. The question simple: Could you please direct me step-by-step through the useful/practical unattended threads?!? There are so many of them that I get confused sometimes... Where should I start with?!? I am eager to learn and to read as much as possible! So, please don't hesitate to help! Regards,

I'm confused - it asks for a houseparty.com login email (email of my host?) in order to get the free subsription. But I've never had a host in my life WTF?!?

Noone to answer?!?

As the title reads, that's the question I face when I want to copy & replace default notepad.exe found in the System32 folder with notepad2.exe renamed to notepad.exe. A pop-up message says I cannot replace the system file with mine since it's protected. It was possible to edit some registry entries in XP, and the problem would have been solved... Unofrtunately, I didn't find any "SFCQuota" entry/key in Windows 7 registry. My system is Windows 7 x64. Anybody to help?!? Thank you! RUSTAM

Anyone with answer?!? 65 views and no replies...

Hi there, I'm quite new to Windows 7, not to say that I've never used neither it nor Vista before. However, I've gone quite well making an unattended CD/DVDs for my Windows XP. As far as I can see, the deployment of Windows 7 in unattended environment (is this correct wording?) is quite cumbersome compared to Win XP. And I know that cluberti and some other guys are working on a "polished" version of the Unattended Guide for post-XP systems incl. Windows 7. But for the start I would like to know how can I start making unattended installation of Windows 7 x64 for me?!? Which tools should I use, where can I find useful information (a sort of a guide or smth)?!? I will highly appreciate your help, guys! Thank you!

Thanks to strel and his regular updates on the first page, I've decided to make my own contribution here to make the life easier for those who find .NET integration (particularly the editing of _SNMsynth.ini file) difficult. Below is MY OWN understanding - explained in a layman terms - of how this file should be edited to get successful results for different scenarios, based on strel's instructions. His instructions is a must-read before posting here. Although the description inside .INI is self-explanatory, based on my own experience, I hoped this post will make the things easier for lazies like me. This info is for English version of XP only! Users of systems with different languages must download separate language packs. strel and other gurus, please correct me if I'm wrong. Again, this in NO WAY compares to strel's full explanation of the process and reflects my own understanding of the integration process only! So, here we go: SCENARIO 1 Goals: - to make a merged installer which contains .NET 1.1, 2.0 SP2, 3.0 SP2 and 3.5 SP1. - to apply all regular hotfixes for the above. - to avoid possible error messages in Event Viewer after Windows startup. - optional: to avoid installation of Firefox ClickOnce addon - number of "_SNMsynth.cmd" runs: 1 Solution: 1) Read "INSTRUCTIONS" section to know which files are required to start integration and download them as instructed. 2) Download the following files and put ALL of them together with files mentioned at point 1 inside a single folder: .NET 1.1 Redistributable Package NDP1.1sp1-KB867460-X86.exe NDP1.1sp1-KB928366-X86.exe .NET 3.5 SP1 Redistributable Package NDP20SP2-KB958481-x86.exe NDP30SP2-KB958483-x86.exe NDP35SP1-KB958484-x86.exe 3) Edit "_SNMsynth.ini" as follows (without my comments inside the code): PROCESS_DNF1=YES ; builds installer with .NET 1.1 PROCESS_DNF2= PROCESS_DNF35_DNF2=YES ; builds installer with .NET 2.0 SP2 portion of .NET 3.5 SP1 redistributable package PROCESS_DNF35_DNF3=YES ; builds installer with .NET 3.0 SP2 portion of .NET 3.5 SP1 redistributable package PROCESS_DNF35_DNF35=YES ; builds installer with .NET 3.5 SP1 PROCESS_DNF3_RGBRAST=YES PROCESS_DNF3_WINIMAGING=YES PROCESS_DNF3_MSXML6=YES PROCESS_DNF3_XMLPSSC=YES DNF_FF_ADDON=NO PROCESS_LNG_DNF1=NO PROCESS_LNG_DNF2=NO PROCESS_LNG_DNF35_DNF2=NO PROCESS_LNG_DNF35_DNF3=NO PROCESS_LNG_DNF35_DNF35=NO ADDON=YES MERGE_FRAMEWORKS=YES SILENT=YES COMPRESSION_RATIO=HIGHER 4) Run "_SNMsynth.cmd" and wait until the merged .NET installer is ready. NOTE: Make sure you use RunOnceEx method with this scenario to avoid resulting Event Viewer errors at the end of installation. To use partial (!) SVCPACK method or to slipstream driver packs which require installation of .NET-dependent applications like ATI Catalyst Control Panel into Windows installation disc (more info @ DriverPacks.NET), please use Scenario 2 below. SCENARIO 2 Goals: - to make separate installers for i) .NET 1.1 and 2.0 SP2; ii) 3.0 SP2 and 3.5 SP1. - to apply all regular hotfixes for the above. - to avoid possible error messages in Event Viewer after drivers' installation and at Windows startup. - optional: to avoid installation of Firefox ClickOnce addon - number of "_SNMsynth.cmd" runs: 2 Solution: 1) same as at point 1 of Scenario 1 2) same as at point 2 of Scenario 1 3) For the first run, i.e. to make a separate merged installer for .NET 1.1 and .NET 2.0 SP2, edit "_SNMsynth.ini" as follows: PROCESS_DNF1=YES ; builds installer with .NET 1.1 PROCESS_DNF2= PROCESS_DNF35_DNF2=YES ; builds installer with .NET 2.0 SP2 portion of .NET 3.0 SP2. PROCESS_DNF35_DNF3= PROCESS_DNF35_DNF35= PROCESS_DNF3_RGBRAST=YES PROCESS_DNF3_WINIMAGING=YES PROCESS_DNF3_MSXML6=YES PROCESS_DNF3_XMLPSSC=YES DNF_FF_ADDON=NO PROCESS_LNG_DNF1=NO PROCESS_LNG_DNF2=NO PROCESS_LNG_DNF35_DNF2=NO PROCESS_LNG_DNF35_DNF3=NO PROCESS_LNG_DNF35_DNF35=NO ADDON=YES MERGE_FRAMEWORKS=YES SILENT=YES COMPRESSION_RATIO=HIGHER Note: Optionally you can download NetFx20SP2_x86.exe to build a merged installer for .NET 1.1 + 2.0 SP2. This is advantageous for those with weak systems, if you don't want to wait long until the silent maker extracts the 2.0 SP2 portion out of 3.5 SP1, as shown above. In this case you need to replace "PROCESS_DNF35_DNF2=YES" with "PROCESS_DNF2=YES". 4) Run "_SNMsynth.cmd" and wait until the merged .NET installer is ready. 5) For the second run, i.e. to make a separate merged installer for .NET 3.0 SP2 and .NET 3.5 SP1, edit "_SNMsynth.ini" as follows: PROCESS_DNF1= PROCESS_DNF2= PROCESS_DNF35_DNF2= PROCESS_DNF35_DNF3=YES ; builds installer with .NET 3.0 SP2 PROCESS_DNF35_DNF35=YES ; builds installer with .NET 3.5 SP1 PROCESS_DNF3_RGBRAST=YES PROCESS_DNF3_WINIMAGING=YES PROCESS_DNF3_MSXML6=YES PROCESS_DNF3_XMLPSSC=YES DNF_FF_ADDON=NO PROCESS_LNG_DNF1=NO PROCESS_LNG_DNF2=NO PROCESS_LNG_DNF35_DNF2=NO PROCESS_LNG_DNF35_DNF3=NO PROCESS_LNG_DNF35_DNF35=NO ADDON=YES MERGE_FRAMEWORKS=YES SILENT=YES COMPRESSION_RATIO=HIGHER 6) Again, run "_SNMsynth.cmd" and wait until the merged .NET installer is ready. NOTE: This scenario requires that you use SVCPACK method first to install the merged installer for .NET 1.1 + 2.0 SP2 at T-13/T-12, and only then apply RunOnceEx method to run the installer for .NET 3.0 SP2 + 3.5 SP1. Applies to both scenarios: 1) If you want to add an uninstall button to .NET Framework Assistant 1.0 add-on for Firefox, download NDP35SP1-KB963707-x86.exe as well. Put "DNF_FF_ADDON=YES" if you want to install this optional fix for Firefox. Caution: If you include Firefox ClickOnce addon ("DNF_FF_ADDON=YES"), before running the compiled .NET installer through either of SVCPACK or RunOnceEx methods, make sure that you edit respective .inf or .cmd files so that Firefox has priority in the list, i.e. is installed first! As recommended by strel, if you choose to install the Firefox addon, the script makes you apply KB963707 to build installers since the last version it's mandatory to use "DNF_FF_ADDON=YES" because KB963707 contains important fixes for the Firefox addon. 2) Since the LAST FOUR STRINGS are self-explanatory and do not have a direct impact on integration process, I just show my own edits here but you may change them to "NO" or "YES" as you like. 3) If you use OncePiece's post-SP3 update pack v2.7.0 for Windows XP, it already contains updated MSXML (KB954459 and KB960380-v2 which supersedes KB954459) and you install it before 3.0 during Windows setup, you don't need to include MSXML in 3.0 installer (PROCESS_DNF3_MSXML6=NO). That's it for now! Don't know, may be other scenarios are also possible to derive out of strel's recommendations but I use the above two in particular with no side-effects yet. Feel free to comment on this post! Hope this helps!

Thank you mate! But what does "Time to RMA" mean?