2013 MacBook Air problems, bugs resolved with update

By Updated on

When Apple released the 2013 MacBook Air with Haswell processor, it was met with one or two problems, such as the screen experiencing flickering when running Adobe Photoshop, as well as the bug that would often cause the Wi-Fi to disconnect. However, yesterday Apple released an update to help address these very issues.

2013 MacBook Air problems resolved – It wasn’t long after Apple’s latest version of their MacBook Air that users began to experience these issue, and we’re sure they were not pleased when their screens began to flicker while using Photoshop, as this would be a huge issue while trying to edit photos.

The problem was thought to have been an issue with a driver or the GPU, but whatever it was, the issue has thankfully been resolved. As for the Wi-Fi bug, it was obvious that there would be some teething issues, considering the fact that the new MacBook Air was using the new newest 802.11ac Wi-Fi standard, which is meant to offer faster connectivity.

It’s no secret that the 2013 MacBook Air price is a little on the expensive side, and as such many Apple haters out there feel as though these problems should have been ironed out before its release, and while we agree in one respect, it’s hard to fix all issues before a product is released.

As yet we have not heard from any MacBook Air mid-2013 owners letting us know that these issues have in fact been resolved, but we’d appreciate if you could. In the mean time you are advised to update your device now.

2013 MacBook Air sales – There is a concern that sales of this newer MacBook have been a little on the low side, and as a result has caused Apple to fall further down the rankings for laptop sales. However, as with all new products like this, some people would rather wait to purchase one until they know the issues have been fixed, so maybe we should see a spike in MacBook Air sales for the 2013 model now?

Also See: iMessage not working with Mac sync

2013 MacBook Air problems, bugs resolved with update