If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#16
|
|||
|
|||
Add'l Info
"philo " wrote in message
... Over the weekend I ended up having to update a number of XP machines and it looks like things have changed just a bit. The machines had IE6 and I was able to perform Windows updates with no problem. However...to get MSE directly from Microsoft, you cannot get to the page unless you first install IE8 I don't know what problem you had, but that isn't true. I assume you really mean it doesn't work with IE6, which I can't test at the moment, but you don't need IE8. http://windows.microsoft.com/en-US/w...tials-download works just fine here with IE7. It also works with Opera and Firefox. -- Glen Ventura MS MVP Oct. 2002 - Sept. 2009 CompTIA A+ |
Ads |
#17
|
|||
|
|||
Add'l Info
On 11/17/2012 07:04 AM, glee wrote:
"philo " wrote in message ... Over the weekend I ended up having to update a number of XP machines and it looks like things have changed just a bit. The machines had IE6 and I was able to perform Windows updates with no problem. However...to get MSE directly from Microsoft, you cannot get to the page unless you first install IE8 I don't know what problem you had, but that isn't true. I assume you really mean it doesn't work with IE6, correct which I can't test at the moment, but you don't need IE8. http://windows.microsoft.com/en-US/w...tials-download works just fine here with IE7. It also works with Opera and Firefox. Yep...it works fine with those two browsers... all I am saying is it does not work so fine with IE6. The page redirects to the "Update your browser" page which in turn leads to an IE8 download. -- https://www.createspace.com/3707686 |
#18
|
|||
|
|||
Add'l Info
"philo " wrote in message
... On 11/17/2012 07:04 AM, glee wrote: "philo " wrote in message ... Over the weekend I ended up having to update a number of XP machines and it looks like things have changed just a bit. The machines had IE6 and I was able to perform Windows updates with no problem. However...to get MSE directly from Microsoft, you cannot get to the page unless you first install IE8 I don't know what problem you had, but that isn't true. I assume you really mean it doesn't work with IE6, correct which I can't test at the moment, but you don't need IE8. http://windows.microsoft.com/en-US/w...tials-download works just fine here with IE7. It also works with Opera and Firefox. Yep...it works fine with those two browsers... all I am saying is it does not work so fine with IE6. The page redirects to the "Update your browser" page which in turn leads to an IE8 download. Okee-dokie... got it. -- Glen Ventura MS MVP Oct. 2002 - Sept. 2009 CompTIA A+ |
#19
|
|||
|
|||
MS Update Site failures after a clean installation
http://groups.google.com/group/micro...dfe3478b98afb2
[ Tony cited problems with SP3 from MS Update site and success with downloaded standalone version. ] Why does SP3 fail from the update site so much? I too had better luck with downloading it standalone and installing it. On Nov 15, 6:16 am, "glee" wrote: Well, it doesn't... the majority of installs via auto-update are successful. *Failures are reported in forums and newsgroups, the much larger numbers with no problems don't report in forums that they had a non-problem. *That said, many of the failures can be attributed to leaving an aggressive anti-virus/Internet security suite active during the installation. For SP2 and SP3 installs I have done in my shop, I use the standalone because I already have it downloaded, but on the occasions that I have installed them on-site via auto-update, I have not had any problems. I've never had a problem with service packs via auto-update on Vista or Win Seven. YMMV, as always. You do know this is an XP usenet group, don't ya Glen? Your argument that it works fine on MOST computers is weak. Your assertion that SP3 doesn't fail from the update site because you say it works on MOST computers is illogical. I have a small fleet of identical computers chosen because this exact model sold in the tens of thousands, maybe more. Fresh install and all updates brought current only a month ago yet some updates can't install because the ones they replace refuse to uninstall. That's not the kind of thing that should be machine specific. Rebuilding from the OEM install CD (Win XP Pro SP2), SP3 and all updates worked just fine, but building a clean install with all of the updates should not be like a game of Jenga. Updates that FAIL to uninstall when they need to be replaced by new ones should be an embarassment to Microsoft. KB2656405 KB2656353 KB2633880 and KB2633870 refused to uninstall, preventing updates to KB2737019 KB2698023 KB2729450 and KB2729449 errors were 0x66A 0x64C 0x645 and 0x66A respectively. On my new build with all updates, I WONDER how many MS updates would FAIL to uninstall? I realize that some are never supposed to be uninstalled, but how many do you think would FAIL to uninstall if I tested this question? There are so many Framework updates and they take so LONG to install that I'm getting a sneaking suspicion that HALF of my time doing updates on a fresh system install is just Framework, like 2 hours worth... I may take more copious notes with time annotations next time. WHY does SP3 update fail so much from MS Update site? Even on a fresh clean install with no malware software installed yet! |
#20
|
|||
|
|||
MS Update Site failures after a clean installation
"Greegor" wrote in message ...
You do know this is an XP usenet group, don't ya Glen? Your argument that it works fine on MOST computers is weak. Your assertion that SP3 doesn't fail from the update site because you say it works on MOST computers is illogical. I have a small fleet of identical computers chosen because this exact model sold in the tens of thousands, maybe more. Fresh install and all updates brought current only a month ago yet some updates can't install because the ones they replace refuse to uninstall. That's not the kind of thing that should be machine specific. Rebuilding from the OEM install CD (Win XP Pro SP2), SP3 and all updates worked just fine, but building a clean install with all of the updates should not be like a game of Jenga. Updates that FAIL to uninstall when they need to be replaced by new ones should be an embarassment to Microsoft. KB2656405 KB2656353 KB2633880 and KB2633870 refused to uninstall, preventing updates to KB2737019 KB2698023 KB2729450 and KB2729449 errors were 0x66A 0x64C 0x645 and 0x66A respectively. On my new build with all updates, I WONDER how many MS updates would FAIL to uninstall? I realize that some are never supposed to be uninstalled, but how many do you think would FAIL to uninstall if I tested this question? There are so many Framework updates and they take so LONG to install that I'm getting a sneaking suspicion that HALF of my time doing updates on a fresh system install is just Framework, like 2 hours worth... Framework just in stall .net3.5 and it up dates http://www.microsoft.com/en-us/downl....aspx?id=25150 I may take more copious notes with time annotations next time. WHY does SP3 update fail so much from MS Update site? Because you need IE8 or newer. For you are running IE6 sp1 with a clean install. http://www.microsoft.com/en-us/downl...ils.aspx?id=43 Plus MS Update need to be Windows Installer 4.5 Redistributable http://www.microsoft.com/en-us/downl...s.aspx?id=8483 Even on a fresh clean install with no malware software installed yet! |
#21
|
|||
|
|||
MS Update Site failures after a clean installation
On Nov 23, 6:52*pm, "John Smith" wrote:
"Greegor" wrote You do know this is an XP usenet group, don't ya Glen? Your argument that it works fine on MOST computers is weak. Your assertion that SP3 doesn't fail from the update site because you say it works on MOST computers is illogical. I have a small fleet of identical computers chosen because this exact model sold in the tens of thousands, maybe more. Fresh install and all updates brought current only a month ago yet some updates can't install because the ones they replace refuse to uninstall. That's not the kind of thing that should be machine specific. Rebuilding from the OEM install CD (Win XP Pro SP2), SP3 and all updates worked just fine, but building a clean install with all of the updates should not be like a game of Jenga. Updates that FAIL to uninstall when they need to be replaced by new ones should be an embarassment to Microsoft. KB2656405 KB2656353 KB2633880 and KB2633870 refused to uninstall, preventing updates to KB2737019 KB2698023 KB2729450 and KB2729449 errors were 0x66A 0x64C 0x645 and 0x66A respectively. On my new build with all updates, I WONDER how many MS updates would FAIL to uninstall? I realize that some are never supposed to be uninstalled, but how many do you think would FAIL to uninstall if I tested this question? There are so many Framework updates and they take so LONG to install that I'm getting a sneaking suspicion that HALF of my time doing updates on a fresh system install is just Framework, like 2 hours worth... Framework just in stall .net3.5 and it up dates http://www.microsoft.com/en-us/downl....aspx?id=25150 That might work. Then again, Why isn't Framework 4.0 backward compatible with all previous versions of Framework? I may take more copious notes with time annotations next time. WHY does SP3 update fail so much from MS Update site? JS Because you need IE8 or newer. JS For you are running IE6 sp1 with a clean install. http://www.microsoft.com/en-us/downl...ils.aspx?id=43 If I need IE8 before installing SP3 then why doesn't MS update site install IE8 before SP3? Is this dependency you describe documented somewhere? JS Plus MS Update need to be Windows Installer 4.5 Redistributable http://www.microsoft.com/en-us/downl...s.aspx?id=8483 MS Update makes absolutely no attempt to push MSI 4.5 at any point in the update process. MSI 4.5 might even fix some installs but apparently some old updates and installs have FAULTY uninstall files that MSI 4.5 does not fix. For example, Microsoft Security Essentials installed before August 2012 apparently has faulty uninstall files, mistakenly looking for some crucial files in a bizarre directory named with a long string of random characters. Directory names like that are apparently for temporary scratch files. Curiously, even though MS Update Site does not push MSI 4.5, it apparently notices whether you have it installed and offers the exact identical revision of MS Security Essentials in MSI 3.1 or MSI 4.5 format, accordingly. |
#22
|
|||
|
|||
MS Update Site failures after a clean installation
"Greegor" wrote in message ...
On Nov 23, 6:52 pm, "John Smith" wrote: "Greegor" wrote You do know this is an XP usenet group, don't ya Glen? Your argument that it works fine on MOST computers is weak. Your assertion that SP3 doesn't fail from the update site because you say it works on MOST computers is illogical. I have a small fleet of identical computers chosen because this exact model sold in the tens of thousands, maybe more. Fresh install and all updates brought current only a month ago yet some updates can't install because the ones they replace refuse to uninstall. That's not the kind of thing that should be machine specific. Rebuilding from the OEM install CD (Win XP Pro SP2), SP3 and all updates worked just fine, but building a clean install with all of the updates should not be like a game of Jenga. Updates that FAIL to uninstall when they need to be replaced by new ones should be an embarassment to Microsoft. KB2656405 KB2656353 KB2633880 and KB2633870 refused to uninstall, preventing updates to KB2737019 KB2698023 KB2729450 and KB2729449 errors were 0x66A 0x64C 0x645 and 0x66A respectively. On my new build with all updates, I WONDER how many MS updates would FAIL to uninstall? I realize that some are never supposed to be uninstalled, but how many do you think would FAIL to uninstall if I tested this question? There are so many Framework updates and they take so LONG to install that I'm getting a sneaking suspicion that HALF of my time doing updates on a fresh system install is just Framework, like 2 hours worth... Framework just in stall .net3.5 and it up dates http://www.microsoft.com/en-us/downl....aspx?id=25150 That might work. Then again, Why isn't Framework 4.0 backward compatible with all previous versions of Framework? ..NET 3.5 is all versions of Framework, After all updates, ..NET 4.0 is the next versions of Framework.. It you install MS software that need, it it will be update to .NET 4.0 for you. I may take more copious notes with time annotations next time. WHY does SP3 update fail so much from MS Update site? JS Because you need IE8 or newer. JS For you are running IE6 sp1 with a clean install. http://www.microsoft.com/en-us/downl...ils.aspx?id=43 If I need IE8 before installing SP3 then why doesn't MS update site install IE8 before SP3? Is this dependency you describe documented somewhere? JS Plus MS Update need to be Windows Installer 4.5 Redistributable http://www.microsoft.com/en-us/downl...s.aspx?id=8483 MS Update makes absolutely no attempt to push MSI 4.5 at any point in the update process. MSI 4.5 might even fix some installs but apparently some old updates and installs have FAULTY uninstall files that MSI 4.5 does not fix. For example, Microsoft Security Essentials installed before August 2012 apparently has faulty uninstall files, mistakenly looking for some crucial files in a bizarre directory named with a long string of random characters. Directory names like that are apparently for temporary scratch files. Faulty uninstall files. Now you need to know how to use MS Fix-It http://fixitcenter.support.microsoft.com/Portal Curiously, even though MS Update Site does not push MSI 4.5, it apparently notices whether you have it installed and offers the exact identical revision of MS Security Essentials in MSI 3.1 or MSI 4.5 format, accordingly. The MS Update Website need it, to in stall .NET 4.0, For today New MS Software use MSI 4.5, For MSI 3.1 is for old MS Software, like Windows SP1.... |
#23
|
|||
|
|||
MS Update Site failures after a clean installation
On Nov 25, 12:51*pm, "John Smith" wrote:
"Greegor" wrote in ... On Nov 23, 6:52 pm, "John Smith" wrote: "Greegor" wrote You do know this is an XP usenet group, don't ya Glen? Your argument that it works fine on MOST computers is weak. Your assertion that SP3 doesn't fail from the update site because you say it works on MOST computers is illogical. I have a small fleet of identical computers chosen because this exact model sold in the tens of thousands, maybe more. Fresh install and all updates brought current only a month ago yet some updates can't install because the ones they replace refuse to uninstall. That's not the kind of thing that should be machine specific. Rebuilding from the OEM install CD (Win XP Pro SP2), SP3 and all updates worked just fine, but building a clean install with all of the updates should not be like a game of Jenga. Updates that FAIL to uninstall when they need to be replaced by new ones should be an embarassment to Microsoft. KB2656405 KB2656353 KB2633880 and KB2633870 refused to uninstall, preventing updates to KB2737019 KB2698023 KB2729450 and KB2729449 errors were 0x66A 0x64C 0x645 and 0x66A respectively. On my new build with all updates, I WONDER how many MS updates would FAIL to uninstall? I realize that some are never supposed to be uninstalled, but how many do you think would FAIL to uninstall if I tested this question? There are so many Framework updates and they take so LONG to install that I'm getting a sneaking suspicion that HALF of my time doing updates on a fresh system install is just Framework, like 2 hours worth... Framework just in stall .net3.5 and it up dates http://www.microsoft.com/en-us/downl....aspx?id=25150 That might work. Then again, Why isn't Framework 4.0 backward compatible with all previous versions of Framework? .NET 3.5 is all versions of Framework, After all updates, Got any links to Microsoft documentation that this is the case? If it were true then why does MS Update push FW1,2 and 3 installs after FW 3.5 is installed already? .NET 4.0 is the next versions of Framework.. It you install MS software that need, it it will be update to .NET 4.0 for you. MS Update pushes all Framework updates before any application SW actually needs them. I may take more copious notes with time annotations next time. WHY does SP3 update fail so much from MS Update site? JS Because you need IE8 or newer. JS For you are running IE6 sp1 with a clean install. http://www.microsoft.com/en-us/downl...ils.aspx?id=43 If I need IE8 before installing SP3 then why doesn't MS update site install IE8 before SP3? Is this dependency you describe documented somewhere? JS Plus MS Update need to be Windows Installer 4.5 Redistributable http://www.microsoft.com/en-us/downl...s.aspx?id=8483 MS Update makes absolutely no attempt to push MSI 4.5 at any point in the update process. MSI 4.5 might even fix some installs but apparently some old updates and installs have FAULTY uninstall files that MSI 4.5 does not fix. For example, Microsoft Security Essentials installed before August 2012 apparently has faulty uninstall files, mistakenly looking for some crucial files in a bizarre directory named with a long string of random characters. Directory names like that are apparently for temporary scratch files. Faulty uninstall files. Now you need to know how to use MS Fix-It http://fixitcenter.support.microsoft.com/Portal FAILED to fix MSE uninstall failure due to faulty uninstall file. Does Microsoft pretend that either version of Fixit repairs badly written uninstall files? Curiously, even though MS Update Site does not push MSI 4.5, it apparently notices whether you have it installed and offers the exact identical revision of MS Security Essentials in MSI 3.1 or MSI 4.5 format, accordingly. The MS Update Website need it, to in stall .NET 4.0, If so, then why doesn't MS Update PUSH MSI 4.5 before pushing out FW 4.0? |
#24
|
|||
|
|||
MS Update Site failures after a clean installation
"Greegor" wrote in message ...
On Nov 25, 12:51 pm, "John Smith" wrote If it were true then why does MS Update push FW1,2 and 3 installs after FW 3.5 is installed already? MS Updates for FW1,2 Because you install them, they come not with SP1 or SP2 MS Update pushes all Framework updates before any application SW actually needs them. FAILED to fix MSE uninstall failure due to faulty uninstall file. Does Microsoft pretend that either version of Fixit repairs badly written uninstall files? Curiously, even though MS Update Site does not push MSI 4.5, it apparently notices whether you have it installed and offers the exact identical revision of MS Security Essentials in MSI 3.1 or MSI 4.5 format, accordingly. The MS Update Website need it, to in stall .NET 4.0, If so, then why doesn't MS Update PUSH MSI 4.5 before pushing out FW 4.0? Because sp1 did not have all of it updates, Because SP2 did not have all of it updates, Because SP2-RollUp-1 did not have all of it updates, Because SP2-RollUp-2 did not have all of it updates, and Because SP3 did not have all of it updates.. that is why! You see the Roll-Up you miss before you can move on to SP3 Always turning on the Automatic Updates feature in Windows XP, it will up date Sp1 all the to Sp3 for you, So it will take 3 or 4 days or more to do it, By Restart and I know logging in gets old, but is the right way. Just look how many day, you been doing your way.. Just Start over and do it the right way with, Automatic Updates feature for Windows XP.. Just take the time and do it right.. I just like you all I have is; a Windows XP Sp-1 CD Plus all way get all of you Updates first, in the Sp1, Sp2, and , before install new Software, that go for .NET's, MS Security Essentials, Do not install, until Automatic Updates get you pass the Sp3 Update |
#25
|
|||
|
|||
MS Update Site failures after a clean installation
Do you have any documentation that FW 3.5
will run software written for previous versions? Is there documentation that FW 4.0 will run software written for previous FW versions? If FW 4.0 will run SW written for all previous FW versions, then perhaps update site should stop pushing the old versions once somebody has FW 4.0 on an XT system? In fact, if that's true, why even maintain the old versions at all? Does FW 4.0 really supercede previous versions of FW? Is this documented from Microsoft? Is backwards compatability of FW documented anywhere? |
#26
|
|||
|
|||
MS Update Site failures after a clean installation
"Greegor" wrote in message
... Do you have any documentation that FW 3.5 will run software written for previous versions? Is there documentation that FW 4.0 will run software written for previous FW versions? If FW 4.0 will run SW written for all previous FW versions, then perhaps update site should stop pushing the old versions once somebody has FW 4.0 on an XT system? In fact, if that's true, why even maintain the old versions at all? Does FW 4.0 really supercede previous versions of FW? Is this documented from Microsoft? Is backwards compatability of FW documented anywhere? If you spend just a few minutes doing some online searching, you'd have had your answers long ago: Mailbag: Do I need still need older versions of the .NET Framework on my system after installing .NET Framework 3.5 SP1? http://blogs.msdn.com/b/astebner/arc...0/9557946.aspx Mailbag: Do I need still need older versions of the .NET Framework on my system after installing the .NET Framework 4? http://blogs.msdn.com/b/astebner/arc.../10219046.aspx -- Glen Ventura MS MVP Oct. 2002 - Sept. 2009 CompTIA A+ |
#27
|
|||
|
|||
MS Update Site failures after a clean installation
"John Smith" wrote in message
... "Greegor" wrote in message news:015184a8-457c-453e-93f7- snip WHY does SP3 update fail so much from MS Update site? Because you need IE8 or newer. For you are running IE6 sp1 with a clean install. http://www.microsoft.com/en-us/downl...ils.aspx?id=43 No.... you do NOT need IE8 to update to SP3 or to get updates via Windows or Microsoft Update. If you have XP Gold or SP1, you have IE6 SP1 and cannot access Windows Update.... but if you have XP SP2 or SP3, you have at least IE6 SP2. Formerly there was a problem accessing Windows Update with IE6 SP2 but apparently this is no longer the case and you can update using IE6 SP2.... I don't have IE6 installed anywhere to confirm this. You can also access Windows Update with IE7. There is no requirement for IE8 whatsoever. Plus MS Update need to be Windows Installer 4.5 Redistributable http://www.microsoft.com/en-us/downl...s.aspx?id=8483 Wrong again. Windows Installer 4.5 is NOT needed to use Windows Update or Microsoft Update, or to install XP service packs. -- Glen Ventura MS MVP Oct. 2002 - Sept. 2009 CompTIA A+ |
#28
|
|||
|
|||
MS Update Site failures after a clean installation
"Greegor"
all Usenet do not have:::: alt.windows-xp, alt.os.windows-xp, microsoft.public.windowsxp.setup_deployment, microsoft.public.windowsxp.help_and_support, microsoft.public.windowsxp.general and have Errors if we post to more then Two Groups I on::::: microsoft.public.windowsxp.help_and_support, microsoft.public.windowsxp.general Only............................ wrote in message ... Do you have any documentation that FW 3.5 will run software written for previous versions? Is there documentation that FW 4.0 will run software written for previous FW versions? If FW 4.0 will run SW written for all previous FW versions, then perhaps update site should stop pushing the old versions once somebody has FW 4.0 on an XT system? You have a Windows 7 with on an UI system for all it have and START OUT WITH is: Microsoft .NET Framework 4 Client Profile 38.8MB Version 4.0.30319 In fact, if that's true, why even maintain the old versions at all? Because you running a Old OS call XP..... Does FW 4.0 really supercede previous versions of FW? Yes in Windows 7, 7sp1, 8, and 9. for it was not made for Win-XPsp3 or 2000sp4 Is this documented from Microsoft? yes use www.bing.com for all Microsoft documents.. Is backwards compatability of FW documented anywhere? Full Package To download the full package, rather than the bootstrapper, click on the link below: ..NET Framework 3.5 Service Pack 1 (Full Package) http://download.microsoft.com/downlo...dotnetfx35.exe IMPORTANT: After installing the .NET Framework 3.5 SP1 package (either the bootstrapper or the full package) you should immediately install the update KB959209 to address a set of known application compatibility issues. http://support.microsoft.com/kb/959209 In addition, on Windows Vista x64 and Windows Server 2008 x64, install the update KB967190 to address a file association issue for XPS documents. You Said: Why does SP3 fail from the update site so much? I too had better luck with downloading it standalone and installing it. Because you use a standalone installing, Not the Automatic Updates feature.... For the Automatic Updates feature will install, Web-site update for you to use, For the Web-site have to be in stall to be use, So that Win95 and 98 will not to be able to use it, Because Automatic Updates feature have been disable, in older versions of windows, And the to is coming that XP to will be disable.. -- Always turning on the Automatic Updates feature in Windows XP. Faulty uninstall files. Now you need to know how to use MS Fix-It http://fixitcenter.support.microsoft.com/Portal |
#29
|
|||
|
|||
MS Update Site failures after a clean installation
"glee" wrote in message ...
"John Smith" wrote in message ... "Greegor" wrote in message news:015184a8-457c-453e-93f7- snip WHY does SP3 update fail so much from MS Update site? Because you need IE8 or newer. For you are running IE6 sp1 with a clean install. http://www.microsoft.com/en-us/downl...ils.aspx?id=43 No.... you do NOT need IE8 to update to SP3 or to get updates via Windows or Microsoft Update. If you have XP Gold or SP1, you have IE6 SP1 and cannot access Windows Update.... but if you have XP SP2 or SP3, you have at least IE6 SP2. Formerly there was a problem accessing Windows Update with IE6 SP2 but apparently this is no longer the case and you can update using IE6 SP2.... I don't have IE6 installed anywhere to confirm this. You can also access Windows Update with IE7. There is no requirement for IE8 whatsoever. He running IE6sp1 on a XPsp3, I requirement a latest software........ for that OS Plus MS Update need to be Windows Installer 4.5 Redistributable http://www.microsoft.com/en-us/downl...s.aspx?id=8483 Wrong again. Windows Installer 4.5 is NOT needed to use Windows Update or Microsoft Update, or to install XP service packs. Need for .NET4 and up.... Mr. Glen Ventura He stated whit XP Service Pack 1, He needed to Automatic Updates too, XP Service Pack 2, It would Update Internet Explorer 6 for XP Service Pack 2, Before moving on to all Updates to XP Service Pack 3.... Update for Internet Explorer 6 for XP Service Pack 2 (KB888240) System requirements Supported operating systems: Windows XP Service Pack 2 This update applies to Internet Explorer 6.0 with the following operating systems: XP Service Pack 2 (SP2) http://www.microsoft.com/en-us/downl...ils.aspx?id=22 Windows Internet Explorer 7 for Windows XP System requirements Supported operating systems: Windows XP Service Pack 2, Windows XP Service Pack 3 Supported Operating Systems: Windows XP Service Pack 2 (SP2); Windows XP Service Pack 3 (SP3) Computer/Processor: Computer with a 233MHz processor or higher (Pentium processor recommended) Memory: Memory requirements listed below are for Internet Explorer itself. Any machine with the recommended amount of memory for Windows (for example, 128 MB for Windows XP) will meet the memory requirements for Internet Explorer 7. Windows XP Service Pack 2 (SP2) - 64 MB Windows XP Service Pack 3 (SP3) - 64 MB Drive: CD-ROM drive (if installation is done from a CD-ROM) Display: Super VGA (800 x 600) or higher-resolution monitor with 256 colors Peripherals: Modem or Internet connection; Microsoft Mouse, Microsoft IntelliMouse, or compatible pointing device http://www.microsoft.com/en-us/downl...ails.aspx?id=2 Windows Internet Explorer 8 for Windows XP System requirements Supported operating systems: Windows XP Service Pack 2, Windows XP Service Pack 3 Internet Explorer 8 runs on any of the following operating systems: Windows 7, 32-bit versions Windows 7, 64-bit versions Windows Vista, 32-bit versions Windows Vista, 64-bit versions Windows Vista with Service Pack 1 (SP 1) or a later version Windows XP, 32-bit versions with Service Pack 2 (SP2) or a later version Windows XP Professional, 64-bit Edition Windows Server 2003, 32-bit versions with Service Pack 2 (SP2) or a later version Windows Server 2003, 64-bit versions with Service Pack 2 (SP2) or a later version Windows Server 2008, 32-bit, or a later version Windows Server 2008, 64-bit, or a later version http://www.microsoft.com/en-us/downl...ils.aspx?id=43 -- Always turning on the Automatic Updates feature in Windows XP. Faulty uninstall files. Now you need to know how to use MS Fix-It http://fixitcenter.support.microsoft.com/Portal |
#30
|
|||
|
|||
MS Update Site failures after a clean installation
"Greegor" wrote in message
... [ Tony cited problems with SP3 from MS Update site and success with downloaded standalone version. ] Why does SP3 fail from the update site so much? I too had better luck with downloading it standalone and installing it. On Nov 15, 6:16 am, "glee" wrote: Well, it doesn't... the majority of installs via auto-update are successful. Failures are reported in forums and newsgroups, the much larger numbers with no problems don't report in forums that they had a non-problem. That said, many of the failures can be attributed to leaving an aggressive anti-virus/Internet security suite active during the installation. For SP2 and SP3 installs I have done in my shop, I use the standalone because I already have it downloaded, but on the occasions that I have installed them on-site via auto-update, I have not had any problems. I've never had a problem with service packs via auto-update on Vista or Win Seven. YMMV, as always. You do know this is an XP usenet group, don't ya Glen? Yes, I do. I specifically posted about XP service packs, and rarely seeing issues installing them via automatic updates. I then mentioned I have also not seen an issue installing Vista and Seven service packs. Again, you seem to be having a problem reading what is written. Your argument that it works fine on MOST computers is weak. Your assertion that SP3 doesn't fail from the update site because you say it works on MOST computers is illogical. That's because I did NOT make such an assertion. Once again, you can't read. I did NOT state "SP3 doesn't fail from the update site" as you claim.... I specifically stated: "the majority of installs via auto-update are successful. Failures are reported in forums and newsgroups, the much larger numbers with no problems don't report in forums that they had a non-problem. That said, many of the failures can be attributed to leaving an aggressive anti-virus/Internet security suite active during the installation." I have a small fleet of identical computers chosen because this exact model sold in the tens of thousands, maybe more. Fresh install and all updates brought current only a month ago yet some updates can't install because the ones they replace refuse to uninstall. What updates are you referring to, from the past month? What "refuses to uninstall"? You don't uninstall updates to "replace" them with others. If an update supersedes an older one (described as "replacing" it in a KB article), it's installation routine takes care of replacement. It sounds like you don't know how to install updates in the first place. That's not the kind of thing that should be machine specific. Rebuilding from the OEM install CD (Win XP Pro SP2), SP3 and all updates worked just fine, but building a clean install with all of the updates should not be like a game of Jenga. Updates that FAIL to uninstall when they need to be replaced by new ones should be an embarassment to Microsoft. KB2656405 KB2656353 KB2633880 and KB2633870 refused to uninstall, preventing updates to KB2737019 KB2698023 KB2729450 and KB2729449 You don't uninstall the older updates prior to installing the newer ones listed. Again, you are installing updates incorrectly, then complaining that the process gives you errors due to your own interference. errors were 0x66A 0x64C 0x645 and 0x66A respectively. On my new build with all updates, I WONDER how many MS updates would FAIL to uninstall? I realize that some are never supposed to be uninstalled, but how many do you think would FAIL to uninstall if I tested this question? It depends on what was installed since they were. Some updates no longer uninstall because they were superseded during a later update's installation. There are so many Framework updates and they take so LONG to install that I'm getting a sneaking suspicion that HALF of my time doing updates on a fresh system install is just Framework, like 2 hours worth... I install updates, including .NET updates, on client machines all the time. It takes nowhere near two hours to install the .NET updates. I may take more copious notes with time annotations next time. WHY does SP3 update fail so much from MS Update site? It doesn't "fail so much".... the majority of installations are successful from Microsoft Upodate or via Automatic Updates. Even on a fresh clean install with no malware software installed yet! -- Glen Ventura MS MVP Oct. 2002 - Sept. 2009 CompTIA A+ |
Thread Tools | |
Display Modes | |
|
|