cant run diagnotic mode - error 2101


hi all.

im getting an issue with my 2019 16” MBP where it’s getting very very hot even when i’m not doing a lot of intensive tasks.

so i try to start up in diagnostic mode but i get this error -2101D.

i spoke to apple over chat but they are utterly useless… didn’t have any idea what the error was and said that installing monterey would fix the overheating issue.

i feel very disappointed by their support in general tbh.

anyway… can someone please advise me on how i can fix this?

thanks.

MacBook Pro 16" (2021)

Posted on Dec 11, 2021 12:34 AM

Reply
25 replies

Dec 11, 2021 5:06 AM in response to benjigordon

Suggest downloading the Application Etrecheck directly from a well Respected ASC Contributor. 


Disclaimer: I am not affiliated with nor receive compensation from the Developer.


The application is free or paid from added features. 


Run the application with Full Disc Access ( Security & Privacy - Full Disc Access ).


It will take a Snap Shot -  both the hardware and software.


 The Report will Not Reveal Any Personal Information. 


Post back the Full Report - copy and paste - using the Additional Text Icon ( 3rd Icon to last )


We can have a look at the report for possible issues and may have possible suggestions to resolve the issues.


Any Third Party Applications that will interfere with the normal operation of the OS, alter, modify, remove or delete or attempt to do so is an invitation for disaster and may require a Reinstallation of the OS.


This includes AntiVirus, Disk Cleaners, Disk Optimizes, UnInstaller etc.


The The Built in Security  is all that is required.

Dec 12, 2021 10:55 AM in response to benjigordon

I don't think so because I ran it in customize mode on a 2011 iMac and didn't experience overheating. But that was an iMac vs your MBP.


I'd fully reinstate the SIP as follows:


1 - Boot into the Recovery volume (boot with the Command + R keys held down).

2 - launch the Terminal.

3 - enter the following command followed by the Return or Enter key:


csrutil enable


Then download and run Etrecheck.  Copy and paste the results into your reply. Etrecheck is a diagnostic tool that was developed by one of the most respected users here in the ASC and recommended by Apple Support  to provide a snapshot of the system and help identify the more obvious culprits that can adversely affect a Mac's performance.


IMPORTANT:

Before running Etrecheck assign Full Disk Access to Etrecheck in the Etrecheck's Privacy preference pane so that it can get additional information from the Console and log files for the report:



Also click and read the About info to further permit full disk access.



Copy the report



and use the Additional Text button to include the report in your reply.




Dec 11, 2021 11:25 AM in response to benjigordon

Thank you for the Report.


The two biggest issue as I see it is AdGuard and the Custom Kernel Boot Arguments


That and the disabling of some key Apple Protections available as part of a normal Installation of Big Sur



Antivirus software: AdGuard


A - There are no known Windows-like Viruses in the wild that self replicate and affect macOS, because of the underling UNIX  Foundation and Permission Limitation. 


Details: Restrictive config permissions - possibly adware


System Integrity Protection: unknown (Custom Configuration)


Kernel boot arguments - This computer has custom kernel boot arguments.

Kernel boot arguments - This computer has custom kernel boot arguments.


System modifications - There are a large number of system modifications running in the background.


Unsigned files - There are unsigned software files installed that could be adware and should be reviewed.

System Integrity Protection disabled - System Integrity Protection is disabled. This computer is at risk of malware infection.


Apple security disabled - Apple security software is disabled. This computer is at risk of malware infection.


Clean up - There are orphan files that could be removed.


Kernel extensions present - This computer has kernel extensions that may not work in the future.









Dec 11, 2021 12:19 PM in response to Owl-53

It depends on why it was customized. I ran a customize SIP a couple of systems bak so I could run a system dock modification (make the dock transparent) but it was no big problem. It still protected but allowed the mod.


The csrutil status command will tell benjigorden if it's enabled or not. If' it's enabled and he doesn't know why we can give him the commands to reenable it.



Dec 11, 2021 11:35 AM in response to Owl-53

thanks for this.

ive uninstalled AdGuard but it was a very useful piece of software because it meant being able to browse the internet without any ads.

what was it that you could see was causing an issue?

also SIP is enabled and i just checked by starting in recovery mode and then restarting the etrecheck scan and it said it was still disabled.

also what are - Custom Kernel Boot Arguments and how do I address those?

cheers!

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

cant run diagnotic mode - error 2101

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.