1 reply to this topic

[icnocop]

Hello.

The DirectX and DotNet Addon Packs are not working correctly with /unattend for some reason.

Windows XP Pro SP3

Here is my scenario:

1. unattended install of xp pro with sp3 integrated\slipstreamed

This works without problems.

2. cmdlines.txt will add an entry in HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx to launch WPI

This works without problems.

3. WPI will automatically install VMware Tools (unattended)

This works without problems.


4. WPI will automatically launch autopatcher.exe to update the machine with post SP3 updates:

"%wpipath%\\install\\apup_WinXP\\autopatcher.exe" /nolicense /unattend /noreboot /log /report /verbose /recommended /answerfile:"%wpipath%\\install\\apup_WinXP\\apup_WinXP.aaf"

This works without problems.


5. WPI will automatically launch autopatcher.exe to update the machine with DirectX:

"%wpipath%\\install\\apup_DirectX\\autopatcher.exe" /nolicense /unattend /noreboot /log /report /verbose /recommended /answerfile:"%wpipath%\\install\\apup_DirectX\\apup_DirectX.aaf"

What happens here is autopatcher will get launched, scan for modules, but then immediately exit. DirectX does not get installed.

apup_DirectX.aaf contains:
WINDOWS_COMPONENTS_PARENT
DX

The autopatcher.log file contains:

AutoPatcher 5.6 loaded the filesystem.

AutoPatcher was run with the following commandline arguments: /nolicense /unattend /noreboot /log /report /verbose /recommended /answerfile:"d:\WPI\install\apup_DirectX\apup_DirectX.aaf"
Detected English (1033) Windows XP Professional Service Pack 3

System Components:
	Internet Explorer: 7.0.5730.13
	Windows Media Player: 11.0.5721.5145
	.NET Framework: 
	Windows Installer: 4.5.6001.22159
	DirectX: 4.09.00.0904
	MSN/Live Messenger: 

Office Components:
	Microsoft Word: 
	Microsoft Excel: 
	Microsoft PowerPoint: 
	Microsoft Outlook: 
	Microsoft Access: 
	Microsoft Project: 
	Microsoft Publisher: 
	Microsoft OneNote: 
	Microsoft FrontPage: 
	Microsoft InfoPath: 
	Microsoft Visio: 
	Microsoft SharePoint Designer: 
	Microsoft Groove: 

AutoPatcher was instructed to treat recommended modules as critical. The following list includes recommended modules.
The following items are flagged as critical:
The following is a list of items that were marked for removal:
The following is a list of items that were marked for installation:

6. WPI will automatically launch autopatcher.exe to update the machine with DotNet

"%wpipath%\\install\\apup_DotNet\\autopatcher.exe" /nolicense /unattend /noreboot /log /report /verbose /recommended /answerfile:"%wpipath%\\install\\apup_DotNet\\apup_DotNet.aaf"

What happens here is the same with DirectX

apup_DotNet.aaf contains:
WINDOWS_COMPONENTS_PARENT
DOTNET_PARENT
DOTNET1.1
DOTNET1.1_SP1
DOTNET3.5

The autopatcher.log file contains the same contents as with the DirectX run.



7. WPI will automatically launch autopatcher.exe to update the machine with Extras

"%wpipath%\\install\\apup_Extras\\autopatcher.exe" /nolicense /unattend /noreboot /log /report /verbose /recommended /answerfile:"%wpipath%\\install\\apup_Extras\\apup_Extras.aaf"

This works without problems.


8. A reboot will be issued

This works without problems.


If I manually run the directx setup or autopatcher.exe (without any command line arguments), for example, it works without any problems.

Any ideas?

Thank you.

Edited by icnocop, 30 June 2008 - 08:14 AM.

[James]

Hmm, 100+ views with no reply. That's probably because AutoPatcher is intended for use after Windows is installed, not during the Windows install itself.

Let me preface my own answer by saying I know only a little about WPI myself (WPI = Windows Post-Install Wizard, if anyone else is wondering).

I am curious as to why you seem to have three copies of autopatcher.exe in three different sub-folders. Is this just for diagnostic purposes?

Since, at step 4, autopatcher runs successfully, this strongly suggests the problem is not with autopatcher itself.

As you may already know, installing DOTNET and other stuff that requires the MSI installer during an unattended Windows install can be problematic. It's enough to send people prematurely insane! As a workaround, why don't you use the specially configured packages posted on the usual unattended install forums?

--
James