wyDay blog

• Next: Peppier Website
• Previous: Gnats and Nights

Comments

• John the Electrician - February 13th, 2009 at 11:27 am

  I am a republican, and I usually feel the democrats have the “it’s not only acceptable, but really good” mentality. In a bi-partisan move; let us agree we both feel this way about Microsoft.

  Installation without authorization, .NET was allowed, but they over stepped the permission they were given, and no un-install option. Even if the un-install problem lies in FF itself, MS deployed an un-installable add-on. They took the time to make the add-on, but not the time to properly field test or support. So regardless where the root cause is, MS allowed it to propagate.

• GriffenJBS - February 13th, 2009 at 11:40 am

  Has anyone mentioned FFClickOnce? It’s is a third-party Firefox extension that also enables ClickOnce for client installations that have Firefox plus .NET Framework

• Harry - February 14th, 2009 at 5:28 pm

  Wyatt … just to say thank you for the uninstall information.

• thx - February 14th, 2009 at 11:05 pm

  thanks

• Ian Wright - February 15th, 2009 at 3:48 pm

  Thanks a lot, Pete! Solved the answer at one go. I dream of the day robots take over the world and, as their first act of imperial government, outlaw Windows. Except for use at Redmond, where it will be mandatory. And in hell, of course. But that goes without saying.

• Ian Wright - February 15th, 2009 at 3:51 pm

  I meant thanks to Wyatt. Sorry. Pete was the bloke who sent me the link.

• David Sisson - February 15th, 2009 at 7:11 pm

  Thanks a lot, Wyatt. Not only was this the location for the .NET issue, but the Java Quick Start was also there. I deleted both registry entries and VOILA, no more .NET or JQS.

• Beelzebub - February 18th, 2009 at 9:27 am

  Thanks! I already deleted this once but once again the MS “important” updates put it back.

• thanks!!!! - February 24th, 2009 at 12:02 pm

  Thank you for posting this — HUGE help!!!

• anonymous - March 4th, 2009 at 3:13 pm

  Thanks for this useful tip!

  Back to work now :)

• everlastingangst - March 9th, 2009 at 7:41 pm

  No one understands my pain… oh wait, wrong page.

  Thx for the tip Wyatt.

• Matti - March 15th, 2009 at 6:27 pm

  That the uninstall is disabled is coming from Firefox.
  The extensions are installed outside of Firefox and without the control of Firefox and Firefox simple can not uninstall such extensions because Firefox doesn’t know where files are dropped by the installer. The external addon installer could for example put files in the Firefox directory. That’s the reason why extensions installed with the registry are not uninstallable inside Firefox.

  The point is that every external extension installer should ask before installing and don’t do that silent.

• ander - March 21st, 2009 at 1:10 am

  Apparetly, a few more steps are required to really uninstall the plugin—see http://www.annoyances.org/exec/show/article08-600

• Wyatt O'Day - March 21st, 2009 at 9:16 am

  Thanks ander, I’ve added it to the main post.

• Sanders - March 21st, 2009 at 3:00 pm

  I think the question is: why the heck does Mozilla allow for extensions being installed outside Firefox’s control? do they want to repeat MS’s past mistakes regarding browser security?

• RickX - April 28th, 2009 at 10:55 am

  Hmmmm The government pushed out this patch and installed this “freak” of a thing on my machine at work. Can’t remove it without admin privs (can’t edit the registry).

  What does this do exactly? I can’t find much other than “it shouldn’t be there”, “opens up Firefox for attacks” – things like that. No specifics.

  Any other way to remove it than registry?

• Wyatt O'Day - April 28th, 2009 at 11:08 am

  RickX,

  It’s not malicious, despite what the multitude of imbeciles might suggest. If you can’t remove it, it’s no biggie.

  All it does is waste a little bit of time on Firefox startup. You can solve this problem by getting the gov to buy you a better computer.

  – Wyatt

• Michael - May 26th, 2009 at 1:09 pm

  Hmm, that’s weird, my uninstall button was working.
  Running Firefox 3.0.10 on Windows 7 RC (x86)

• Thanks! - June 3rd, 2009 at 10:51 am

  Thanks for the help.

• Andy Fore - June 3rd, 2009 at 11:08 am

  @Michael The reason your Uninstall button is working is due to an update to the actual extension from Microsoft. If you don’t have the update, only the Enable/Disable button should be functional for stopping the extension from doing whatever it is programmed to do.

  The update can be obtained here:

  http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=cecc62dc-96a7-4657-af91-6383ba034eab

  The fun part is that since the update is installed outside of the normal add-on mechanism for Firefox, you can’t get the update via the add-on update check.

  This is why people should work within the accepted system instead of just auto installing software (plugins, extensions, applications, etc.) automagically.

  Apple has been pinged on this with regards to Safari, Apple Update, and Bonjour for Windows.

  Andy

• Matt - June 23rd, 2009 at 8:55 am

  Hanselman has a good write-up on this.

  http://www.hanselman.com/blog/HowToRemoveTheNETClickOnceFirefoxExtension.aspx

• Rick Cain - June 30th, 2009 at 4:26 pm

  On a positive note, it is incompatible (at least for now) with the new Firefox 3.5 so FF mercifully disables the add-on for you.

• Info from ms - August 11th, 2009 at 3:13 am

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

• Marthin - August 22nd, 2009 at 8:32 am

  Thanks a lot Wyatt – nice try from MS to make people return to IE

