GOD

  • Thread starter Thread starter Lynn
  • Start date Start date
L

Lynn

Guest
WHAT A NIGHTMAIRE?????? !!!!!!!!!!!!! WHAT THE HECK IS GOING ON
MICROSOFT????????????????????????????????????????????????????????????????
 
No one here represents or works for Microsoft.

Perhap your stuck CapsLock key is causing your problems?
--
~PA Bear


Lynn wrote:
> WHAT A NIGHTMAIRE?????? !!!!!!!!!!!!! WHAT THE HECK IS GOING ON
> MICROSOFT????????????????????????????????????????????????????????????????
 
I notice you left off your usual signature in that reply:

~Robear Dyer (PA Bear)
MS MVP-Windows (IE, OE, Security, Shell/User)
AumHa VSOP & Admin; DTS-L.org

PA Bear wrote:

> No one here represents or works for Microsoft.
>
> Perhap your stuck CapsLock key is causing your problems?
>
> Lynn wrote:
>> WHAT A NIGHTMAIRE?????? !!!!!!!!!!!!! WHAT THE HECK IS GOING ON
>> MICROSOFT????????????????????????????????????????????????????????????????
 
Lynn wrote:
> WHAT A NIGHTMAIRE?????? !!!!!!!!!!!!! WHAT THE HECK IS GOING ON
> MICROSOFT????????????????????????????????????????????????????????????????

What does "God" have to do with whatever problem you think you are having?
(I say "you think" because you gave no clue beyond the newsgroup you are
posting in what your specific issue might be.)

As far as "What the heck is going on, Microsoft?" (Notice - I did not use
all upper case lettering and I utilized minimal punctuation) - I am going to
throw myself out there and make a LARGE assumption that you may be speaking
of the numbers of .NET framewwork update issues being posted about over the
last week.

"What is going on" (what I have seen reported - may/may not be true) is that
an update (or more) was released that seemingly did not check some things it
should have (in particular - if certain previous updates (optional) that
were necessary to this update (or more) were installed before applying
itself.) This has caused various issues.


The general solution to this is a long one - although it seems deceptively
simple:

- Remove ALL traces (uninstall completely) every version of the .NET
Framework you now have installed.
- Install each of the versions (1.1, 2.0 at least, 3.0 as well for good
measure) and their patches (one version at a time, in time/date order for
the patches for each version - in other words... 1.1, patches for 1.1 in
date order... 2.0, patches for 2.0 in date order... 3.0, patches for 3.0 in
date order.)

Then your problem with the repeating installation (or other possible
scenarios) should be over.


Although there have been reports of such fixes *not* working - one cannot be
sure that ANY part was done correctly/completely - as this can become quite
technical and not everyone may be leaning into that area of skill/expertise.

There are also people who have had luck with other solutions/work-arounds
that are much simpler (Repairing the .NET Frameworks as opposed to
removing/properly patching them.) That may work for you and those methods
are covered in the articles linked below - under the title(s), "Repair the
..NET Framework".


The solution I am throwing into the mix...

(1) You need to repair .NET Framework 1.1 - obliterating all remnants of it
and installing it/patching it fully.

How to troubleshoot Microsoft .NET Framework 1.1 installation issues
http://support.microsoft.com/kb/824643
- Unregister and then reregister Windows Installer (See article)
- Manually remove and then reinstall the .NET Framework 1.1 (See Article)
For the articles below, follow the "IT professionals" link and find the
download for your OS.
- Download/Install http://support.microsoft.com/kb/867460/
- Download/Install http://support.microsoft.com/kb/886903/
- Download/Install http://support.microsoft.com/kb/928366/

Reboot as needed and at the end.

(2) You need to repair .NET Framework 2.0 - obliterating all remnants of it
and installing it/patching it fully.

How to troubleshoot Microsoft .NET Framework 2.0 installation issues
http://support.microsoft.com/kb/908077/
- Unregister and then reregister Windows Installer (See article)
- Manually remove and then reinstall the .NET Framework 2.0 (See Article)
For the articles below, follow the "IT professionals" link and find the
download for your OS.
- Download/Install http://support.microsoft.com/kb/917283/
- Download/Install http://support.microsoft.com/kb/922770/
- Download/Install http://support.microsoft.com/kb/928365/

Reboot as needed and at the end.

(3) You need to repair .NET Framework 3.0 - obliterating all remnants of it
and installing it/patching it fully.

Unfortunately - there is no particular article pertaining to .NET Framework
3.0 that I could find. I have not had issues, however, just going into the
Control Panel --> Add or Remove Programs and just locating/removing it and
its patches. I suggest you do the same...

Download/install using this distributable package:
http://www.microsoft.com/downloads/...0B-F857-4A14-83F5-25634C3BF043&displaylang=en

Reboot as needed and at the end.

(4) Cleanup your updates system...

