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: 1) The address bar is removed in the main taskbar, so I tried Right clicking on the taskbar > Toolbars> but notice that the Address option has been removed in SP3. Any way to restore it? 2) Old Windows Messenger was reinstalled, so I uninstalled it. 3) Each time I try to open MSN Messenger an install window opens displaying that MSN Messenger is being restored, so I cancel the process and MSN Messenger opens up normally. Any way to prevent this reinstall from opening up each time I open MSN Messenger? 4) If I try to activate Error Checking after reboot (by right clicking "C" drive in My Computer-Properties-Tools-Error Checking) and reboot it won't go thru error checking, it will skip it. How to fix this?
All of the above issues promted me to uninstall SP3 from my system using Add/Remove Programs in Control Panel and now my PC is back to SP2 and everything restored and working normally. I'd like however to know how to handle the above issues to be able to update to SP3. Thanks.
> 1) The address bar is removed in the main taskbar, so I tried Right clicking > on the taskbar > Toolbars> but notice that the Address option has been > removed in SP3. Any way to restore it?
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:
- 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:
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:
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.
> 2) Old Windows Messenger was reinstalled, so I uninstalled it.
Probably because there were updates to apply to it. I always uninstall it by going to the Add/Remove Programs applet and using the Add/Remove Windows Components applet.
> 3) Each time I try to open MSN Messenger an install window opens displaying > that MSN Messenger is being restored, so I cancel the process and MSN > Messenger opens up normally. Any way to prevent this reinstall from opening > up each time I open MSN Messenger?
I thought Microsoft had discontinued the old MSN Messenger and gone to the new Windows Live Messenger (http://get.live.com).
> 4) If I try to activate Error Checking after reboot (by right clicking "C" > drive in My Computer-Properties-Tools-Error Checking) and reboot it won't go > thru error checking, it will skip it. How to fix this?
Does the same skip-on-reboot problem occur if you run "chkdsk c: /r" from a DOS shell? I added the /r option which take longer to do some checking on the readability of sectors. You could instead use the /f switch to fix any problems that it finds. There is no point in running chkdsk without any options to tell you there are problems and then not bother to do anything about them. In the DOS shell, and after entering the chkdsk command, you'll be told the partition is inuse (well, because it's the OS partition) and the checking is not performed until a reboot. See if the checking does indeed get done during the reboot.
> All of the above issues promted me to uninstall SP3 from my system using > Add/Remove Programs in Control Panel and now my PC is back to SP2 and > everything restored and working normally. I'd like however to know how to > handle the above issues to be able to update to SP3. Thanks.
Personally I don't rely or trust a software uninstall procedure to return the OS partition back to the EXACT state as it was before the service pack install and without any remnant pollution left by the new service pack. For any major change in your system, save a partition image so you get back exactly what you had before.
> ... > 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:
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):
Free unlimited installation and compatibility support is available for Windows XP, but only for Service Pack 3 (SP3), until 14 Apr-09. Chat and e-mail support is available only in the United States and Canada.
Steps to take before you install WinXP SP3 (includes numerous windowsupdate.log Error Codes, if encountered during installation) http://support.microsoft.com/kb/950717
<IMHO> Temporarily disable all real-time protections afforded by your anti-virus application, any anti-spyware applications, and any third-party firewall prior to installing SP3. If you disable a third-party firewall, make sure you then enable the Windows Firewall: The machine should not be connected to the internet without an active firewall.
After installing SP3 /and rebooting twice/, check to make sure your real-time protections have been re-enabled; If you disabled a third-party firewall, remember to re-enable it and disable the Windows Firewall. </IMHO> -- ~Robear Dyer (PA Bear) MS MVP-IE, Mail, Security, Windows Desktop Experience - since 2002 AumHa VSOP & Admin http://aumha.net DTS-L http://dts-l.net/
Ale wrote: > 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: > 1) The address bar is removed in the main taskbar, so I tried Right > clicking > on the taskbar > Toolbars> but notice that the Address option has been > removed in SP3. Any way to restore it? > 2) Old Windows Messenger was reinstalled, so I uninstalled it. > 3) Each time I try to open MSN Messenger an install window opens > displaying > that MSN Messenger is being restored, so I cancel the process and MSN > Messenger opens up normally. Any way to prevent this reinstall from > opening > up each time I open MSN Messenger? > 4) If I try to activate Error Checking after reboot (by right clicking "C" > drive in My Computer-Properties-Tools-Error Checking) and reboot it won't > go > thru error checking, it will skip it. How to fix this?
> All of the above issues promted me to uninstall SP3 from my system using > Add/Remove Programs in Control Panel and now my PC is back to SP2 and > everything restored and working normally. I'd like however to know how to > handle the above issues to be able to update to SP3. Thanks.
Also, if I ever try clean installing SP3 from scratch, which of these methods would you recommend? (I own a Dell PC): 1) Install WinXP Pro SP0 (OEM CD), then SP2, then SP3 2) Install WinXP Pro SP0 (OEM CD), then SP3 3) Install winXP Pro SP2 (OEM CD), then SP3
"VanguardLH" wrote: > "VanguardLH" wrote in <news:fvrvu1$ci6$1@registered.motzarella.org>: > > ... > > 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:
> 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):
Thanks Bear...would you suggest installing SP3 or can I live secure with SP2? Also, if I ever try clean installing SP3 from scratch, which of these methods would you recommend? (I own a Dell PC): 1) Install WinXP Pro SP0 (OEM CD), then SP2, then SP3 2) Install WinXP Pro SP0 (OEM CD), then SP3 3) Install winXP Pro SP2 (OEM CD), then SP3
> Free unlimited installation and compatibility support is available for > Windows XP, but only for Service Pack 3 (SP3), until 14 Apr-09. Chat and > e-mail support is available only in the United States and Canada.
> Steps to take before you install WinXP SP3 > (includes numerous windowsupdate.log Error Codes, if encountered during > installation) > http://support.microsoft.com/kb/950717
> <IMHO> > Temporarily disable all real-time protections afforded by your anti-virus > application, any anti-spyware applications, and any third-party firewall > prior to installing SP3. If you disable a third-party firewall, make sure > you then enable the Windows Firewall: The machine should not be connected to > the internet without an active firewall.
> After installing SP3 /and rebooting twice/, check to make sure your > real-time protections have been re-enabled; If you disabled a third-party > firewall, remember to re-enable it and disable the Windows Firewall. > </IMHO> > -- > ~Robear Dyer (PA Bear) > MS MVP-IE, Mail, Security, Windows Desktop Experience - since 2002 > AumHa VSOP & Admin http://aumha.net > DTS-L http://dts-l.net/
> Ale wrote: > > 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: > > 1) The address bar is removed in the main taskbar, so I tried Right > > clicking > > on the taskbar > Toolbars> but notice that the Address option has been > > removed in SP3. Any way to restore it? > > 2) Old Windows Messenger was reinstalled, so I uninstalled it. > > 3) Each time I try to open MSN Messenger an install window opens > > displaying > > that MSN Messenger is being restored, so I cancel the process and MSN > > Messenger opens up normally. Any way to prevent this reinstall from > > opening > > up each time I open MSN Messenger? > > 4) If I try to activate Error Checking after reboot (by right clicking "C" > > drive in My Computer-Properties-Tools-Error Checking) and reboot it won't > > go > > thru error checking, it will skip it. How to fix this?
> > All of the above issues promted me to uninstall SP3 from my system using > > Add/Remove Programs in Control Panel and now my PC is back to SP2 and > > everything restored and working normally. I'd like however to know how to > > handle the above issues to be able to update to SP3. Thanks.
First of all, 2) is not possible. MS has blocked it on Windows Update.
Either 1) or 3) produces the same result.
However, why not avoid the issue entirely (as follows)?
Using your SP0 cd and the SP2 standalone installation package for IT Pros, make a slipstreamed cd (called an integrated XP Pro SP2 cd). Using that and the standlaone package for SP3, make an XP Pro SP3 integrated cd that can be used to directly install XP Pro SP3 whenever you want. It has the added advantage that it would be the required cd in order to do a repair install later anyway should you ever need to do that.
"Ale" <A...@discussions.microsoft.com> wrote in message
> Thanks Bear...would you suggest installing SP3 or can I live secure with > SP2? > Also, if I ever try clean installing SP3 from scratch, which of these > methods would you recommend? (I own a Dell PC): > 1) Install WinXP Pro SP0 (OEM CD), then SP2, then SP3 > 2) Install WinXP Pro SP0 (OEM CD), then SP3 > 3) Install winXP Pro SP2 (OEM CD), then SP3
> "PA Bear [MS MVP]" wrote:
>> Free unlimited installation and compatibility support is available for >> Windows XP, but only for Service Pack 3 (SP3), until 14 Apr-09. Chat and >> e-mail support is available only in the United States and Canada.
>> Steps to take before you install WinXP SP3 >> (includes numerous windowsupdate.log Error Codes, if encountered during >> installation) >> http://support.microsoft.com/kb/950717
>> <IMHO> >> Temporarily disable all real-time protections afforded by your anti-virus >> application, any anti-spyware applications, and any third-party firewall >> prior to installing SP3. If you disable a third-party firewall, make >> sure >> you then enable the Windows Firewall: The machine should not be connected >> to >> the internet without an active firewall.
>> After installing SP3 /and rebooting twice/, check to make sure your >> real-time protections have been re-enabled; If you disabled a third-party >> firewall, remember to re-enable it and disable the Windows Firewall. >> </IMHO> >> -- >> ~Robear Dyer (PA Bear) >> MS MVP-IE, Mail, Security, Windows Desktop Experience - since 2002 >> AumHa VSOP & Admin http://aumha.net >> DTS-L http://dts-l.net/
>> Ale wrote: >> > 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: >> > 1) The address bar is removed in the main taskbar, so I tried Right >> > clicking >> > on the taskbar > Toolbars> but notice that the Address option has been >> > removed in SP3. Any way to restore it? >> > 2) Old Windows Messenger was reinstalled, so I uninstalled it. >> > 3) Each time I try to open MSN Messenger an install window opens >> > displaying >> > that MSN Messenger is being restored, so I cancel the process and MSN >> > Messenger opens up normally. Any way to prevent this reinstall from >> > opening >> > up each time I open MSN Messenger? >> > 4) If I try to activate Error Checking after reboot (by right clicking >> > "C" >> > drive in My Computer-Properties-Tools-Error Checking) and reboot it >> > won't >> > go >> > thru error checking, it will skip it. How to fix this?
>> > All of the above issues promted me to uninstall SP3 from my system >> > using >> > Add/Remove Programs in Control Panel and now my PC is back to SP2 and >> > everything restored and working normally. I'd like however to know how >> > to >> > handle the above issues to be able to update to SP3. Thanks.
When support for WinXP SP2 ends a few years from now, you'll need to have SP3 installed to get any further critical security updates. SP3 is not a security update.
The machine must be running WinXP SP1 or WinXP SP2 to be able to install SP3, so I'll pick Door #3!
Ale wrote: > Thanks Bear...would you suggest installing SP3 or can I live secure with > SP2? Also, if I ever try clean installing SP3 from scratch, which of these > methods would you recommend? (I own a Dell PC): > 1) Install WinXP Pro SP0 (OEM CD), then SP2, then SP3 > 2) Install WinXP Pro SP0 (OEM CD), then SP3 > 3) Install winXP Pro SP2 (OEM CD), then SP3
> "PA Bear [MS MVP]" wrote:
>> Free unlimited installation and compatibility support is available for >> Windows XP, but only for Service Pack 3 (SP3), until 14 Apr-09. Chat and >> e-mail support is available only in the United States and Canada.
>> Steps to take before you install WinXP SP3 >> (includes numerous windowsupdate.log Error Codes, if encountered during >> installation) >> http://support.microsoft.com/kb/950717
>> <IMHO> >> Temporarily disable all real-time protections afforded by your anti-virus >> application, any anti-spyware applications, and any third-party firewall >> prior to installing SP3. If you disable a third-party firewall, make >> sure >> you then enable the Windows Firewall: The machine should not be connected >> to the internet without an active firewall.
>> After installing SP3 /and rebooting twice/, check to make sure your >> real-time protections have been re-enabled; If you disabled a third-party >> firewall, remember to re-enable it and disable the Windows Firewall. >> </IMHO> >> -- >> ~Robear Dyer (PA Bear) >> MS MVP-IE, Mail, Security, Windows Desktop Experience - since 2002 >> AumHa VSOP & Admin http://aumha.net >> DTS-L http://dts-l.net/
>> Ale wrote: >>> 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: >>> 1) The address bar is removed in the main taskbar, so I tried Right >>> clicking >>> on the taskbar > Toolbars> but notice that the Address option has been >>> removed in SP3. Any way to restore it? >>> 2) Old Windows Messenger was reinstalled, so I uninstalled it. >>> 3) Each time I try to open MSN Messenger an install window opens >>> displaying >>> that MSN Messenger is being restored, so I cancel the process and MSN >>> Messenger opens up normally. Any way to prevent this reinstall from >>> opening >>> up each time I open MSN Messenger? >>> 4) If I try to activate Error Checking after reboot (by right clicking >>> "C" >>> drive in My Computer-Properties-Tools-Error Checking) and reboot it >>> won't >>> go >>> thru error checking, it will skip it. How to fix this?
>>> All of the above issues promted me to uninstall SP3 from my system using >>> Add/Remove Programs in Control Panel and now my PC is back to SP2 and >>> everything restored and working normally. I'd like however to know how >>> to >>> handle the above issues to be able to update to SP3. Thanks.
I didn't go the 3rd party route to add someone else's toolbar (which still has defects).
> Also, if I ever try clean installing SP3 from scratch, which of these > methods would you recommend? (I own a Dell PC): > 1) Install WinXP Pro SP0 (OEM CD), then SP2, then SP3 > 2) Install WinXP Pro SP0 (OEM CD), then SP3 > 3) Install winXP Pro SP2 (OEM CD), then SP3
Use the WinXP SP2 to slipstream in SP3 to create a WinXP SP3 install CD.
The reason why I did not mention the option of slipstreaming SP3 into the XP SP2 CD is that from what I read it is not possible to slipstream, or at least it's more problematic, when the CD is an OEM version, right?
> I didn't go the 3rd party route to add someone else's toolbar (which > still has defects).
> > Also, if I ever try clean installing SP3 from scratch, which of these > > methods would you recommend? (I own a Dell PC): > > 1) Install WinXP Pro SP0 (OEM CD), then SP2, then SP3 > > 2) Install WinXP Pro SP0 (OEM CD), then SP3 > > 3) Install winXP Pro SP2 (OEM CD), then SP3
> Use the WinXP SP2 to slipstream in SP3 to create a WinXP SP3 install CD.
Vanguard, that's precisely the point, SP3 release notes say that it does not significantly impact the XP experience and that it does not add any additional security patches other than those already released thru Windows Update. It only seems to add the convenience of unifying all previous patches in a single file. Therefore, it odes not seem to be a critical patch, so why go thru the trouble of messing with system files? I guess the only reason to eventually consider is the lack of support for SP2 in a couple of years.
> The reason why I did not mention the option of slipstreaming SP3 into the XP > SP2 CD is that from what I read it is not possible to slipstream, or at least > it's more problematic, when the CD is an OEM version, right?
I slipstreamed SP-2 into my OEM CD for Windows XP Pro SP-1. So why can't SP-3 be slipstreamed into an OEM CD for Windows XP Pro SP-2? The slipstreaming is done on your hard disk and then you copy the files onto your own recordable CD. Unless I missed it, I never saw mention that I cannot slipstream using an OEM CD as the baseline version. Obviously a service pack updates retail or OEM versions of Windows.
Please point me at the articles you read that say OEM cannot be used as baseline to create a slipstreamed modified version of it.
VanguardLH <V...@nguard.LH> wrote: >I slipstreamed SP-2 into my OEM CD for Windows XP Pro SP-1. So why >can't SP-3 be slipstreamed into an OEM CD for Windows XP Pro SP-2?
>> What in the release notes for SP-3 convinced you that you must have >> SP-3?
> Vanguard, that's precisely the point, SP3 release notes say that it does not > significantly impact the XP experience and that it does not add any > additional security patches other than those already released thru Windows > Update. It only seems to add the convenience of unifying all previous patches > in a single file. Therefore, it odes not seem to be a critical patch, so why > go thru the trouble of messing with system files? I guess the only reason to > eventually consider is the lack of support for SP2 in a couple of years.
No, the release notes *do* mention additional functionality that was added in SP-3 but most, if not all, of them might not apply in your computing environment. Do you know what is NAP? If you do, is it applicable in your computing environment? There are some other additions but you need to read the release notes to see if they apply to your setup. 80% of SP-3 is SP-2 plus subsequent updates since the release of SP-2. So if you have SP-2 and been staying up to date then SP-3 gives you little additional functionality, and what it does give you in additional functionality may not be usable to you.
- Adds NAP (I won't bother to decode the initials since if you don't know what NAP means then you don't need it). - New version of MMC. Yes, you use MMC but a new version isn't need for those applets that use it now. - Says it adds MSXML v6 yet I already have it (and I don't have SP-3). Check for %windir%\system32\msxml*.dll to see the highest version you already have; however, it is possible that I manually installed the latest version of MDAC and not as part of Windows Update. - MSI 3.1 (from 3.0). A minor update. If any update in the future from Microsoft requires it, they'll shove it at you when you visit Windows Update. - Newer version of BITS. Again, if you don't recognize the initials then you don't need a newer version. V1.0 came in Windows XP. V1.5 came in Windows Server 2003. So V2.5 is a major upgrade. See http://download.microsoft.com/download/b/3/d/b3d8e8ea-8c3f-4962-8a01-... for info on BITS. Do you even have a server host in your network? You do at work but then *you* shouldn't be updating your employer's workstations as that is a task to be performed only by their IT group when they decide to deploy that service pack. - IPSEC update. Do you even define IPSEC filters? Didn't think so. - DIMS. Again, are you on a corporate network and logging under a domain? - Peer Name Resolution. Possibly helpful if your intranet includes a mix of Windows XP and Vista hosts. It has been working for me so far so the "update" is hardly a requirement. - RDP upped to v6.1. I already had v6.0 (again possibly because I downloaded it rather than getting it through Windows Update). - WPA v2. Possibly useful. I haven't bothered to check into this one yet. - More descriptive text explaining the options for security policies. Well, if you haven't figured them out by now, you don't use policies. If you do use policies, you would've already figured them out by now. The added help comes too late. I'd rather see more info added to the BSOD error codes. - Windows Product Activation. Claims that you can "now" opt to now activate during an install and can activate later after the OS has been installed. It was there before but not obvious so Microsoft just made it obvious.
In addition, and without official notification by Microsoft despite their claims to notify: - Removes the Address toolbar from the Windows taskbar.
> > The reason why I did not mention the option of slipstreaming SP3 into the XP > > SP2 CD is that from what I read it is not possible to slipstream, or at least > > it's more problematic, when the CD is an OEM version, right?
> I slipstreamed SP-2 into my OEM CD for Windows XP Pro SP-1. So why > can't SP-3 be slipstreamed into an OEM CD for Windows XP Pro SP-2? The > slipstreaming is done on your hard disk and then you copy the files onto > your own recordable CD. Unless I missed it, I never saw mention that I > cannot slipstream using an OEM CD as the baseline version. Obviously a > service pack updates retail or OEM versions of Windows.
> Please point me at the articles you read that say OEM cannot be used as > baseline to create a slipstreamed modified version of it.
Hello...you are not alone! Same problem here on my wife's laptop running XP. Address bar has gone since installing SP3 and no obvious option available to restore it, haven't noticed any other difficulties as yet but it's early days. No doubt she'll keep me informed! I'm researching and will advise if I find a solution...hope you will do the same if you beat me to it. Regards Bob
Hi Bob, try this simple solution to the address bar: 1. create a new bar on the taskbar (Links for example) 2. drag it to desktop to undock it (it will change to a panel, you have to undock it as it won't work otherwise) 3. now you can add the address bar (rightcklick on the undocked panel) 4. drag the newly created address bar to taskbar
> Hello...you are not alone! Same problem here on my wife's laptop running > XP. Address bar has gone since installing SP3 and no obvious option > available to restore it, haven't noticed any other difficulties as yet > but it's early days. No doubt she'll keep me informed! I'm researching > and will advise if I find a solution...hope you will do the same if you > beat me to it. > Regards > Bob
I've installed SP3 and I haven't got this much problems since I had the worst Virus in my pc. My pc doesn't start anymore, I can't enter in my XP because BSOD just appears due to (I think) a logitech driver. There is some sort of a conflict. I've managed to do a chkdsk and WOW! What kind of software have you guys released and installed in my pc? My entire harddisk is gone real bad. Geez...
I knew it. My automatic updates was always off, and here I was thinking "hey an update can't hurt, right?" Yeah right... Think again.
My advice to everyone as an experienced PC/XP user: DO NOT UPDATE UNLESS YOUR PC IS UNSTABLE. If it's stable just leave it that way! Trust me, if you do an update you'll do more harm then good.
> I've installed SP3 and I haven't got this much problems since I had the > worst Virus in my pc. My pc doesn't start anymore, I can't enter in my XP > because BSOD just appears due to (I think) a logitech driver. There is > some > sort of a conflict. I've managed to do a chkdsk and WOW! What kind of > software have you guys released and installed in my pc? My entire harddisk > is gone real bad. Geez...
> I knew it. My automatic updates was always off, and here I was thinking > "hey > an update can't hurt, right?" Yeah right... Think again.
> My advice to everyone as an experienced PC/XP user: DO NOT UPDATE UNLESS > YOUR PC IS UNSTABLE. If it's stable just leave it that way! Trust me, if > you > do an update you'll do more harm then good.
Has it ever occurred to you that your computer was so full of trash that a clean install of SP3 was impossible? Amazing how people like you always blames Microsoft. Care to guess how many successful installs there are?
"Dreams" <Dre...@discussions.microsoft.com> wrote in message
> I've installed SP3 and I haven't got this much problems since I had the > worst Virus in my pc. My pc doesn't start anymore, I can't enter in my XP > because BSOD just appears due to (I think) a logitech driver. There is > some > sort of a conflict. I've managed to do a chkdsk and WOW! What kind of > software have you guys released and installed in my pc? My entire harddisk > is > gone real bad. Geez...
> I knew it. My automatic updates was always off, and here I was thinking > "hey > an update can't hurt, right?" Yeah right... Think again.
> My advice to everyone as an experienced PC/XP user: DO NOT UPDATE UNLESS > YOUR PC IS UNSTABLE. If it's stable just leave it that way! Trust me, if > you > do an update you'll do more harm then good.
> I've installed SP3 and I haven't got this much problems since I had the > worst Virus in my pc. My pc doesn't start anymore, I can't enter in my XP > because BSOD just appears due to (I think) a logitech driver. There is some > sort of a conflict. I've managed to do a chkdsk and WOW! What kind of > software have you guys released and installed in my pc? My entire harddisk is > gone real bad. Geez...
> I knew it. My automatic updates was always off, and here I was thinking "hey > an update can't hurt, right?" Yeah right... Think again.
> My advice to everyone as an experienced PC/XP user: DO NOT UPDATE UNLESS > YOUR PC IS UNSTABLE. If it's stable just leave it that way! Trust me, if you > do an update you'll do more harm then good.
So you install updates without ever reading the notes for them to know what they are for. Guess you also drive around with a blindfold over your eyes hoping that everywhere you drive is clear.
Always do a custom install of updates so you can see what you are getting, and read their notes and even the KB article which is indicated. Express and automatic updates means you are driving blind.
I hate to be a bearer of bad news, but methinks that there's an "oops" in there. I reckon, from trying this, that "movefile" does what it says on the tin (i.e. *moves* the file). So, what happens is that the move to dllcache goes off and then the move to system32 goes pear-shaped as there's now no source file for it to move from :-} Took me a while to work that one out. I resorted to using a Bart PE disk to copy the DLLs, but I reckon that using "movefile" with two copies to start with should also be OK.
Anyhow, despite traffic to the contrary, this *does* restore the address bar to the vanilla, release version of SP3.
"VanguardLH" wrote: > "VanguardLH" wrote in <news:fvrvu1$ci6$1@registered.motzarella.org>: > > ... > > 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:
> 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):
> I hate to be a bearer of bad news, but methinks that there's an "oops" in > there. I reckon, from trying this, that "movefile" does what it says on the > tin (i.e. *moves* the file). So, what happens is that the move to dllcache > goes off and then the move to system32 goes pear-shaped as there's now no > source file for it to move from :-} > Took me a while to work that one out. I resorted to using a Bart PE disk to > copy the DLLs, but I reckon that using "movefile" with two copies to start > with should also be OK.
> Anyhow, despite traffic to the contrary, this *does* restore the address bar > to the vanilla, release version of SP3.
Thanks for the check. I had assumed 'movefile' would do copy but it makes sense that it moves. I tried using Microsoft's 'inuse' utility but it it checks if the file is protected by WFP. Since it is a protected file, inuse refuses to setup the pending file change on Windows startup using the registry key. I wanted to instruct using a utility rather than have users go editing the registry.
When I did the original test in a virtual machine, I had only used 'movefile' with the system32 destination. Then later I realized that it should also get replaced in the dllcache to subvert WFP.
|
