This is a known issue that appeared in 9.0.1.173
A fix was applied in 9.0.1.186, however those that experience the issue will be required to re-activate after applying 9.0.1.186 but should no longer be required to update beyond 9.0.1.186 (activating after 186 will now hold)