Get Dial-a-Fix:
http://wiki.djlizard.net/Dial-a-fix

Use its options to fix:
- Windows Installer
- Windows Update
- All the Registration Center options

Turn off the "Empty System32\Catroot 2"
Do NOT do "Flush SoftwareDistribution".

Then click "GO"... May take a while.

Reboot when it is done...

(5) Visit http://windowsupdate.microsoft.com/ and scan for updates. Choose
the critical updates you need and install them. Do not bother getting
hardware updates (unless you happen to have some Microsoft hardware
installed) and "Optional Updates" are *usually* just what the name infers -
but feel free to see if you want any of the "Optional" ones.

(6) Come back here and let us know how you faired.

--
Shenan Stanley
MS-MVP
--
How To Ask Questions The Smart Way
http://www.catb.org/~esr/faqs/smart-questions.html
 
Shenan,

I think the concept of a crappy software writer from Microsoft pushing out
patches had occurred to many of us -- including me -- a few days ago.

It really would be nice for Microsoft to pay a knowledgeable software writer
much more money than it paid the original author(s) for them to push out a
GOOD patch and automatically fix this debacle.

Alan

"Alan" <somewhere@nospam.not> wrote in message
news:e1IEjjCxHHA.4076@TK2MSFTNGP02.phx.gbl...
> TaurArian,
>
> That's a very glib and cavalier response. You seem to be very sure that
> the problem so many people here are having is somehow THEIR fault, and not
> the update itself.
>
> Shouldn't someone from the number one Software company in the world who
> writes -- and publishes -- an update for a prior installation that MAY
> (according to you) be corrupt first test for that possible corruption?
>
> And if it IS corrupt, shouldn't a well-written update try to fix the
> corruption and then install? Or just not attempt to install.
>
> I think a phrase from the Hippocratic Oath that all doctors pledge is apt
> here: "To help, or at least to do no harm."
>
> Alan
>
> "TaurArian" <TaurArian@discussions.microsoft.com> wrote in message
> news:4645EDDE-BA11-4369-B593-D09A779CB37C@microsoft.com...
>> The framework update is failing due to corruption of the original
>> installation of the framework package. That to me appears to be a problem
>> with your computer not the update. Perhaps blame the person who looks
>> after
>> the maintenance etc on your computer.
>>
>>


"Shenan Stanley" <newshelper@gmail.com> wrote in message
news:OR0cahnxHHA.1184@TK2MSFTNGP04.phx.gbl...

> {Snipped}

> What is going on" (what I have seen reported - may/may not be true) is
> that an update (or more) was released that seemingly did not check some
> things it should have (in particular - if certain previous updates
> (optional) that were necessary to this update (or more) were installed
> before applying itself.) This has caused various issues.
>
> {Snip Rest}
 
Lynn wrote:
> WHAT A NIGHTMAIRE?????? !!!!!!!!!!!!! WHAT THE HECK IS GOING ON
> MICROSOFT????????????????????????????????????????????????????????????????

Shenan Stanley wrote:
> What does "God" have to do with whatever problem you think you are
> having? (I say "you think" because you gave no clue beyond the
> newsgroup you are posting in what your specific issue might be.)
>
> As far as "What the heck is going on, Microsoft?" (Notice - I did
> not use all upper case lettering and I utilized minimal
> punctuation) - I am going to throw myself out there and make a
> LARGE assumption that you may be speaking of the numbers of .NET
> framewwork update issues being posted about over the last week.
>
> "What is going on" (what I have seen reported - may/may not be
> true) is that an update (or more) was released that seemingly did
> not check some things it should have (in particular - if certain
> previous updates (optional) that were necessary to this update (or
> more) were installed before applying itself.) This has caused
> various issues.
>
> The general solution to this is a long one - although it seems
> deceptively simple:
>
> - Remove ALL traces (uninstall completely) every version of the .NET
> Framework you now have installed.
> - Install each of the versions (1.1, 2.0 at least, 3.0 as well for
> good measure) and their patches (one version at a time, in
> time/date order for the patches for each version - in other
> words... 1.1, patches for 1.1 in date order... 2.0, patches for 2.0
> in date order... 3.0, patches for 3.0 in date order.)
>
> Then your problem with the repeating installation (or other possible
> scenarios) should be over.
>
>
> Although there have been reports of such fixes *not* working - one
> cannot be sure that ANY part was done correctly/completely - as
> this can become quite technical and not everyone may be leaning
> into that area of skill/expertise.
> There are also people who have had luck with other
> solutions/work-arounds that are much simpler (Repairing the .NET
> Frameworks as opposed to removing/properly patching them.) That
> may work for you and those methods are covered in the articles
> linked below - under the title(s), "Repair the .NET Framework".
<snipped steps>
<the thread - in its entirity - can be found:>
http://groups.google.com/group/micr...53a68232da1/c44b22454462ea1b?lnk=st&q=&rnum=4

