What is the procedure for removing NET Framework 2.0?

[Guest Denise]

Hi, I installed NET Framework 2.0 in order to use a program. The program

still can't run without installing another program, which I don't want to do.

I don't and won't need NET Framework 2.0 for the other things that it is

used for, i.e., developing code. Since I'm no longer in need of it, how can

I completely remove it from my computer? It's not listed in Add/Remove

Programs and there's no uninstaller. I created a restore point prior to

installing it. If I restore my computer to the system state using the

restore point, will my computer no longer have NF 2.0?

--

Denise

 

~ If you don't know where you came from, you won't know where you're going.

[Guest Charlie Russel - MVP]

Re: What is the procedure for removing NET Framework 2.0?

 

First, the .NET Framework IS listed under Add/Remove programs as Microsoft

..NET Framework 2.0. (x64)

 

Second, yes, you can restore back to a point prior to installing the

framework and it won't be installed. It probably doesn't actually remove the

files - I'd have to check, but I suspect not.

 

--

Charlie.

http://msmvps.com/xperts64

http://mvp.support.microsoft.com/profile/charlie.russel

 

 

"Denise" <Denise@discussions.microsoft.com> wrote in message

news:A5D5AC71-789E-475C-96D5-9F04093463EE@microsoft.com...

> Hi, I installed NET Framework 2.0 in order to use a program. The program

> still can't run without installing another program, which I don't want to

> do.

> I don't and won't need NET Framework 2.0 for the other things that it is

> used for, i.e., developing code. Since I'm no longer in need of it, how

> can

> I completely remove it from my computer? It's not listed in Add/Remove

> Programs and there's no uninstaller. I created a restore point prior to

> installing it. If I restore my computer to the system state using the

> restore point, will my computer no longer have NF 2.0?

> --

> Denise

>

> ~ If you don't know where you came from, you won't know where you're

> going.

[Guest Tony Sperling]

Re: What is the procedure for removing NET Framework 2.0?

 

Hi Denice,

 

one observation is:

most of all, the framework is an API (application progamming interface) and

is not running anything in the background unless you run a process that

relies on the API. So,unless your installation gives you any headache (which

some have reported), it probably won't be long before you'll need it again,

and removing it will be repetition of extra unneccessary work, at best..

 

More and more modern development is relying on the API as a platform for

more well behaved applications, it takes up some space on your drive, but as

long as you're not asking for it's services it's not doing anything, and

Microsoft API's are known as being considerably more than just simply

rock-solid!. If 'space'is your concern, you already need a much bigger HD.

 

Framework 2.0 is already a bit old and is not a rare requirement - many new

app's will require Framework 3.0 and later.

 

I cannot tell you if removing it is a good idea or not - just that you might

want to give it an extra bit of thought.

 

 

Tony. . .

 

 

"Denise" <Denise@discussions.microsoft.com> wrote in message

news:A5D5AC71-789E-475C-96D5-9F04093463EE@microsoft.com...

> Hi, I installed NET Framework 2.0 in order to use a program. The program

> still can't run without installing another program, which I don't want to

do.

> I don't and won't need NET Framework 2.0 for the other things that it is

> used for, i.e., developing code. Since I'm no longer in need of it, how

can

> I completely remove it from my computer? It's not listed in Add/Remove

> Programs and there's no uninstaller. I created a restore point prior to

> installing it. If I restore my computer to the system state using the

> restore point, will my computer no longer have NF 2.0?

> --

> Denise

>

> ~ If you don't know where you came from, you won't know where you're

going.

[Guest Denise]

Re: What is the procedure for removing NET Framework 2.0?

 

Sorry,. . . when I looked in Add/Remove programs, I looked alphabetically

for NETFramework, not under Microsoft, and I missed it. Thanks :)

--

Denise

 

~ If you don't know where you came from, you won't know where you're going.

 

 

 

"Charlie Russel - MVP" wrote:

> First, the .NET Framework IS listed under Add/Remove programs as Microsoft

> .NET Framework 2.0. (x64)

>

> Second, yes, you can restore back to a point prior to installing the

> framework and it won't be installed. It probably doesn't actually remove the

> files - I'd have to check, but I suspect not.

>

> --

> Charlie.

> http://msmvps.com/xperts64

> http://mvp.support.microsoft.com/profile/charlie.russel

>

>

> "Denise" <Denise@discussions.microsoft.com> wrote in message

> news:A5D5AC71-789E-475C-96D5-9F04093463EE@microsoft.com...

> > Hi, I installed NET Framework 2.0 in order to use a program. The program

> > still can't run without installing another program, which I don't want to

> > do.

> > I don't and won't need NET Framework 2.0 for the other things that it is

