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.
Do I need to uninstall and reinstall the SQL Server engine?
Sorry this is long, but I need to show some context so people will understand that the object of this is for the user to get back to using Dynamics GP 10.0 with the original database. I have an occasional customer who has been using Microsoft Dynamics GP with SQL Server Express 2005 on a Server 2003 to run his small distribution business. I have been asked to come out and fix this old relic now and then (I recently needed to replace his DIMMs.) His software is installed on his C drive (RAID1) while his data has been kept on his D drive (RAID5.) His RAID5 drive was apparently running on two drives with one marked as missing and now one of those drives failed. Luckily, he had a recent backup of the D drive. I have replaced the RAID drives and put back his files from the backup. I also restored his database on SQL Server Express 2012 on my laptop just to make sure we had his data. He needs this to run on his server so we can access the data through Dynamics GP. By the way, he was in the middle of moving all this to the cloud with some other company, but he needs to export certain tables from Dynamics to them (I'm not a SQL Server developer so this giant jumble of tables aren't very helpful - I exported some "Views" to CSV for him but there's quite a bit else I can't deal with.) So today, on the server, I ran his SQL Server Management Studio and though I could not connect to the non-existent database, I chose Object Explorer and then right clicked Database in the left menu and then chose Restore database. His database was listed in the dropdown and I selected it. I played around in there trying to figure out how to connect to the BAK file I had copied to the new RAID5 drive but then figured I had to use the SCRIPT button. Amazingly, the script filled itself in with the correct path to the external drive that contained the backup! The problem is that it executes with errors. See attached image. Does this mean that I need to reinstall SQL Server Express 2005? Is this going to break anything? Any advice would be appreciated before I press on.
Free Amazon Kindle Reader
I am trying to install the Amazon Kindle reader on my desktop but Windows 10 keeps sending me to go download the priced version in the Windows app store. Amazon gives this away for free, so why is Microsoft selling it for a price in the Microsoft app store? is there a workaround that would allow me to by pass this requirement to install the Microsoft version? Any help will be greatly appreciated.
VBox: Remote Management / Add Roles & Features: The WS-Management service cannot process the request
Hello, I have installed Windows Server 2019 in a VirtualBox 6.1 machine. In the Server Manager I want to activate remote management and install roles like AD DS, but these error messages appear: Local Server \ Remote Management: "The WS-Management service cannot process the request because the XML is invalid." Add Roles and Features: "The WS-Management service cannot process the request. The service in configured to not accept any remote shell requests." I have created the VirtualBox virtual machine as "Windows 2016" and tried several options like EFI, I/O APIC, PAE/NX, nested VT-x, nested paging, NAT, bridged adapter. In the Local Group Policy Editor (Windows Server virtual machine), I have manually enabled "Allow Remote Shell Access" in Local Computer Policy > Computer Configuration > Administrative Templates > Windows Components > Remote Shell and run gpupdate /force. I have also installed Windows Server in VirtualBox on two other computers, but the same problem appears. I hope anyone can help me solve this problem. What has to be configured to make the WS-Management service work correctly?
