WPI start before all addons and cmd files in Synchronous has install c

[coucou]

Hi,

I've prepared an unattended Win7 SP1 with WPI v8.1.0 and everything works just fine

However, I noticed since always, that WPI start installing the progs before all addons and cmd files in Synchronous (Autounattend.xml) has installation completed.

Is there anyhow to correct that?

Regards

[myselfidem]

Yes, I use the option to wait before WPI installs the programs. You can choose the time you want!

Launch WPI.exe and select the General options: you will see Inside useroptions.js:

// General tab

NumCols=1;

// ---

Timer=true;

Seconds=120;

StartBeepAtSecs=10;

[coucou]

TNX myselfidem.

I knew that and already tested it., without success.

In fact, I get the time delay (10 minutes). The problem is that with or without the delay, when the first WPI screen appear some addons start installing, especially VC++.

Regards

[ricktendo]

You could use Autounattend.xml to launch wpi instead of setupcomplete.cmd

[coucou]

You could use Autounattend.xmlto launch wpi instead of setupcomplete.cmd

That what I'm doing in SynchronousCommand Order 7 Autounattend.xml via CDVD-Switcher.exe. CDVD-Switcher.exe is an AutoIt script I wrote to enable me passing from the first DVD (Win7) to the next DVD (progs), then it launch WPI.

BTW, in my Autounattend.xml, SynchronousCommand Order 6, there is a batch file MyTweaks.bat which launching a MyTweaks.reg (>70 tweaks). I noticed that many tweaks are not applied allthoug they were tested working.

Do you think if I launch that MyTweaks.bat file as RunOnce/RunOnceEx all the registries will be applied?

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx\MyTweaks] 
"MyTweaks"="c:\Windows\Setup\scripts\MyTweaks.bat"

Regards

Edited May 26, 2011 by coucou

[myselfidem]

You can use SetupComplete.cmd to add your registry Tweaks!

Set the Tweaks registry inside the same folder: $OEM$\$$\Setup\Scripts

Using RunOnceEx with SetupComplete.cmd:

@echo off
SET KEY=HKLM\Software\Microsoft\Windows\CurrentVersion\RunOnceEx
REG ADD %KEY%\001 /V 1 /D "REGEDIT /S %systemroot%\Setup\Scripts\Tweaks.reg" /f

You can also add inside your Autounattend.xml file to all SynchronusCommands:

<FirstLogonCommands>

<SynchronousCommand wcm:action="add">

<RequiresUserInput>false</RequiresUserInput>

Edited May 26, 2011 by myselfidem

[coucou]

TNX myselfidem for yr help.

1) This will be added as "order 1" RunOnceEx\001.

@echo off 
SET KEY=HKLM\Software\Microsoft\Windows\CurrentVersion\RunOnceEx 
REG ADD %KEY%\001 /V 1 /D "REGEDIT /S %systemroot%\Setup\Scripts\Tweaks.reg" /f

If other RunOnceEx\001 already exists, it will be replaced?

Is there anyhow to automatic increment the last RunOnceEx order number?

If no automatic increment , what if I put REG ADD %KEY%\1000 Do it still run?

2) What does mean <RequiresUserInput>false</RequiresUserInput> ?

3) A part of my registries need to be "Run As Administrator". What to modify inside the following batch file?

@ECHO OFF
ECHO.
REGEDIT /S "%systemroot%\Setup\Scripts\MyTweaks.reg"
EXIT

Regards

Edited May 26, 2011 by coucou

[coucou]

Hi myselfidem

I find that nircmd.exe from nirsoft can "Run As Administrator" easily... But it not solve the problem.

On reflection, I noticed that the problem is NOT (or not only) run elevate. It's the Full Control Permissions for Administrators not cheked Allow.

I opened a new topic for that HERE

Regards

[myselfidem]

To try to answer quetions:

1) the swith /f remove the value if it exists and the value will be replaced with the new one!

You can use inside command prompt: add reg /? t o see explainations.

The execution is carried out with order number!

I think you can use: REG ADD %KEY%\1000 to execute the last reg add!

2) In fact with your Autounattend.xml, you don't need: <RequiresUserInput>false</RequiresUserInput> ; value true or false, because your account is Administrator!

Default value is : false

Extract: Unattented Windows Setup Reference for Windows 7.chm

RequiresUserInput

RequiresUserInput specifies whether the first logon command launches a dialog that requires input from the user.

After Windows® Welcome, the "Preparing Your Desktop" screen appears for up to two minutes. This screen prevents users from interacting with the first logon commands, and is intended to efficiently run the logon commands that do not require user input.

If a first logon command requires user input, end users may be forced to wait up to two minutes before they can see the desktop. After this delay, they can interact with the user interface that requires their input. You can use the RequiresUserInput setting to reduce this delay.

3) Your are Admistrator but some Tweaks needs a reboot to see the changes!

It seems the problem is with some Addons!

Edited May 27, 2011 by myselfidem

[coucou]

3) Your are Admistrator but some Tweaks needs a reboot to see the changes!

It seems the problem is with some Addons!

TNX for replying.

Although I'm Administrator, I've NOT the Full Control Permissions for Administrators Allow checked for the following regs. Test it by yourself and you'll see. (see impost and image HERE)

; Remove Control Panel from the Windows 7 Explorer Navigation Panel
[HKEY_CLASSES_ROOT\CLSID\{26EE0668-A00A-44D7-9371-BEB064C98683}\ShellFolder]
"Attributes"=dword:a0900004

;--------------------------------------------------------------------------------
; Remove Favorites from the Windows 7 Explorer Navigation Panel
[HKEY_CLASSES_ROOT\CLSID\{323CA680-C24D-4099-B94D-446DD2D7249E}\ShellFolder]
"Attributes"=dword:a9400100

In fact these Tweaks needs a Reboot or Log off to see the changes. But, you get also a return message by the registry editor.

without the Full Control Permissions

with the Full Control Permissions

I confirm that to apply these registries I need the Full Control Permissions for Administrators Allow checked.

I'll appreciate if you can help with that

Regards

[coucou]

Finally I got success

HERE