2017 MacBook Pro Wi-Fi disconnects every 30 minutes

zhiyah288 wrote:

Having issues with my 2017 macbook pro i just recently got it, it is refurbished everything seems great on it but for some reason every 30 minutes or so the wifi decides to stop working which is odd because my wifi stays connected to my mac but just doesn’t work and every time it happens i have to turn the wifi off and back on or reset the whole mac. it gets annoying because i really don’t want to be doing that every 30 minutes just for my wifi to be working ive tried every reset, reboot, and even messed around with the settings but it still proceeds to do the same thing if anyone can help me it would be greatly appreciated

[Re-Titled by Moderator]

Original Title: kWifiLocNoInternetTitle error code

Take the machine to where you purchased it

As for a Full Refund

Shop elsewhere from a Reliable Apple Retailers or directly from Apple

Predicated on the placement of your question >> macOS 16 Sequoia

There is No " 2017 MacBook pro " that Qualifies to run Sequoia

The best this machine could run is macOS 13 Ventura

zhiyah288 wrote:

As of now it’s only been hooked up to one network which is my home wifi. i don't have any vpns connected currently.

if you have any VPN apps installed, whether or not you think the VPNs are in use or not, remove the apps, and test again.

Please download and run (free) EtreCheck, and share the results to the clipboard. Then open a new reply here, and press the Additional Text button that looks like a printed page, and paste and post the hardware and software configuration report here. From that, we can get a little more detail about what is installed and what is running here.

Your post was likely removed because you were/are running pre-release software, including MacOS and an advanced version of Safari.

We can not offer support for un-released versions of MacOS or Safari, and you are prohibited from posting ANY explicit information about software that Apple has not yet released.

----------

You MIGHT have a serious hardware error.

this crash report suggests you encountered a Machine check. you should fetch and post the complete report form that date&time:

2025-08-30 13:02:34 Kernel Panic

Details:

*** MCA Error Report ***

CPU Machine Check Architecture Error Dump (CPU: Intel(R) Core(TM) i5-7

360U CPU @ 2.30GHz, CPUID: 0x806E9)\r

CATERR detected! No MCA data found.\r

Kernel Panic Reports are stored in the Folder at:

/Library/Logs/DiagnosticReports

If you copy and paste that string into:

Finder > Go menu > Go to Folder

it will take you to the Folder where those reports are stored.

Kernel panic reports are named with Date&Time and start or end in ‘panic’

If you find one, please post as much as you can here, by using the “additional text” Icon in the reply footer (looks like a paper with writing). (Once the report devolves into incessant software-names or incessant Base-64 dumps with lots of AAAAAA lines, you are done.)

Please don’t post more about 20 lines of any other types of reports — they are interminable, and any information useful for this purpose is on the first screenful.

If you post your kernel panic here in its entirety, using the additional text icon in the reply footer, we do have some Readers (typically with developer background) who can attempt to interpret those panic reports. Even if no clear symptom emerges, this can still save a step if you DO need to contact Apple support later, because Apple Support specialists can read the panic reports you posted here, if you tell them what discussion or what Avatar.

Machine check errors are either bad hardware, or bugs in low-level software, or in firmware.

This CATERR case is a “catastrophic error”, and with no related machine check data available for this shutdown.

Use or revert to macOS 15, and test again, and then check with Apple Support.

I’ve met some flaky Intel processors among the latter-series Intel Mac models. This case is probably a failing logic board.

If the crashes continue on macOS 15, and given it’s a 2017 i5 Intel, and barring AppleCare coverage, I’d replace it with a newer or new Mac, rather than spending on a repair.

zhiyah288 wrote:

Having issues with my 2017 macbook pro

... offered to update my macbook to sequoia trough some software im a first time mac user so everythings new to me.

[Re-Titled by Moderator]

Original Title: kWifiLocNoInternetTitle error code

We can not support hack-a-mac here in these communities

2017 MBP is not on the list of supported hardware for Sequoia.

macOS Sequoia is compatible with these computers - Apple Support

The last supported MacOS for the 2107 model is macOS 13 Ventura.

to go back to that version, you will need to ERASE your Mac.

You should have your "friend" first install Ventura for you and get it running right before you decide to add unsupported add-ons.

Grant Bennet-Alder wrote:

The last supported MacOS for the 2107 model is macOS 13 Ventura.

to go back to that version, you will need to ERASE your Mac.

You should have your "friend" first install Ventura for you and get it running right before you decide to add unsupported add-ons.

And if it’s tossing out machine checks, and that’s often indicative of flaky hardware, all (stability) bets are off.

As was mentioned,  almost from the outside in your plea for help 

Return the machine for a full refund.

Not only is it running a “ Hacked “ version of Sequoia 

It also has,  as per

@ Grant Bennet-Alder  “ You MIGHT have a serious hardware error. “

@ MrHoffman “ Machine check errors are either bad hardware, or bugs in low-level software, or in firmware. “ and

“ And if it’s tossing out machine checks, and that’s often indicative of flaky hardware, all (stability) bets are off. “

We understand that having an Apple Computer for first time sounds like a great idea.

But purchasing an Apple Device is best purchased directly from Apple or a Reputable  Apple Retailer, as Brand New 

Every half hour from one Wi-Fi network, or from any Wi-Fi network?

Any “coffee shop” VPN apps installed here? If so, remove all, and test again.

Without drawing any conclusion, for some reason the Etrecheck Report seem to have been removed

You may try to post that report again via the suggestions from @MrHoffman