Steven_Murawski_13 wrote:
Hey Steve,
Thanks for your reply! Very insightful and promising to know other users are not experiencing this issue on the newest MacOS updates! I have been having this issue on my own personal laptop and I am not an IT professional. Would you have any suggested troubleshooting steps or debugging steps I could try to figure out what the root cause may be?
-Best!
Well, at least you have a "workaround" for now.
I think the best approach here, where you have a very large community of experienced users (most more experienced than me) reading, is to download Etrecheck and post its report here using the Additional Text button below. Instructions are provided here:
How to use the Add Text Feature When Post… - Apple Community
The elegant thing about Etrecheck is that it is only a diagnostic tool, it won't change or "fix" anything. Also, while it provides a lot of insightful information about what is installed and how the Mac is configured, it does so in an anonymous way so no personal information is revealed. You can check that for yourself in the report, before posting it. Etrecheck is also open source so one can even inspect the code. It basically extracts system information (without serial numbers, IP addresses, etc., those are not included in the report) that anyone can get themselves using Terminal or other provided Mac tools, but the report is easy to read and to experts reading it, candidates for the cause of the issue often pop out. Basically you are "crowd sourcing" the issue.
It could always be a Microsoft issue, but it would be an unusual one where many Macs are not affected and a significant number are. But it has happened before and might have happened again.