In computing specifically, disabled has no negative connotations. Instead, it just means a feature or option is turned off.
It is not necessarily the same as "Not Enabled", though in some cases it might be. Other answers reference the implied default values, which is a valid difference.
Another difference could be tri-states - for example, a certain option could be Enabled, Disabled, or Unmodified/Default. This could be used to compare user settings to a certain global default - if you have [option] Enabled, you get it, if you have it disabled, you don't, and if you haven't touched the option, it instead follows a global default, which may change with or without your knowledge and/or input.
In such a case, Disabled is the explicit instruction that you don't want [feature], while "not enabled" is ambiguous between "disabled" and "don't care/just do default".
I'm a software engineer. A while ago I build a system that can be Enabled, Disabled, and Enabled-Outside-Office-Hours (because of server load concerns).
Please use the word "Disabled" whenever the interface does as well, especially when contacting technical support. Precise language use in those cases will reduce the time they need to help you, and make it easier for them to understand your problem.
If you are instead designing an interface, look at comparable interfaces and use the same. In this case, the Principle of Least Astonishment should be your primary guide. (TL:DR; Do what surprises the fewest people. It's kind of off-topic for this side, but please google it if you're building any kind of interface and haven't already.)