Latest news with #MicrosoftSupport
Forbes
19-05-2025
- Forbes
Microsoft Confirms Emergency Update For Windows Users
Emergency update confirmed for Windows users. Getty Images Microsoft has just confirmed an emergency update for Windows 10, after an increasing number of users reported May's mandatory security update breaking Windows. Affected users have been hit with BitLocker Recovery screens and even dreaded Blue Screens of Death after downloading and trying to install the latest critical update. 'Windows 10 might repeatedly display the BitLocker recovery screen at startup,' the company warned, confirming an out of bounds update via Microsoft's Update Catalog. The issue affects users 'on devices with Intel Trusted Execution Technology (TXT) enabled on 10th generation or later Intel vPro processors.' Those who have not yet deployed May's update should install the out of bounds update instead. For those who have tried to install the update and are now stuck, Microsoft says: Windows Latest was first to flag the issue, reporting that 'the KB5058379 install starts, but ends up at 'Enter the recovery key to get going again (Keyboard layout: US)' screen, and there's a text field to add the recovery key. In some cases, there's a BSOD as well.' Microsoft has again warned Windows users that its support team 'doesn't have the ability to retrieve, provide, or recreate a lost BitLocker recovery key,' but can use this link to find your BitLocker recovery key.' This issue and fix primarily applies to enterprise users, as 'consumer devices typically do not use Intel vPro processors and are less likely to be impacted by this issue.' May is proving an interesting month for the Windows-maker, with the wider release of its controversial Recall photographic memory for Copilot+ owners and the continuing drive to push 700 million Windows 10 users to upgrade ahead of October's deadline.
Forbes
18-05-2025
- Forbes
Microsoft Confirms New Update Locks Windows 10 — Or Worse. Here's What To Do
Windows 10 users have recently come across a problem caused by the latest Windows 10 KB5058379 update. The problem is, it's a mandatory update. Here's what you should do. Windows 10 operating system logo NurPhoto via Getty Images The issue was reported on May 15 by Windows Latest. 'Windows 10 KB5058379 is causing PCs to boot into Windows Recovery and require BitLocker key… In some cases, there's a BSOD as well… Windows 10 KB5058379 is a mandatory security update rolling out for everyone, including businesses or enterprises, and you don't have a choice but to install the update,' Windows Latest said. On Saturday, May 17, Microsoft updated a support document to acknowledge the issue. 'We are aware of a known issue on devices with Intel Trusted Execution Technology (TXT) enabled on 10th generation or later Intel vPro processors,' it said. It also shared some good news. 'Consumer devices typically do not use Intel vPro processors and are less likely to be impacted by this issue. This issue ONLY applies to the affected platforms listed below. Windows 10, versions 22H2; Windows 10 Enterprise LTSC 2021, Server: None,' Microsoft said in its support document. So, if you have a PC with Intel vPro chip, you could be tempted not to install it yet, though since it's mandatory, it's not advisable to skip it. Take heart, though: Microsoft is working on it. 'We are urgently working on a resolution for this issue, with plans to release an Out-of-band update to the Microsoft Update Catalog in the coming days,' it says, and the fact that the latest support document was filed on a Saturday indicates the urgency. The first stage, obviously, is to find your 48-digit Bitlocker recovery key. Here are Windows Latest's helpful instructions for what you need to do. You need to reboot into BIOS/UEFI, which can be done by pressing a key after power-on, but the keys are different across all OEMs. On most Dell/HP/Lenovo: press F2, F10/F12, or Esc immediately after power-on to enter BIOS/UEFI. Next, in BIOS, look for Security, open Virtualization or Advanced CPU Settings and turn off Intel TXT. This could also be referred to as Trusted Execution, or OS Kernel DMA Support. Note that you can leave VT for Direct I/O (or VT-d) enabled. Finally, save changes and exit BIOS. 'The idea is to disable Intel TXT / Trusted Execution and allow KB5058379 to finish installation. If you followed the steps correctly, you won't run into BitLocker Recovery or BSOD. Remember that the BSOD or BitLocker is triggered when installing KB5058379, but you won't have the issue after the update is installed successfully. The catch is that it's a challenge to install the security patch without turning off Intel TXT / Trusted Execution in BIOS,' Windows Latest explains. Windows 11 is not affected by this issue, it seems.
Yahoo
23-04-2025
- Yahoo
Chatham Police officer stops scam, saves woman from losing thousands of dollars
CHATHAM, Ill. (WCIA) — An elderly woman was recently saved from being scammed out of thousands of dollars thanks to the efforts of a Chatham Police officer who responded to her call for help. The Chatham Police Department posted on Facebook that Officer Logan Muncy was the person who handled the call. When he met with the woman, officials said she was 'very shaken up, frustrated, and embarrassed.' Murder trial date for Sean Grayson announced 'She had clicked a pop-up message on her computer claiming to be from Microsoft Support, but it was fake,' officials said. 'She spoke with someone claiming to be a 'representative' from Microsoft Support, and she allowed him to remote access into her computer to help him 'fix' the problem.' The scammer then told the woman that there was a problem with her bank account and began asking for the login information for her account. He also claimed there was a virus on her computer. 'The conman told the woman he could help fix the problem by sending him gift cards. At his direction, she purchased gift cards to Apple and Target totaling several thousand dollars, and she sent the gift cards to him electronically,' officials said. 'As soon as she had done this, she immediately realized her mistake and that something was terribly wrong. She became sick to her stomach over it.' Pritzker goes to Jacksonville to announce money for downtown revitalization projects Once Officer Muncy was aware of the situation, officials said he quickly went to work, calling the fraud departments at both Apple and Target. Except for one gift card, Muncy was able to cancel all of them before the scammers could cash them, and he was able to secure refunds for the woman. Before Muncy left her home, the woman reset her computer to factory conditions to ensure there any malware or malicious programs the scammers left on it were eliminated. Officials said she was very grateful for Muncy's help and everything he had done for her. 'She sent a thank you card to the PD for him and she also brought in one of her baking specialties for all of us to enjoy: a traditional Jewish dish that was absolutely delicious,' officials said. Copyright 2025 Nexstar Media, Inc. All rights reserved. This material may not be published, broadcast, rewritten, or redistributed.
Yahoo
06-03-2025
- Yahoo
Microsoft suggests four fixes for ancient Microsoft Store bug
After six years, Microsoft has officially released four methods for fixing the 'Try that again' or '0x80131500' Microsoft Store error. The bug was first reported in 2019, but the good news is that there is now an official solution for you. You can fix the 'Try that again' error by resetting the Microsoft Store app, using the Microsoft Store troubleshooter (Windows 10 only), checking for updates, and updating your internet's TLS (Transport Layer Security) settings. However, Microsoft recommends enabling TLS 1.2 and TLS 1.3 for compatibility. However, if the first three methods don't work, the issue may be due to TLS incompatibility. If this sounds too technical, don't worry; just follow these steps: press the Windows key > search for Run > type > press enter > click Advanced tab to ensure that the Use TLS 1.2 and 1.3 are checked. That's all there is to it. Before these official solutions, you may have turned to different workarounds. You possibly paused the antivirus protection (even if it was one of the best antivirus software), created a new local Windows account, turned off your VPN, or maybe even logged in with Safe mode turned on. So, what causes the 0x80131500 error? Various potential causes include an unstable Internet connection, firewall blocking access, incorrect proxy settings, or even a missing Windows update. Microsoft hasn't explained why releasing this official solution for the Microsoft Store bug took so long, but at least they're here for everyone. If, after trying all the suggested solutions, you still need more help, you can contact Microsoft Support to continue looking for a possible fix for your Windows-related issue.
