Nethan

Oups sorry, I forgot it. Here it goes. The old ok, and the new ok. All hotfixes are still inside the new one but the "Hotfixes and Update Packs" option is unchecked. LAST SESSION OLD OK.INI LAST SESSION NEW OK.ini

Indeed, my UnattendSwitch is already at "No". Well, finally I know what is wrong. I made an ultimate test : The Lastsession of my first post, exactly the same, but I removed ALL hotfixes & the IE8 addon. OOBE works now. So there is an hotfix who screw OOBE. I will see it the next time I will update the CD...

Ok, only at spare time ^^ In all cases, I will do everything only the next time I need to add/remove security patches. OOBE is not critical ^^ Yes, it is a XP Pro CD with SP3 slipstreamed manually since a while, sorry for the confusion. I don't know if it would be better to have a XP/SP3 directly & officialy integrated but it is not something I can get actually anyway :/ So yes, I use my version as base, but I don't launch nLite on the same source multiple times, I "restart" each time it needed (like patches). For the Autologon, I have already it at off/none as I stated in my first post (username : none, and count at 0). Did you mean to try WITH it ?

Oups, cross-posting with johnhc ^^ johnhc > I mean by OOBE, the part of the installation where Windows asks you to create one to five users, and try to activate himself, before the first login. Actually on my last CDs created by nLite, this part is skipped but it shouldn't be. Does this make a difference ? Not really, I can live without it even if I create some users, I can create them manually, but I post this topic to see if someone would have an idea to correct it if it was possible. I frakking hate bugs ^^ I don't know if the fact that launch nLite on a x64 system change something, but I will make a try when I can on a 32b system. Ponch > I start with a XP Pro 32 bits with the SP3 slipstreamed in. OOBE works fine if I don't use nLite (I have to use Driverpack nevertheless - no floppy drive - so make it an ISO, but it don't change the result : it works). OOBE also works fine on my old nLited CD who has the same XP Pro as base, and I don't see any difference on the Lastsession.ini files who could explain why it don't work on my last nLited CDs. I am sure that it is a component that I removed, but I have no idea what it can be, and don't have the courage to test one by one ^^ so also why I post ^^. Apart that, I use at least one more user. I can create the user by myself, so it is not a critical problem. It is just that I hate bugs, and as nLite has some problems, I am curious about any problem.

No, autologon is off, well at none.

Hello, It will probably sound unusual on this forum ^^, but I want to keep the OOBE section after the installation of my unattended Windows XP CD. I always use nLite, and I have "Skip OOBE" unchecked. All components about Windows Activation & OOBE are protected from removal (normaly). It was recommended by the nLite FAQ (section "why is OOBE skipped"). Also, Autologon is off... But still, OOBE don't want be launched on the final CD. The most curious, is that I get this screen on an old Windows CD that I created too by nLite and with nearly the same options ! (apart some components and patches. I use Winmerge to compare them) So I don't understand why, but now it refuses to appear and I don't manage to see why. It is not that I can't do without of course, but if there is a way to restore it, I would appreciate ^^ I attach in this topic my nLite file, if that can help. Cordialy, Nethan Windows Conventionnel v3.ini

I guess I will avoid updates for MSI 4.5 for a moment ^^ About the KB923789, after checking, it is not really redundant. Indeed, files of the flash version 6 stays in the system if I install Flash 10 without uninstalling the old one, who is the common method with Internet Explorer, and I don't know if it is dangerous. Nevertheless, this patch is useless if the Flash uninstaller is used : This files are removed by it. I read that this patch gave some conflicts with Flash 9. It don't concern Flash 10, but I will not take any risks. As you said, we have the choice. So I will use the uninstaller through a vbscript Thanks for your answer and your help

Hello, I have two remarks : 1) I can read that you link the 048 KB927891-v5-x64-ENU.exe (MSI reliability update) patch, but there is something curious. Indeed, when I read the KB927891, it is required to install two files : The WindowsUpdateAgent30-x64.exe is considered in your first post as "Optional". I agree with that, but the KB927891 patch should be considered too as optional, as it seems to be useless alone. 2) The MSI Installer 4.5 has a patch, the KB958655. Could be useful if you want to install SQL Server or things like that without problems. Maybe you could add it in the list (it would be better if MS took some time to create an updated installer...). I have also a question : The KB923789 update, who concerns Flash Player 6... Is it really necessary ? I mean, I will install Flash Player 10. Should the vulnerabilities be corrected at the same time ?