• Welcome to Tux Reports: Where Penguins Fly. We hope you find the topics varied, interesting, and worthy of your time. Please become a member and join in the discussions.

Windows Update

K

KCB

Flightless Bird
I have three (3) computers at my house that run Windows XP. All three have
been updated to SP3, with Internet Explorer 8, and all other critical, and
most recommended updates, and I haven't had a problem with ANY updates. One
is a home-built desktop, one is a Toshiba laptop, and the last one is a
desktop from HP. Can you imagine that? Three entirely different machines,
all updated to SP3 (with IE8), and NO problems!
 
R

Rob

Flightless Bird
KCB <bcgc_qc@hootmail.com> wrote:
> I have three (3) computers at my house that run Windows XP. All three have
> been updated to SP3, with Internet Explorer 8, and all other critical, and
> most recommended updates, and I haven't had a problem with ANY updates. One
> is a home-built desktop, one is a Toshiba laptop, and the last one is a
> desktop from HP. Can you imagine that? Three entirely different machines,
> all updated to SP3 (with IE8), and NO problems!


The majority of users are like you.
Only BillW50 is imagining a lot of problems, but like you I have not
seen them myself. Every of the several hundred computers at work are
updated just fine.
 
B

BillW50

Flightless Bird
KCB wrote on Sat, 4 Sep 2010 22:53:47 -0400:
> I have three (3) computers at my house that run Windows XP. All three
> have been updated to SP3, with Internet Explorer 8, and all other
> critical, and most recommended updates, and I haven't had a problem with
> ANY updates. One is a home-built desktop, one is a Toshiba laptop, and
> the last one is a desktop from HP. Can you imagine that? Three
> entirely different machines, all updated to SP3 (with IE8), and NO
> problems!


That is how it is supposed to work! Although I have a dozen plus
computers here and some of them were flawless when updating. But some
others wasn't. Two of them were HP computers with AMD CPUs. And they
would no longer boot after SP3 was installed.

Two of my Celeron HP machines would have endless problems from Windows
updates with Explorer (shell) crashing. One update would cause it to
become unstable and the next one would fix it. Then the next one made it
unstable and the next one would fix it. And this was endless. I finally
got tired of this nonsense and installed Aston Shell to replace Explorer
Shell.

The point of all of this is that there are millions of different
configurations out there. And it is impossible to always get it right,
even if you are Microsoft. Thus it doesn't always work. That is why some
experts say don't put your eggs into one basket and jump on the newest
and latest version or update. As it is better to wait until most of the
bugs have been worked out.

And remember there are new bugs in SP3 that Microsoft have no plans on
fixing. One of them causes OE6 to hang on folder,dbx during automatic
compacting. And some other applications and drivers still haven't been
updated to work with SP3 and probably never will.

If you care to do research you can search all of this under Internet
search engines. As it is all there if you look for it.

--
Bill
Asus EEE PC 702G4 ~ 2GB RAM ~ 16GB-SDHC
Xandros Linux (build 2007-10-19 13:03)
 
B

BillW50

Flightless Bird
Rob wrote on 05 Sep 2010 09:16:54 GMT:
> KCB <bcgc_qc@hootmail.com> wrote:
>> I have three (3) computers at my house that run Windows XP. All three have
>> been updated to SP3, with Internet Explorer 8, and all other critical, and
>> most recommended updates, and I haven't had a problem with ANY updates. One
>> is a home-built desktop, one is a Toshiba laptop, and the last one is a
>> desktop from HP. Can you imagine that? Three entirely different machines,
>> all updated to SP3 (with IE8), and NO problems!

>
> The majority of users are like you.
> Only BillW50 is imagining a lot of problems, but like you I have not
> seen them myself. Every of the several hundred computers at work are
> updated just fine.


There are no imaging problems! As the problems are very real and
Microsoft has acknowledged some of them. I have a dozen plus computers
here and some update fine and some don't do well at all. The biggest
problems I had were on HP machines. I haven't seen a problem with as
Toshiba computers yet, but that doesn't mean they don't exist. As they
very well could be for all I know.

Now if you wasn't to put your head in the sand and want to believe no
Windows update ever screwed up anybodies computer. Well that is your
choice. But it is pretty foolish thinking if you ask me. And I feel
sorry for anybody computers your advice has screwed up.

