I do use include and have no problems. BTW. do you install any third party software? Have you checked the startup line with Autoruns? it was a vanilla WinXP SP3 updated with the latest Mim0's file-checker, nothing in the autorun or anywhere. Like said Mim0, you have to copy KB961742-v3 to HFSVCPACK_SW1 directory, not HF. Same "My Documents" problem here. What I have found out is that if you slipstream KB961742-v3 in HFSVCPACK_SW1(perhaps with some bad interaction with other unknown fixes), for some reason registry value of "Userinit" at HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon becomes not as intended(by installer). Without 961742-v3 "Userinit"="C:\Windows\system32\userinit.exe," 961742-v3 at HFSVCPACK_SW1 "Userinit"="C:\Windows\system32\userinit.exe,C:\Windows\system32\rdpinit.exe," 961742-v3 at standalone(after you've installed OS without 961742-v3 slipstreamed) "Userinit"="C:\Windows\system32\rdpinit.exe," I think that either userinit.exe or rdpinit.exe causes explorer.exe(intended as shell) to launch at logon so if you have double entry in here, one more (unwanted) windows explorer launches. To fix it, just replace that entry with correct value manually. "Userinit"="C:\Windows\system32\rdpinit.exe," I have personally verified the correctness of registry entry after I manually fixed and uninstalled KB961642-v3 after this fix. After uninstallation, this entry becomes original value "Userinit"="C:\Windows\system32\userinit.exe," regardless of manually modifying this entry, BUT YOUR MILAGE MAY VARY SO BE CAREFUL - this entry is crucial on successful launch of windows. I'm now wondering if there is a way to automatically apply registry fix after HFSVCPACK_SW1 slipstreamed 961742-v3 installs. Some help would be really appreciated;) Thanks.