Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

This thread was closed and archived. Please ask a new question if you need help.

DISABLE UPDATE & NAGGING

  • 1 reply
  • 1 has this problem
  • 1 view
  • Last reply by McCoy

more options

Just going to shit up your boards every now and then until the option is restored. -Don't care if I can do it with a policy file. -Don't care if this is the way *you* think it should be So, if either of these is going to be the response, kindly suck down shot of shotgun mouthwash, you will not be missed.

There is absolutely no reason for this checkbox to be gone. There is absolutely no reason that I should have to edit some fucking json file with a "lol third party text editor" to prevent something that was formerly done with a checkbox. That's right, I cannot configure your software-- your giant, bloated, RAM and soul-sucking software from within the program. That's pathetic by any metric. Fire everybody responsible for suggesting and implementing this """""""""""BUG FIX."""""""""""""" Want to update Windows? Hurrr quit windows and edit windows.ini and then restart Windows duurrrrrr. It's like Back to the Future except we only went back to '93.

Restore the check box to disable updates. Stop obfuscating shit intentionally, and stop trying to look down your nose while telling people that it's somehow better because you did.

PS: As far as I can tell, all the original """bug""" report said was, "I'm too retarded to live, save me." Instead of doing the Spartan thing and simply saying, "No"-- we find ourselves here. With countless long-time users dropping your product so that one or two retards might continue using it.

I look forward to this complaint being thrown into the trash can, the account banned and the software remaining broken while at least $20 of Mozillabux spent on a safe space teddy bear to coddle the feelings of an incensed mouth-breather. Perhaps some sort of mandatory PTSD counseling for the staff... Anything but call the retard a retard and go back to making sane software defaults.

Just going to shit up your boards every now and then until the option is restored. -Don't care if I can do it with a policy file. -Don't care if this is the way *you* think it should be So, if either of these is going to be the response, kindly suck down shot of shotgun mouthwash, you will not be missed. There is absolutely no reason for this checkbox to be gone. There is absolutely no reason that I should have to edit some fucking json file with a "lol third party text editor" to prevent something that was formerly done with a checkbox. That's right, I cannot configure your software-- your giant, bloated, RAM and soul-sucking software from within the program. That's pathetic by any metric. Fire everybody responsible for suggesting and implementing this """""""""""BUG FIX."""""""""""""" Want to update Windows? Hurrr quit windows and edit windows.ini and then restart Windows duurrrrrr. It's like Back to the Future except we only went back to '93. Restore the check box to disable updates. Stop obfuscating shit intentionally, and stop trying to look down your nose while telling people that it's somehow better because you did. PS: As far as I can tell, all the original """bug""" report said was, "I'm too retarded to live, save me." Instead of doing the Spartan thing and simply saying, "No"-- we find ourselves here. With countless long-time users dropping your product so that one or two retards might continue using it. I look forward to this complaint being thrown into the trash can, the account banned and the software remaining broken while at least $20 of Mozillabux spent on a safe space teddy bear to coddle the feelings of an incensed mouth-breather. Perhaps some sort of mandatory PTSD counseling for the staff... Anything but call the retard a retard and go back to making sane software defaults.

All Replies (1)

more options