Heck, it isn't just Windows updates that screws up some computers. This
Xandros Linux for example used to have updates on Asus' servers. The
newer ones changed the way Xandros worked. And it gave Linux the ability
to see drives with drive letters. So it was more friendly for users who
was used to Windows. Although this made it very unlike Linux and I
didn't see the point. And now all updates are gone from their servers.
And I don't think you can find new netbooks with Linux on them anymore.
As Linux netbooks (or even computers) just don't sell too well. So not
many of them are supporting Linux machines anymore.

And speaking about netbooks and those especially with SSDs... most of
them don't have enough room to do Windows updates anyway. As Microsoft
claims you need 900MB free to update to SP3. Well I think the real
number is closer to needing 1.5GB free during my tests. And some of
these machines just doesn't have that kind of room to successfully
install SP3 anyway.

--
Bill
Asus EEE PC 702G4 ~ 2GB RAM ~ 16GB-SDHC
Xandros Linux (build 2007-10-19 13:03)
 
J

Jeff Strickland

Flightless Bird
"KCB" <bcgc_qc@hootmail.com> wrote in message
news:i5v0o7$hj4$1@news.eternal-september.org...
>I have three (3) computers at my house that run Windows XP. All three have
>been updated to SP3, with Internet Explorer 8, and all other critical, and
>most recommended updates, and I haven't had a problem with ANY updates.
>One is a home-built desktop, one is a Toshiba laptop, and the last one is a
>desktop from HP. Can you imagine that? Three entirely different machines,
>all updated to SP3 (with IE8), and NO problems!


This happens more than you might expect. All of the machines I've worked on
are updated to SP3 and the subesquent "recommended updates" and I've had no
problems.
 
B

BillW50

Flightless Bird
Jeff Strickland wrote on Sun, 5 Sep 2010 09:46:31 -0700:
> "KCB" <bcgc_qc@hootmail.com> wrote in message
> news:i5v0o7$hj4$1@news.eternal-september.org...
>> I have three (3) computers at my house that run Windows XP. All three have
>> been updated to SP3, with Internet Explorer 8, and all other critical, and
>> most recommended updates, and I haven't had a problem with ANY updates.
>> One is a home-built desktop, one is a Toshiba laptop, and the last one is a
>> desktop from HP. Can you imagine that? Three entirely different machines,
>> all updated to SP3 (with IE8), and NO problems!

>
> This happens more than you might expect. All of the machines I've worked on
> are updated to SP3 and the subesquent "recommended updates" and I've had no
> problems.


Not for me! All of the HP machines running AMD processors would no
longer boot. HP blames Microsoft and Microsoft blames HP... well whatever!

And those that have been burned by updates before have a right to be gun
shy of them. Fool me once, shame on you; fool me twice, shame on me.

Speaking about updates, SP2 was once of the worst I have ever
experienced. Oh they all worked, but every single system I have updated
from SP1 to SP2 has always lost lots of performance. And the only way I
got around this problem was to slipstream SP2 on an install disc and
then it worked fine. Although you had to reinstall Windows to do this.

And even if SP3 updates just fine (you must not use OE6 and auto
compacting), it eats up lots of room. As the Windows updates doesn't
give you a choice to clean up all of the unnecessary files you don't
need anymore. That is just sloppy programming. If you don't care about
sloppy programming, then I guess it wouldn't bother you.

Nonetheless, there are still thousands of not millions of users who have
been burned by Windows updates. This is undeniable and it is real. Even
Microsoft have documented some of these problems.

--
Bill
Asus EEE PC 702G4 ~ 2GB RAM ~ 16GB-SDHC
Xandros Linux (build 2007-10-19 13:03)
 
J

Jeff Strickland

Flightless Bird
"BillW50" <BillW50@aol.kom> wrote in message
news:i60km8$9hs$1@news.eternal-september.org...
> Jeff Strickland wrote on Sun, 5 Sep 2010 09:46:31 -0700:
>> "KCB" <bcgc_qc@hootmail.com> wrote in message
>> news:i5v0o7$hj4$1@news.eternal-september.org...
>>> I have three (3) computers at my house that run Windows XP. All three
>>> have been updated to SP3, with Internet Explorer 8, and all other
>>> critical, and most recommended updates, and I haven't had a problem with
>>> ANY updates. One is a home-built desktop, one is a Toshiba laptop, and
>>> the last one is a desktop from HP. Can you imagine that? Three
>>> entirely different machines, all updated to SP3 (with IE8), and NO
>>> problems!

>>
>> This happens more than you might expect. All of the machines I've worked
>> on are updated to SP3 and the subesquent "recommended updates" and I've
>> had no problems.