• jim - August 27th, 2009 at 6:58 pm

  For crying out loud. This has nothing to do with IE. And, when things are done in the proper order, everything works and the Enable / Disable / Uninstall buttons work just fine.

  It is the sequence of updates that eludes most of you apparently.

  The original .NET Framework 3.5 SP1 update is NOT compatible with Firefox. M$ says this if you read – RIF – the KB article that goes with it.

  That is why they released a separate .NET 3.5 Framework Assistant SP1 update JUST FOR Firefox users. They did NOT have to do that. In fact, NOT doing so would force users back to IE, eh Marthin!

  Here’s the rub. The .NET Framework 3.5 SP1 update installs Framework Assistant 1.0. Version 1.0 is ONLY compatible with Firefox 3.0.x (NOT 3.5.x). So the .NET Framework Assistant 1.1 update cannot update an existing FF 3.5.x installation because the Framework Assistant is not enabled.

  HOWEVER, if one is still using FF 3.0.x, one may proceed to install the .NET Framework 3.5 SP1 update, ensure that Framework Assistant 1.0 is enabled in the FF addon list, then install the Framework Assistant update to 1.1. THEN one can update to FF 3.5.x and all is well.

  I know. I did it last night on the backup XP MCE machine and it worked faultlessly.

  Now before all you MAC / Unix / Linux / etc fanboys get on my case, I don’t think anyone who follows my pitifully few postings would ever even consider calling me a M$ supporter. In fact I think the way Bill uses his monopoly borders on criminal (and some folks in the EU agree). BUT the fact that it works if one follows the specified order of events shows that M$ was at least thinking about how to accommodate FF.

  Anyhow, y’all can rant and rave about .NET (I know I hated what they did to VB6) but if someone writes a program in .NET and you want to run it, guess what! You gotta have it. And whatever it is that Assistant does is likely to be required by application developers for something down the road (if not now) or M$ would not have bothered spending money on it. Remember they are in the business of making money.

  Now I’m getting back to my original question: if one has already upgraded to FF 3.5.x, how does one get .NET Framework Assistant 1.1 installed properly since version 1.0 cannot be enabled in FF 3.5.x!!

• SpamBucket - October 16th, 2009 at 9:40 pm

  Jim–have you tried the update found at:

  http://www.microsoft.com/downloads/details.aspx?FamilyID=cecc62dc-96a7-4657-af91-6383ba034eab&displaylang=en

• RockRedGenesis - October 17th, 2009 at 4:08 am

  I’m writing this pretty much after my firefox warned me about this add-on and advised me to disable it. I did, and then i successfully uninstalled this add-on from firefox. the Button wasn’t greyed out. should i be worried about it coming back on it own? (Like some kinds malware that we’ve heard about)

• Wyatt O'Day - October 17th, 2009 at 4:16 am

  the Button wasn’t greyed out.

  The button wasn’t greyed because MS got their act together and fixed the bug.

  should i be worried about it coming back on it own?

  No.

• Matt - October 17th, 2009 at 6:50 pm

  A lot of people contributing to this thread are asking why they should disable .NET Framework Assistant? What harm is it causing Firefox. Well here is a possible answer. And Firefox today automatically disabled .NFA and WPF!

  Battle of the Softwares: Microsoft vs Mozilla Firefox!

• teesbro - October 19th, 2009 at 9:21 am

  nice work dude

• ben ca - November 7th, 2009 at 5:21 pm

  thanks for uninstal netfrmework ..great..firefox will be faster..

• Ellen B - December 2nd, 2009 at 12:50 pm

  That was easy! Thanks for that fix, Wyatt. I was sitting here cursing Microsoft for automatically sneaking another useless file into my machine, and found your blog. I’m glad I found you.

  xox
  Ellen

• Wyatt O'Day - December 2nd, 2009 at 2:30 pm

  No problem at all, I’m glad I could help.

• polocanada - December 30th, 2009 at 12:13 pm

  Thank you thank you thank you… you just made my day.

• The Boss - June 5th, 2010 at 8:06 pm

  Thanks for the information. I been trying for months to get ride of this pesky idiot add-on from Microsoft.

  Once again, thanks for the info.

• iceman19631 - June 10th, 2010 at 12:09 pm

  Imagine half-ass installing a software or two on your personal computer and it’s trying to boot up with Windows. What do you think will happen? What’s likely to happen is…your system becomes unstable and crash with a B.S.O.D.

  My FF 3.6.3 started crashing recently for no reason and when I looked at it’s installed plug-ins I found out that Microsoft Net Framework Assistant 1.0 plug-in was grayed out. When restarting FF from previous before crash, I ran about 15 attempts at re-loading the plug-in’s website and it caused FF to crash while loading. After removal, FF is running smoother without crashing.

  I wouldn’t suggest that any half ass installs as being safe. Call me paranoid if you like but, if it’s not installed correctly folks, then get it off of your system. Best to be safe than sorry.

  A great big THANK YOU!!! goes out to Wyatt from me.

• sara - May 26th, 2011 at 3:11 am

  As an extension developer, how can you grey out “disable/uninstall” buttons?

• Wyatt O'Day - May 26th, 2011 at 1:43 pm

  If you’ve gleaned anything from this article it’s that you absolutely should not emulate this behavior.

• Celine Murnock - May 26th, 2012 at 3:57 pm

  I really like your writing style, good info, thanks for putting up :D. “Much unhappiness has come into the world because of bewilderment and things left unsaid.” by Feodor Mikhailovich Dostoyevsky.

• Glenn Kaai - June 22nd, 2012 at 7:07 am

  I’m still learning from you, while I’m trying to achieve my goals. I definitely love reading everything that is written on your blog.Keep the information coming. I loved it!

• Absolute Ave - October 8th, 2012 at 8:24 am

  Simply Awsome post !

• a - June 14th, 2014 at 4:36 pm

  This blog was… how do I say it? Relevant!!
  Finally I’ve found something which helped me. Thank you!