Alan wrote:
> I think the concept of a crappy software writer from Microsoft
> pushing out patches had occurred to many of us -- including me -- a
> few days ago.
> It really would be nice for Microsoft to pay a knowledgeable
> software writer much more money than it paid the original author(s)
> for them to push out a GOOD patch and automatically fix this
> debacle.

<Alan also attached this to the response in this thread>
<... for reasons unknown ...>

<begin extraneous quote here>


TaurArian wrote:
> The framework update is failing due to corruption of the original
> installation of the framework package. That to me appears to be a
> problem with your computer not the update. Perhaps blame the
> person who looks after the maintenance etc on your computer.

Alan wrote:
> TaurArian,
>
> That's a very glib and cavalier response. You seem to be very sure
> that the problem so many people here are having is somehow THEIR
> fault, and not the update itself.
>
> Shouldn't someone from the number one Software company in the
> world who writes -- and publishes -- an update for a prior
> installation that MAY (according to you) be corrupt first test for
> that possible corruption?
> And if it IS corrupt, shouldn't a well-written update try to fix
> the corruption and then install? Or just not attempt to install.
>
> I think a phrase from the Hippocratic Oath that all doctors pledge
> is apt here: "To help, or at least to do no harm."

<end extraneous quote here>

While I agree - it would be nice for there to be some tool put out to
correct this issue (and it wouldn't be too hard to script most of it
actually) - I don't plan on ceasing my attempts to help those who ask for.
The best I can do right now - beyond writing some script that might help -
is to put the steps out there. Perhaps someone will look at them and use
them as pseudo-code to fix it and in the meantime - someone else might fix
their own issues and not have to worry about waiting. Heck - perhaps
someone will look at the steps I publish and eliminate some, correct
something or just have an epiphany of an easier method of fixing it. If two
brains are better than one - what are dozens?

You have to remember - this 'debacle' has only existed (in its current state
in reference to the latest (July 10, 2007) .NET Framework issues) for a
total of four (4) full days. Admittedly - this is one of the first times I
have seen quite this overwhelming response to a released update/patch
(excluding perhaps SP2) - but it doesn't change the desire to try and help.

--
Shenan Stanley
MS-MVP
--
How To Ask Questions The Smart Way
http://www.catb.org/~esr/faqs/smart-questions.html
 
Shenan,

I'm sorry if you might have thought I was criticizing your attempt to help.
That wasn't my intent at all.

I'm not a Microsoft basher by any means. In another thread in this newsgroup
I have mentioned that I used to work for a company in the mid-90's to which
Microsoft outsourced its phone support.

To the world, when people dialed Redmond and reached us, WE were Microsoft.
And I was proud of my connection to Microsoft.

I suppose I'm just disappointed -- and to a degree, a bit angry -- that
Microsoft has allowed something of this magnitude to be released and has not
seen fit to at least publicly mention that they might have messed up and are
actively working to correct it.

Alan