>
> Not for me! All of the HP machines running AMD processors would no longer
> boot. HP blames Microsoft and Microsoft blames HP... well whatever!
>
> And those that have been burned by updates before have a right to be gun
> shy of them. Fool me once, shame on you; fool me twice, shame on me.
>
> Speaking about updates, SP2 was once of the worst I have ever experienced.
> Oh they all worked, but every single system I have updated from SP1 to SP2
> has always lost lots of performance. And the only way I got around this
> problem was to slipstream SP2 on an install disc and then it worked fine.
> Although you had to reinstall Windows to do this.
>
> And even if SP3 updates just fine (you must not use OE6 and auto
> compacting), it eats up lots of room. As the Windows updates doesn't give
> you a choice to clean up all of the unnecessary files you don't need
> anymore. That is just sloppy programming. If you don't care about sloppy
> programming, then I guess it wouldn't bother you.
>
> Nonetheless, there are still thousands of not millions of users who have
> been burned by Windows updates. This is undeniable and it is real. Even
> Microsoft have documented some of these problems.
>
> --


I'm running an HP with XPPro, SP3, IE8, and all of the recommended updates.
You are a corner case.
 
J

Jeff Strickland

Flightless Bird
"Daave" <daave@example.com> wrote in message
news:i60msp$ulv$1@news.eternal-september.org...
> BillW50 wrote:
>> All of the HP machines running AMD processors would no
>> longer boot. HP blames Microsoft and Microsoft blames HP... well
>> whatever!

>
> If you are talking about the SP3 upgrade, this has already been addressed.
> The fault was with HP, and they offered a patch to correct their mistake:
>
> http://h10025.www1.hp.com/ewfrf/wc/document?lc=en&dlc=en&cc=us&docname=c01457284
>



The "fault was HP," yet you continue to put MSoft on the hook. It sucks to
be you. Get over it and move on.
 
B

BillW50

Flightless Bird
Jeff Strickland wrote on Sun, 5 Sep 2010 12:07:33 -0700:
> "Daave" <daave@example.com> wrote in message
> news:i60msp$ulv$1@news.eternal-september.org...
>> BillW50 wrote:
>>> All of the HP machines running AMD processors would no
>>> longer boot. HP blames Microsoft and Microsoft blames HP... well
>>> whatever!

>> If you are talking about the SP3 upgrade, this has already been addressed.
>> The fault was with HP, and they offered a patch to correct their mistake:
>>
>> http://h10025.www1.hp.com/ewfrf/wc/document?lc=en&dlc=en&cc=us&docname=c01457284

>
> The "fault was HP," yet you continue to put MSoft on the hook. It sucks to
> be you. Get over it and move on.


I did get over it Jeff. I stripped the HP computers for parts. And
Microsoft is always on the hook! And that isn't my fault, as it is
Microsoft's fault. So don't look at me.

I personally believe all of the great programmers at Microsoft have
already retired. So Microsoft is in a new direction and they lost their
focus. I personally don't like where it is going. But I personally have
no interest if Microsoft wins or loses. So what do I care? Heck there is
always Mac and Linux if Microsoft goes belly up.

--
Bill
Asus EEE PC 702G4 ~ 2GB RAM ~ 16GB-SDHC
Xandros Linux (build 2007-10-19 13:03)
 
B

BillW50

Flightless Bird
Jeff Strickland wrote on Sun, 5 Sep 2010 12:06:06 -0700:
> I'm running an HP with XPPro, SP3, IE8, and all of the recommended updates.
> You are a corner case.


That is great Jeff! My XP Pro machines are doing well with SP3 and IE8
too. I wish I could say the same for some of my XP Home machines though.

--
Bill
Asus EEE PC 702G4 ~ 2GB RAM ~ 16GB-SDHC
Xandros Linux (build 2007-10-19 13:03)
 
J

Jeff Strickland

Flightless Bird
"BillW50" <BillW50@aol.kom> wrote in message
news:i60r27$nrp$1@news.eternal-september.org...
> Jeff Strickland wrote on Sun, 5 Sep 2010 12:07:33 -0700:
>> "Daave" <daave@example.com> wrote in message
>> news:i60msp$ulv$1@news.eternal-september.org...
>>> BillW50 wrote:
>>>> All of the HP machines running AMD processors would no
>>>> longer boot. HP blames Microsoft and Microsoft blames HP... well
>>>> whatever!
>>> If you are talking about the SP3 upgrade, this has already been
>>> addressed. The fault was with HP, and they offered a patch to correct
>>> their mistake:
>>>
>>> http://h10025.www1.hp.com/ewfrf/wc/document?lc=en&dlc=en&cc=us&docname=c01457284

