XP SP3 Problems - Printable Version -Shoutbox (https://shoutbox.menthix.net) +-- Forum: MsgHelp Archive (/forumdisplay.php?fid=58) +--- Forum: Skype & Technology (/forumdisplay.php?fid=9) +---- Forum: Tech Talk (/forumdisplay.php?fid=17) +----- Thread: XP SP3 Problems (/showthread.php?tid=83576) XP SP3 Problems by alegator on 05-07-2008 at 09:35 AM
Hi, I just installed SP3 using Windows Update (I had XP SP2 Pro fully updated). Everything went fine, I restarted the PC and apparently everything fine after the desktop showed up (no error messages, etc). But after examining my system I found the following changes: RE: XP SP3 Problems by markee on 05-07-2008 at 09:52 AM
quote:Take a read of this article RE: XP SP3 Problems by djdannyp on 05-07-2008 at 11:44 AM
quote: I experienced this problem with the RCs of SP3. all you have to do is uninstall Messenger and reinstall it and it solves the problem completely RE: RE: XP SP3 Problems by alegator on 05-08-2008 at 08:08 AM
quote: Thanks for that 3rd party tool.I also got this approach to tackle the issue from another forum: After installing Service Pack 3 to Windows XP, the Address toolbar is no longer available in the Windows taskbar. It's a legal thing as to why Microsoft says it was forced to remove it. The quick answer to restoring the Address toolbar in the taskbar is: In %windir%\system32, replace the SP-3 version of browseui.dll with the SP-2 version. Unfortunately, Windows File Protection gets in the way (and so does explorer.exe for the Windows desktop and some other processes). The workaround is to use the PendingFileRenameOperations key in the registry. Values under this key specify which files to move, replace, or delete when Windows starts up. Get the PendMoves.zip file from SysInternals (http://www.sysinternals.com) which contains the pendmoves.exe and movefile.exe utilities. pendmoves tells you what is already in that registry key to get renamed on the next Windows startup (afterwhich this key gets cleared). movefile lets you add entries to this registry key. - If you haven't yet installed SP-3, save a copy of the file: md c:\backup copy "%windir%\system32\browseui.dll" c:\temp\ - If you have already installed SP-3, you will have to get a copy of browseui.dl_ (ends with the underscore character) from your backups, from a Windows SP-2 install CD, from another of your hosts still running Windows XP SP-2, or from a friend that you really trust. If you get the compressed browseui.dl_ file, decompress it: expand [drive:[path]]browseui.dl_ c:\backup\browseui.dll Now that you have the old version of the browseui.dll file, you need to replace the SP-3 version with the old version. Run the following command in a DOS shell: copy c:\windows\system32\browseui.dll c:\windows\system32\browseui_sp3.dll movefile c:\backup\browseui.dll c:\windows\system32\browseui.dll (Oops, I forgot about WFP (Windows File Protection). The backup copy of the file should also be replaced in the dllcache folder. So use the following commands for the movefile (which replaces on reboot): copy c:\windows\system32\browseui.dll c:\windows\system32\browseui_sp3.dll movefile c:\backup\browseui.dll c:\windows\system32\dllcache\browseui.dll movefile c:\backup\browseui.dll c:\windows\system32\browseui.dll <reboot> Each movefile is on one line (so be careful due to any line wrapping in your newsreader).) The assumptions are: movefile.exe is in the current directory or found by the PATH environment variable and that you saved the old version of browseui.dll under c:\backup. Do NOT use "%windir%\system32\browseui.dll" for the destination since the windir environment variable won't be defined when the move operation is performed during Windows startup. In the above, I save a copy of the SP-3 version of browseui.dll just in case it is found later that using the old version causes problems and I have to revert back to using the SP-3 version along with having to sacrifice the Address toolbar. While this gets back the Address toolbar in the Windows taskbar, the browseui.dll file is used by lots of different functions within Windows. So it is possible that reverting to the old version could cause problems with other functionality. |