"Shenan Stanley" <newshelper@gmail.com> wrote in message
news:eYkCEzoxHHA.3616@TK2MSFTNGP02.phx.gbl...
> Lynn wrote:
>> WHAT A NIGHTMAIRE?????? !!!!!!!!!!!!! WHAT THE HECK IS GOING ON
>> MICROSOFT????????????????????????????????????????????????????????????????
>
> Shenan Stanley wrote:
>> What does "God" have to do with whatever problem you think you are
>> having? (I say "you think" because you gave no clue beyond the
>> newsgroup you are posting in what your specific issue might be.)
>>
>> As far as "What the heck is going on, Microsoft?" (Notice - I did
>> not use all upper case lettering and I utilized minimal
>> punctuation) - I am going to throw myself out there and make a
>> LARGE assumption that you may be speaking of the numbers of .NET
>> framewwork update issues being posted about over the last week.
>>
>> "What is going on" (what I have seen reported - may/may not be
>> true) is that an update (or more) was released that seemingly did
>> not check some things it should have (in particular - if certain
>> previous updates (optional) that were necessary to this update (or
>> more) were installed before applying itself.) This has caused
>> various issues.
>>
>> The general solution to this is a long one - although it seems
>> deceptively simple:
>>
>> - Remove ALL traces (uninstall completely) every version of the .NET
>> Framework you now have installed.
>> - Install each of the versions (1.1, 2.0 at least, 3.0 as well for
>> good measure) and their patches (one version at a time, in
>> time/date order for the patches for each version - in other
>> words... 1.1, patches for 1.1 in date order... 2.0, patches for 2.0
>> in date order... 3.0, patches for 3.0 in date order.)
>>
>> Then your problem with the repeating installation (or other possible
>> scenarios) should be over.
>>
>>
>> Although there have been reports of such fixes *not* working - one
>> cannot be sure that ANY part was done correctly/completely - as
>> this can become quite technical and not everyone may be leaning
>> into that area of skill/expertise.
>> There are also people who have had luck with other
>> solutions/work-arounds that are much simpler (Repairing the .NET
>> Frameworks as opposed to removing/properly patching them.) That
>> may work for you and those methods are covered in the articles
>> linked below - under the title(s), "Repair the .NET Framework".
> <snipped steps>
> <the thread - in its entirity - can be found:>
> http://groups.google.com/group/micr...53a68232da1/c44b22454462ea1b?lnk=st&q=&rnum=4
>
> Alan wrote:
>> I think the concept of a crappy software writer from Microsoft
>> pushing out patches had occurred to many of us -- including me -- a
>> few days ago.
>> It really would be nice for Microsoft to pay a knowledgeable
>> software writer much more money than it paid the original author(s)
>> for them to push out a GOOD patch and automatically fix this
>> debacle.
>
> <Alan also attached this to the response in this thread>
> <... for reasons unknown ...>
>
> <begin extraneous quote here>
>
>
> TaurArian wrote:
>> The framework update is failing due to corruption of the original
>> installation of the framework package. That to me appears to be a
>> problem with your computer not the update. Perhaps blame the
>> person who looks after the maintenance etc on your computer.
>
> Alan wrote:
>> TaurArian,
>>
>> That's a very glib and cavalier response. You seem to be very sure
>> that the problem so many people here are having is somehow THEIR
>> fault, and not the update itself.
>>
>> Shouldn't someone from the number one Software company in the
>> world who writes -- and publishes -- an update for a prior
>> installation that MAY (according to you) be corrupt first test for
>> that possible corruption?
>> And if it IS corrupt, shouldn't a well-written update try to fix
>> the corruption and then install? Or just not attempt to install.
>>
>> I think a phrase from the Hippocratic Oath that all doctors pledge
>> is apt here: "To help, or at least to do no harm."
>
> <end extraneous quote here>
>
> While I agree - it would be nice for there to be some tool put out to
> correct this issue (and it wouldn't be too hard to script most of it
> actually) - I don't plan on ceasing my attempts to help those who ask for.
> The best I can do right now - beyond writing some script that might help -
> is to put the steps out there. Perhaps someone will look at them and use
> them as pseudo-code to fix it and in the meantime - someone else might fix
> their own issues and not have to worry about waiting. Heck - perhaps
> someone will look at the steps I publish and eliminate some, correct
> something or just have an epiphany of an easier method of fixing it. If
> two brains are better than one - what are dozens?
>
> You have to remember - this 'debacle' has only existed (in its current
> state in reference to the latest (July 10, 2007) .NET Framework issues)
> for a total of four (4) full days. Admittedly - this is one of the first
> times I have seen quite this overwhelming response to a released
> update/patch (excluding perhaps SP2) - but it doesn't change the desire to
> try and help.
>
> --
> Shenan Stanley
> MS-MVP
> --
> How To Ask Questions The Smart Way
> http://www.catb.org/~esr/faqs/smart-questions.html
>
 
Hi there,

I strongly believe the software is not crappy since everything installed
just fine on my 2 windows Xp machines which are fully updated.

I suspect that the problem is more related to the man or woman behind the
PC;)

Best regards,
Michel Denie