>>
>> The "fault was HP," yet you continue to put MSoft on the hook. It sucks
>> to be you. Get over it and move on.

>
> I did get over it Jeff. I stripped the HP computers for parts. And
> Microsoft is always on the hook! And that isn't my fault, as it is
> Microsoft's fault. So don't look at me.
>


I don't think it's MSoft's fault if HP had to come out with a patch that
makes its machines work right, and the other machines already work right.
Think what you want.
 
B

BillW50

Flightless Bird
Jeff Strickland wrote on Sun, 5 Sep 2010 13:28:33 -0700:
> "BillW50" <BillW50@aol.kom> wrote in message
> news:i60r27$nrp$1@news.eternal-september.org...
>> Jeff Strickland wrote on Sun, 5 Sep 2010 12:07:33 -0700:
>>> "Daave" <daave@example.com> wrote in message
>>> news:i60msp$ulv$1@news.eternal-september.org...
>>>> BillW50 wrote:
>>>>> All of the HP machines running AMD processors would no
>>>>> longer boot. HP blames Microsoft and Microsoft blames HP... well
>>>>> whatever!
>>>> If you are talking about the SP3 upgrade, this has already been
>>>> addressed. The fault was with HP, and they offered a patch to correct
>>>> their mistake:
>>>>
>>>> http://h10025.www1.hp.com/ewfrf/wc/document?lc=en&dlc=en&cc=us&docname=c01457284
>>> The "fault was HP," yet you continue to put MSoft on the hook. It sucks
>>> to be you. Get over it and move on.

>> I did get over it Jeff. I stripped the HP computers for parts. And
>> Microsoft is always on the hook! And that isn't my fault, as it is
>> Microsoft's fault. So don't look at me.
>>

>
> I don't think it's MSoft's fault if HP had to come out with a patch that
> makes its machines work right, and the other machines already work right.
> Think what you want.


I too think it was HP fault! But that doesn't totally excuse Microsoft
either. As why did Microsoft screw up OE6 automatic compacting with SP3
and doesn't care to fix it? Microsoft claims they no longer support it.

Well okay, well then why bother to update it to screw it up? When
Microsoft doesn't care about its own applications, then I don't care
about Microsoft. As that is what made Microsoft great in the beginning.
Otherwise they become no better than anybody else. Microsoft has changed
a lot in the last few years. And I don't see it as the better.

--
Bill
Asus EEE PC 702G4 ~ 2GB RAM ~ 16GB-SDHC
Xandros Linux (build 2007-10-19 13:03)
 
O

Ottmar Freudenberger

Flightless Bird
"BillW50" <BillW50@aol.kom> schrieb:

> Not for me! All of the HP machines running AMD processors would no
> longer boot. HP blames Microsoft and Microsoft blames HP... well whatever!


Once again:
http://support.microsoft.com/kb/953356/en-us
The update is offered via WU/AU to possibly affected systems *prior* to
SP3. http://catalog.update.microsoft.com/v7/site/Search.aspx?q=953356

Why is this issue caused by a lazy OEM (not only HP)?

| This problem occurs when a System Preparation (Sysprep) image is created
| on a computer that uses an Intel processor and is then deployed to a
| computer that does not use an Intel processor.

Bye,
Freudi
 
R

Rob

Flightless Bird
Jeff Strickland <crwlrjeff@yahoo.com> wrote:
> I don't think it's MSoft's fault if HP had to come out with a patch that
> makes its machines work right, and the other machines already work right.
> Think what you want.


HP used an invalid method of putting the OS on their systems, which
caused an invalid file to be present in their image.

I never install systems using disk imaging, but only using unattended
install from the network. This problem never occurs in that case
because Windows autodetects the hardware including processor.
 
B

BillW50

Flightless Bird
Rob wrote on 06 Sep 2010 07:44:30 GMT:
> Jeff Strickland <crwlrjeff@yahoo.com> wrote:
>> I don't think it's MSoft's fault if HP had to come out with a patch that
>> makes its machines work right, and the other machines already work right.
>> Think what you want.

>
> HP used an invalid method of putting the OS on their systems, which
> caused an invalid file to be present in their image.
>
> I never install systems using disk imaging, but only using unattended
> install from the network. This problem never occurs in that case
> because Windows autodetects the hardware including processor.


