Mac Mini M2s have big problems connecting to the Internet, WiFi is unusable
On Apple support forums, several Mac Mini M2 users have expressed frustration with throughput issues. While their connection is stable and shows the usual performance, the last computer has trouble displaying pages and downloading files. It would even be “unusable” in Wi-Fi.
If you are one of the first users to have jumped on the Mac Mini M2 as soon as they were released a few days ago, your experience may already be mixed. Indeed, Apple’s new in-house processor has something to impress in its first benchmarks, which makes it easier to perform certain tasks on the small computer. But, for many users, the experience is marred by a very annoying connection issue.
Since the launch of Mac Mini M2, calls for help have followed one another on Apple’s support forums. All point to the same problem: the computer suffers from a catastrophic Internet speed. Of course, the authors specify that they have tested their connection beforehand, but all ensure that the problem does not come from there and that the speed tests all deliver the usual results.
The Mac Mini M2 is “unusable” in Wi-Fi
The bug seems to mainly affect computers connected via Wi-Fi. One user even goes so far as to say that the computer is simply “unusable” in this setup. Words also confirmed in several comments. Nothing seems to fix the situation, be it a transition to Wi-Fi 5 and Wi-Fi 6, or even a computer reset.
On the same subject: Apple formalizes MacBook Pro M2 Pro and M2 Max even more powerful and indestructible
However, Ethernet connections also seem to be impacted for some users, suggesting that the problem is elsewhere. A user has also found a temporary solution. The latter explains that he went to the network settings of his Mac, where he selected the option “configure manually” to deactivate the AVB / EAV mode. Following his message, other users have testified to obtain better speeds.
On the other hand, no solution seems to have been found on the Wi-Fi side at the moment. In other words, the problem is more likely on the software side, which should be fixed in a future update.