"Alan" <somewhere@nospam.not> wrote in message
news:OVVrz7oxHHA.4928@TK2MSFTNGP03.phx.gbl...
> Shenan,
>
> I'm sorry if you might have thought I was criticizing your attempt to
> help. That wasn't my intent at all.
>
> I'm not a Microsoft basher by any means. In another thread in this
> newsgroup I have mentioned that I used to work for a company in the
> mid-90's to which Microsoft outsourced its phone support.
>
> To the world, when people dialed Redmond and reached us, WE were
> Microsoft. And I was proud of my connection to Microsoft.
>
> I suppose I'm just disappointed -- and to a degree, a bit angry -- that
> Microsoft has allowed something of this magnitude to be released and has
> not seen fit to at least publicly mention that they might have messed up
> and are actively working to correct it.
>
> Alan
>
> "Shenan Stanley" <newshelper@gmail.com> wrote in message
> news:eYkCEzoxHHA.3616@TK2MSFTNGP02.phx.gbl...
>> Lynn wrote:
>>> WHAT A NIGHTMAIRE?????? !!!!!!!!!!!!! WHAT THE HECK IS GOING ON
>>> MICROSOFT????????????????????????????????????????????????????????????????
>>
>> Shenan Stanley wrote:
>>> What does "God" have to do with whatever problem you think you are
>>> having? (I say "you think" because you gave no clue beyond the
>>> newsgroup you are posting in what your specific issue might be.)
>>>
>>> As far as "What the heck is going on, Microsoft?" (Notice - I did
>>> not use all upper case lettering and I utilized minimal
>>> punctuation) - I am going to throw myself out there and make a
>>> LARGE assumption that you may be speaking of the numbers of .NET
>>> framewwork update issues being posted about over the last week.
>>>
>>> "What is going on" (what I have seen reported - may/may not be
>>> true) is that an update (or more) was released that seemingly did
>>> not check some things it should have (in particular - if certain
>>> previous updates (optional) that were necessary to this update (or
>>> more) were installed before applying itself.) This has caused
>>> various issues.
>>>
>>> The general solution to this is a long one - although it seems
>>> deceptively simple:
>>>
>>> - Remove ALL traces (uninstall completely) every version of the .NET
>>> Framework you now have installed.
>>> - Install each of the versions (1.1, 2.0 at least, 3.0 as well for
>>> good measure) and their patches (one version at a time, in
>>> time/date order for the patches for each version - in other
>>> words... 1.1, patches for 1.1 in date order... 2.0, patches for 2.0
>>> in date order... 3.0, patches for 3.0 in date order.)
>>>
>>> Then your problem with the repeating installation (or other possible
>>> scenarios) should be over.
>>>
>>>
>>> Although there have been reports of such fixes *not* working - one
>>> cannot be sure that ANY part was done correctly/completely - as
>>> this can become quite technical and not everyone may be leaning
>>> into that area of skill/expertise.
>>> There are also people who have had luck with other
>>> solutions/work-arounds that are much simpler (Repairing the .NET
>>> Frameworks as opposed to removing/properly patching them.) That
>>> may work for you and those methods are covered in the articles
>>> linked below - under the title(s), "Repair the .NET Framework".
>> <snipped steps>
>> <the thread - in its entirity - can be found:>
>> http://groups.google.com/group/micr...53a68232da1/c44b22454462ea1b?lnk=st&q=&rnum=4
>>
>> Alan wrote:
>>> I think the concept of a crappy software writer from Microsoft
>>> pushing out patches had occurred to many of us -- including me -- a
>>> few days ago.
>>> It really would be nice for Microsoft to pay a knowledgeable
>>> software writer much more money than it paid the original author(s)
>>> for them to push out a GOOD patch and automatically fix this
>>> debacle.
>>
>> <Alan also attached this to the response in this thread>
>> <... for reasons unknown ...>
>>
>> <begin extraneous quote here>
>>
>>
>> TaurArian wrote:
>>> The framework update is failing due to corruption of the original
>>> installation of the framework package. That to me appears to be a
>>> problem with your computer not the update. Perhaps blame the
>>> person who looks after the maintenance etc on your computer.
>>
>> Alan wrote:
>>> TaurArian,
>>>
>>> That's a very glib and cavalier response. You seem to be very sure
>>> that the problem so many people here are having is somehow THEIR
>>> fault, and not the update itself.
>>>
>>> Shouldn't someone from the number one Software company in the
>>> world who writes -- and publishes -- an update for a prior
>>> installation that MAY (according to you) be corrupt first test for
>>> that possible corruption?
>>> And if it IS corrupt, shouldn't a well-written update try to fix
>>> the corruption and then install? Or just not attempt to install.
>>>
>>> I think a phrase from the Hippocratic Oath that all doctors pledge
>>> is apt here: "To help, or at least to do no harm."
>>
>> <end extraneous quote here>
>>
>> While I agree - it would be nice for there to be some tool put out to
>> correct this issue (and it wouldn't be too hard to script most of it
>> actually) - I don't plan on ceasing my attempts to help those who ask
>> for. The best I can do right now - beyond writing some script that might
>> help - is to put the steps out there. Perhaps someone will look at them
>> and use them as pseudo-code to fix it and in the meantime - someone else
>> might fix their own issues and not have to worry about waiting. Heck -
>> perhaps someone will look at the steps I publish and eliminate some,
>> correct something or just have an epiphany of an easier method of fixing
>> it. If two brains are better than one - what are dozens?
>>
>> You have to remember - this 'debacle' has only existed (in its current
>> state in reference to the latest (July 10, 2007) .NET Framework issues)
>> for a total of four (4) full days. Admittedly - this is one of the first
>> times I have seen quite this overwhelming response to a released
>> update/patch (excluding perhaps SP2) - but it doesn't change the desire
>> to try and help.
>>
>> --
>> Shenan Stanley
>> MS-MVP
>> --
>> How To Ask Questions The Smart Way
>> http://www.catb.org/~esr/faqs/smart-questions.html
>>
>
>
 
Kind of like God's will, huh?? :>

I actually had no problems installing this latest round of patches. My
problem occurred between the June and July patches, when I was getting error
messages whenever I went to the Windows Update site.

Alan

