Reputation Activity
-
ElmerBeFuddled got a reaction from digital john in The Little ThingsEven though I've un-checked the "Detect AntiVirus" button, when I start to make an image it still sends a pop-up 'AntiVirus detected'.
I discovered this mainly when I took the dog out for an hour, when I got back I discovered my image hadn't even started!
-
You cannot take my work, put your name on it and re-share it (this is not nsanedown)
-
ElmerBeFuddled got a reaction from RicaNeaga in Sticky Keys Prompt in unattended installAfter a couple of cups of coffee and whilst (she) was on a trip to the shop to get me some baccy, the step-daughters PC miraculously unlocked itself!
The SD learnt a lesson there. Don't use the same password to lock your PC that you was using when you were 14! She now has that sort of 'look of terror' as to what I may, or may not (not!) seen on her PC. I, of course, are remaining silent, but giving plenty of knowing smiles and winks out! Well, you have to take the mickey, don't you!
It was actually a Public Network I was trying to set in the autounattend file as opposed to a Home one. Although those registry key entries will come in very handy and a big Thanks for those!
-
ElmerBeFuddled reacted to RicaNeaga in Sticky Keys Prompt in unattended installLaughed alot about the step-daughter issues btw, what's the finale?
Also, please post here your autounnatended.xml. I have that one with the network skipped just fine, don't know why that's happening to you.
LE: Nevermind, I saw it in your second post. Here's how mine looks like:
<?xml version="1.0" encoding="utf-8"?><unattend xmlns="urn:schemas-microsoft-com:unattend"> <settings pass="windowsPE"> <component name="Microsoft-Windows-International-Core-WinPE" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <SetupUILanguage> <UILanguage>en-US</UILanguage> </SetupUILanguage> <UserLocale>ro-RO</UserLocale> <InputLocale>en-US</InputLocale> <SystemLocale>en-US</SystemLocale> <UILanguage>en-US</UILanguage> </component> <component name="Microsoft-Windows-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <DiskConfiguration> <WillShowUI>Always</WillShowUI> </DiskConfiguration> <ImageInstall> <OSImage> <InstallFrom> <MetaData wcm:action="add"> <Key>/IMAGE/NAME</Key> <Value>Windows 7 HOMEPREMIUM</Value> </MetaData> </InstallFrom> </OSImage> </ImageInstall> <UserData> <AcceptEula>true</AcceptEula> <ProductKey> <Key>RHPQ2-RMFJH-74XYM-BH4JX-XM76F</Key> <WillShowUI>OnError</WillShowUI> </ProductKey> </UserData> </component> </settings> <settings pass="specialize"> <component name="Microsoft-Windows-Security-SPP-UX" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <SkipAutoActivation>true</SkipAutoActivation> </component> <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <ComputerName>Admin-PC</ComputerName> <ProductKey>RHPQ2-RMFJH-74XYM-BH4JX-XM76F</ProductKey> </component> </settings> <settings pass="oobeSystem"> <component name="Microsoft-Windows-International-Core" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <UserLocale>ro-RO</UserLocale> <InputLocale>en-US; ro-RO</InputLocale> <SystemLocale>en-US</SystemLocale> <UILanguage>en-US</UILanguage> </component> <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <TimeZone>GTB Standard Time</TimeZone> <OOBE> <HideEULAPage>true</HideEULAPage> <HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE> <NetworkLocation>Home</NetworkLocation> <ProtectYourPC>3</ProtectYourPC> </OOBE> <AutoLogon> <Password> <Value></Value> </Password> <Enabled>true</Enabled> <LogonCount>2</LogonCount> <Username>Administrator</Username> </AutoLogon> <UserAccounts> <LocalAccounts> <LocalAccount wcm:action="add"> <Password> <Value></Value> <PlainText>true</PlainText> </Password> <DisplayName>Administrator</DisplayName> <Name>Administrator</Name> <Group>Administrators</Group> </LocalAccount> </LocalAccounts> </UserAccounts> </component> </settings></unattend>So, <NetworkLocation>Home</NetworkLocation> should do the trick and make the install process fully quiet.
Also, if you don't want the network location wizard to ever pop up, use this tweak:
Windows Registry Editor Version 5.00[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Network\NetworkLocationWizard]"HideWizard"=dword:00000001[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Control\Network\NetworkLocationWizard]"HideWizard"=dword:00000001 -
ElmerBeFuddled got a reaction from RicaNeaga in Sticky Keys Prompt in unattended installAah Haa! Issue is resolved!
It appears to happen when dotNET 4.5 slim is being installed into the virtual machine. By the use of logging when it starts and ends I've discovered it takes anything from 10 to 15 minutes to fully install with mscorsvw.exe doing its thing. Its during this time I usually nip to the loo, do a brew, grab a sarnie, have a tab or two etc.. Today I thought I'd go and stand in the garden and catch some rays.
It was then I spotted my 27 yr old step-daughter rapidly tapping the shift key!!! Oh how she laughed!!
She's off out tonight. Wonder if she'll laugh tomorrow when she discovers I've changed her log in password that she thinks I don't know!!
Now one thing I would like to know. If I set network in the autounattend file to Public as opposed to Home the install fails on any version of Win 7 I try out in VBox. Is there any way I can do this? If I try to skip choosing a network I get the window prompting me to set one when I finally get to the desktop. Any ideas?
-
ElmerBeFuddled reacted to Legolash2o in How to restore stripped out Windows Media Player feature without re-installProbably quicker and better to start with a new image. Also VLC is so much better
-
ElmerBeFuddled reacted to Etz in Donation = No AdsWondering, why I feel like an complete idiot now... :doh:
-
ElmerBeFuddled reacted to Legolash2o in Removing components a second time?Nah you don't need to select them again.
-
ElmerBeFuddled reacted to Legolash2o in [Solved] 1.50 t38 ProblemFixed, thanks.
-
ElmerBeFuddled reacted to Thiersee in Background questionsKB2533552: WTK puts this one under Silent-Installer-SFX; this patch is present under Windows-Update, even if it has been already installed.
KB2592687: WTK puts this one under Silent-Installer-SFX; for this patch to install you need KB2574819 installed (WTK puts this one in the prerequisite).
KB2603229: WTK puts this one under Silent-Installer-SFX.
Regards, Thiersee
-
@ElmerBeFuddled, .NET 3.5, and earlier, are part of Win 7, not a separate addon or install. Updates, when necessary, should also be included automatically by WU/MU without user intervention. So unless you do something specific yourself they should already be installed and active, I believe. .NET 4.0 is a separate install, and .NET 4.5, if used, should completely replace, or include, 4.0 and only 4.0. Other .NET frameworks will not be affected. As to why you still see the .4.0.3.319 folder, I haven't researched this so I'm guessing here, but I'm assuming that when 4.5 replaces 4.0 it either (1) continues to update 4.0 like 3.5 continued to update 3.0 and 2.0, or (2) puts hardlinks in the 4.0 folder, actually using the 4.5 files. The reason for doing either of these would be to handle poorly written software that checks for the availability of .NET by looking for specific files in specific folders. Bottom line, as a user, once you install 4.5 you don't have to worry anymore about updates for 4.0, you won't be offered them or see them as installed.
@sp0ilesbrat, AFAIK all mention of any .NET greater than 3.5 regards to Win Toolkit has been by a user, not by the author Legolash2o. If any change is put in place to affect the use of Win Toolkit on XP I'm sure it will be announced and probably discussed in advance.
Cheers and Regards
-
ElmerBeFuddled reacted to dareckibmw in KB2533552 Problemscreate folders: $OEM$\$$\SETUP\SCRIPTS then you put KB2533552 hotfix inside folder (SCRIPT) along with setupcomplete.cmd
save this as setupcomplete.cmd and then drop the whole thing in "sources" folder, then save it as an new .iso (I use UltraISO, best for win7, I think)
@echo off
WUSA Windows6.1-KB2533552-x86.msu /QUIET /NORESTART
-
ElmerBeFuddled reacted to dareckibmw in KB2533552 ProblemsI always integrate KB2533552 via $oem$ and setupcomplete.cmd with this code (below), it works and doesnt show up on WU anymore
WUSA Windows6.1-KB2533552-x86.msu /QUIET /NORESTART
-
ElmerBeFuddled reacted to bphlpt in Windows 7 Toolkit Question (name change)Just take out the "7" Kel, since it does Win8 as well.
Cheers and Regards
-
ElmerBeFuddled reacted to Legolash2o in Net Framework Error?Unfortunately, those errors did not tell me where the error happened, however i have discovered that code which catches errors did not work for everyone but me, so i've fixed that and from now on it will write errors like that to a text file, which i hope it will tell me where the issue is and it will be in v15.
-
ElmerBeFuddled reacted to Legolash2o in Uninstall Add-Ons once Compiled?I'm no longer live in Bridlington but in Hull at University
-
ElmerBeFuddled reacted to Legolash2o in Uninstall Add-Ons once Compiled?Those seem to be silent installers, you can either just simply delete them from the DVD root (Apps folder) which is the quickest option, you can also use Registry Hive Mounter to go to HKLM\\WIM_Software\\W7T and delete the registry key.