From all our feedback and communications, this issue has been resolved. Go ahead and do the update and please reach back out if it doesn't work for you.
@KansasCloud