"realcestmoi" <mdenie@dutchweb.nl> wrote in message
news:eMen3wqxHHA.4476@TK2MSFTNGP06.phx.gbl...
> Hi there,
>
> I strongly believe the software is not crappy since everything installed
> just fine on my 2 windows Xp machines which are fully updated.
>
> I suspect that the problem is more related to the man or woman behind the
> PC;)
>
> Best regards,
> Michel Denie
>
> "Alan" <somewhere@nospam.not> wrote in message
> news:OVVrz7oxHHA.4928@TK2MSFTNGP03.phx.gbl...
>> Shenan,
>>
>> I'm sorry if you might have thought I was criticizing your attempt to
>> help. That wasn't my intent at all.
>>
>> I'm not a Microsoft basher by any means. In another thread in this
>> newsgroup I have mentioned that I used to work for a company in the
>> mid-90's to which Microsoft outsourced its phone support.
>>
>> To the world, when people dialed Redmond and reached us, WE were
>> Microsoft. And I was proud of my connection to Microsoft.
>>
>> I suppose I'm just disappointed -- and to a degree, a bit angry -- that
>> Microsoft has allowed something of this magnitude to be released and has
>> not seen fit to at least publicly mention that they might have messed up
>> and are actively working to correct it.
>>
>> Alan
>>
>> "Shenan Stanley" <newshelper@gmail.com> wrote in message
>> news:eYkCEzoxHHA.3616@TK2MSFTNGP02.phx.gbl...
>>> Lynn wrote:
>>>> WHAT A NIGHTMAIRE?????? !!!!!!!!!!!!! WHAT THE HECK IS GOING ON
>>>> MICROSOFT????????????????????????????????????????????????????????????????
>>>
>>> Shenan Stanley wrote:
>>>> What does "God" have to do with whatever problem you think you are
>>>> having? (I say "you think" because you gave no clue beyond the
>>>> newsgroup you are posting in what your specific issue might be.)
>>>>
>>>> As far as "What the heck is going on, Microsoft?" (Notice - I did
>>>> not use all upper case lettering and I utilized minimal
>>>> punctuation) - I am going to throw myself out there and make a
>>>> LARGE assumption that you may be speaking of the numbers of .NET
>>>> framewwork update issues being posted about over the last week.
>>>>
>>>> "What is going on" (what I have seen reported - may/may not be
>>>> true) is that an update (or more) was released that seemingly did
>>>> not check some things it should have (in particular - if certain
>>>> previous updates (optional) that were necessary to this update (or
>>>> more) were installed before applying itself.) This has caused
>>>> various issues.
>>>>
>>>> The general solution to this is a long one - although it seems
>>>> deceptively simple:
>>>>
>>>> - Remove ALL traces (uninstall completely) every version of the .NET
>>>> Framework you now have installed.
>>>> - Install each of the versions (1.1, 2.0 at least, 3.0 as well for
>>>> good measure) and their patches (one version at a time, in
>>>> time/date order for the patches for each version - in other
>>>> words... 1.1, patches for 1.1 in date order... 2.0, patches for 2.0
>>>> in date order... 3.0, patches for 3.0 in date order.)
>>>>
>>>> Then your problem with the repeating installation (or other possible
>>>> scenarios) should be over.
>>>>
>>>>
>>>> Although there have been reports of such fixes *not* working - one
>>>> cannot be sure that ANY part was done correctly/completely - as
>>>> this can become quite technical and not everyone may be leaning
>>>> into that area of skill/expertise.
>>>> There are also people who have had luck with other
>>>> solutions/work-arounds that are much simpler (Repairing the .NET
>>>> Frameworks as opposed to removing/properly patching them.) That
>>>> may work for you and those methods are covered in the articles
>>>> linked below - under the title(s), "Repair the .NET Framework".
>>> <snipped steps>
>>> <the thread - in its entirity - can be found:>
>>> http://groups.google.com/group/micr...53a68232da1/c44b22454462ea1b?lnk=st&q=&rnum=4
>>>
>>> Alan wrote:
>>>> I think the concept of a crappy software writer from Microsoft
>>>> pushing out patches had occurred to many of us -- including me -- a
>>>> few days ago.
>>>> It really would be nice for Microsoft to pay a knowledgeable
>>>> software writer much more money than it paid the original author(s)
>>>> for them to push out a GOOD patch and automatically fix this
>>>> debacle.
>>>
>>> <Alan also attached this to the response in this thread>
>>> <... for reasons unknown ...>
>>>
>>> <begin extraneous quote here>
>>>
>>>
>>> TaurArian wrote:
>>>> The framework update is failing due to corruption of the original
>>>> installation of the framework package. That to me appears to be a
>>>> problem with your computer not the update. Perhaps blame the
>>>> person who looks after the maintenance etc on your computer.
>>>
>>> Alan wrote:
>>>> TaurArian,
>>>>
>>>> That's a very glib and cavalier response. You seem to be very sure
>>>> that the problem so many people here are having is somehow THEIR
>>>> fault, and not the update itself.
>>>>
>>>> Shouldn't someone from the number one Software company in the
>>>> world who writes -- and publishes -- an update for a prior
>>>> installation that MAY (according to you) be corrupt first test for
>>>> that possible corruption?
>>>> And if it IS corrupt, shouldn't a well-written update try to fix
>>>> the corruption and then install? Or just not attempt to install.
>>>>
>>>> I think a phrase from the Hippocratic Oath that all doctors pledge
>>>> is apt here: "To help, or at least to do no harm."
>>>
>>> <end extraneous quote here>
>>>
>>> While I agree - it would be nice for there to be some tool put out to
>>> correct this issue (and it wouldn't be too hard to script most of it
>>> actually) - I don't plan on ceasing my attempts to help those who ask
>>> for. The best I can do right now - beyond writing some script that might
>>> help - is to put the steps out there. Perhaps someone will look at them
>>> and use them as pseudo-code to fix it and in the meantime - someone else
>>> might fix their own issues and not have to worry about waiting. Heck -
>>> perhaps someone will look at the steps I publish and eliminate some,
>>> correct something or just have an epiphany of an easier method of fixing
>>> it. If two brains are better than one - what are dozens?
>>>
>>> You have to remember - this 'debacle' has only existed (in its current
>>> state in reference to the latest (July 10, 2007) .NET Framework issues)
>>> for a total of four (4) full days. Admittedly - this is one of the
>>> first times I have seen quite this overwhelming response to a released
>>> update/patch (excluding perhaps SP2) - but it doesn't change the desire
>>> to try and help.
>>>
>>> --
>>> Shenan Stanley
>>> MS-MVP
>>> --
>>> How To Ask Questions The Smart Way
>>> http://www.catb.org/~esr/faqs/smart-questions.html
>>>
>>
>>
>
>
 
