Jump to content

Search the Community

Showing results for tags 'bugfix'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Site Related
    • News & Updates
    • Site / Forum Feedback
    • Member Introduction
  • News
    • General News
    • FileSharing News
    • Mobile News
    • Software News
    • Security & Privacy News
    • Technology News
  • Downloads
    • nsane.down
  • General Discussions & Support
    • Filesharing Chat
    • Security & Privacy Center
    • Software Chat
    • Mobile Mania
    • Technology Talk
    • Entertainment Exchange
    • Guides & Tutorials
  • Off-Topic Chat
    • The Chat Bar
    • Jokes & Funny Stuff
    • Polling Station


  • Drivers
  • Filesharing
    • BitTorrent
    • eDonkey & Direct Connect (DC)
    • NewsReaders (Usenet)
    • Other P2P Clients & Tools
  • Internet
    • Download Managers & FTP Clients
    • Messengers
    • Web Browsers
    • Other Internet Tools
  • Multimedia
    • Codecs & Converters
    • Image Viewers & Editors
    • Media Players
    • Other Multimedia Software
  • Security
    • Anti-Malware
    • Firewalls
    • Other Security Tools
  • System
    • Benchmarking & System Info
    • Customization
    • Defrag Tools
    • Disc & Registry Cleaners
    • Management Suites
    • Other System Tools
  • Other Apps
    • Burning & Imaging
    • Document Viewers & Editors
    • File Managers & Archivers
    • Miscellaneous Applications
  • Linux Distributions


  • General News
  • File Sharing News
  • Mobile News
  • Software News
  • Security & Privacy News
  • Technology News

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...

