WINNT.SIF config causing weird bug (XP Home)

[SniperKnifer]

So I have a strange bug with my config for my unattended config. I have a fully updated/driverpacked/unattended xp pro install, that works just fine. I went ahead and ran the equivalent sysprep.exe for XP home, but I didn't see any appreciable difference between the two versions for the config file. What I have done is I have copied the same file I used for the pro version into my home edition disk but on the home disk does everything right *except* creating a user account! Here's a picture of how it looks:

You can bypass it by booting into safemode-->administrator and creating an account, but it's not unattended then. Weirder still, when using it on a virtual machine, it works just fine: it's only on a CD install that the issue happens.

See if you can spot the problem! Here's my sif file.

;SetupMgrTag

[Components]

PowerShellISE = off

WDSearch = off

BitLockerToGo = off

BrowserChoice = off

[Data]

AutoPartition=0

UnattendedInstall = "yes"

MsDosInitiated=No

[unattended]

UnattendMode=FullUnattended

Repartition=No

FileSystem=*

UnattendSwitch="yes"

WaitForReboot="No"

OemSkipEula=Yes

OemPreinstall=No

TargetPath=\WINDOWS

DriverSigningPolicy=Ignore

NonDriverSigningPolicy=Ignore

[GuiUnattended]

AdminPassword=*

EncryptedAdminPassword=NO

OEMSkipRegional=1

TimeZone=255

OemSkipWelcome=1

[userData]

ProductKey=00000-00000-00000-00000-00000

FullName="Owner"

OrgName="Personal"

ComputerName=Owner-PC

[TapiLocation]

CountryCode=61

[identification]

JoinWorkgroup=WORKGROUP

[Networking]

InstallDefaultComponents=Yes

;

; Edited by DriverPacks BASE 10.06

; http://www.driverpacks.net/

;

[GUIRunOnce]

command9="%SystemDrive%\DPsFnshr.exe"

I figure that if there's any problem, it'll be in the user data portion of the code. It's just strange that otherwise this code works perfectly fine with the pro version.

Also hi! I'll be keeping an eye on the boards for the future, looks like a good technician resource

[SniperKnifer]

After going through and installing after every step one-by-one, I've found out that it is the driverpack slipstream that causes it (from driverpacks.net). Anybody have a good idea why an automated driver install would cause this issue?