God works in mysteriousways: so do patches;)

By the way the two systems are totaly different one is a 775 conroe machine
and the other is an AMD Atlhon X2 64


"Alan" <somewhere@nospam.not> wrote in message
news:%23xlRTUuxHHA.3364@TK2MSFTNGP02.phx.gbl...
> Kind of like God's will, huh?? :>
>
> I actually had no problems installing this latest round of patches. My
> problem occurred between the June and July patches, when I was getting
> error messages whenever I went to the Windows Update site.
>
> Alan
>
> "realcestmoi" <mdenie@dutchweb.nl> wrote in message
> news:eMen3wqxHHA.4476@TK2MSFTNGP06.phx.gbl...
>> Hi there,
>>
>> I strongly believe the software is not crappy since everything installed
>> just fine on my 2 windows Xp machines which are fully updated.
>>
>> I suspect that the problem is more related to the man or woman behind the
>> PC;)
>>
>> Best regards,
>> Michel Denie
>>
>> "Alan" <somewhere@nospam.not> wrote in message
>> news:OVVrz7oxHHA.4928@TK2MSFTNGP03.phx.gbl...
>>> Shenan,
>>>
>>> I'm sorry if you might have thought I was criticizing your attempt to
>>> help. That wasn't my intent at all.
>>>
>>> I'm not a Microsoft basher by any means. In another thread in this
>>> newsgroup I have mentioned that I used to work for a company in the
>>> mid-90's to which Microsoft outsourced its phone support.
>>>
>>> To the world, when people dialed Redmond and reached us, WE were
>>> Microsoft. And I was proud of my connection to Microsoft.
>>>
>>> I suppose I'm just disappointed -- and to a degree, a bit angry -- that
>>> Microsoft has allowed something of this magnitude to be released and has
>>> not seen fit to at least publicly mention that they might have messed up
>>> and are actively working to correct it.
>>>
>>> Alan
>>>
>>> "Shenan Stanley" <newshelper@gmail.com> wrote in message
>>> news:eYkCEzoxHHA.3616@TK2MSFTNGP02.phx.gbl...
>>>> Lynn wrote:
>>>>> WHAT A NIGHTMAIRE?????? !!!!!!!!!!!!! WHAT THE HECK IS GOING ON
>>>>> MICROSOFT????????????????????????????????????????????????????????????????
>>>>
>>>> Shenan Stanley wrote:
>>>>> What does "God" have to do with whatever problem you think you are
>>>>> having? (I say "you think" because you gave no clue beyond the
>>>>> newsgroup you are posting in what your specific issue might be.)
>>>>>
>>>>> As far as "What the heck is going on, Microsoft?" (Notice - I did
>>>>> not use all upper case lettering and I utilized minimal
>>>>> punctuation) - I am going to throw myself out there and make a
>>>>> LARGE assumption that you may be speaking of the numbers of .NET
>>>>> framewwork update issues being posted about over the last week.
>>>>>
>>>>> "What is going on" (what I have seen reported - may/may not be
>>>>> true) is that an update (or more) was released that seemingly did
>>>>> not check some things it should have (in particular - if certain
>>>>> previous updates (optional) that were necessary to this update (or
>>>>> more) were installed before applying itself.) This has caused
>>>>> various issues.
>>>>>
>>>>> The general solution to this is a long one - although it seems
>>>>> deceptively simple:
>>>>>
>>>>> - Remove ALL traces (uninstall completely) every version of the .NET
>>>>> Framework you now have installed.
>>>>> - Install each of the versions (1.1, 2.0 at least, 3.0 as well for
>>>>> good measure) and their patches (one version at a time, in
>>>>> time/date order for the patches for each version - in other
>>>>> words... 1.1, patches for 1.1 in date order... 2.0, patches for 2.0
>>>>> in date order... 3.0, patches for 3.0 in date order.)
>>>>>
>>>>> Then your problem with the repeating installation (or other possible
>>>>> scenarios) should be over.
>>>>>
>>>>>
>>>>> Although there have been reports of such fixes *not* working - one
>>>>> cannot be sure that ANY part was done correctly/completely - as
>>>>> this can become quite technical and not everyone may be leaning
>>>>> into that area of skill/expertise.
>>>>> There are also people who have had luck with other
>>>>> solutions/work-arounds that are much simpler (Repairing the .NET
>>>>> Frameworks as opposed to removing/properly patching them.) That
>>>>> may work for you and those methods are covered in the articles
>>>>> linked below - under the title(s), "Repair the .NET Framework".
>>>> <snipped steps>
>>>> <the thread - in its entirity - can be found:>
>>>> http://groups.google.com/group/micr...53a68232da1/c44b22454462ea1b?lnk=st&q=&rnum=4
>>>>
>>>> Alan wrote:
>>>>> I think the concept of a crappy software writer from Microsoft
>>>>> pushing out patches had occurred to many of us -- including me -- a
>>>>> few days ago.
>>>>> It really would be nice for Microsoft to pay a knowledgeable
>>>>> software writer much more money than it paid the original author(s)
>>>>> for them to push out a GOOD patch and automatically fix this
>>>>> debacle.
>>>>
>>>> <Alan also attached this to the response in this thread>
>>>> <... for reasons unknown ...>
>>>>
>>>> <begin extraneous quote here>
>>>>
>>>>
>>>> TaurArian wrote:
>>>>> The framework update is failing due to corruption of the original
>>>>> installation of the framework package. That to me appears to be a
>>>>> problem with your computer not the update. Perhaps blame the
>>>>> person who looks after the maintenance etc on your computer.
>>>>
>>>> Alan wrote:
>>>>> TaurArian,
>>>>>
>>>>> That's a very glib and cavalier response. You seem to be very sure
>>>>> that the problem so many people here are having is somehow THEIR
>>>>> fault, and not the update itself.
>>>>>
>>>>> Shouldn't someone from the number one Software company in the
>>>>> world who writes -- and publishes -- an update for a prior
>>>>> installation that MAY (according to you) be corrupt first test for
>>>>> that possible corruption?
>>>>> And if it IS corrupt, shouldn't a well-written update try to fix
>>>>> the corruption and then install? Or just not attempt to install.
>>>>>
>>>>> I think a phrase from the Hippocratic Oath that all doctors pledge
>>>>> is apt here: "To help, or at least to do no harm."
>>>>
>>>> <end extraneous quote here>
>>>>
>>>> While I agree - it would be nice for there to be some tool put out to
>>>> correct this issue (and it wouldn't be too hard to script most of it
>>>> actually) - I don't plan on ceasing my attempts to help those who ask
>>>> for. The best I can do right now - beyond writing some script that
>>>> might help - is to put the steps out there. Perhaps someone will look
>>>> at them and use them as pseudo-code to fix it and in the meantime -
>>>> someone else might fix their own issues and not have to worry about
>>>> waiting. Heck - perhaps someone will look at the steps I publish and
>>>> eliminate some, correct something or just have an epiphany of an easier
>>>> method of fixing it. If two brains are better than one - what are
>>>> dozens?
>>>>
>>>> You have to remember - this 'debacle' has only existed (in its current
>>>> state in reference to the latest (July 10, 2007) .NET Framework issues)
>>>> for a total of four (4) full days. Admittedly - this is one of the
>>>> first times I have seen quite this overwhelming response to a released
>>>> update/patch (excluding perhaps SP2) - but it doesn't change the desire
>>>> to try and help.
>>>>
>>>> --
>>>> Shenan Stanley
>>>> MS-MVP
>>>> --
>>>> How To Ask Questions The Smart Way
>>>> http://www.catb.org/~esr/faqs/smart-questions.html
>>>>
>>>
>>>
>>
>>
>
>
 
You must log in or register to reply here.
Back
Top