Classic outlook - Teams add-in not loading
We recently had a partner experience an issue that is causing the teams add-in feature to not load properly in classic outlook when creating a new meeting. For some background info, we are using a Virtual environment within remote desktop running windows 11. Our servers are provided by AWS. The issue only began as recently as December, as far as we can ascertain with the customers information. I have noticed this issue occurs with numerous partners but is inconsistent, as some load and others do not. I followed troubleshooting steps such as an uninstall/reinstall, verifying the load behavior in the registry was set to 3, and tried to re-register the related teams.addinLoader.dll. A colleague did implement a script to the environment task scheduler that will run every time outlook is launched to re-install that add-in as a break fix, but this still requires closing outlook and reloading it to work. I was curious if anyone else had encountered this within remote desktop with classic outlook, and if they had any success in fixing it. The easiest thing, obviously, is moving over to new outlook since teams' integration is native, but we have some that prefer classic. Though, with it being retired in 2029 it may be worth starting the move away while in a remote environment.
Unable to get SMS verification when trying to reset Outlook account password
This is the error message I get, it's in Swedish but it says that the verification method doesn't work at the moment. Has anyone else gotten this issue? What's the solution for it? I don't have an alternativ mail to use for getting the verification code and any manual account reset hasn't worked out either.Screen Sharing Causes System Shutdown on Surface Pro
Dear Microsoft Teams Support, We are encountering a persistent issue with one of our users involving Microsoft Teams on a Microsoft Surface Pro 2 device. Each time she attempts to initiate screen sharing, the computer abruptly shuts down. We have already performed extensive troubleshooting, including: Verified that all drivers are up to date. Closed all background applications before attempting screen sharing. Updated Microsoft Teams to the latest version. Cleared the Teams cache. Attempted both repair and reset of Teams via Windows Settings. Ran System File Checker (SFC) and DISM scans, both of which reported no issues. Uninstalled Teams and downloaded the latest installer, but reinstallation fails. Despite these efforts, the issue remains unresolved. We would appreciate your guidance on further steps or escalation to resolve this problem. Thank you for your support.Identify Which Process Is Blocking a File in Windows
When you see the error "The process cannot access the file because it is being used by another process," you can use several built-in or free tools to find out which process is locking the file or folder. Using Resource Monitor Resource Monitor is built into Windows: Press Win + R, type resmon, and press Enter. This will open Resource Monitor. Go to the CPU tab. In the Associated Handles section, use the search box to enter part of the file or folder name. The results will show which processes are using the file. Check the Image and PID columns to identify the process. You can right-click the process and select End Process if necessary (be cautious when ending processes). Using Process Explorer Process Explorer is a free tool from Microsoft Sysinternals: Download and run Process Explorer as administrator. You can acquire Process Explorer using the following WingGet command: Winget install Microsoft.Sysinternals.ProcessExplorer In Process Explorer, Press Ctrl + F or go to Find > Find Handle or DLL. Type part of the file or folder name and click Search. The tool will list all processes currently using the file. Click an entry to highlight the process in the main window. You can right-click the handle and select Close Handle to release the file (use with caution). Using Command Line Tools openfiles: Run openfiles /query in Command Prompt (may require enabling with openfiles /local on and a restart). This shows which files are open and by which process. You’d have to enable the local on option before the file got locked of course. handle.exe: Download from Sysinternals. You can acquire Handle.exe with the following WinGet command: winget install Microsoft.Sysinternals.Handle Run handle.exe <filename> to list processes using the file.
