HP LaserJet Printer stopped working on my MacBook, after latest macOS Sonoma update.

I wanted to share experience with Sonoma 14.4 after update completed. This was duplicated on two (2) Macbook Pro after it was updated. Observation noted that Defender “com.microsoft.dlp” full disk access was disabled on 14.3 and after upgrading to 14.4. Process of elimination leads me to believe that Windows Defender made a change that now requires MacOS full disk access. See below:

• All printers are deleted from <Printers & Scanners> settings after 14.4 upgrade. The following message is displayed when trying to manually add printers:

Screen Example

• CUPS (i.e. LOCALHOST:631) access is also affected not allowing users to any changes from the main menus.

• The issue was resolved by clicking on the <Apple> logo followed by <Privacy & Security> <Full Disk Access> and give "com.microsoft.dlp" full disk access. 

Screen Example

Hello!

In our case the Microsoft Defender crashes the CUPS Server Daemon.

Answer from Apple Entersprise:

I have just looked at the logs you have uploaded and it looks the dlpdaemon daemon is crashing repeatedly. I believe this daemon is associated with Microsoft Defender. Could you please remove it and reboot the machine before trying to add a printer again?

I uninstalled MS Defender from all Macs in our company with macOS 14.4 - and now the printers are back again.

Hope this helps you too.

BG

René

Hi cygoonda,

We have the same issue as well here, academic staff start complaining theirs printer disappearing after recently installed macOS Sonoma update 14.4.0 . Everything was working fine up until few days ago before installing the update. The last version installed was 14.3.1. So far we have approximately 40 devices affected. We then try to replicate the issue and this is what we found below,

• latest updated macOS Ventura 13.6.5 device was working fine.
• Printer removed and reinstalled fine on macOS 14.4.0 Beta version on arm64 device
• Arm64 device that is still running macOS Sonoma 14.3.1 printer still present and working fine. We even try to reset the printer system, restart and reinstall all seems to be working fine.

we are also using smb printing - papercut and our institution using Ricoh MFD.

we are currently advising staff member not to install 14.4.0 update until we heard further.

we have contacted Apple Support and they said they will investigate this issue.

if you have any tips or tricks to fix this issue that would be greatly appreciated.

Best regards, John

Hi!

We have 26 Macs with updated to macOS 14.4 in our environment. All these macs have a broken printer cups connection.

$ cupsctl

cupsctl: Unable to connect to server: Bad file descriptor

Currently I don't know, how we can fix that.

BG René

Hi,

We have 60 Macbooks which we manage via Jamf Pro. Since MacOS 14.4, all printing functionality on the Macs is broken. There are no printing drivers on the Mac and any printer related activity comes up with the error message "cupsctl: Unable to connect to server: Bad file descriptor".

Same issue on a fresh new Macbook or a factory reset one.

Cheers,

Filip

Exactly. Most users just come to complain and “me too” things without taking the initiative to report the problem. That’s likely because many users believe these forums are official Apple support. They are not.

Feedback - Apple TV - Apple

Which exact model is this LaserJet printer? Is this printer AirPrint-capable?

How is this printer connected:

• Directly to your Mac?
• Connected to the local network by Ethernet or Wi-Fi?
• Connected to another Mac that is sharing in to the network?

I see that you already tried resetting the Mac's print system, but have you tried simply removing, and then, re-adding this printer while logged onto your Mac with an Administrator account? Doing so will reset the device drivers and printer queue. Have you tried resetting the printer to its factory default configuration?

Is this issue with printing from one particular app or from any app?

FWIW ... Although Apple does provide printer drivers for the most popular printer models, they get them from the manufacturers. New installations of macOS only include Apple and generic print drivers; whereas; upgrade installations also install drivers for printers already in use by the Mac. We are still dependent on the printer manufacturers for print drivers that "full featured" for theis specific printers.

>$ cupsctl

>cupsctl: Unable to connect to server: Bad file descriptor

same as on my MacBook.. which likely means that the entire printing system is broken

I don't run Defender and have this problem. Any help?

I am sorry you are having printer problems. If you will bear with me, I will offer some things to consider. Whenever we install an operating system upgrade or some OS updates, printers and scanners will often stop working. Then, a new OS compliant printer software must be installed. What you can do is to thoroughly check the printer web site for an updated driver that works with the newly installed operating system. If one is not available, then you should ask when one will be released. If that doesn't work, if the Printer has the Air Print feature, that can be used and no driver will be needed. If not, then you can check the respected web site below where volunteers write free drivers for older printers which are no longer supported, but which work with newer operating systems. It is worth checking out. Good luck.

Gutenprint Supported Printers

What you have encountered is not unusual. Apple does not develop its operating systems to conform to every printer's requirements. What Apple does is to provide OS requirements to all the various vendors who have equipment they wish to connect to and work with Macs, etc. Then the vendors must provide updated printer drivers (in this case) to meet those published requirements. This is how it has always been.

faoasy wrote:

We have 60 Macbooks which we manage via Jamf Pro. Since MacOS 14.4, all printing functionality on the Macs is broken. There are no printing drivers on the Mac and any printer related activity comes up with the error message "cupsctl: Unable to connect to server: Bad file descriptor".

Same issue on a fresh new Macbook or a factory reset one.

This is interesting... looking at the posts, it seems to rather happen to managed PCs (mine too). I set up a fresh install in a virtual machine via UTM, and it worked fine. Thanks for your post, I was close to factory resetting my Mac

Because you mentioned jamf, this might be related to an issue mentioned elsewhere when cups reports a bad file descriptor.

Are there any crash logs for Microsoft's dlpdaemon? Or sandbox errors about restricted access for the dlpdaemon process?

Error 0x0 0 0 kernel: (Sandbox) System Policy: dlpdaemon(8192) deny(1) system-privilege

If so, one workaround, until Microsoft addresses the crash, is to grant DLP (dlpdaemon) full disk access in Privacy & Security. cupsd may need to be restarted also…

Another guess, this was probably a security change by Apple that Microsoft has not had time to address.

Hope this helps.

@jblanchard1

I don't see crashes of dlpdaemon, I don't see "deny system-priviledge" in the console. Granting dlpdaemon full disk access doesn't help. It doesn't seem to have to do with dlpdaemon, but I'm not 100% sure. Something is killing the cups socket periodically, see here for more info: https://github.com/apple/cups/issues/6189