My support nightmare
-
I seen people install and uninstall and have nightmares with there os from hidden settings. Maybe you should format your machine. :-D
"I do not know with what weapons World War 3 will be fought, but World War 4 will be fought with sticks and stones." Einstein
Yes, I told them that I think a reformat will fix it, but the machine is underpowered anyhow, so I think they should buy a new one.
Christian Graus Driven to the arms of OSX by Vista. Please read this[^] if you don't like the answer I gave to your question. "! i don't exactly like or do programming and it only gives me a headache." - spotted in VB forums.
-
Yes, I told them that I think a reformat will fix it, but the machine is underpowered anyhow, so I think they should buy a new one.
Christian Graus Driven to the arms of OSX by Vista. Please read this[^] if you don't like the answer I gave to your question. "! i don't exactly like or do programming and it only gives me a headache." - spotted in VB forums.
Buying a new PC is not an ideal solution to Microsoft's inability to provide an unistaller that actually works. I've seen this problem repeatedly (and others like it) since .Net was introduced. Any installation leaves behind a footprint somewhere when you uninstall it, and those settings are detected by any future installation.
"A Journey of a Thousand Rest Stops Begins with a Single Movement"
-
Buying a new PC is not an ideal solution to Microsoft's inability to provide an unistaller that actually works. I've seen this problem repeatedly (and others like it) since .Net was introduced. Any installation leaves behind a footprint somewhere when you uninstall it, and those settings are detected by any future installation.
"A Journey of a Thousand Rest Stops Begins with a Single Movement"
I agree. I was thinking of starting a blog at MicrosoftSucks.com, but it's taken. Surprise. I did find a hardcore removal tool, which I am passing on.
Christian Graus Driven to the arms of OSX by Vista. Please read this[^] if you don't like the answer I gave to your question. "! i don't exactly like or do programming and it only gives me a headache." - spotted in VB forums.
-
So, I dialled into a client machine to try to work out why our WPF app would not work. Here's what I found. .NET 1.1 was installed. Apart from that, it was all 3.5 SP1, that is, the 2.0 and 3.0 service pack that come with those as well. Our app would crash when run. At one point it had run and THEN crashed ( because some moron decided it was OK for a .NET 3.5 app to crash and report invalid XAML if WMP 10 was not installed ), I have the error log to prove that. But now, it just crashes. I wrote a winforms 'hello world' app, just a button that, when pressed, showed 'hello world'. This also crashes when I try to run it. I uninstalled .NET 3.5 SP1, and installed just 3.5. This did not fix the issue. So, I uninstalled 3.5, which I needed to do before it would let me uninstall 3.0 SP1 and 2.0 SP2. Having done all that, I tried to reinstall 3.5. The installer now crashes every time I try to install it. I download the original 2.0 installer. It won't install, it says it's incompatible with other updates ( I assume the footprints of SP1 ). I try to install 2.0 SP2 by itself. That just shows a dialog with no text in it, and 'installer error' as the title. So, I am back with 3.5 SP1. I reinstall this, no issues. But, I am back where I started. Any .NET app, crashes. I look in the error log and find: .NET Runtime version 2.0.50727.3053 - Fatal Execution Engine Error (7A097706) (80131506) I googled this and got a suggestion to clear my temp directories, but the remote session I was working in dropped out and the client had gone home. Three and a half hours later, I have achieved nothing. Has anyone seen anything like this ?
Christian Graus Driven to the arms of OSX by Vista. Please read this[^] if you don't like the answer I gave to your question. "! i don't exactly like or do programming and it only gives me a headache." - spotted in VB forums.
Christian - Speaking to your installer issue with you not being able to get the installers to reinstall - I've seen that happen before, because the uninstall leaves behind the .NET directory and some files (although I do not recall seeing the error messages you are seeing) Uninstall the whole mess, then: Make certain the C:\Windows\Microsoft.NET\Framework\v2.0.50727 folder is gone Make certain the C:\Windows\Microsoft.NET\Framework\v3.0 folder is gone Make certain the C:\Windows\Microsoft.NET\Framework\v3.5 folder is gone Then you can try to reinstall
:..::. Douglas H. Troy ::..
Bad Astronomy |VCF|wxWidgets|WTL -
Christian - Speaking to your installer issue with you not being able to get the installers to reinstall - I've seen that happen before, because the uninstall leaves behind the .NET directory and some files (although I do not recall seeing the error messages you are seeing) Uninstall the whole mess, then: Make certain the C:\Windows\Microsoft.NET\Framework\v2.0.50727 folder is gone Make certain the C:\Windows\Microsoft.NET\Framework\v3.0 folder is gone Make certain the C:\Windows\Microsoft.NET\Framework\v3.5 folder is gone Then you can try to reinstall
:..::. Douglas H. Troy ::..
Bad Astronomy |VCF|wxWidgets|WTLThanks - I think my issue is more registry entries, but I've downloaded a tool to remove them, so we'll try that and see.
Christian Graus Driven to the arms of OSX by Vista. Please read this[^] if you don't like the answer I gave to your question. "! i don't exactly like or do programming and it only gives me a headache." - spotted in VB forums.
-
Thanks - I think my issue is more registry entries, but I've downloaded a tool to remove them, so we'll try that and see.
Christian Graus Driven to the arms of OSX by Vista. Please read this[^] if you don't like the answer I gave to your question. "! i don't exactly like or do programming and it only gives me a headache." - spotted in VB forums.
I've been through the whole mess myself. Even down to killing the directories, GAC folders, and registry entries, and stll ended up formatting the machine and starting over. Worked like a charm after that...
A guide to posting questions on CodeProject[^]
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007, 2008 -
I've been through the whole mess myself. Even down to killing the directories, GAC folders, and registry entries, and stll ended up formatting the machine and starting over. Worked like a charm after that...
A guide to posting questions on CodeProject[^]
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007, 2008 -
So, I dialled into a client machine to try to work out why our WPF app would not work. Here's what I found. .NET 1.1 was installed. Apart from that, it was all 3.5 SP1, that is, the 2.0 and 3.0 service pack that come with those as well. Our app would crash when run. At one point it had run and THEN crashed ( because some moron decided it was OK for a .NET 3.5 app to crash and report invalid XAML if WMP 10 was not installed ), I have the error log to prove that. But now, it just crashes. I wrote a winforms 'hello world' app, just a button that, when pressed, showed 'hello world'. This also crashes when I try to run it. I uninstalled .NET 3.5 SP1, and installed just 3.5. This did not fix the issue. So, I uninstalled 3.5, which I needed to do before it would let me uninstall 3.0 SP1 and 2.0 SP2. Having done all that, I tried to reinstall 3.5. The installer now crashes every time I try to install it. I download the original 2.0 installer. It won't install, it says it's incompatible with other updates ( I assume the footprints of SP1 ). I try to install 2.0 SP2 by itself. That just shows a dialog with no text in it, and 'installer error' as the title. So, I am back with 3.5 SP1. I reinstall this, no issues. But, I am back where I started. Any .NET app, crashes. I look in the error log and find: .NET Runtime version 2.0.50727.3053 - Fatal Execution Engine Error (7A097706) (80131506) I googled this and got a suggestion to clear my temp directories, but the remote session I was working in dropped out and the client had gone home. Three and a half hours later, I have achieved nothing. Has anyone seen anything like this ?
Christian Graus Driven to the arms of OSX by Vista. Please read this[^] if you don't like the answer I gave to your question. "! i don't exactly like or do programming and it only gives me a headache." - spotted in VB forums.
That is awful. Do you have an MSDN subscription? Call Microsoft! After reading your post I am so thankful that I only write web applications. Yeah, it comes with it own set of headaches but nothing like that. The worst part is that you end up looking like an incompetent ass and it is completely not your fault.
I didn't get any requirements for the signature
-
That is awful. Do you have an MSDN subscription? Call Microsoft! After reading your post I am so thankful that I only write web applications. Yeah, it comes with it own set of headaches but nothing like that. The worst part is that you end up looking like an incompetent ass and it is completely not your fault.
I didn't get any requirements for the signature
ToddHileHoffer wrote:
Do you have an MSDN subscription? Call Microsoft!
Microsoft support is non existant. Even when I was an MVP, it was a joke.
Christian Graus Driven to the arms of OSX by Vista. Please read this[^] if you don't like the answer I gave to your question. "! i don't exactly like or do programming and it only gives me a headache." - spotted in VB forums.
-
So, I dialled into a client machine to try to work out why our WPF app would not work. Here's what I found. .NET 1.1 was installed. Apart from that, it was all 3.5 SP1, that is, the 2.0 and 3.0 service pack that come with those as well. Our app would crash when run. At one point it had run and THEN crashed ( because some moron decided it was OK for a .NET 3.5 app to crash and report invalid XAML if WMP 10 was not installed ), I have the error log to prove that. But now, it just crashes. I wrote a winforms 'hello world' app, just a button that, when pressed, showed 'hello world'. This also crashes when I try to run it. I uninstalled .NET 3.5 SP1, and installed just 3.5. This did not fix the issue. So, I uninstalled 3.5, which I needed to do before it would let me uninstall 3.0 SP1 and 2.0 SP2. Having done all that, I tried to reinstall 3.5. The installer now crashes every time I try to install it. I download the original 2.0 installer. It won't install, it says it's incompatible with other updates ( I assume the footprints of SP1 ). I try to install 2.0 SP2 by itself. That just shows a dialog with no text in it, and 'installer error' as the title. So, I am back with 3.5 SP1. I reinstall this, no issues. But, I am back where I started. Any .NET app, crashes. I look in the error log and find: .NET Runtime version 2.0.50727.3053 - Fatal Execution Engine Error (7A097706) (80131506) I googled this and got a suggestion to clear my temp directories, but the remote session I was working in dropped out and the client had gone home. Three and a half hours later, I have achieved nothing. Has anyone seen anything like this ?
Christian Graus Driven to the arms of OSX by Vista. Please read this[^] if you don't like the answer I gave to your question. "! i don't exactly like or do programming and it only gives me a headache." - spotted in VB forums.
-
It was quicker than pulling my hair out for another 4 hours... What's left of it anyway. :-D
A guide to posting questions on CodeProject[^]
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007, 2008 -
So, I dialled into a client machine to try to work out why our WPF app would not work. Here's what I found. .NET 1.1 was installed. Apart from that, it was all 3.5 SP1, that is, the 2.0 and 3.0 service pack that come with those as well. Our app would crash when run. At one point it had run and THEN crashed ( because some moron decided it was OK for a .NET 3.5 app to crash and report invalid XAML if WMP 10 was not installed ), I have the error log to prove that. But now, it just crashes. I wrote a winforms 'hello world' app, just a button that, when pressed, showed 'hello world'. This also crashes when I try to run it. I uninstalled .NET 3.5 SP1, and installed just 3.5. This did not fix the issue. So, I uninstalled 3.5, which I needed to do before it would let me uninstall 3.0 SP1 and 2.0 SP2. Having done all that, I tried to reinstall 3.5. The installer now crashes every time I try to install it. I download the original 2.0 installer. It won't install, it says it's incompatible with other updates ( I assume the footprints of SP1 ). I try to install 2.0 SP2 by itself. That just shows a dialog with no text in it, and 'installer error' as the title. So, I am back with 3.5 SP1. I reinstall this, no issues. But, I am back where I started. Any .NET app, crashes. I look in the error log and find: .NET Runtime version 2.0.50727.3053 - Fatal Execution Engine Error (7A097706) (80131506) I googled this and got a suggestion to clear my temp directories, but the remote session I was working in dropped out and the client had gone home. Three and a half hours later, I have achieved nothing. Has anyone seen anything like this ?
Christian Graus Driven to the arms of OSX by Vista. Please read this[^] if you don't like the answer I gave to your question. "! i don't exactly like or do programming and it only gives me a headache." - spotted in VB forums.
-
So, I dialled into a client machine to try to work out why our WPF app would not work. Here's what I found. .NET 1.1 was installed. Apart from that, it was all 3.5 SP1, that is, the 2.0 and 3.0 service pack that come with those as well. Our app would crash when run. At one point it had run and THEN crashed ( because some moron decided it was OK for a .NET 3.5 app to crash and report invalid XAML if WMP 10 was not installed ), I have the error log to prove that. But now, it just crashes. I wrote a winforms 'hello world' app, just a button that, when pressed, showed 'hello world'. This also crashes when I try to run it. I uninstalled .NET 3.5 SP1, and installed just 3.5. This did not fix the issue. So, I uninstalled 3.5, which I needed to do before it would let me uninstall 3.0 SP1 and 2.0 SP2. Having done all that, I tried to reinstall 3.5. The installer now crashes every time I try to install it. I download the original 2.0 installer. It won't install, it says it's incompatible with other updates ( I assume the footprints of SP1 ). I try to install 2.0 SP2 by itself. That just shows a dialog with no text in it, and 'installer error' as the title. So, I am back with 3.5 SP1. I reinstall this, no issues. But, I am back where I started. Any .NET app, crashes. I look in the error log and find: .NET Runtime version 2.0.50727.3053 - Fatal Execution Engine Error (7A097706) (80131506) I googled this and got a suggestion to clear my temp directories, but the remote session I was working in dropped out and the client had gone home. Three and a half hours later, I have achieved nothing. Has anyone seen anything like this ?
Christian Graus Driven to the arms of OSX by Vista. Please read this[^] if you don't like the answer I gave to your question. "! i don't exactly like or do programming and it only gives me a headache." - spotted in VB forums.
Christian Graus wrote:
Has anyone seen anything like this ?
Yes, in many products in their infancy stage. Oh wait, you wanted a solution?
Don't attribute to stupidity what can be equally well explained by buerocracy.
My latest article | Linkify!| FoldWithUs! | sighist -
So, I dialled into a client machine to try to work out why our WPF app would not work. Here's what I found. .NET 1.1 was installed. Apart from that, it was all 3.5 SP1, that is, the 2.0 and 3.0 service pack that come with those as well. Our app would crash when run. At one point it had run and THEN crashed ( because some moron decided it was OK for a .NET 3.5 app to crash and report invalid XAML if WMP 10 was not installed ), I have the error log to prove that. But now, it just crashes. I wrote a winforms 'hello world' app, just a button that, when pressed, showed 'hello world'. This also crashes when I try to run it. I uninstalled .NET 3.5 SP1, and installed just 3.5. This did not fix the issue. So, I uninstalled 3.5, which I needed to do before it would let me uninstall 3.0 SP1 and 2.0 SP2. Having done all that, I tried to reinstall 3.5. The installer now crashes every time I try to install it. I download the original 2.0 installer. It won't install, it says it's incompatible with other updates ( I assume the footprints of SP1 ). I try to install 2.0 SP2 by itself. That just shows a dialog with no text in it, and 'installer error' as the title. So, I am back with 3.5 SP1. I reinstall this, no issues. But, I am back where I started. Any .NET app, crashes. I look in the error log and find: .NET Runtime version 2.0.50727.3053 - Fatal Execution Engine Error (7A097706) (80131506) I googled this and got a suggestion to clear my temp directories, but the remote session I was working in dropped out and the client had gone home. Three and a half hours later, I have achieved nothing. Has anyone seen anything like this ?
Christian Graus Driven to the arms of OSX by Vista. Please read this[^] if you don't like the answer I gave to your question. "! i don't exactly like or do programming and it only gives me a headache." - spotted in VB forums.
I've had a similar problem, reinstalling/repairing the .net 3.5sp1 fixed it, failing that it could be down to registry problems.
Software Kinetics (requires SL3 beta) - Moving software
-
I was one of the victim of of the issue. I removed all the .net framework and reinstalled .net frame work 2 the again installed 3.5 which resolved my problem. I think you can try that.
-
Did you install the 3 recommended patches after 3.5 SP1 as noted on the SP1 download page?
xacc.ide
IronScheme - 1.0 beta 3 - out now!
((lambda (x) `((lambda (x) ,x) ',x)) '`((lambda (x) ,x) ',x))There's MORE patches AFTER all the ones that SP1 installs ? No, I didn't install SP1 at ALL, the client did, and all I did was focus on winding back. I HAVE run SP1 without any other patches on my machine tho and had no issues.
Christian Graus Driven to the arms of OSX by Vista. Please read this[^] if you don't like the answer I gave to your question. "! i don't exactly like or do programming and it only gives me a headache." - spotted in VB forums.
-
ToddHileHoffer wrote:
Do you have an MSDN subscription? Call Microsoft!
Microsoft support is non existant. Even when I was an MVP, it was a joke.
Christian Graus Driven to the arms of OSX by Vista. Please read this[^] if you don't like the answer I gave to your question. "! i don't exactly like or do programming and it only gives me a headache." - spotted in VB forums.
In a way sometimes the vendor support of any major now looks horrible. We would need to carefully assess their solutions before implementing their recommendations so that we are not pushed to a situation of pulling our hairs at the 23rd hour with an embarrasing face before the client. On a personal front, I once encountered a true moronic dumbnut in Nokia Customercare who suggested me to use 'Restore Factory Settings' (equivalent of formatting) on the device just to check and assess the battery life. I have shared out a review here: www.mouthshut.com/review/Nokia_5800_XpressMusic-168046-1.html[^] (The category for my mobile Nokia 6030 is unavailable still and hence requested MouthShut support to have one created and the article moved there). Had this been another layman, he would have religiously followed their advice only to see all his downloaded ringtones, Phone Memory based Phonebook, Personalised Settings vanish that easily.
Vasudevan Deepak Kumar Personal Homepage
Tech Gossips
The woods are lovely, dark and deep, But I have promises to keep, And miles to go before I sleep, And miles to go before I sleep! -
Christian Graus wrote:
Has anyone seen anything like this ?
Yes, in many products in their infancy stage. Oh wait, you wanted a solution?
Don't attribute to stupidity what can be equally well explained by buerocracy.
My latest article | Linkify!| FoldWithUs! | sighistpeterchen wrote:
Yes, in many products in their infancy stage.
.NET has been out since 2002, seven years is long enough to work out how to install a patch. And, no, I didn't really expect a solution, I just wanted to complain.
Christian Graus Driven to the arms of OSX by Vista. Please read this[^] if you don't like the answer I gave to your question. "! i don't exactly like or do programming and it only gives me a headache." - spotted in VB forums.
-
peterchen wrote:
Yes, in many products in their infancy stage.
.NET has been out since 2002, seven years is long enough to work out how to install a patch. And, no, I didn't really expect a solution, I just wanted to complain.
Christian Graus Driven to the arms of OSX by Vista. Please read this[^] if you don't like the answer I gave to your question. "! i don't exactly like or do programming and it only gives me a headache." - spotted in VB forums.
I didn't say .NET is in its infacy....
Don't attribute to stupidity what can be equally well explained by buerocracy.
My latest article | Linkify!| FoldWithUs! | sighist -
So, I dialled into a client machine to try to work out why our WPF app would not work. Here's what I found. .NET 1.1 was installed. Apart from that, it was all 3.5 SP1, that is, the 2.0 and 3.0 service pack that come with those as well. Our app would crash when run. At one point it had run and THEN crashed ( because some moron decided it was OK for a .NET 3.5 app to crash and report invalid XAML if WMP 10 was not installed ), I have the error log to prove that. But now, it just crashes. I wrote a winforms 'hello world' app, just a button that, when pressed, showed 'hello world'. This also crashes when I try to run it. I uninstalled .NET 3.5 SP1, and installed just 3.5. This did not fix the issue. So, I uninstalled 3.5, which I needed to do before it would let me uninstall 3.0 SP1 and 2.0 SP2. Having done all that, I tried to reinstall 3.5. The installer now crashes every time I try to install it. I download the original 2.0 installer. It won't install, it says it's incompatible with other updates ( I assume the footprints of SP1 ). I try to install 2.0 SP2 by itself. That just shows a dialog with no text in it, and 'installer error' as the title. So, I am back with 3.5 SP1. I reinstall this, no issues. But, I am back where I started. Any .NET app, crashes. I look in the error log and find: .NET Runtime version 2.0.50727.3053 - Fatal Execution Engine Error (7A097706) (80131506) I googled this and got a suggestion to clear my temp directories, but the remote session I was working in dropped out and the client had gone home. Three and a half hours later, I have achieved nothing. Has anyone seen anything like this ?
Christian Graus Driven to the arms of OSX by Vista. Please read this[^] if you don't like the answer I gave to your question. "! i don't exactly like or do programming and it only gives me a headache." - spotted in VB forums.
Just curiuos, why are you not using the Dotnet cleanup tool ? http://blogs.msdn.com/astebner/pages/8904493.aspx[^] This should cleanup all of dotnet including all reg settings
My second computer is your linux box.
