Hi tonygables, welcome to the community! The issue you are experiencing has been investigated and reported by the development team. Here is a link to the issue so you can track its progress:
I’m aware that the issue does not occur on 3.0.0 CMS and some users have reported that 3.0.3 also does not have the issue. As a workaround until the issue is resolved, you could install one of these versions instead.