1. Why Is My Mac Crashing

I haven't seen this particular issue addressed anywhere yet, so I hope I'm not repeating something. I run Teams on a MacBook Pro running Sierra 10.12.3. Teams launches and runs fine, but about 10 times a day I'll go to use Teams and it will be closed. I'm not getting errors — the app is just no longer running. When I click Teams in dock to open it (or, more often, use Alfred), the app seems to open, but the window doesn't appear. I need to click on Window from the menu bar and select an option that says something like 'Teams is loading' (I can't recreate it now, so don't recall what it says exactly).

Mac Mail constantly crashes with the issue above. I can use it for about 1 to 30 minutes before it crashes again. Beyond that it works just fine. Have multiple Exchange accounts, Gmail, MSN/Hotmail. Aug 14, 2018  Blizzard Entertainment uses cookies and similar technologies on its websites. By continuing your browsing after being presented with the cookie information you consent to such use.

I also get a message popup that says that I've installed all updates and that I'm running the most current version of Teams (again, I can't recreate right now, so don't recall the exact language). Is there a known issue with Teams closing itself regularly on Macs? None of my Windows users (which is pretty much everyone else) are experiencing this issue. It's almost like the app times out if it's not used for a while and closes. It's annoying, though, because I'll get an update on my phone and then realize that the desktop app has stopped running again. Super annoying — please help!

Hello, I'm experiencing the same problem on MacBook Air running Sierra 10.12.3 too. What I think is that Teams checks updates availability, and even if I have the last build (I think: 0.7.00.3101), it seems that it finds it has a most recent update to do, so installs it and closes (and not restarting).

But it has just installed the same build, again and again. When I 'check for updates' manually, it works in background and then says 'update done; please refresh'. But after restart: still the same build. Very annoying, I agree! And I didn't find a way to deactivate automatic update. I'm experiencing this on several 10.12.3 Macs, as well with a range of versions, most recently 0.00.75204, to which I updated manually last week.

The updater seems to want to relaunch Teams several times per day, but does not actually update. Occasionally following the relaunch, Teams displays a 'something went wrong' message, and has to be relaunched manually. Further, in some cases, Teams places additional duplicate copies of the update package at /Libarary/Application Support/Microsoft/Teams/tmp/, and doesn't always clean them up. Most Macs have several copies of the package accounting for 500-1500MB in this directory. I found one Mac that had been running teams for a couple weeks with 257 copies of the package in this directory, accounting for 20GB of disk space.

All of these Macs are logged-in to a single account most of the time. It's a standard (non-admin) mobile AD account with a local home. On at least one of these, Teams prompted for admin privileges at first run about 20 times, in what looked like an attempt at setting up an update helper daemon run by root (screenshot attached). Other Macs never prompted for this, or only did once. All of them run two procs called 'Microsoft Teams Helper' under the standard user while Teams is running. Something that is mostly a separate issue, but is exacerbated by the relaunch behavior, is that Teams has stored a credential in my login keychain (whether I tell it to or not), and seems capable of using it, but prompts for auth using a dialoge with the user/pass already populated.

So, it seems capable of automatically authenticating, but is asking me to click an additional 'submit' button for no apparent reason fairly often. Screenshot attached. For me, this seems to be an ongoing problem on the Mac client in the releases following the GA announcement, on all Macs I've seen that primarily use standard accounts. For what it's worth, I've calmed the relaunching/crashing in my environment by borking permissions on a directory used by the squirrel update framework, which has made the Teams client more tolerable for Mac users. This isn't desireable, increases manual update burden, and I don't expect it to help indefinitely, but it has made the Teams client a more stable and consistent experience for now. We are experiencing the same issue over here in our org. Oddly enough, it only seems to prevail on 50% of the macs while the other 50% seem to have no issue.

We run a standardized environment so all hardware and software is identical across the board - leaving this problem to seem like a user specific one. I originally guessed that it might be something that was caused due to these affected users installing some sort of software that conflicted with Teams but have not been able to find anything as of yet.

Are you all running your Mac user account as 'Standard' rather than Admin? I am, and I have the problem. My colleagues are not, and it works fine. Here is what I think is happening: Teams goes to look for a new version, downloads it, closes itself to auto-update, tries to but fails as it does not have admin privileges. Thus it silently fails to update and re-open.

Usually applications that need admin privaleges pop up a dialog box to ask for it. I suspect the update process for Teams is meant to be silent/background and hence has no UI interaction to pop it up. Workaround - go to the MS website and manually download latest version. Delete current version from Applications, install new version. Sadly you have to do this manually everytime there is a new version until MS realises this and fixes it. Chaz - yours will seem stable until there is a new version!

Just wanted to chime in here as I too have 3 users (including myself) with Macbooks running Sierra v.10.12.6 and Teams v. 1.0.00.24351 and Teams is 'crashing'.

No notification that it has a 'helper tool' to install or anything. I did a full app removal of Teams on 9/12, downloaded and installed the version noted above on the same day. That process eliminated the 'Helper Tool' installation prompts, but now Teams just closes. What I noticed today, is that when I lock my Mac and then return and unlock it, Teams is closed upon unlocking. The process is not running in the background, the app is simply closed. I have moved to the web version of the tool for now as it is driving myself and the other 2 insane. Does this help anyone else here understand what might be happening?

I have found the quick solution for this resides in the same way that I have to deploy some of my software via our MDM solution. You can either:. Install Teams into the /Users/username/Applications folder instead of /Applications - this gives the user rights to update/re-install it without a problem.

This is only really effective if you have a 1:1 environment as if you have multiple User Accounts on the machine, then you will need multiple copies under each User./Applications folder. UNTESTED - You can install in the /Users/Shared folder which all User Accounts have rights to. The issue here is that some applications do not like being installed there (which I have run into with other apps) which can/will cause them to have undesired behavior. Hi, this was my solution: - in finder navigate to Applications - cmd+click Microsoft Teams App, and select Get info - cmd+click another App, E.g. Microsoft Word App, and select Get info - on the Microsoft Teams App Info unlock the padlock - compare the admin Privilege and make them match the Word app info.

(for me it needed to be changed from Read only to Read&Write). I had previously tried uninstalling, reinstalling, removing all references to preferences, a new Teams account and a bunch of other stuff to no avail. It appears that the app needs admin read/write privilege in order to update itself (if it doesn't have it, it crashes and restarts with the existing update).

I'll update on here if this happens again. The other Office apps have a user called 'System' that you can't add from the GUI, you can force it from command line if you know how. The other office apps (at least in our company installs) all have read/write to the 'wheel' group. Again not something you can do from the GUI as it is a hidden group.

If you have some sort of Management software like Casper Suite or JAMF suite as its known now. You can make a script to be run on each machine on next login that does something like this: sudo chown USERNAME:wheel /Applications/'Microsoft Teams.app' You would have to replace USERNAME with the short name of the user on that Mac.

Hl-dt-st cd rw gce-8483b drivers for mac windows 10. HL DT ST CD RW GCE 8483B DRIVER FOR MAC - Search Advanced Search section: When you click on the download links on this site you are NOT downloading any specific driver itself, BUT rather an automatic driver update utility that may or may not be able to find the exact driver in question.

Why Is My Mac Crashing

Attention, Internet Explorer User Announcement: Jive has discontinued support for Internet Explorer 7 and below. In order to provide the best platform for continued innovation, Jive no longer supports Internet Explorer 7. Jive will not function with this version of Internet Explorer. Please consider upgrading to a more recent version of Internet Explorer, or trying another browser such as Firefox, Safari, or Google Chrome. (Please remember to honor your company's IT policies before installing new software!).