MSFN Forum: WindowsXP-KB956391-x86 - MSFN Forum

Jump to content



Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

WindowsXP-KB956391-x86 Not working with HFSLIP? Rate Topic: -----

#1 User is offline   Bugs Bunny 

  • Junior
  • Pip
  • Group: Members
  • Posts: 62
  • Joined: 07-December 05

Posted 16 October 2008 - 02:02 PM

I've put WindowsXP-KB956391-x86 in the HF folder but after installing the HFSLIPed XP, Microsoft Update still wants WindowsXP-KB956391-x86.
Anyone else experiencing this? Is there a workaround?


#2 User is offline   Drizzt_Kueh 

  • Disturber of the peace
  • Group: Members
  • Posts: 26
  • Joined: 29-October 07

Posted 16 October 2008 - 02:05 PM

The problem you're describing seems to be the same wich is happening to me.
http://www.msfn.org/board/index.php?showtopic=124752

This post has been edited by Drizzt_Kueh: 16 October 2008 - 02:06 PM


#3 User is offline   cluberti 

  • Gustatus similis pullus
  • Group: Supervisor
  • Posts: 10,936
  • Joined: 09-September 01
  • OS:Windows 7 x64
  • Country: Country Flag

Posted 16 October 2008 - 03:47 PM

This hotfix does not install any files, it just makes registry changes. However, it's branching information does seem to indicate that it does not check for any other hotfixes before installing.

Are you sure that you have the same IE files in your %windir%\system32 and %windir%\system32\dllcache folders? For example, do you have 7.x versions (say mshtml.dll) in \system32 and 6.x versions in \system32\dllcache (or vice-versa). I've seen the (failed) integration of Internet Explorer 7 (and some IE hotfixes) cause all kinds of "missing hotfix' grief post-build.

#4 User is offline   redxii 

  • Member
  • PipPip
  • Group: Members
  • Posts: 286
  • Joined: 18-August 05

Posted 16 October 2008 - 03:53 PM

Find the following registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{0002E510-0000-0000-C000-000000000046}

'Compatibility Flags' should be set to '0x00000400 (1024)'. It is probably getting written over because during registering components phase in setup something sets it to 0x00040000. And if so you have to find some way of setting it back to 0x00000400 after T13.

* I don't use HFSLIP, rather I have my own update pack w/ nLite as integration and noticed that because of that key being overwritten MU thinks it isn't installed and saw this thread; and fixed it by creating it again at 13 minutes left.

This post has been edited by redxii: 16 October 2008 - 03:58 PM


Share this topic:


Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

1 User(s) are reading this topic
0 members, 1 guests, 0 anonymous users



All trademarks mentioned on this page are the property of their respective owners
Copyright © 2001 - 2011 msfn.org
Privacy Policy