> > used for, i.e., developing code. Since I'm no longer in need of it, how

> > can

> > I completely remove it from my computer? It's not listed in Add/Remove

> > Programs and there's no uninstaller. I created a restore point prior to

> > installing it. If I restore my computer to the system state using the

> > restore point, will my computer no longer have NF 2.0?

> > --

> > Denise

> >

> > ~ If you don't know where you came from, you won't know where you're

> > going.

>

[Guest Denise]

Re: What is the procedure for removing NET Framework 2.0?

 

NET Framework 2.0 requires Dr. Watson debugger. In my last computer, I

installed both programs and I soon learned to regret it. I constantly

received Dr. Watson messages, so I don't want to go that route again if I can

help it.

--

Denise

 

~ If you don't know where you came from, you won't know where you're going.

 

 

"Tony Sperling" wrote:

> Hi Denice,

>

> one observation is:

> most of all, the framework is an API (application progamming interface) and

> is not running anything in the background unless you run a process that

> relies on the API. So,unless your installation gives you any headache (which

> some have reported), it probably won't be long before you'll need it again,

> and removing it will be repetition of extra unneccessary work, at best..

>

> More and more modern development is relying on the API as a platform for

> more well behaved applications, it takes up some space on your drive, but as

> long as you're not asking for it's services it's not doing anything, and

> Microsoft API's are known as being considerably more than just simply

> rock-solid!. If 'space'is your concern, you already need a much bigger HD.

>

> Framework 2.0 is already a bit old and is not a rare requirement - many new

> app's will require Framework 3.0 and later.

>

> I cannot tell you if removing it is a good idea or not - just that you might

> want to give it an extra bit of thought.

>

>

> Tony. . .

>

>

> "Denise" <Denise@discussions.microsoft.com> wrote in message

> news:A5D5AC71-789E-475C-96D5-9F04093463EE@microsoft.com...

> > Hi, I installed NET Framework 2.0 in order to use a program. The program

> > still can't run without installing another program, which I don't want to

> do.

> > I don't and won't need NET Framework 2.0 for the other things that it is

> > used for, i.e., developing code. Since I'm no longer in need of it, how

> can

> > I completely remove it from my computer? It's not listed in Add/Remove

> > Programs and there's no uninstaller. I created a restore point prior to

> > installing it. If I restore my computer to the system state using the

> > restore point, will my computer no longer have NF 2.0?

> > --

> > Denise

> >

> > ~ If you don't know where you came from, you won't know where you're

> going.

>

>

>

[Guest Theo]

Re: What is the procedure for removing NET Framework 2.0?

 

Perhaps you need to look at other sources for your problems.

I currently have .NET 1.1, 2.0, & 3.0 installed on all my

systems, 6 XP Pro 32-bit and 2 XP Pro x64, and I have never

encountered a problem with .NET

 

In all cases I installed .NET 1.1 first and updates, then

..NET 2.0 and updates, then .NET 3.0 without any problems to

date.

 

There are quite a few pieces of software that utilize the

..NET framework.

 

 

Denise wrote:

> Hi, I installed NET Framework 2.0 in order to use a program. The program

> still can't run without installing another program, which I don't want to do.

> I don't and won't need NET Framework 2.0 for the other things that it is

> used for, i.e., developing code. Since I'm no longer in need of it, how can

> I completely remove it from my computer? It's not listed in Add/Remove

> Programs and there's no uninstaller. I created a restore point prior to

> installing it. If I restore my computer to the system state using the

> restore point, will my computer no longer have NF 2.0?

[Guest Denise]

Re: What is the procedure for removing NET Framework 2.0?

 

See the end of this message for details on invoking

just-in-time (JIT) debugging instead of this dialog box.

 

************** Exception Text **************

System.BadImageFormatException: Could not load file or assembly 'SpawnCLR,

Version=1.0.2624.20502, Culture=neutral, PublicKeyToken=null' or one of its

dependencies. An attempt was made to load a program with an incorrect format.

File name: 'SpawnCLR, Version=1.0.2624.20502, Culture=neutral,

PublicKeyToken=null'

at SeaToolsforWindows.Pipes.StartPipe(Int32 i)

at SeaToolsforWindows.Pipes.GetAvailablePipe(Object& pipe)

at SeaToolsforWindows.frmSTXMain.Run_Script(Byte testFunction, String

script)

at SeaToolsforWindows.frmSTXMain.LocalizeTool(String newLanguage)

at SeaToolsforWindows.frmSTXMain.frmSTXMain_Load(Object sender, EventArgs

e)

at System.EventHandler.Invoke(Object sender, EventArgs e)

at System.Windows.Forms.Form.OnLoad(EventArgs e)

