eger Posted January 4, 2008 Share Posted January 4, 2008 I am trying to integrate KB942615 using the /integrate switch (building my slipstreamed CD by hand) and am coming across the issue found in this thread: http://www.msfn.org/board/index.php?showtopic=88472I have determined it to be after I integrate KB942615 that the issue happens (finally found after countless days of starting from scratch).Is there a workaround to integrate KB942615 without having to use nLite or HFSLIP? Anything other than the /integrate switch I can use?I am using Windows 2003 Standard and all other updates integrate flawless and this is the only one showing under Windows Update when I am finished. Not sure where I can throw this in to be slipstreamed without killing the installer with the lsass problem Link to comment Share on other sites More sharing options...
DarkShadows Posted January 5, 2008 Share Posted January 5, 2008 Yes! Well, at least I think so. I believe I encountered the same issue on Windows XP Pro SP2, except that I couldn't catch the error dialog, as it went by so fast. But my Virtual PC just kept rebooting. Microsoft released an update that fixed this for me (on WinXP SP2). See my new thread here. If you follow the KB link, there is a download for Win2k3.Post back if it works for you and I will add it to that other thread under Win2K3.Good Luck! Link to comment Share on other sites More sharing options...
eger Posted January 6, 2008 Author Share Posted January 6, 2008 Very interesting. So if I am reading that correctly I should add KB946627 in line with KB942615 in my svcpack.ini method (using integrate switches)? Or should I replace it with KB946627?I will test this out next week when I work on my slipstreamed win2k3 install more. Thanks! Link to comment Share on other sites More sharing options...
DarkShadows Posted January 7, 2008 Share Posted January 7, 2008 I just integrated them both. The thing is, that I'm not sure if it will work with Windows Server or not. The KB article explicitly listed WinXP. Link to comment Share on other sites More sharing options...
eger Posted January 7, 2008 Author Share Posted January 7, 2008 Yep, it is for Windows XP only. It would not let me integrate it into the Windoes 2003 distribution. Hopefully someone else will know a workaround. Link to comment Share on other sites More sharing options...
eger Posted January 10, 2008 Author Share Posted January 10, 2008 Some interesting additional information. Recently there were 3 more updates for XP/2K/2K3. One of which was KB943485 which was a fix for lsass (which was throwing the initial error when trying to integrate the KB942615 patch). After I integrated KB943485 I decided to try KB942615 integration again for kicks and giggles. This time it works and integrates and windows setup does not throw any errors about lsass and completed fine. However KB942615 still shows as not installed and is trying to be updated by windows update.I am going to play with it a little more as it seems like KB943485 allows KB942615 to be integrated now with no problems and maybe it's just an incorrect order now? Link to comment Share on other sites More sharing options...
DarkShadows Posted January 11, 2008 Share Posted January 11, 2008 The integration order really should not matter. I always add QChain.exe to svcpack.inf. Some people have said this is no longer a requirement, but I figure it's better to be safe than sorry. I do not work with Win2K3, so I can't test. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now