Found 23 results

  1. A couple of days ago, Microsoft released a new Windows 11 Insider build, version 22000.282 to the Beta and Release Preview channels. The update carried plenty of changes and improvements with perhaps the most important one being a performance fix for AMD's Ryzen CPUs that were exhibiting a massive degradation in the L3 cache latency output ever since the first public release of the OS. In fact, the problem apparently was amplified after the Patch Tuesday update. This particular issue is different from the performance loss seen with Virtualization-based Security (VBS) enabled which is a consequence of the lack of MBEC on older CPUs. That is why, as confirmed by AIDA64 itself, even the latest Zen 3-based parts like the Ryzen 9 5900X were susceptible to this performance bug, even though Zen 3 is officially supported by Microsoft for Windows 11, and has significant architectural upgrades in terms of cache performance over its predecessors. Now that the performance patch for the issue has been released with the new Build 22000.282 (KB5006746), AIDA64 decided to test the new build as well to see if indeed Microsoft's claims are correct. Three test runs were done to measure the L3 cache latency under Windows 10, Windows 11 pre-patch, and Windows 11 post-patch environments. Unlike last time, a Zen 2-based Ryzen 9 PRO 3900 processor paired with a dual-channel DDR4-2667 kit on an AORUS X570 motherboard was used for the tests. The results are provided in the images below (click to enlarge): The obtained results show that the patch has worked like a charm and the L3 performance of Ryzen CPUs after this update is back up to where they should be. Hence, all Windows 11 insiders who are using a Ryzen-based PC should probably upgrade to this build. Source: AIDA64 (Twitter) AIDA64 confirms Windows 11 performance patch for AMD's Ryzen L3 issue works like magic
  2. Microsoft has fixed a known Windows 10 issue causing smartcard authentication to fail when trying to connect using Remote Desktop after installing the cumulative updates released during last month's Patch Tuesday. As explained by the company, devices attempting to make Remote Desktop connections to devices in untrusted domains might be unable to connect. "After installing KB5005611 or later updates, when connecting to devices in an untrusted domain using Remote Desktop, connections might fail to authenticate when using smart card authentication," Microsoft explained. "You might receive the prompt, 'Your credentials did not work. The credentials that were used to connect to [device name] did not work. Please enter new credentials.' and 'The login attempt failed' in red." Windows platforms affected by this issue include both client (Windows 10 21H1, Windows 10 20H2, and Windows 10 2004) and server (Windows Server 2022, Windows Serve 20H2, and Windows Server 2004). Fixed via Known Issue Rollback Microsoft has already rolled out a fix to address this issue via the Known Issue Rollback (KIR) feature to affected Windows 10 devices. "This issue is resolved using Known Issue Rollback (KIR). Please note that it might take up to 24 hours for the resolution to propagate automatically to consumer devices and non-managed business devices. Restarting your Windows device might help the resolution apply to your device faster." On enterprise-managed devices, customers can also install and configure group policies to resolve the issue. Microsoft has released the following group policies to address this specific issue (a restart is required after configuring the Group Policy): Windows Server 2022 Windows 10, version 2004, Windows 10, version 20H2 and Windows 10, version 21H1 Redmond has been using the Known Issue Rollback feature to roll back computers impacted by problematic bug fixes to a working state since late 2019. A fully working version of KIR was introduced in Windows 10 2004 when all components started working together as a complete system. While fixes issued through KIR are distributed via Windows Update, they are not delivered as actual updates. Instead, they are deployed by creating Windows Registry entries that disable changes made in previous updates. Known Issue Rollout fixes usually propagate to all affected systems within 24 hours, and that restarting impacted computers may speed up the process. Microsoft previously used Known Issue Rollout fixes to performance issues while gaming, resolve printing issues, and app freezes and crashes. Microsoft fixes Windows 10 auth issue impacting Remote Desktop
  3. Windows 11 has been rolling out for around 2 weeks to regular users, but the operating system continues to have a number of issues. Microsoft recently rollout out Windows 11 Build 22000.282 to Beta and Release Preview Channel Insiders which contains a large number of fixes, including for the AMD performance problem, and that should be rolling out to regular Windows 11 users by the end of the month. The operating system however has other performance issues, including one users are complaining about affecting File Explorer. Users are complaining of poor performance when they drag to select files, a rather basic feature of File Explorer. Microsoft says their investigation revealed that the Command Bar was doing unnecessary calculations when navigating to folders, causing an unexpected increase decrease in performance. A fix for this is currently being tested in Windows 11 Insider Preview Build 22478 which is currently in the Dev channel. If no serious issues show up the fix will presumable be backported to Windows 11 Build 22000. via WindowsLatest Microsoft is testing fix for Windows 11 File Explorer performance issue in Dev channel
  4. Update is reportedly being prepared for public release early next week. Now that Windows 11 is out, the arduous process of fixing the new operating system's bugs can begin. The OS got its first Patch Tuesday update earlier this week, and now another update is rolling out to Windows Insiders in the Beta and Release Preview channels. It fixes a long list of early problems with Windows 11. The headliner here is a fix for a problem affecting L3 cache latency on AMD Ryzen processors. According to AMD, the bug can reduce performance by 3–5 percent. The Windows 11 update released earlier this week may have actually made the problem worse, but at least a fix is imminent. The L3 latency bug is one of a pair of problems that AMD identified with Windows 11 earlier this month. The other Windows 11 problem AMD identified, which can prevent high-core-count, high-wattage Ryzen chips from correctly assigning work to the processor's fastest individual cores, will be fixed via an AMD driver update. The Release Preview Insider channel is usually a Windows update's last stop before public distribution. A post shared on Reddit suggests that the Windows update is being targeted for release on Tuesday, October 19th, while the AMD driver update for the other problem should be released two days later, on the 21st. Other bugs addressed in the Windows 11 update include one that prevented some upgraders from seeing the new Taskbar or using the Start menu, a PowerShell bug that can fill up a storage volume with "an infinite number of child directories" when you try to move a directory into its own child directory, and a number of problems that could cause freezes, crashes, and slowdowns. Fixes for AMD Ryzen performance, other Windows 11 issues rolling out to testers now
  5. Microsoft has released an emergency fix for freezing and crashing app issues caused by September's KB5005565 and KB5005101 cumulative updates. With the release of the Windows 10 KB5005101 preview update and the KB5005565 cumulative update, Microsoft states that users may have experienced app freezes, app crashes, and the inability to launch an application. These issues only affected users utilizing the Microsoft Exploit Protection Export Address Filtering (EAF) feature, which is used to detect dangerous operations used by malicious code or exploit modules. "After installing KB5005101 or a later update on devices using Microsoft Exploit Protection Export Address Filtering (EAF), you might have issues with some applications," explained Microsoft. "You might be experiencing this issue if apps fail to open, fail to open files, or you might receive a white window when attempting to login." Microsoft has rolled out a fix using the Known Issue Rollback (KIR) feature, distributed to Windows 10 devices using Windows Update. "This issue is resolved using Known Issue Rollback (KIR). Please note that it might take up to 24 hours for the resolution to propagate automatically to consumer devices and non-managed business devices. Restarting your Windows device might help the resolution apply to your device faster." For enterprise users or those who wish to receive the update sooner, you can also install various group policies or add Registry keys to install the fix. Microsoft has released the following group policies, which users can install to apply the fix. It is critical that users only install the group policy associated with a device's version of Windows. Windows Server 2022 Windows 10, version 2004, Windows 10, version 20H2 and Windows 10, version 21H1 Windows 10, version 1909 Windows 10, version 1809, Windows Server 2019 Windows users can also install the fix immediately by running one of the following commands from a Windows 10 elevated command prompt. Like the registry policies, only run the command associated with your version of Windows. Windows Server 2022: reg add HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Policies\Microsoft\FeatureManagement\Overrides /v 2801335948 /t REG_DWORD /d 0 /f Windows 10, version 2004, Windows 10, version 20H2 and Windows 10, version 21H1: reg add HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Policies\Microsoft\FeatureManagement\Overrides /v 2767781516 /t REG_DWORD /d 0 /f Windows 10, version 1909: reg add HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Policies\Microsoft\FeatureManagement\Overrides /v 928713355 /t REG_DWORD /d 0 /f Windows 10, version 1809, Windows Server 2019: reg add HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Policies\Microsoft\FeatureManagement\Overrides /v 2371422858 /t REG_DWORD /d 0 /f Resolved using the Known Issue Rollback feature When Microsoft releases new updates to fix known bugs, the new code may cause further issues in Windows 10. If Windows telemetry and diagnostics indicate that a large audience of Windows 10 users are affected by a new issue, Microsoft can release a Known Issue Rollback (KIR) fix to disable the new code causing the issues, as illustrated below. Illustration of how Known Issue Rollout fixes are delivered In the past, Microsoft has used Known Issue Rollout fixes to resolve printing issues and performance issues while gaming. While these fixes are distributed via Windows Update, they are not delivered as an actual update. Instead, they are deployed by creating Windows Registry entries that disable changes made in previous updates. Microsoft says that Known Issue Rollout fixes are usually installed within 24 hours and that restarting the computer may speed up this process. Windows 10 emergency update resolves KB5005565 app freezes, crashes
  6. Microsoft Edge Canary build users were facing a serious inconvenience over the weekend. After the Edge was started, the browser started opening windows, seemingly at random. After 5 minutes or so, users will have 6-7 new Edge windows apart from the one they opened intentionally. Today, Microsoft released a new Edge Canary build to fix the issue. You can update to Edge version 1008 to fix this random window issue. Source: Microsoft Microsoft fixes the Edge canary build issue which opened new windows randomly
  7. Microsoft accidentally broke the Start menu and taskbar on systems of Windows Insiders after pushing a Teams promo to the desktops of users running Windows 11 preview builds. While the company didn't explain the reason behind Dev and Beta Channel Insiders experiencing Start menu and taskbar unresponsive and having issues accessing other OS areas, including Settings, developer Daniel Aleksandersen discovered that a buggy promo deployment caused the problem. "The problem wasn’t caused by an update delivered through Windows Update," Aleksandersen explained."Instead, it was caused by a small file [..] [that] contained an advertisement for Microsoft Teams." "The promo intended to promote the upcoming operating system’s integration with Microsoft Teams Instead, it caused Explorer (the Windows desktop shell) to stop responding and left users without a working Start menu and taskbar." Windows 11 Teams promo (Daniel Aleksandersen) Windows Insiders impacted by this issue reported that they couldn't use their computers because Explorer and the Taskbar are gone, and the Windows desktop shell is not accessible even after reinstalling the system. After being flooded with reports, Microsoft acknowledged the issue and pinned it on a "server-side deployment" problem. "Recently, Windows Insiders in both the Dev and Beta Channels began reporting that Start and Taskbar were unresponsive and Settings and other areas of the OS wouldn’t load," Microsoft said. "We quickly discovered an issue with a server-side deployment that went out to Insiders and canceled that deployment." Windows Insiders whose computers' were impacted by the buggy Teams promo need to go through the following steps to get their PCs back into a working state: Step 1: Use CTRL-ALT-DEL and choose to open Task Manager. Step 2: Choose “More details” at the bottom of Task Manager to expand Task Manager. Step 3: Go to “File” and choose “Run new task.” Step 4: Type “cmd” in the “Open” field. Step 5: Paste the following (everything in bold): reg delete HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\IrisService /f && shutdown -r -t 0 Step 6: Hit enter, and then your PC should reboot. After rebooting, everything should be back to normal. Update: When asked for more details about this issue, a Microsoft spokesperson told BleepingComputer that "Microsoft has nothing to share on this topic besides the update published in this Windows Insider Blog: Announcing Windows 11 Insider Preview Build 22449 | Windows Insider Blog and tweet from the Windows Insider Twitter." Microsoft breaks Windows 11 Start Menu, Taskbar with Teams promo
  8. Some Windows 10 administrators experienced an odd behavior on devices running Windows 10 version 2004 or higher that started in May 2021. Any attempt at installing cumulative updates for the operating system would result in a PSFX_E_MATCHING_BINARY_MISSING error and failure to install the update. The issue started to happen on devices after the May 25, 2021 update, KB5003214, or the June 21, 2021, KB5003690, updates were installed on affected machines. Affected are machines running Windows 10 versions 2004, 20H2 and 21H1. According to Microsoft, the issue may occur on devices on which outdated resource records were removed from automatically. Microsoft describes the cause of the issue in the following way: This issue occurs on devices that have been scavenged automatically to remove outdated resource records. When a system is scavenged, the recently installed latest cumulative update (LCU) is marked as permanent and the older components are removed from the system. After scavenging is complete and a device is in this state, you cannot uninstall KB5003214 or KB5003690, and you cannot install future LCUs. Microsoft published a solution on August 24, 2021 on its support website. Administrators need to perform an in-place upgrade to resolve the issue. Microsoft notes that in-place upgrades are only available to devices that have been online for at least 30 days. For ARM devices, it is only working if the update KB5005932 has already been installed on the device. Open the Start menu. Type cmd. Command Prompt should be displayed as the first result. Select "run as administrator" to launch it with elevated rights. Run the following command: Reg.exe Add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion /v AllowInplaceUpgrade /t REG_DWORD /f /d 1 The command marks the system for an in-place upgrade. The Registry key will be removed automatically after the in-place upgrade has completed. Microsoft notes that it may take up to 48 hours before the upgrade is offered to the device. The device will be upgraded to a clean version of the operating system along with the latest monthly security update installed. Closing Words Being unable to install any updates for Windows 10 is quite the serious problem. Microsoft released several updates with critical security patches since May 25th, which the affected systems missed out on because of the issue. Microsoft has a fix for Windows 10's PSFX_E_MATCHING_BINARY_MISSING update error
  9. The latest Windows 11 Insider Preview Build is breaking Windows Hello, here is the fix Many Windows 11 Insiders are running into a Windows Hello “Something went wrong” error after installing the latest preview build 22000.100. This was a known issue Microsoft was aware of prior to the release of the build, with Microsoft saying: Windows Hello (Face) may show an error saying “Something went wrong” when attempting to sign in after upgrading. There are two workarounds. One is simply to use your PIN, until the next build fixes the issue. The other is to uninstall the Windows Hello biometric driver and let Microsoft install a fresh version that works better. To do this: Open Device Manager Navigate to “Biometric devices” Right-click on and choose to Uninstall “Windows Hello Face Software Device” Reboot your PC. Your PC should automatically install a new driver which should fix the issue. The latest Windows 11 Insider Preview Build is breaking Windows Hello, here is the fix
  10. A fix is coming for those locked out of their Chromebooks by Google’s update This follows another borked update earlier this month A bad update to Chrome OS, version 91.0.4472.165, has left some users unable to log in to their accounts, or reportedly with boot-looping computers (via Android Central). If you’ve found yourself locked out of your Chromebook, help is on the way: Google posted on its system status page that it’s working on a fix, which it expects to release on Wednesday. It’s also pulled the update, which should prevent more users from experiencing the issue. According to Google, the only options to immediately regain access to your Chrome OS device (if it unfortunately downloaded and installed the update) will lead to the local data on the device being wiped. If you can wait until the new fix the issue is released, though, your device should automatically download that update as well. Or, you can manually trigger the update using the guest account. If your computer has downloaded the bad update but not installed it, you might want to avoid shutting it down or rebooting it until the fix is out. If you can’t wait for the fixed update, Google recommends either “Powerwashing” (factory resetting) your Chrome OS device, rolling back the update with a recovery USB key, or removing your account and re-adding it. Again, all these solutions will delete local data on the device, so be careful. Google’s status page also doesn’t address the boot looping issues — Android Central says that if you’re experiencing those issues you’ll have to use the recovery USB key method to reinstall Chrome OS. The broken 91.0.4472.165 update is actually the second bad Chrome OS update we’ve seen this month: Google had to pull another update around July 7th after users discovered that some Chromebooks were having their performance seriously throttled. A fix is coming for those locked out of their Chromebooks by Google’s update
  11. Microsoft fixes Outlook crash issues when using Search bar Microsoft will roll out a fix for a known issue causing Outlook for Microsoft 365 to crash on systems where users attempted using the Search bar or Search Suggestions features. Starting February, users have reported encountering this bug on various online platforms, including Microsoft's community website and Tech Community, as well as Reddit. As Microsoft describes the issue, "if you attempt to use the “Search” bar within Outlook, the application will shut down." Redmond says that a fix has already been developed for this issue, with a fix being planned to roll out worldwide to all impacted users on Tuesday, July 13. To install the Outlook update addressing this known bug, you have to follow the instructions available on the Install Office updates support document. Unofficial workarounds While no official workarounds are available yet for Outlook customers affected by these crash issues, users reported that clearing out the local folder and recreating your profile should eliminate the bug. To do so, you will have to go through the following steps: Open the Run dialog using Windows + R. Open %appdata%\local\microsoft\outlook and delete everything in the folder. Go to Control Panel > Mail > Show Profiles and delete the old Outlook profile. Create a new Profile and start Outlook. Others successfully mitigated the issue by rolling back to a previous Outlook version (the one released in May), not affected by this bug. The only step required for this is to run the following command from the Command Prompt: "C:\Program Files\Common Files\microsoft shared\ClickToRun\OfficeC2RClient.exe" /update user updatetoversion=16.0.14026.20246 In June, Microsoft fixed another issue causing Microsoft 365 users to experience authentication issues when logging into desktop client apps like Microsoft Teams, OneDrive for Business, and Microsoft Outlook. The company also addressed an Outlook bug that blocked users from forwarding or replying to emails bundling embedded hyperlinks pointing to long URLs. Redmond is currently also investigating an Outlook crash when using the 'Find Related' search feature in the Tasks Module and an issue where the follow-up flag status is displayed in sent messages incorrectly. Microsoft fixes Outlook crash issues when using Search bar
  12. Microsoft pushes emergency fix for Windows 10 KB5004945 printing issues Microsoft has released an emergency fix for printing issues affecting Zebra and Dymo receipt or label printers caused by changes in the recently released KB5003690, KB5004760, and KB5004945 updates. This week, Microsoft released the out-of-band KB5004760 and KB5004945 security update to fix the actively exploited PrintNightmare vulnerability. After installing the update, Windows users found that they could no longer print to their Zebra and Dymo label and receipt printers connected via USB. As most people reported the issues after installing the out-of-band updates, users assumed that the problem was related to the patch for the PrintNightmare vulnerability. However, Microsoft announced today that the issues are not "not related to CVE-2021-34527 or CVE-2021-1675," and are caused by changes introduced in the June 2021 cumulative update preview. Fixed using Known Issue Rollback feature Thursday night, Microsoft released an emergency fix for Windows 10 2004, Windows 10 20H2, and Windows 10 21H1 to resolve these issues. "After installing KB5003690 or later updates (including out of band updates, KB5004760 and KB5004945), you might have issues printing to certain printers. Most affected printers are receipt or label printers that connect via USB," Microsoft stated in a new issue posted to the Windows 10 health dashboard. This fix is being rolled out through Microsoft's Known Issue Rollback (KIR) feature, which distributes fixes for known issues through Windows Update and should reach most people within 24 hours. "This issue is resolved using Known Issue Rollback (KIR). Please note that it might take up to 24 hours for the resolution to propagate automatically to consumer devices and non-managed business devices. Restarting your Windows device might help the resolution apply to your device faster," explains Microsoft. "For enterprise-managed devices that have installed an affected update and encountered this issue, it can be resolved by installing and configuring a special Group Policy. Note Devices need to be restarted after configuring the special Group Policy. For help, please see How to use Group Policy to deploy a Known Issue Rollback. For general information on using Group Policies, see Group Policy Overview." When Microsoft releases new cumulative updates to fix a bug, the new changes may cause other issues in Windows 10. Using diagnostics and telemetry shared by Windows 10 computers, Microsoft can detect when issues arise and determine how wide an impact they have. If the issues are affecting a large population of Windows 10 users, Microsoft will issue a Known Issue Rollback (KIR) through Windows Update that disables the change causing the issues, as shown below. Illustration of how Known Issue Rollout fixes are delivered While these fixes are distributed via Windows Update, they are not delivered as an actual update. Therefore, there is no easy way for Windows 10 users to know when a Known Issue Rollout fix is installed without checking the Registry. To determine if this KIR is installed on your computer, you can open the Registry Editor and check if the following key exists. If it does, then the KIR has been installed on your computer. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FeatureManagement\Overrides\4\1861952651 If you do not see the KIR in the Registry, do not panic. It simply means it has not been pushed down to your computer yet. Microsoft says the rollout is expected to be complete within 24 hours and that restarting the computer may speed up this process. Microsoft pushes emergency fix for Windows 10 KB5004945 printing issues
  13. Microsoft releases out of band KB5004760 Windows 10 update fixing problems with PDF Microsoft has released an out of band cumulative update KB5004760 for Windows 10. The new update fixes an issue with PDF files not opening on the web when using Internet Explorer 11 or similar applications that are based on the 64-bit version of WebBrowser Control. Another issue related to PDFs that the update says it fixes is a rendering problem where the PDF file's background would only be displayed in the color gray when using the Adobe Acrobat plug-in. The update also includes certain improvements to the servicing stack. As usual, a few known issues are present in this cumulative update. They are listed below alongside their possible workarounds: Symptoms Workaround When using the Microsoft Japanese Input Method Editor (IME) to enter Kanji characters in an app that automatically allows the input of Furigana characters, you might not get the correct Furigana characters. You might need to enter the Furigana characters manually. Note: The affected apps are using the ImmGetCompositionString() function. We are working on a resolution and will provide an update in an upcoming release. Devices with Windows installations created from custom offline media or custom ISO image might have Microsoft Edge Legacy removed by this update, but not automatically replaced by the new Microsoft Edge. This issue is only encountered when custom offline media or ISO images are created by slipstreaming this update into the image without having first installed the standalone servicing stack update (SSU) released March 29, 2021 or later. Note: Devices that connect directly to Windows Update to receive updates are not affected. This includes devices using Windows Update for Business. Any device connecting to Windows Update should always receive the latest versions of the SSU and latest cumulative update (LCU) without any extra steps. To avoid this issue, be sure to first slipstream the SSU released March 29, 2021 or later into the custom offline media or ISO image before slipstreaming the LCU. To do this with the combined SSU and LCU packages now used for Windows 10, version 20H2 and Windows 10, version 2004, you will need to extract the SSU from the combined package. Use the following steps to extract the using SSU: Extract the cab from the msu via this command line (using the package for KB5000842 as an example): expand Windows10.0-KB5000842-x64.msu /f:Windows10.0-KB5000842-x64.cab Extract the SSU from the previously extracted cab via this command line: expand Windows10.0-KB5000842-x64.cab /f:* You will then have the SSU cab, in this example named SSU-19041.903-x64.cab. Slipstream this file into your offline image first, then the LCU. The update is applicable to all editions of Windows 10 version 1903 and newer. To download the update you can visit Microsoft Update Catalog and search for the update version, or you can simply download it from here. You can find more information on the update on Microsoft's official support page here. Microsoft releases out of band KB5004760 Windows 10 update fixing problems with PDF
  14. Microsoft fixes high-pitched noise bug in Windows 10 Microsoft has fixed a known issue causing applications to play high-pitched or squeaking noises while using certain apps in Windows 10 2004, Windows 10 20H2, and Windows 10 21H1. This issue was first introduced in the March 2021 KB5000842 preview cumulative update but continued through cumulative updates released afterward. Microsoft states that the issue only affected some Windows 10 users using 5.1 and only affected certain apps. "After installing KB5000842 or later updates, 5.1 Dolby Digital audio may play containing a high-pitched noise or squeak in certain apps when using certain audio devices and Windows settings," explains Microsoft on their Windows 10 Known issues and notifications center. For Windows 10 users with stereo audio configuration, the issue does not occur. This week, Microsoft released the Windows 10 KB5003690 preview cumulative update, which now fixes this audio bug for affected users. Windows 10 KB5003690 update As the KB5003690 update is an optional update, Windows 10 users will only receive the fix if they manually perform a 'Check for updates' in Windows Update and install the update. Those who do not wish to install the preview update can wait until the mandatory July 2021 Patch Tuesday updates to receive the fix. Last month, Microsoft also removed the final compatibility holds preventing customers from upgrading to Windows 10 2004, 20H2, and 21H1. This hold was related to Conexant and Synaptics audio driver issues that caused issues installing Windows 10 updates. Microsoft fixes high-pitched noise bug in Windows 10
  15. Microsoft pushes emergency update for Windows 10 Xbox Game Pass bug Microsoft has released the KB5004476 emergency out-of-band update for Windows 10 that fixes problems installing or playing an Xbox Game Pass game. Since 2019, some Windows 10 users have been having issues [1, 2, 3, 4] installing or playing Xbox Game Pass games. When attempting to do so, users would be prompted to install the 'Gaming Services' app from the Microsoft Store, which would fail with a 0x80073D26 or 0x8007139F error, as shown below. Receiving a 0x80073D26 error when installing Game Services Microsoft released a manual fix yesterday to explain how to fix the problem by manually removing the Windows services for the Game Services app. However, it is never advisable to recommend people manually remove Registry entries as a mistake could cause Windows to become unusable. Out-of-band Windows 10 update released To make it easier to fix this Xbox Game Pass issue, Microsoft has released the KB5004476 emergency update to fix the bug without having users manually delete Registry keys. "Updates an issue that might redirect you to the Microsoft Store page for Gaming Services when you try to install or start an Xbox Game Pass game on your Windows 10 device," explains the KB5004476 support bulletin. Microsoft states that this bug only affects users running Windows 10 2004, Windows 10 20H1, Windows 10 20H2, and Windows 10 21H1. To install the update, you must open Windows Update and perform a manual 'Check for update.' Windows Update will then offer KB5004476 as an optional update. Windows 10 KB5004476 optional update Before installing the KB5004476 OOB update, Windows users must first install the May 11th, 2021 KB5003173 cumulative update or later. Microsoft pushes emergency update for Windows 10 Xbox Game Pass bug
  16. Microsoft fixes issue blocking Microsoft Teams, Outlook logins Microsoft has fixed a known issue causing Microsoft 365 to experience authentication issues when logging into desktop client apps like Microsoft Teams, OneDrive for Business, and Microsoft Outlook. When attempting to sign in, users are shown a message saying, "We ran into a problem. Reconnecting…" and asking them to restart the application. This same screen will also display 80080300 error codes at the bottom left of the window and suggesting reaching out to an IT admin if the login problems persist. This known issue is caused by the Windows 10 1909 KB5003169 cumulative update released last month as part of the May 2021 Patch Tuesday updates. Microsoft suggested a temporary workaround that would allow impacted customers to sign into the impacted Microsoft 365 apps. "To mitigate this issue on most devices, you can restart your device a second time," the company said. "Most devices will sign into affected apps as expected for all subsequent restarts after the first restart that completes installation of the update." If restarting the affected systems doesn't allow logins, customers are also advised to use the web versions of Microsoft Teams, OneDrive for Business, and Outlook. Microsoft Teams 80080300 error (BleepingComputer) Fix issued with June Patch Tuesday updates While Microsoft initially suggested a workaround to bypass this known issue on affected devices, the company has now resolved the known issue in the KB5003635 Windows 10 1909 cumulative update. Microsoft says that KB5003635 "addresses an issue that might prevent you from signing in to some Microsoft 365 desktop client apps after installing the May 11, 2021 or later update and restarting your device." The KB5003635 will be automatically installed via Windows Update, Windows Update for Business, or Windows Server Update Services (WSUS). If configured policies on your system prevent the update from being downloaded and installed automatically, you can also get the standalone package from the Microsoft Update Catalog and do it manually. Microsoft also recently shared a workaround for customers experiencing 0x8004de40 errors when attempting to log ino their OneDrive accounts. Customers are also seeing 0x80049d61 errors when trying to launch the OneDrive Store app. Until a fix is available, users are advised to use the OneDrive desktop app or go to Onedrive.com. Microsoft fixes issue blocking Microsoft Teams, Outlook logins
  17. macOS 11.4 apparently fixes reported issue with SSD wear in M1 Macs Version 11.4 update seemingly solves gremlins in the SSD works A problem where the SSDs of Apple Macs running M1 chips were supposedly being hit with excessive wear – or at least apparent misreported excessive wear – has been fixed, according to a new report. You may recall the original story about SSD wear which appeared back in February, observing that the issue was only a serious problem for a very small number of Mac owners – but nonetheless, it obviously prompted some concern. Apple was never drawn to comment on the purported SSD gremlins in the works here, but AppleInsider now reports that the problem is seemingly cured in the new macOS 11.4 update (which emerged late in May) – while noting that a source within Apple told them off the record that this bug was actually a data reporting error in the software measuring SSD usage (a possibly raised back at the time). In other words, the observed (in some rare cases) alarming wear-and-tear wasn’t actually happening to the drive physically (rather, it was just being misreported as happening). That inside Apple source informed the tech site that the macOS 11.4 update has solved the problem, and AppleInsider confirmed that the operating system is now reporting ‘proper uptime statistics’ where it wasn’t before. Thrash no more One of the denizens of Twitter who flagged up the problem initially, developer Hector Martin, also separately stated (just before the release of macOS 11.4) that: “Update on the macOS SSD thrashing issue: It seems the issue is fixed in 11.4.” Martin, however, maintains in that Twitter thread that this was an actual problem causing drive wear as opposed to a misreporting issue as indicated by AppleInsider and its source. At any rate, the issue appears to have been remedied with macOS 11.4, so should now be a thing of the past once that update is applied. That 11.4 update also applies a bunch of security fixes, and cures some bugs including problems with Safari. Via Tom’s Hardware macOS 11.4 apparently fixes reported issue with SSD wear in M1 Macs
  18. Microsoft fixes Windows 10 chkdsk issue that corrupted disks and caused blue screens Microsoft released the usual set of Patch Tuesday updates to supported Windows versions earlier this month. While the updates brought the usual bug fixes, improvements, and security patches, there were also known issues documented in the KB articles. However, one of the issues that wasn’t documented, which users began reporting (spotted by the Planet3DNow and Borncity), was that of a problem with the chkdsk error-checking utility. The bug – supposedly introduced with KB4592438 – affects Windows 10 versions 2004 and 20H2, and causes the chkdsk /f command to affect file systems adversely, resulting in blue screens (BSOD) and corruption of the file system in the worst case. The issue seemingly affects SSDs and can be reproduced even when run on a virtual machine (VM). Microsoft has now acknowledged the issue, documented a workaround, and has begun rolling out a fix. The Redmond firm has updated the list of known issues for KB4592438 and KB4586853 with a workaround for the error for those devices that are able to start up. Here are the steps that are to be performed: The device should automatically start up into the Recovery Console after failing to start up a few times. Select Advanced options. Select Command Prompt from the list of actions. Once Command Prompt opens, type: chkdsk /f Allow chkdsk to complete the scan, this can take a little while. Once it has completed, type: exit The device should now start up as expected. If it restarts into Recovery Console, select Exit and continue to Windows 10. The company adds that devices might run chkdsk after a restart once the steps are completed. As for the fix that prevents the error, it is currently being rolled out to "non-manged devices" - meaning consumers - and should propagate to all devices in the next 24 hours. It is not clear if the change is a server-side one, as there is no new KB article added to the update history. Enterprise-managed devices, however, can resolve the issue by installing and configuring a special Group Policy, which the company has provided here. Source: Microsoft (1)(2) via BleepingComputer Microsoft fixes Windows 10 chkdsk issue that corrupted disks and caused blue screens
  19. New Cyberpunk 2077 patch fixes frustrating Takemura quest bugs CD Projekt Red releases update fixing item and quest bugs. (Image credit: CD Projekt) CD Projekt Red has released an update to fix frustrating item and quest-related bugs in Cyberpunk 2077. The developer says the Hotfix 1.11 patch — available now on PC, consoles and Stadia — will address issues that arose after Patch 1.1, including the restoration of item randomization and a frustrating bug that halts progress in the Down on the Street sidequest. During the mission, players had been encountering bugs at the "Wait For Takemura's call" objective if playing on a save made in version 1.06 of the game. After loading the same save on version 1.1, the holocall would lack dialogue options and block interactions with other NPCs, leaving players unable to progress through the sidequest. CD Projekt Red now says the issue has been patched, and also added that the save/load loot exploit — which allowed players to generate unlimited eurodollars pre-update — will be “investigated further.” Slowly improving After the shakiest of shaky starts, which saw CD Projekt Red refund players who bought the game but were left unhappy with its crippling bugs, Cyberpunk 2077 is on the up. The game received a significant patch in December 2020, containing major fixes to crashes and ‘multiple stability improvements’, with the developer committing itself to repairing quest-breaking bugs which prevented players from progressing through the game. This latest update comes as proof that CD Projekt Red is engaging with Cyberpunk’s still-strong player-base and quickly responding to issues arising from glitches and previous updates. But does the sudden attention to detail mean too little too late for some? Steam recently reported that the futuristic RPG had lost 75% of its players post-launch, with many seemingly unwilling to return to a game that induced fury around the world for its lack of polish and playability. In any case, for those players still roaming the admittedly-remarkable streets of Night City, CD Projekt Red’s latest update will come as a welcome reminder that they haven’t been abandoned. New Cyberpunk 2077 patch fixes frustrating Takemura quest bugs
  20. Microsoft has a fix for Windows 10's Password Saving issue Shortly after the release of Windows 10 version 2004 in April 2020, some users reported issues getting passwords to save in web browsers such as Google Chrome or Microsoft Edge, and also in other applications such as OneDrive or Outlook. Microsoft acknowledged the issue in June 2020 and published a support page on its official support site. Microsoft is actively investigating on this topic; our metrics for OSCrypt.Win.KeyDecryptionError do not show a huge or significantly growing number of hits, but it's big enough that we're looking at it. It would be interesting to see whether Chrome's data for that metric shows movement over time. The support page informs users that the issue is caused by certain Windows 10 Task Scheduler tasks such as HP Customer participation utility task, and that it affects devices running Windows 10 Version 2004 Build 19041.173 or later. Microsoft's workaround suggests to run a Powershell command to list tasks that affect the password saving functionality on the operating system. Start an elevated Windows PowerShell prompt. Run the command Get-ScheduledTask | foreach { If (([xml](Export-ScheduledTask -TaskName $_.TaskName -TaskPath $_.TaskPath)).GetElementsByTagName("LogonType").'#text' -eq "S4U") { $_.TaskName } } Note tasks listed by the command. Open the Windows Task Scheduler. Locate the tasks listed by the PowerShell command, right-click on each and select disable. Restart Windows. Microsoft Edge Program Manager Eric Lawrence confirmed on December 18, 2020 that Microsoft has found a permanent fix for the issue. The company has integrated the fix in the latest Windows 10 Insider Build and plans to include it in an upcoming update for all Windows 10 users. The exact release date is unclear; the most likely scenario will see a release as part of a coming cumulative update. The next cumulative updates will be released on January 12, 2021, February 9, 2021 and March 9, 2021 respectively. Lawrence notes that a "comparatively small number of users with S4U tasks" is affected by the issue. Microsoft has a fix for Windows 10's Password Saving issue
  21. Google Chrome fixes antivirus 'file locking' bug on Windows 10 Google Chrome has fixed a bug that enabled antivirus programs on Windows 10 to lock newly created files. The patching of the bug means antivirus programs running on Windows would no longer block new files generated by the Chrome web browser, such as bookmarks. Antivirus programs briefly lock new files As a safety precaution, oftentimes antivirus programs temporarily lock newly generated files on a system until these can be scanned and ruled out for malicious activity. On Windows 10 machines, in particular, this created issues for the Google Chrome web browser when it would use `ImportantFileWriter` to output certain files. "Anti-virus programs and other scanners may briefly lock new files which can lead to frequent problems with saving bookmarks and other files that use the ImportantFileWriter," explained Bruce Dawson, a Google engineer. This meant Windows 10 users would experience issues trying to save bookmarks, for example, due to the web browser having difficulty creating the corresponding file. As first reported by Windows Latest this week, a recent enhancement made by the Chromium project lets the Chrome web browser run smoothly on Windows 10, even when antivirus tools are enabled. Fix attempts file creation multiple times The fix published to Chromium's Google Source codebase resolves this bug by retrying the execution of ReplaceFile method multiple times to overcome the possible race condition in which an antivirus program takes control of (and locks) a file being simultaneously accessed by Chrome. The code change also has a machine learning aspect to it which means, over time Chromium will teach itself to fine-tune the number of attempts needed to bypass such race conditions. Fix made by Chromium for Windows OS versions to retry new file creations multiple times Source: Chromium Gerrit "This change also adds instrumentation to record how many retries are needed, for future tuning," stated Dawson. The engineer also states this bug only impacts Windows systems which is why the fix made into important_file_writer.cc was specific to Windows OS, as shown in the screenshot above (line 45). Since the fix has been merged into the repository as of December 30, 2020, it is expected the next version of Google Chrome will come shipped with it. Chrome users should keep an eye out for any upcoming releases and ensure they update their web browsers promptly. Google Chrome fixes antivirus 'file locking' bug on Windows 10
  22. Windows 10 gets a fix for annoying stuttering in some games Patch KB4601382 is a preview update, though, with the usual caveats (Image credit: Shutterstock; Future) Windows 10 has received a preview version of a cumulative update, and it’s one that gamers might want to apply if they’ve been having any kind of trouble with stuttering or flickering (or indeed other rendering issues) when playing certain games. As Microsoft states, patch KB4601382 (for Windows 10 May 2020 Update and October 2020 Update) applies the following fix: “Updates an issue with screen rendering after opening games with certain hardware configurations.” As it’s in preview, you’ll have to manually find and install this bunch of fixes via Windows Update (this patch will be next month’s cumulative update when it lands on March 9 – but folks who are exasperated with the bugs that it cures may just want to grab it now to save them from another week of pulling their hair out). As mentioned, as well as the problems with games, there are other fixes here. These include several display-related bugbears like an “issue that might cause video playback to flicker when rendering on certain low-latency capable monitors”, and incorrect refresh rates showing under advanced display settings when it comes to HDR-capable monitors. KB4601382 also delivers a solution for unexpected screens popping up in the Windows 10 setup experience (initial out of box installation process, that is). Caution first If you’re not affected by any of these issues, or at least not bothered by them to any pressing degree, it’s best to steer clear of a preview update – because as the name suggests, these are still in testing, so may be rough around the edges or have unintended consequences in one form or another. Strictly speaking, it’s best to wait for the finalized patch (indeed, as we’ve seen many times in the past, even the finished version can mistakenly introduce fresh bugs – so preview updates need to be treated with some caution). Via Windows Latest Windows 10 gets a fix for annoying stuttering in some games
  23. Microsoft fixes Windows Defender flaw which would execute instead of deleting malware Microsoft has fixed a flaw in Windows Defender which was being actively exploited in the wild. The Microsoft Defender Remote Code Execution Vulnerability (CVE-2021-1647) would see Windows Defender turn into the attacker, triggering the execution of malware when the malware was scanned, instead of quarantining and deleting it. This means a file could be sent by email or USB drive, and when downloaded and automatically scanned be immediately triggered. The exploit was fixed as part of Patch Tuesday on the 12th and was one of 80 flaws which were addressed. To check if you are protected, checked the version number of the scan engine in the Windows Security app by searching for Windows Security in the start menu, opening the app, and going to Settings and About. Version 1.1.17700.4 and above are not vulnerable to the exploit. via GrahamCluley Microsoft fixes Windows Defender flaw which would execute instead of deleting malware
  • Create New...