Microsoft never heard of beta testing before? There are millions of HP
computers out there and Microsoft was too lazy to test one of them?

--
Bill
Asus EEE PC 702G4 ~ 2GB RAM ~ 16GB-SDHC
Xandros Linux (build 2007-10-19 13:03)
 
R

Rob

Flightless Bird
BillW50 <BillW50@aol.kom> wrote:
> Rob wrote on 06 Sep 2010 07:44:30 GMT:
>> Jeff Strickland <crwlrjeff@yahoo.com> wrote:
>>> I don't think it's MSoft's fault if HP had to come out with a patch that
>>> makes its machines work right, and the other machines already work right.
>>> Think what you want.

>>
>> HP used an invalid method of putting the OS on their systems, which
>> caused an invalid file to be present in their image.
>>
>> I never install systems using disk imaging, but only using unattended
>> install from the network. This problem never occurs in that case
>> because Windows autodetects the hardware including processor.

>
> Microsoft never heard of beta testing before? There are millions of HP
> computers out there and Microsoft was too lazy to test one of them?


They probably test only with machines that were installed according
to their directions, not with machines that violate those rules.

And HP violated the rules.
 
O

Ottmar Freudenberger

Flightless Bird
"BillW50" <BillW50@aol.kom> schrieb:
> Rob wrote on 06 Sep 2010 07:44:30 GMT:
>> Jeff Strickland <crwlrjeff@yahoo.com> wrote:
>>> I don't think it's MSoft's fault if HP had to come out with a patch that
>>> makes its machines work right, and the other machines already work right.
>>> Think what you want.

>>
>> HP used an invalid method of putting the OS on their systems, which
>> caused an invalid file to be present in their image.
>>
>> I never install systems using disk imaging, but only using unattended
>> install from the network. This problem never occurs in that case
>> because Windows autodetects the hardware including processor.

>
> Microsoft never heard of beta testing before?


HP (and other OEM) didn't either?

> There are millions of HP
> computers out there and Microsoft was too lazy to test one of them?


No problem if it's a Intel processor or the "master" has been
configured properly.

Bye,
Freudi
 
B

BillW50

Flightless Bird
Rob wrote on 06 Sep 2010 15:28:38 GMT:
> BillW50 <BillW50@aol.kom> wrote:
>> Rob wrote on 06 Sep 2010 07:44:30 GMT:
>>> Jeff Strickland <crwlrjeff@yahoo.com> wrote:
>>>> I don't think it's MSoft's fault if HP had to come out with a patch that
>>>> makes its machines work right, and the other machines already work right.
>>>> Think what you want.
>>> HP used an invalid method of putting the OS on their systems, which
>>> caused an invalid file to be present in their image.
>>>
>>> I never install systems using disk imaging, but only using unattended
>>> install from the network. This problem never occurs in that case
>>> because Windows autodetects the hardware including processor.

>> Microsoft never heard of beta testing before? There are millions of HP
>> computers out there and Microsoft was too lazy to test one of them?

>
> They probably test only with machines that were installed according
> to their directions, not with machines that violate those rules.
>
> And HP violated the rules.


What rules Rob? All major manufactures image the drives. Are you telling
me all major manufactures don't follow the rules? Whatever they are?

--
Bill
Asus EEE PC 702G4 ~ 2GB RAM ~ 16GB-SDHC
Xandros Linux (build 2007-10-19 13:03)
 
O

Ottmar Freudenberger

Flightless Bird
"BillW50" <BillW50@aol.kom> schrieb:
> Rob wrote on 06 Sep 2010 15:28:38 GMT:
>> BillW50 <BillW50@aol.kom> wrote:


>>> Microsoft never heard of beta testing before? There are millions of HP
>>> computers out there and Microsoft was too lazy to test one of them?

>>
>> They probably test only with machines that were installed according
>> to their directions, not with machines that violate those rules.
>>
>> And HP violated the rules.

>
> What rules Rob?


http://support.microsoft.com/kb/828287/

| Different processor vendors
| We do not support using Sysprep to install an operating system from
| an image if the image was created by using a computer that has a
| different processor. For example, you cannot create a Sysprep image
| on a computer that has an Intel processor and deploy the image to a
| computer that has an AMD processor.

And now, please feel free to reread MSKB article 9553356 once again(?)

> All major manufactures image the drives. Are you telling
> me all major manufactures don't follow the rules?


He didn't. You may need to rejustify your logic module.

Bye,
Freudi
 
Top