M1 MacBook Air "Missing USB Class Driver" when trying to print to Dymo 4xl

Glad I am not the only one. I got the M1 on day one only because my previous mac died 2 days before. I use multiple dymo printers for my business, and after contacting Dymo I was essentially told 'well, we know it doesn't work, oh well'. I am using my daughters computer to print labels for my company, its awesome. Another stated it worked initially and then didn't, I noticed the same thing with my 3.0 usb hub. I used it to upload a time machine backup, and then after updating, wallah, 3.0 accessories no longer work and had to buy 3.1. Apple....... you are frustrating.

This happened about six or seven years ago with a new version of macOS and I recall it taking DYMO months to ever post an updated version of the Mac software. I'm not holding my breath, but I don't see any alternatives to the DYMO LabelWriter Twin Turbo 450 that I use.

I've had the same issue with my M1 Macbook pro, I receive the same message with my PIXMA ip2700 series printer. When I called apple support, I was told to unistall/reinstall the drivers. Then led to reinstall big sur, which failed to reinstall leaving me with no functioning device. my printer is connected via USB.

strangely, i managed to print one page after installing the driver and restarting but quickly went back to "error".

Brother says the brother QL-810W (wireless) should work just fine for any Mac (Intel or M1) using Big Sur. They have macOS 11 software and drivers available on their website. I only need this for standard letter address labels so I'm tempted to order one and try it.

Just verified Brother QL-1110NWB also works great printing wide labels via USB connected to our MacBook Air M1.

But as mentioned we switched to using the wifi direct capability on our Mobile devices (iPad, iPhone ). Very efficient for us and DYMO's software driver problem isn't an issue for our business anymore.

I expect the ROLLO printers should work also AND they have awesome customer support based on our past use a few years ago with these printers.

Reinstall macOS? Trying to get even one to print.

Same problem here. I called apple tech support and was told to reinstall my operating system, which was a giant pain since I had just got everything the way I wanted it. I did so, still having the same issue. I was told to bring the computer in to run a diagnostic. As my MacBook Pro is currently sent out for service due to a battery recall and I had to buy this computer to get my small business through the busiest time of year, the fact that my label printer is not working and I have no time for more service trips is incredibly frustrating. Not too pleased with apple at the moment. Desperately awaiting a fix.

Same exact problem here. Was on the phone with apple support for hours. I've tried uninstalling and reinstalling so many times. If i completely remove everything and reinstall, i can get it to print one label. As soon as i unplug or restart the computer, all of the problems begin. I also tried safe mode and reinstalling the OS. Super frustrating considering my entire business revolves around shipping items. Good luck to all with this issue!

Looking into a new label printer as well with all the dymo issues but honestly, I having trouble with all but one of my printers (I have 4 for different uses) also issues with my mouse and keyboard, I have to keep unplugging and plugging everything back in and deleting the printers then reinstalling just to print one **** thing. Has anyone else experienced this? I’m honestly thinking the M1 is not remotely worth the hassle, probably going back. I spoke to Apple support, they had me reinstall the whole OS and when that didn’t fix it, they said I need to bring this brand new computer in for service— again, not worth it.

@Artem8787 - This is a known issue. I have the M1 MacBook and the M1 mini and the issue is with Bluetooth connectivity. 1-3 times a day on both machines I have to restart, which then works fine for a few hours. Affects the keyboard, mouse and trackpad. If you Google it, you'll see what I mean. Apple is surely going to fix this ASAP - I'd guess the first update, which is currently in Developer Beta 2 right now. The M1 is way too nice a machine to go back to Intel. Wait it out...you'll be happy in the end.

And this is exactly the problem with Apple Care first tier support. They don't know the existing problems with the M1. I had the same experience trying to explain to them the Bluetooth connectivity problem. It's all over the internet, yet Apple Care won't admit to it or actually don't know about it.

Yes, I sold my DYMO and purchased a Brother QL-1110NWB for 4x6 label printing. I use the Wireless capability but this allowed me to use my iPhone 12 to print wi-fi shipping labels ( via Wi-Fi direct) which is what I'm doing.

My memory is failing me (:)) and can't remember if I tested the Brother usb connection with the M1..pretty sure I did...but will retest for grins within a day and respond.

The LabelWriter 450 Twin Turbo is not a wireless printer. So this is yet one more thing that doesn't work on an M1 Mac. I am beginning to have second thoughts about having purchased the M1 MBP and M1 Mac mini. I sure Hope there's a fix on the near horizon. I realize Apple always fixes these things, but in years past some have taken a very long time.

Larry- No, not at all! I didn't even know it was a problem. We use the Magic Mouse and keyboard with the M1 MacBook Pros.

Although I have had my mouse disconnect a few times but not near as many times as I did with the old MacBook. That was a couple times a day.

Sorry to hear your having problems though. I know the feeling. Very Annoying!

@Hedegaard8 - I also have two M1 Macs and have at least found a fast way to fix the Bluetooth problem when it randomly occurs. "Shift+Option" and click on the Bluetooth icon in the Menu Bar. Then click on "Reset the Bluetooth Module". The mouse, keyboard, trackpad...whatever you have connected via BT will disconnect and immediately re-connect. It only takes about 5-7 seconds and you're back in business. Before I discovered this I was restarting, which fixes it temporarily, but also takes longer than a few seconds.