Except that "disabled" is an odd state to reason about for a "progress
bar".
Buttons are active items that accept user interaction (click on
button). "Disablement" for a button makes sense as it prevents
"activation" of the button until it is later enabled.
A progress bar (at least a normal one) is a "one-way" widget. It
conveys information to a user, but there is usually no "interaction"
from the user (no clicking on the bar to do something). Therefore,
with no "interaction", there is nothing to "disable", and setting it to
"disabled" is an odd state to ask about.