at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)

at System.Windows.Forms.Control.CreateControl()

at System.Windows.Forms.Control.WmShowWindow(Message& m)

at System.Windows.Forms.Control.WndProc(Message& m)

at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)

at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg,

IntPtr wparam, IntPtr lparam)

 

WRN: Assembly binding logging is turned OFF.

To enable assembly bind failure logging, set the registry value

[HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.

Note: There is some performance penalty associated with assembly bind

failure logging.

To turn this feature off, remove the registry value

[HKLM\Software\Microsoft\Fusion!EnableLog].

 

 

 

************** Loaded Assemblies **************

mscorlib

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.42 (RTM.050727-4200)

CodeBase:

file:///C:/WINDOWS/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll

----------------------------------------

SeaToolsforWindows

Assembly Version: 1.1.0.3

Win32 Version: 1.1.0.3

CodeBase:

file:///C:/Program%20Files%20(x86)/SeaTools/SeaToolsforWindows.exe

----------------------------------------

Microsoft.VisualBasic

Assembly Version: 8.0.0.0

Win32 Version: 8.0.50727.42 (RTM.050727-4200)

CodeBase:

file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll

----------------------------------------

System.Windows.Forms

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.42 (RTM.050727-4200)

CodeBase:

file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll

----------------------------------------

System

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.42 (RTM.050727-4200)

CodeBase:

file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll

----------------------------------------

System.Drawing

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.42 (RTM.050727-4200)

CodeBase:

file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll

----------------------------------------

System.Runtime.Remoting

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.42 (RTM.050727-4200)

CodeBase:

file:///C:/WINDOWS/assembly/GAC_MSIL/System.Runtime.Remoting/2.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll

----------------------------------------

SeagateDriveControls

Assembly Version: 1.0.0.0

Win32 Version: 1.0.0.0

CodeBase:

file:///C:/Program%20Files%20(x86)/SeaTools/SeagateDriveControls.DLL

----------------------------------------

 

************** JIT Debugging **************

To enable just-in-time (JIT) debugging, the .config file for this

application or computer (machine.config) must have the

jitDebugging value set in the system.windows.forms section.

The application must also be compiled with debugging

enabled.

 

For example:

 

<configuration>

<system.windows.forms jitDebugging="true" />

</configuration>

 

When JIT debugging is enabled, any unhandled exception

will be sent to the JIT debugger registered on the computer

rather than be handled by this dialog box.

[Guest Denise]

Re: What is the procedure for removing NET Framework 2.0?

 

When I installed 2.0 in my old pc, the change happened immediately. When the

first program I opened needed 2.0, I received a message that I need to have

JustInTime Debugging installed. I installed it and I continued to get the

JIT Debugging messaged constantly.

 

When I installed 2.0 yesterday, I immediately received a message that stated

that I need JIT debuging installed. I don't want to go down that road again.

If it becomes absolutely imperative that I need to install 2.0 and JIT

debugging, then I'll install it. Until that time, I won't install them again.

 

The reason I installed it yesterday is because I installed SeaTools. When I

tried to run it, it required 2.0. I didn't want to install it but I did. As

soon as I installed it, I received the message that said that JIT Debugging

needed to be installed. I took the chance and installed JIT Debugging. When

I tried to run SeaTools, I immediately received this message:

 

"Unhandled exception has occurred in your application. If you click

Continue, the application will ignore this error and attempt to continue. If

you click Quit, the application will close immediately.

 

Could not load file or assembly 'SpawnCLR. Version=1.0.2624.20502.

Culture=neutral. PublicKeyToken=null' or one of its dependencies. An

attempt was made to load a program with an incorrect formal."

 

I don't know if there's a limit to the number of characters that's allowed

in a post so I'm going to open another response window and paste it.

--

Denise

 

~ If you don't know where you came from, you won't know where you're going.

[Guest Theo]

Re: What is the procedure for removing NET Framework 2.0?

 

As I stated before, you probably need to look at other

things causing problems. I installed .NET 1.1 a couple of

years ago specifically to run programs that were designed

for the .NET framework, but to date I have never encountered

a problem with it and I am still using programs that are

written for .NET

 

There are even some web applications utilizing .NET in a

manner similar to Java and Flash.

 

I don't have the JIT on any of my systems and I have never

gotten a message asking for it.

 

 

Denise wrote:

> When I installed 2.0 in my old pc, the change happened immediately. When the

> first program I opened needed 2.0, I received a message that I need to have

> JustInTime Debugging installed. I installed it and I continued to get the

> JIT Debugging messaged constantly.

>

> When I installed 2.0 yesterday, I immediately received a message that stated

> that I need JIT debuging installed. I don't want to go down that road again.

> If it becomes absolutely imperative that I need to install 2.0 and JIT

> debugging, then I'll install it. Until that time, I won't install them again.

>

> The reason I installed it yesterday is because I installed SeaTools. When I

> tried to run it, it required 2.0. I didn't want to install it but I did. As

> soon as I installed it, I received the message that said that JIT Debugging

> needed to be installed. I took the chance and installed JIT Debugging. When

> I tried to run SeaTools, I immediately received this message:

>

> "Unhandled exception has occurred in your application. If you click

> Continue, the application will ignore this error and attempt to continue. If

> you click Quit, the application will close immediately.

>

> Could not load file or assembly 'SpawnCLR. Version=1.0.2624.20502.

> Culture=neutral. PublicKeyToken=null' or one of its dependencies. An

> attempt was made to load a program with an incorrect formal."

>

> I don't know if there's a limit to the number of characters that's allowed

> in a post so I'm going to open another response window and paste it.

[Guest Denise]

Re: What is the procedure for removing NET Framework 2.0?

 

I think you misunderstood my problem. I have NETFramework 1.1. A program,

SeaTools, needs 2.0. NETFramework 1.1 has never caused me a problem either.

NETFramework 2.0 causes me a lot of problems.

--

Denise

 

~ If you don't know where you came from, you won't know where you're going.

 

 

"Theo" wrote:

> As I stated before, you probably need to look at other

> things causing problems. I installed .NET 1.1 a couple of

> years ago specifically to run programs that were designed

> for the .NET framework, but to date I have never encountered

> a problem with it and I am still using programs that are

> written for .NET

>

> There are even some web applications utilizing .NET in a

> manner similar to Java and Flash.

>

> I don't have the JIT on any of my systems and I have never

> gotten a message asking for it.

>

>

> Denise wrote:

> > When I installed 2.0 in my old pc, the change happened immediately. When the

> > first program I opened needed 2.0, I received a message that I need to have

> > JustInTime Debugging installed. I installed it and I continued to get the

> > JIT Debugging messaged constantly.

> >

> > When I installed 2.0 yesterday, I immediately received a message that stated

> > that I need JIT debuging installed. I don't want to go down that road again.

> > If it becomes absolutely imperative that I need to install 2.0 and JIT

> > debugging, then I'll install it. Until that time, I won't install them again.

> >

> > The reason I installed it yesterday is because I installed SeaTools. When I

> > tried to run it, it required 2.0. I didn't want to install it but I did. As

> > soon as I installed it, I received the message that said that JIT Debugging

> > needed to be installed. I took the chance and installed JIT Debugging. When

> > I tried to run SeaTools, I immediately received this message:

> >

> > "Unhandled exception has occurred in your application. If you click

> > Continue, the application will ignore this error and attempt to continue. If

> > you click Quit, the application will close immediately.

> >

> > Could not load file or assembly 'SpawnCLR. Version=1.0.2624.20502.

> > Culture=neutral. PublicKeyToken=null' or one of its dependencies. An

> > attempt was made to load a program with an incorrect formal."

> >

> > I don't know if there's a limit to the number of characters that's allowed

> > in a post so I'm going to open another response window and paste it.

>

[Guest Theo]

Re: What is the procedure for removing NET Framework 2.0?

 

And, to reemphasize what I said before, there is not a

problem with .NET Framework 2.0.

 

The problem is you're trying to run a problem that does not

install properly in Win x64. It plainly states that it's a

32-bit program.

 

I just installed it in Win x64 and it doesn't work. I get

the same error you posted. Apparently SpawnCLR.dll is a

32-bit .dll and it will not work in Win x64.

 

I also installed it in Win XP 32-bit and the program runs fine.

 

P.S.

~ If you don't know where you came from, you won't know

where you're going.

 

 

Denise wrote:

> I think you misunderstood my problem. I have NETFramework 1.1. A program,

> SeaTools, needs 2.0. NETFramework 1.1 has never caused me a problem either.

> NETFramework 2.0 causes me a lot of problems.

[Guest Denise]

Re: What is the procedure for removing NET Framework 2.0?

 

I said that I had it in my old computer when it caused a multitude of

problems. My old computer had 2000 XP Pro, not X64. The same problems that

I had after installing 2.0 and JIT Debugger in my old computer are the same

problems that I'm having now. There's an X64 version, which I downloaded and

installed and JIT Debugger.

 

I don't like the problems that I have with NET Framework 2.0 and JIT

Debugger. I installed them for the sole reason to run SeaTools and I planned

on uninstalling them as soon as I ran SeaTools. Unfortunately, NET Framework

and JIT Debugger didn't work, as you can see by the detailed explanation that

I posted. It never worked in my old computer and it doesn't work in my new

one. All I ever get are messages that state that it can't continue. If you

read the details of the message, you'll see the reason it didn't work.

--

Denise

 

~ If you don't know where you came from, you won't know where you're going.

 

 

"Theo" wrote:

> And, to reemphasize what I said before, there is not a

> problem with .NET Framework 2.0.

>

> The problem is you're trying to run a problem that does not

> install properly in Win x64. It plainly states that it's a

> 32-bit program.

>

> I just installed it in Win x64 and it doesn't work. I get

> the same error you posted. Apparently SpawnCLR.dll is a

> 32-bit .dll and it will not work in Win x64.

>

> I also installed it in Win XP 32-bit and the program runs fine.

>

> P.S.

> ~ If you don't know where you came from, you won't know

> where you're going.

>

>

> Denise wrote:

> > I think you misunderstood my problem. I have NETFramework 1.1. A program,

> > SeaTools, needs 2.0. NETFramework 1.1 has never caused me a problem either.

> > NETFramework 2.0 causes me a lot of problems.

>

[Guest Theo]

Re: What is the procedure for removing NET Framework 2.0?

 

Unfortunately the whole situation is not a simple

black-and-white solution. There are a multitude of reasons

why you're having problems with .NET 2.0 and the most like

is one or more other programs on your system causing

conflicts. You can't just arbitrarily claim there is a

problem with .NET 2.0 without some substantial proof. Just

because you're having problems would tend to indicate it's

something peculiar with your system(s).

 

Since all versions of .NET are now part of Windows Update,

there are literally millions of people with .NET 2.0 on

their computers. If .NET 2.0 was as flaky as you want us to

believe, there would be millions of people complaining!

 

 

Denise wrote:

> I said that I had it in my old computer when it caused a multitude of

> problems. My old computer had 2000 XP Pro, not X64. The same problems that

> I had after installing 2.0 and JIT Debugger in my old computer are the same

> problems that I'm having now. There's an X64 version, which I downloaded and

> installed and JIT Debugger.

>

> I don't like the problems that I have with NET Framework 2.0 and JIT

> Debugger. I installed them for the sole reason to run SeaTools and I planned

> on uninstalling them as soon as I ran SeaTools. Unfortunately, NET Framework

> and JIT Debugger didn't work, as you can see by the detailed explanation that

> I posted. It never worked in my old computer and it doesn't work in my new

> one. All I ever get are messages that state that it can't continue. If you

> read the details of the message, you'll see the reason it didn't work.

[Guest Denise]

Re: What is the procedure for removing NET Framework 2.0?

 

I'm not asking you to believe anything. I came to this forum to find out how

to uninstall NETFramework 2.0.

 

It don't work on my present computer and it didn't work on my old computer.

Those are facts. I typed in the message that I received and I copied and

pasted the details of the message that I received, proof positive that

NETFramework 2.0 won't work on my computer, the proof that you asked for that

shows that there's something wrong with NETFramework 2.0.

 

I get automatic updates and I let Microsoft choose which updates would be

best for my computer, and the updates are download and installed

automatically. Windows Automatic Update has never attempted to install

NETFramework 2.0 on my computer. it has installed only 1.1 and 1.1 Hotfix

(KB886903). If 2.0 was compatible with my computer, automatic updates would

have installed 2.0, as you mentioned, but it hasn't.

 

I didn't come to this forum to argue with anyone and I don't like what has

happened here. I wanted to uninstall 2.0 and it's done, and I will not check

the box to notify me of replies.

--

Denise

 

~ If you don't know where you came from, you won't know where you're going.

 

 

 

"Theo" wrote:

> Unfortunately the whole situation is not a simple

> black-and-white solution. There are a multitude of reasons

> why you're having problems with .NET 2.0 and the most like

> is one or more other programs on your system causing

> conflicts. You can't just arbitrarily claim there is a

> problem with .NET 2.0 without some substantial proof. Just

> because you're having problems would tend to indicate it's

> something peculiar with your system(s).

>

> Since all versions of .NET are now part of Windows Update,

> there are literally millions of people with .NET 2.0 on

> their computers. If .NET 2.0 was as flaky as you want us to

> believe, there would be millions of people complaining!

>

[Guest Homer J. Simpson]

Re: What is the procedure for removing NET Framework 2.0?

 

I've only had a cursory glance at this thread, and it really sounds to me

like some program on your system, which has been written in .NET, is

crashing, and you're being mislead by the .NET diagnosis messages into

believing that the problem is with .NET itself. That's not the case, and

the JIT debugger is only stepping in trying to help you debug the

program--which is completely useless to you or anyone else without the

program's source code.

 

Bottom line, blame that program and get rid of *it*, not the .NET framework

itself. Whether you're actually going to see this reply or not is

inconsequential; I just want to set the record straight as it seems nobody

else cares enough to step in.

[Guest Theo]

Re: What is the procedure for removing NET Framework 2.0?

 

1. Click on <Start>

2. Click on <Control Panel>

3. Double click on 'Add Remove or Programs'

4. Click on 'Microsoft .NET Framework 2.0'

5. Click on <Change/Remove>

6. Click on 'Uninstall'

7. Click on <Next>

8. Follow the logical steps from there

9. Follow the suggestions as may be presented

 

 

Common sense is not so common.

Voltaire

(1694 - 1778)

 

 

 

Denise wrote:

> I'm not asking you to believe anything. I came to this forum to find out how

> to uninstall NETFramework 2.0.

>

> It don't work on my present computer and it didn't work on my old computer.

> Those are facts. I typed in the message that I received and I copied and

> pasted the details of the message that I received, proof positive that

> NETFramework 2.0 won't work on my computer, the proof that you asked for that

> shows that there's something wrong with NETFramework 2.0.

>

> I get automatic updates and I let Microsoft choose which updates would be

> best for my computer, and the updates are download and installed

> automatically. Windows Automatic Update has never attempted to install

> NETFramework 2.0 on my computer. it has installed only 1.1 and 1.1 Hotfix

> (KB886903). If 2.0 was compatible with my computer, automatic updates would

> have installed 2.0, as you mentioned, but it hasn't.

>

> I didn't come to this forum to argue with anyone and I don't like what has

> happened here. I wanted to uninstall 2.0 and it's done, and I will not check

> the box to notify me of replies.

[Guest vmguy]

Re: What is the procedure for removing NET Framework 2.0?

 

I have to agree with Denise. .NET 2.0 has been nothing but trouble for me on

dozens of machines. I've had to manually uninstall, reinstall, and fight

continuously with Windows update. It does no good to complain to Microsoft

.... nothing gets fixed. Same problems, over and over; each resolution

slightly different from the previous. As long as Microsoft doesn't "fix"

this wonderful API again, I'm happy to stay with what I've got.

 

I also agree with Denise that the Microsoft product names should be more

consistent. I have hundreds of apps installed ... playing the "what did

Microsoft call it this time" game gets real tiresome.

 

 

"Theo" wrote:

> If .NET 2.0 was as flaky as you want us to believe, there would be millions of people complaining!

[Guest Theo]

Re: What is the procedure for removing NET Framework 2.0?

 

Regardless of the problems with .NET Framework, any version,

this forum is specifically for the Operating System. So any

problems with .NET Framework are really not appropriate

being addressed here.

 

We don't want anyone starting a .NET Framework bashing here!!

 

 

vmguy wrote:

> I have to agree with Denise. .NET 2.0 has been nothing but trouble for me on

> dozens of machines. I've had to manually uninstall, reinstall, and fight

> continuously with Windows update. It does no good to complain to Microsoft

> ... nothing gets fixed. Same problems, over and over; each resolution

> slightly different from the previous. As long as Microsoft doesn't "fix"

> this wonderful API again, I'm happy to stay with what I've got.

>

> I also agree with Denise that the Microsoft product names should be more

> consistent. I have hundreds of apps installed ... playing the "what did

> Microsoft call it this time" game gets real tiresome.

>

>

> "Theo" wrote:

>

>> If .NET 2.0 was as flaky as you want us to believe, there would be millions of people complaining!

>

[Guest Denise]

Re: What is the procedure for removing NET Framework 2.0?

 

Nobody tried to start anything here except you. I asked a simple question, I

received an answer, I uninstalled NET Framework 2.0, and you came in

accusing, belittling, arguing and ridiing your white horse to defend 2.0.

 

The version of 2.0 that I installed in my computer that has an X64 os was

the X64 Redistributable Pack. Is that enough X64's to be allowed to stay in

the X64 forum?

 

You have to be nother Microsoft employee afraid to lose his job if he

doesn't get everyone to keep quiet about the problems with X64. X64 rots and

it's the worst purchase I made this decade! I started with Windows 95 when

it first came out. There were less problems with 95 than there are with X64.

Unfortunately, Bill Gates didn't want to take a loss on the research and

development that went into this pathetic operating system that really should

be called a joke, so he marketed it and let the users pay the price. Isn't

greed one of the 5 deadly sins?

 

BTW, who is the "We" you're talking about and why do you think that speaking

one's mind about a product is bashing. A person has the right to not like a

product that doesn't work and the right to speak her mind about it. This is

still America the last time I looked . . . it hasn't yet been changes to

Gates.

--

Denise

 

~ If you don't know where you came from, you won't know where you're going.

 

 

"Theo" wrote:

> Regardless of the problems with .NET Framework, any version,

> this forum is specifically for the Operating System. So any

> problems with .NET Framework are really not appropriate

> being addressed here.

>

> We don't want anyone starting a .NET Framework bashing here!!

>

>

> vmguy wrote:

> > I have to agree with Denise. .NET 2.0 has been nothing but trouble for me on

> > dozens of machines. I've had to manually uninstall, reinstall, and fight

> > continuously with Windows update. It does no good to complain to Microsoft

> > ... nothing gets fixed. Same problems, over and over; each resolution

> > slightly different from the previous. As long as Microsoft doesn't "fix"

> > this wonderful API again, I'm happy to stay with what I've got.

> >

> > I also agree with Denise that the Microsoft product names should be more

> > consistent. I have hundreds of apps installed ... playing the "what did

> > Microsoft call it this time" game gets real tiresome.

> >

> >

> > "Theo" wrote:

> >

> >> If .NET 2.0 was as flaky as you want us to believe, there would be millions of people complaining!

> >

>

[Guest mikeyhsd]

Re: What is the procedure for removing NET Framework 2.0?

 

Denise,

just for your information and maybe to clear the air.

according to the news groups rules posted at MICROSOFT for their news groups.

you are NOT REQUIRED to post into any particular news group.

it is recommended that you make a reasonable attempt to find the most appropriate news group for the subject.

 

feel free to check for your self if you are interested.

 

 

 

mikeyhsd@comcast.net

 

 

 

"Denise" <Denise@discussions.microsoft.com> wrote in message news:B9BF4144-402C-40B7-8F87-6AD60489D272@microsoft.com...

Nobody tried to start anything here except you. I asked a simple question, I

received an answer, I uninstalled NET Framework 2.0, and you came in

accusing, belittling, arguing and ridiing your white horse to defend 2.0.

 

The version of 2.0 that I installed in my computer that has an X64 os was

the X64 Redistributable Pack. Is that enough X64's to be allowed to stay in

the X64 forum?

 

You have to be nother Microsoft employee afraid to lose his job if he

doesn't get everyone to keep quiet about the problems with X64. X64 rots and

it's the worst purchase I made this decade! I started with Windows 95 when

it first came out. There were less problems with 95 than there are with X64.

Unfortunately, Bill Gates didn't want to take a loss on the research and

development that went into this pathetic operating system that really should

be called a joke, so he marketed it and let the users pay the price. Isn't

greed one of the 5 deadly sins?

 

BTW, who is the "We" you're talking about and why do you think that speaking

one's mind about a product is bashing. A person has the right to not like a

product that doesn't work and the right to speak her mind about it. This is

still America the last time I looked . . . it hasn't yet been changes to

Gates.

--

Denise

 

~ If you don't know where you came from, you won't know where you're going.

 

 

"Theo" wrote:

> Regardless of the problems with .NET Framework, any version,

> this forum is specifically for the Operating System. So any

> problems with .NET Framework are really not appropriate

> being addressed here.

>

> We don't want anyone starting a .NET Framework bashing here!!

>

>

> vmguy wrote:

> > I have to agree with Denise. .NET 2.0 has been nothing but trouble for me on

> > dozens of machines. I've had to manually uninstall, reinstall, and fight

> > continuously with Windows update. It does no good to complain to Microsoft

> > ... nothing gets fixed. Same problems, over and over; each resolution

> > slightly different from the previous. As long as Microsoft doesn't "fix"

> > this wonderful API again, I'm happy to stay with what I've got.

> >

> > I also agree with Denise that the Microsoft product names should be more

> > consistent. I have hundreds of apps installed ... playing the "what did

> > Microsoft call it this time" game gets real tiresome.

> >

> >

> > "Theo" wrote:

> >

> >> If .NET 2.0 was as flaky as you want us to believe, there would be millions of people complaining!

> >

>

[Guest John Barnes]

Re: What is the procedure for removing NET Framework 2.0?

 

You really need to calm down. Breathe deeply. XP64 is a wonderful and

STABLE OS if you have the compatible hardware (with the necessary drivers)

and software (many of my programs didn't work. Found others that did, and

used the system as my main system for over a year before switching to

Vista64. Vista 64 still has problems, but all but 1 are due to lack of

proper drivers or incompatible programs. The signed driver requirement is

the biggest hassle as who is going to do that for free programs. Since you

have had such good luck with XP32, that is where you should be, but ranting

about XP64 accomplishes nothing except maybe mislead someone who is capable

of having it run on their system. It just works.

 

"Denise" <Denise@discussions.microsoft.com> wrote in message

news:B9BF4144-402C-40B7-8F87-6AD60489D272@microsoft.com...

> Nobody tried to start anything here except you. I asked a simple

> question, I

> received an answer, I uninstalled NET Framework 2.0, and you came in

> accusing, belittling, arguing and ridiing your white horse to defend 2.0.

>

> The version of 2.0 that I installed in my computer that has an X64 os was

> the X64 Redistributable Pack. Is that enough X64's to be allowed to stay

> in

> the X64 forum?

>

> You have to be nother Microsoft employee afraid to lose his job if he

> doesn't get everyone to keep quiet about the problems with X64. X64 rots

> and

> it's the worst purchase I made this decade! I started with Windows 95

> when

> it first came out. There were less problems with 95 than there are with

> X64.

> Unfortunately, Bill Gates didn't want to take a loss on the research and

> development that went into this pathetic operating system that really

> should

> be called a joke, so he marketed it and let the users pay the price.

> Isn't

> greed one of the 5 deadly sins?

>

> BTW, who is the "We" you're talking about and why do you think that

> speaking

> one's mind about a product is bashing. A person has the right to not like

> a

> product that doesn't work and the right to speak her mind about it. This

> is

> still America the last time I looked . . . it hasn't yet been changes to

> Gates.

> --

> Denise

>

> ~ If you don't know where you came from, you won't know where you're

> going.

>

>

> "Theo" wrote:

>

>> Regardless of the problems with .NET Framework, any version,

>> this forum is specifically for the Operating System. So any

>> problems with .NET Framework are really not appropriate

>> being addressed here.

>>

>> We don't want anyone starting a .NET Framework bashing here!!

>>

>>

>> vmguy wrote:

>> > I have to agree with Denise. .NET 2.0 has been nothing but trouble for

>> > me on

>> > dozens of machines. I've had to manually uninstall, reinstall, and

>> > fight

>> > continuously with Windows update. It does no good to complain to

>> > Microsoft

>> > ... nothing gets fixed. Same problems, over and over; each resolution

>> > slightly different from the previous. As long as Microsoft doesn't

>> > "fix"

>> > this wonderful API again, I'm happy to stay with what I've got.

>> >

>> > I also agree with Denise that the Microsoft product names should be

>> > more

>> > consistent. I have hundreds of apps installed ... playing the "what

>> > did

>> > Microsoft call it this time" game gets real tiresome.

>> >

>> >

>> > "Theo" wrote:

>> >

>> >> If .NET 2.0 was as flaky as you want us to believe, there would be

>> >> millions of people complaining!

>> >

>>

[Guest Homer J. Simpson]

Re: What is the procedure for removing NET Framework 2.0?

 

Such anger.

 

Personally, I think XP x64 is the most rock-solid Windows version yet. I

don't use Server 2003 x64 nearly enough to compare it though.

[Guest Theo]

Re: What is the procedure for removing NET Framework 2.0?

 

..NET Framework is NOT part of the Operating System just

because it's one of the extras Microsoft included on the

Distribution CD. Someday it may be just as Internet

Explorer is now.

 

The major problem with your post was that you tried to use a

program that was not compatible with Win x64 and then

because it doesn't work you want to blame Microsoft for your

inability to read and comprehend something.

 

And, NO, I am not a Microsoft employee, but like any other

subject, it's best to try to learn as much as you can about

something if you want to delve into it very deeply.

 

Would you do mechanical work on your vehicle without trying

to learn how to accomplish your objective task efficiently

and expediently?

 

 

Denise wrote:

> Nobody tried to start anything here except you. I asked a simple question, I

> received an answer, I uninstalled NET Framework 2.0, and you came in

> accusing, belittling, arguing and ridiing your white horse to defend 2.0.

>

> The version of 2.0 that I installed in my computer that has an X64 os was

> the X64 Redistributable Pack. Is that enough X64's to be allowed to stay in

> the X64 forum?

>

> You have to be nother Microsoft employee afraid to lose his job if he

> doesn't get everyone to keep quiet about the problems with X64. X64 rots and

> it's the worst purchase I made this decade! I started with Windows 95 when

> it first came out. There were less problems with 95 than there are with X64.

> Unfortunately, Bill Gates didn't want to take a loss on the research and

> development that went into this pathetic operating system that really should

> be called a joke, so he marketed it and let the users pay the price. Isn't

> greed one of the 5 deadly sins?

>

> BTW, who is the "We" you're talking about and why do you think that speaking

> one's mind about a product is bashing. A person has the right to not like a

> product that doesn't work and the right to speak her mind about it. This is

> still America the last time I looked . . . it hasn't yet been changes to

> Gates.