Jump to content

Search the Community

Showing results for tags 'bugfix'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • 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

Categories

  • 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

Categories

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

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

  1. Microsoft released new Windows 11 Insider builds this week. The Beta channel build added new OneDrive alerts, fixed high CPU usage, among others. Meanwhile, the Dev channel build 25252 was feature-rich with new stuff including a VPN status, new Taskbar search styles, and more. Alongside the new features, the Dev build 25252 also fixes a major bug in Windows 11 22H2 which was causing a noticeable slowdown when copying large files remotely. This is good news as quite a few were complaining and getting exasperated about this longstanding bug. The release note describing this fix says: Fixed an issue where network-to-local copying (for example, when copying a file from a network share) was slower than expected from some users. Although the issue was first suspected to be related to the Server Message Block (SMB) protocol, Ned Pyle, the Principal Program Manager in the Microsoft Windows Server High Availability and Storage group, confirmed later that it was a problem somewhere in the kernel and had "nothing to do with SMB or compression". Hence local file copy speeds were also being affected. Moreover, some users also reported a far worse performance hit than initially thought. Pyle says the fix should be out later as a cumulative update for all users and once again reiterated that the issue was not related to SMB. They say: The permanent production fix will come in a normal monthly cumulative update after this is validated. As I've mentioned before, the fix is not in SMB, and since it's not a component I own, I don't have further details on timing. The file copy issue isn't the only thing Microsoft has fixed recently. The company also resolved the bug(s) which were causing gaming performance degradation in Windows 11 2022 update. Microsoft finally fixes Windows 11 22H2 file copy kernel bug but you may not get it
  2. For those that follow Windows news pretty regularly, you are probably aware of the PrintNightmare saga. In a nutshell, it was a security vulnerability in the Windows print spooler service. This service handles print jobs and related protocols on servers and client PCs. And outside of PrintNightmare too, there have been several printing-related issues that have bugged Windows 11, as well as Windows 10, and version 22H2 has been no exception. We reported on one such problem towards the end of September where adding printers after an update to the 2022 update (version 22H2) had become a hassle for IT admins and engineers. A day later, Microsoft also documented another printer bug where the printer settings stuck on default. Consequently, the company forced a compatibility safeguard and blocked the 22H2 feature update. The company has since resolved the problem and has provided an updated timeline for the issue: October 7, 2022: This safeguard hold has been updated to only safeguard Windows devices with printers using Microsoft IPP Class Driver or Universal Print Class Driver which currently only allow default settings. Please note, if there are no other safeguards that affect your device, it can take up to 48 hours before the upgrade to Windows 11 is offered. Restarting your device and checking for updates might help it to offer sooner. October 21, 2022: A troubleshooter has been released which will automatically download and resolve this issue on affected devices running Windows 11, version 22H2. Once the issue with the installed printer is resolved, the safeguard should be removed and you should be able to upgrade to Windows 11, version 22H2. Please note, if there are no other safeguards that affect your device, it can take up to 48 hours before the upgrade to Windows 11 is offered. Restarting your device and checking for updates might help the troubleshooter apply sooner. November 10, 2022: Any printer still affected by this issue should now get resolved automatically during upgrade to Windows 11, version 22H2. Aside from these, other printer-related problems have also come up since, which include printing fails with domain user authentications, though to the credit of Microsoft, it also did manage to fix a printer bug on Windows 10 recently. Microsoft finally lets you upgrade to Windows 11 22H2 after fixing a major printer bug
  3. Microsoft has released emergency out-of-band (OOB) update KB5020953 today to fix the OneDrive crash issue the company recently informed about. Microsoft laid out multiple scenarios under which OneDrive was crashing or closing unexpectedly. This was the second major bug to hit after the October Patch Tuesday released earlier in the month, The first one produced massive network related issues as it was the outcome of TLS/SSL handshake failures. With this OOB update KB5020953, the build numbers have been bumped to 19042.2194, 19043.2194, and 19044.2194. The update is available for Windows 10 versions 20H2, 21H1, 21H2, and 22H2 for both Arm and x86/64. Microsoft has not disclosed exactly how it solved the issue. The changelog for the update only states the following: It addresses an issue that causes Microsoft OneDrive to stop working. This occurs after you unlink your device, stop syncing, or sign out of your account. Since this is an out-of-band release, the update is not available via Windows Update inside Settings. Instead, it must be manually downloaded from the Microsoft Update Catalog website. You can find the update here. Microsoft releases emergency OOB update KB5020953 to fix OneDrive crashing on Windows
  4. AMD today has launched its new graphics driver with version 22.10.3. The new driver fixes a black screen issue on Radeon GPUs, something which AMD cards are pretty notorious for. The bug has been fixed on Windows 11 version 22H2, mainly on the latest gen Radeon RX 6000 Navi (RDNA 2) GPUs. Aside from the major bug fix, the driver also adds support for Call of Duty Modern Warfare II, and introduces Radeon Boost support on Dying Light 2. The full changelog for the driver is given below: Highlights Support for: Call of Duty®: Modern Warfare® II Radeon™ Boost using Variable Rate Shading in Dying Light 2™ Fixed Issues Elite Dangerous may crash upon launch on Radeon™ RX 6000 series GPUs. Black screen may occur during driver upgrade or settings reset using Microsoft® Windows® 11 version 22H2 on Radeon™ RX 6000 series GPUs. Lower than expected performance on Gotham Knights™ using AMD Processors on some AMD Graphics Products such as Radeon™ RX 6950 XT. Known Issues World Of Warships prediction lines may be missing on Radeon™ RX 6000 series GPUs. [Resolution targeted for 22.11.1] When Radeon™ Anti-Lag is enabled, a beep can be heard when pressing shift + back key. [Resolution targeted for 22.11.1] GPU utilization may be stuck at 100% in Radeon performance metrics after closing games on some AMD Graphics Products such as Radeon™ 570. Stuttering may occur during video playback using hardware acceleration with Firefox on some AMD Graphics Products such as the Radeon™ RX 6900 XT Graphics. Brief display corruption may occur when switching between video and game windows on some AMD Graphics Products such as the Radeon™ RX 6700 XT. The open issues lists a 100% usage bug in the case of Radeon cards, and something similar is also currently plaguing Nvidia GeForce cards too. To download the new AMD driver, head over to the official release notes page on AMD's official site. Since the new 22.10.3 driver is an optional beta update, you'll have to toggle the "Recommended + Optional" choice in case you want to download the driver using the Radeon software. AMD fixes infamous black screen issue on Windows 11 22H2 with latest driver
  5. Hot on the heels of Firefox 106 Stable comes the first point release update for the browser. Firefox 106.0.1 addresses a crash on systems with certain AMD processors. Mozilla released Firefox 106 Stable and Firefox 102.4 ESR just two days ago on October 18, 2022. Firefox 106 included the browser's new Firefox View feature, which improves cross-device use of the browser by highlighting recent tabs open in other instances of Firefox. Other improvements include basic PDF editing capabilities, limiting to drawing on PDF documents and using text write options, useful for form filling. Firefox 106.0.1 Firefox 106.0.1 Stable will be released later today, if you are reading this on October 20, 2022. The new release of the browser addresses a crash issue on AMD Zen 1 devices. The operating systems affected by the bug are not specified, but Windows 10 is among them. Mozilla fixed the crash issue in record time. It was reported on Mozilla's bug tracking site yesterday (20 hours ago at the time of writing), and fixed nine hours later. Mozilla states that Firefox 102.x ESR is not affected by the issue, and that Firefox 106 is the only affected version of the Firefox browser. The bug report includes a technical analysis of the issue and references to other bugs related to it. Firefox 106 installations should receive the update automatically once it is released. Firefox users may download the update from Mozilla's website as well to install it manually. The crash bug should not affect the starting of the Firefox web browser or the automatic update behavior. Firefox users may check the installed version of the web browser by selecting Menu > Help > About Firefox from its main interface. Firefox displays the installed version and runs a check for updates. Any update that the browser finds during the check is downloaded and installed automatically. Now You: when was the last time you experienced a crash in a browser that you are using? Firefox 106.0.1 fixes a crash on certain AMD systems Frontpaged: Mozilla Firefox Browser 106.0.1
  6. Microsoft has released an out-of-band (OOB) update KB5020387 (Build 22000.1100) to fix the Transport Layer Security (TLS)/ Secure Sockets Layer (SSL) handshake failure issue that users are reporting. The bug is leading to failure of connection establishment between clients and servers. These were set off by this month's Patch Tuesday for both Windows 11 and Windows 10. Here is the changelog for the new KB5020387 OOB update that fixes the TLS/SSL handshake issue on Windows 11 21H2: Highlights We address an issue that might affect some types of Secure Sockets Layer (SSL) and Transport Layer Security (TLS) connections. These connections might have handshake failures. For developers, the affected connections are likely to receive one or more records followed by a partial record with a size of less than 5 bytes within a single input buffer. If the connection fails, your app will receive the error, “SEC_E_ILLEGAL_MESSAGE”. Improvements This non-security update includes quality improvements. Key changes include: We address an issue that might affect some types of Secure Sockets Layer (SSL) and Transport Layer Security (TLS) connections. These connections might have handshake failures. For developers, the affected connections are likely to receive one or more records followed by a partial record with a size of less than 5 bytes within a single input buffer. If the connection fails, your app will receive the error, “SEC_E_ILLEGAL_MESSAGE”. To download this update, apply any available Windows update or head over to the Microsoft Update Catalog website. Microsoft outs Windows 11 OOB update (KB5020387) to fix TLS/SLS network issues
  7. Microsoft has released a new update (KB5020435) to Windows 10 machines to address an issue with Secure Sockets Layer (SSL) and Transport Layer Security (TLS) connections. The highlights in this update are the same for Windows 10 20H2, 21H1, and 21H2, they read as follows: Highlights We address an issue that might affect some types of Secure Sockets Layer (SSL) and Transport Layer Security (TLS) connections. These connections might have handshake failures. For developers, the affected connections are likely to receive one or more records followed by a partial record with a size of less than 5 bytes within a single input buffer. If the connection fails, your app will receive the error, “SEC_E_ILLEGAL_MESSAGE”. There are also two known issues with workarounds, they are as follows: Symptoms Symptoms 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 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. If you have already encountered this issue by installing the OS using affected custom media, you can mitigate it by directly installing the new Microsoft Edge. If you need to broadly deploy the new Microsoft Edge for business, see Download and deploy Microsoft Edge for business. After installing this update, some Windows devices might have issues with audio not working. Some affected Windows devices might have no audio, but other affected Windows devices might only have issues on certain ports, certain audio devices or only within certain applications. Most affected audio devices drivers have the "audio enhancements" setting disabled before installing this update or the sound device driver has issues with the "audio enhancements" feature. This issue can be mitigated differently depending on your symptoms and if you have installed the update already. Please see the known issue on Windows release health for instructions to prevent and mitigate this issue. This issue is addressed using a Known Issue Rollback (KIR). This KIR will prevent the issue on Windows devices that have not installed KB5015878, but will have no effect on devices already affected by this known issue. Please note that it might take up to 24 hours for the KIR to propagate automatically to consumer devices and non-managed business devices. Restarting your Windows device might help the KIR apply to your device faster. For enterprise-managed devices that have installed an affected update and encountered this issue, you can address it by installing and configuring a special Group Policy. The special Group Policy can be found in Computer Configuration > Administrative Templates> . For information about deploying and configuring these special Group Policy, see How to use Group Policy to deploy a Known Issue Rollback. Group Policy downloads with Group Policy name: Download for Windows 10, version 21H2, Windows 10, version 21H2, Windows 10, version 20H2 - KB5015878 220706_045043 Known Issue Rollback Important You must install and configure the Group Policy for your version of Windows to resolve this issue. Applying available updates through Windows Update should keep you protected against this issue. If you have an offline computer running Windows 10, you can download the standalone package containing this update from the Microsoft Update Catalog too. Microsoft issues out-of-band update (KB5020435) to Windows 10 to fix connection issues
  8. Back in August, Microsoft published a support document regarding an issue that was causing Outlook to crash or to become unresponsive on startup. After investigating, the company found out that the issue occurred when the EmailAddress string data value under the Office identity was kept blank. Hence, the company devised a potential workaround using the same method to manually input the value to bypass the issue. Additionally, if also recommended disabling support diagnostics in Outlook using a registry edit. Microsoft also recommended the age-old trick of signing out and signing back in to re-populate the entries automatically. Recently, Microsoft came back to the bug and confirmed the issue has now been fixed. The crashfix is available in the current channel version 2209 (Build 15629.20156) and semi-annual enterprise channel (Preview) version 2208 (Build 15601.20158). Microsoft writes: ISSUE When you start Outlook Desktop, it gets past loading profile and processing, briefly opens, and then stops responding. STATUS: FIXED This issue is fixed in Current Channel Version 2209 (Build 15629.20156) and Semi-Annual Enterprise Channel (Preview) Version 2208 (Build 15601.20158). As these builds get to the other channels the fixes will follow. You can find the official support document here. Microsoft finally fixes email bug that was causing Outlook to crash at startup
  9. Last month, we reported that several Windows customers are experiencing issues due to a Daylight Saving Time (DST) bug. Chilean users were primarily affected because in August, the Chilean government announced that it is advancing clocks by one hour in the country starting from September 4 instead of September 10, along with other timezone updates. This led to issues related to incorrect times in Outlook, Calendar, third-party apps, logs, Kerberos authentication, and more. In fact, Microsoft noted that even users outside of Chile could be affected if they are connecting to servers in the country. At the time, the Redmond tech firm issued some workarounds, but it has now rolled out an official fix. For now, the patch is available as a cumulative preview update in the form of KB5017380. This update was initially rolled out to Insiders only but has now been made available to non-Insiders as an optional update too. It is important to note that since this is an optional update available as a preview, you won't get it automatically. In fact, you'll have to go through the "seeker" experience of manually checking for updates in Windows Update. Microsoft says that the update will fix this DST issue and more (see the complete changelog here) on the following SKUs of Windows: Windows 10, version 1809 Windows 10, version 20H2 Windows 10, version 21H1 Windows 10, version 21H2 Windows 10, version 22H2 Windows Server 2022 Windows 11 Those who want to wait for the update to become generally available will have to do so until next month's Patch Tuesday, which falls on October 11 this time around. Microsoft fixes Daylight Saving Time bug in optional update, general patch coming next month
  10. Windows 11 has a built-in speech recognition service that allows users to input text using their voice. For some reason, customers have been lately experiencing various issues with voice typing in Microsoft's latest operating system. Upon clicking Win + H (a dedicated key for launching voice typing), Windows 11 was showing a "Something went wrong" message, preventing customers from entering text using their voice. It did not take too long for Microsoft to acknowledge and fix the problem. The company has posted a new message on the Windows Health Dashboard website, revealing that a server-side change has solved the issue. All affected customers now should be able to access voice typing in Windows 11 using the Win + H shortcut or other methods. Microsoft says the affected platforms include only the client version of Windows 11 21H2, and the bugfix does not require any action from users. Windows 11 still has some known bugs waiting for fixes from Microsoft. The operating system cannot open XPS documents with non-English characters, and there is an issue causing computers to boot into BitLocker recovery after installing a Secure Boot DBX update. Microsoft issues fix for broken voice input in Windows 11
  11. Microsoft says a Windows 11 update released in late August is blocking customers from signing in with newly added Microsoft Account users after restarting or logging off systems running Windows 11, version 21H2. "After installing KB5016691 and adding a new Microsoft account user in Windows, you might be unable to sign in for a brief time after the first restart or sign out. The issue only affects the newly added Microsoft account user and only for the first sign in," Microsoft explained. "This issue only affects devices after adding a Microsoft account. It does not affect Active Directory domain users accounts or Azure Active Directory accounts." Microsoft says it addressed this issue via Known Issue Rollback (KIR), a Windows capability designed to revert buggy Windows non-security fixes pushed through Windows Update. Once rolled out, KIR-issued fixes usually reach all consumer and non-managed business devices within a day. Affected users can also get the fix after restarting any impacted Windows devices. As a workaround, those experiencing this issue can wait for the lock screen to appear again, as it will resolve itself after some time, allowing users to log in as expected. Group policies available for enterprise As an IT admin, you must install and configure a KIR Group Policy to resolve this known issue on affected enterprise-managed devices. "The special Group Policy can be found in Computer Configuration -> Administrative Templates -> KB5016691 220722_051525 Known Issue Rollback -> Windows 11 (original release)," Microsoft added. You can download this Rollback Group Policy for Windows 11, version 21H2, from here. To deploy the Known Issue Rollback via Group Policy, you have to go to the Local Computer Policy or the Domain policy on your domain controller using the Group Policy Editor to choose the Windows version you need to target. Detailed information on how to deploy and configure KIR Group Policies can be found on Microsoft's support website. In July, Microsoft issued another emergency fix via Known Issue Rollback (KIR) to address an issue causing the Windows 11 start menu to malfunction after installing recent updates. Microsoft rolls out emergency fix for blocked Windows logins
  12. Microsoft has released a fresh cumulative non-security update for users sticking to one of the older Windows 10 versions. KB5016690 (build number 17763.3346) is now available for download on systems running Windows 10 2019 LTSC and Server 2019. Home and Pro users will not receive this update because Microsoft stopped supporting Windows 10 version 1809 in May 2021. The main highlight of KB5016690 is a fix for the bug causing an 0x1E error when users try to shut down or restart their systems. Here is the rest of the changelog containing more technical improvements and fixes: New! Enhances Microsoft Defender for Endpoint’s ability to identify and intercept ransomware and advanced attacks. Addresses an issue that causes ServerAssignedConfigurations to be null in a few full configuration scenarios. Addresses an issue that might generate error 0x1E when you shut down or restart a device. Addresses an issue that prevents virtualized App-V Microsoft Office applications from opening or causes them to stop working. Addresses an issue that leads to a false negative when you run scripts while Windows Defender Application Control (WDAC) is turned on. This might cause AppLocker events 8029, 8028, or 8037 to appear in the log when they should not. Addresses an issue that causes the Resultant Set of Policy tool (Rsop.msc) to stop working when it processes 1,000 or more “File System” security settings. Addresses an issue that causes the Settings app to stop working on server domain controllers (DCs) when accessing the Privacy > Activity history page. Addresses a race condition that causes the Local Security Authority Subsystem Service (LSASS) to stop working on Active Directory domain controllers. This issue occurs when LSASS processes simultaneous Lightweight Directory Access Protocol (LDAP) over Transport Layer Security (TLS) requests that fail to decrypt. The exception code is 0xc0000409 (STATUS_STACK_BUFFER_OVERRUN). Addresses an issue that affects a lookup for a nonexistent security ID (SID) from the local domain using read-only domain controller (RODC). The lookup unexpectedly returns the STATUS_TRUSTED_DOMAIN_FAILURE error instead of STATUS_NONE_MAPPED or STATUS_SOME_MAPPED. Addresses an issue that prevents a private virtual LAN (PVLAN) from providing tenant and virtual machine (VM) isolation. Addresses an issue that delays a client’s acquisition of the Internet Protocol version 6 (IPv6) address for extended periods in an IPv6 environment. Addresses an issue that might cause Remote Desktop Session licensing to display a 60-minute disconnection warning after reconnecting. Addresses an issue that causes a RODC to unexpectedly restart. In the event log, you’ll find the following: Event 1074 with the message, “The system process 'C:\Windows\system32\lsass.exe' terminated unexpectedly with status code -1073740286. The system will now shut down and restart.” Event 1015 with the message, “A critical system process, C:\Windows\system32\lsass.exe, failed with status code c0000602. The machine must now be restarted.” Event 1000 with the message, “Faulting application name: lsass.exe, Faulting module name: ESENT.dll, Exception code: 0xc0000602.” Addresses an issue that might cause cldflt.sys to reference invalid memory in race conditions. Users can download KB5016690 from Windows Update (in the optional updates section) or the Microsoft Update Catalog. It is worth noting that Windows 10 2019 LTSC Editions and Server 2019 will soon stop receiving non-security optional updates (C-releases). Starting September 20, 2022, only cumulative security updates (B-releases) or "Patch Tuesday" will be available. Microsoft fixes bug causing 0x1E error when shutting down Windows 10
  13. According to the latest update from Microsoft on the official Windows Health Dashboard website, KB5015878 causes all sorts of audio problems on systems running Windows 10. The company has officially acknowledged the problem, shared workarounds for the affected customers, and applied the Known Issue Rollback System (KIR) to prevent the bug from spreading. The software giant says the newest known bug in Windows 10 affects computers differently. Some users experience a complete audio blackout, while others only have audio on specific ports, devices, or applications. Microsoft's findings reveal that the affected audio drivers have the "audio enhancements" setting disabled before installing KB5015878, or the sound device driver has issues with the "audio enhancements" feature. To prevent the problem from spreading, Microsoft applied the Known Issue Rollback system that can undo problematic changes without any action required from the end user. Interestingly, this time, KIR only ensures the bug will not affect other systems. Those who already have audio issues on Windows 10 after installing KB5015878 should apply one of three workarounds described below: If you have not yet installed the update, you can do the following to prevent the issue: Updating your audio device driver (also called "sound drivers" or "sound card drivers") might prevent this issue. If there are updated drivers available on Windows Update or from your Windows device manufacturer's (OEM) webpage, installing them might prevent this issue. If you are using any advanced audio applications such as Open Broadcaster Software (OBS), it is recommended that you backup all your settings before installing the update. If only certain apps are impacted, you can try the following to mitigate the issue: Verify that the audio devices set within those apps are the expected devices. Audio endpoints might be reinitialized after KB5015878 is installed and some apps might set the audio devices for microphone and speakers to default. If the device settings within the app are as expected, the apps might be caching the Windows Multimedia Device (MMDevice) ID. Caching the MMDevice ID is not recommended and might require reinstallation of the affected app or contacting support for the developer of the app for how to resolve the issue when audio endpoints are reinitialized and have new MMDevice IDs. If you have already installed the update and are experiencing issues with audio on all apps, you can try the following to mitigate the issue: The Windows audio or sound troubleshooter might be able to resolve the issue for you. You can launch the troubleshooter from Fix sound or audio problems in Windows by selecting the Open Get Help button in the article. The Get Help dialog window should open, and you will need to select yes to open the troubleshooter. If your device's audio is still not working as expected, follow the instructions in Disable Audio Enhancements. Note: The article uses the microphone as an example, but you will need to do the steps for any affected audio device. The audio bug in KB5015878 affects only client Windows 10 versions 20H2, 21H1, and 21H2. It should not bother Windows 11 users, just like the recently confirmed BitLocker recovery bug does not affect Windows 10 customers. Microsoft shares workarounds for broken audio on Windows 10 after KB5015878
  14. Microsoft has notified Windows 10 users on the official Windows Health Dashboard website about a new issue the company had to fix using the Known Issue Rollback tool. According to the software giant, Windows 10 had problems displaying the input indicator and language bar in the notification area after installing the recent KB5014666 update: After installing updates released on June 28, 2022 (KB5014666) or later updates, the Input Indicator and Language Bar might not appear in the notification area. The notification area is normally located on the right end of the taskbar. Affected devices have more than one language installed. The Input Indicator and Language Bar is used to switch between input or keyboard languages on Windows devices and is used especially with languages that use Input Method Editors (IME). To fix the problem, Microsoft issued the Known Issue Rollback mechanism that automatically undoes troublesome changes in cumulative updates with no additional action required. Affected users can restart their Windows 10 computers to attempt to apply the rollback faster. On the other hand, Enterprise users need to install a special Group Policy rule that allows Microsoft to fix bugs using Known Issue Rollback. Microsoft has dedicated documentation on the official website about using Group Policy to deploy a Known Issue Rollback. Microsoft says the bug affects Windows 10 client versions 21H2, 21H1, 20H2, and Windows Server 20H2. Windows 11 users and customers using only one input language, are not affected. Besides breaking the input indicator, KB5014666 fixed multiple bugs in Windows 10 and introduced several new printing-related features. You can learn more about the update in our dedicated article. Microsoft issues fix for broken input indicator and language bar on Windows 10
  15. Microsoft has addressed a known issue triggered by recent Windows 10 updates that caused the Input Indicator and Language Bar not to appear in the notification area. This known issue affects devices running Windows 10 version 20H2, 21H1, and 21H2, with more than one language installed. "After installing updates released on June 28, 2022 ( KB5014666) or later updates, the Input Indicator and Language Bar might not appear in the notification area," Redmond explained on the Windows health dashboard on Tuesday. "The Input Indicator and Language Bar is used to switch between input or keyboard languages on Windows devices and is used especially with languages that use Input Method Editors (IME)." Microsoft addressed the issue using the Known Issue Rollback (KIR) Windows capability that helps revert buggy non-security fixes delivered via Windows Update. Fixes pushed through KIR should reach all consumer and non-managed business devices within 24 hours, with users having the option to speed up the rollout by restarting impacted Windows 10 devices. Group policies for enterprise customers To resolve this known issue on enterprise-managed devices, IT admins must install and configure a specific KIR Group Policy associated with the systems' Windows version. You can find this Group Policy in Computer Configuration -> Administrative Templates -> KB5014666 220706_033027 Known Issue Rollback. The steps needed to deploy a Known Issue Rollback via Group Policy require navigating to the Local Computer Policy or the Domain policy on the domain controller using the Group Policy Editor to select the Windows version to target. You can download the Known Issue Rollback Group Policy for affected Windows 10 versions from here. Detailed information on how to deploy and configure KIR Group Policies can be found on Microsoft's support website. Last month, Microsoft addressed another known issue via KIR that was causing the start menu on some Windows 11 to stop opening after installing recent updates. Microsoft rolling out fix for Windows 10 language bar issues
  16. Microsoft is rolling out a fix for a known issue that caused MS Access runtime applications not to open after installing July 2022's Patch Tuesday Office/Access security updates. Based on user complaints on Microsoft's official community website and Reddit, the KB5002112 and KB5002121 updates are the ones triggering this issue for MS Access 2016 and MS Access 2013, respectively. Microsoft says that for Office installation affected by this issue, users may receive a "Requested type library or wizard is not a VBA project" when opening an ACCDE/MDE file or a "Can't complete the output operation" error when attempting to export to text or Excel files. "This issue was introduced in the July 12 Patch Tuesday update across all supported versions of Access," the company further explained. MS Access error (Microsoft) In an update to the initial advisory, Redmond says a fix is already available for customers using retail versions of Office 2016, 2019, and 2021, and for Microsoft 365 Apps Current Channel. The fix is also rolling out to all other affected Access versions, with estimated arrival times between July 25 and August 9. "For Click-to-run versions (all channels except Office 2013 and Office 2016 MSI), you can get the new update when it is available by choosing File/Account/Office Updates/Update Now," Microsoft added. "If you have Access to the original database that was used to create the ACCDE/MDE, and users are on a single version of Office, you can re-create the ACCDE/MDE file using the same version of Office that users are on." Office Product Issue Introduced Fix available Office 2016 Retail Version 2206, Build 15330.20246 Version 2206, Build 15330.20264 Office 2019 Retail Version 2206, Build 15330.20246 Version 2206, Build 15330.20264 Office 2021 Retail Version 2206, Build 15330.20246 Version 2206, Build 15330.20264 Microsoft 365 Apps Current Channel Version 2206, Build 15330.20246 Version 2206, Build 15330.20264 Access users who cannot re-create their ACCDE/MDE files to mitigate the issue and don't want to wait until the fix rollouts to their systems can remove the offending updates to resolve the problems. However, it's important to note that uninstalling this month's cumulative updates will also remove security updates addressing a Microsoft Office security feature bypass vulnerability (CVE-2022-33632) addressed as part of the July 2022 Patch Tuesday. This is because of Microsoft's choice to bundle all security fixes within a single package. Removing Patch Tuesday updates will also remove fixes for any patched security flaws. Therefore, uninstalling the buggy updates to address this MS Access issue should be the last resort option and only be done if absolutely necessary. If you uninstall the July updates, you should also ensure that they won't be reinstalled to trigger the Access launch problems again. You will have to download and run the "Show or hide updates" troubleshooter from here, click on 'Next,' select the update you want to hide, and restart your computer when prompted. Microsoft fixes Access apps failing to open after July updates
  17. The Thunderbird team has released Thunderbird 102.0.3 Stable. The new version of the open source email client fixes a crash on Windows 11 and several other issues in previous versions of the application. Thunderbird 102.0.3 is already available, either as an in-client upgrade or a manual download from the official project website. Only Thunderbird 102.x installations can be upgraded to the new version. Older Thunderbird installations do not get the upgrade offer to version 102 at this point, but this is going to change in the future. Thunderbird 102.0.3 Select Help > About Thunderbird to display the current version and check for updates. If the menubar is not displayed, tap on the Alt-key on the keyboard to display it. The client should pick up the update automatically. A restart is required to complete the installation of the update. The official changelog lists 12 changes that made it into Thunderbird 102.0.3. Windows users who run Thunderbird 102 on Microsoft's Windows 11 operating system may have hade the client crash on startup; this issue has been fixed in the new release. The only change listed in the changelog is the removal of support for Google Talk chat accounts. Thunderbird 102 supports Matrix, Odnoklassniki, IRC and XMPP currently. Access to downloaded messages was not provided in previous versions of Thunderbird after folders were compacted by the client. Compacting reduces the storage that Thunderbird requires on the local device. The developers have addressed the issue in the new release. The following fixes are also listed: When using Unified Folders, marking a message as a favorite (starring it) did not update the thread pane. When S/MIME was configured, Compose failed to populate some fields. The incorrect mime header charset=windows-1250 was set for non-text attachments. The incorrect header X-Mozilla-Cloud-Part was set for messages sent as attachments. Address book importing and exporting has been improved in the profile importer. Unspecified IMAP stability improvements. Addressed an issue that made the offline cache unusable for NNTP accounts. Signing S/MIME messages failed. Unspecified UI improvements. Thunderbird 102.0.3 is the third point release of version 102 of the email client. Thunderbird 102 was a major new release with a large list of improvements and new features. The point releases 102.0.1 and 102.0.2 addressed issues in the new version, similarly to version 102.0.3. Now You: do you use Thunderbird 102 already? Thunderbird 102.0.3 update fixes a crash on Windows 11 Frontpaged: Mozilla Thunderbird 102.0.3
  18. Microsoft has fixed a known issue causing Office applications like Word and Excel to crash when working with cloud documents. The complete list of affected Office apps includes Excel for Microsoft 365, Word for Microsoft 365, and PowerPoint for Microsoft 365. "Word, Excel, and PowerPoint might close unexpectedly when opening, closing, saving, uploading, or downloading cloud files in Office Version 2205," the company described the issue on its support website. According to Redmond, users wouldn't know the cause of these crashes since "no errors are displayed when the application suddenly closes." Microsoft says the Microsoft 365 issue has been addressed in Office Version 2206 Build 16.0.15330.20230, with the fix currently being rolled out to affected customers via an update. Those impacted by this problem who don't want to wait until the update rolls out to their system can manually install it by opening the Office app and clicking "Update Now" under File > Account > Update Options. Excel 365 freezing issues Microsoft has also fixed another Excel 365 issue today where the app might stop responding or experience performance issues when switching between worksheets. "Excel for Microsoft 365 might experience performance problems or stop responding when switching between worksheets of an existing file containing a PivotTable to which a filter has been applied," Microsoft explained. This known issue affects multiple Microsoft 365 Apps builds, including: Office 365 Semi-Annual Enterprise Channel Version 2108 (Build 14326.20962 ) Office 365 Semi-Annual Enterprise Channel (Preview) Version 2202 (Build 14931.20392) Office 365 Monthly Enterprise Channel (MEC) Version 2203 (Build 15028.20248) Redmond says the fix is available for customers in the Current channel Version 2204 or later (Build 15128.20280) and those in the Monthly Enterprise Channel Version 2204 (Build 15128.20280). The fix will also roll out to Office 365 subscription customers this month for those in the Semi-Annual Enterprise Channel (Version 2202) and the Semi-Annual Enterprise Channel Preview (Version 2202). Microsoft also provides a workaround for Office 2021 or Office 2019 customers who will not be provided with a fix. "If a fix is not available for your current version of Excel 365, you can work around the problem by removing the filter from the affected worksheet by selecting File > Home > Sort & Filter > Clear," Redmond added. Those familiar with the Windows Registry can also set a registry key that will have the same effect using the steps detailed here. Microsoft fixes bug crashing Office apps when opening cloud documents
  19. June 2022 is a historical month for Microsoft. As the company ends support for Internet Explorer 11 (introduced in Windows 8.1, which is also about to bite the dust), this month marks the end of the decades-long era of Internet Explorer. Microsoft wants every remaining IE user to switch to the Edge browser with its dedicated IE mode, but, sadly, KB5014019 ruined the party for those ready to leave the old browser. Microsoft has updated the official Windows Health Dashboard documentation with a notification about fixing a somewhat annoying bug in Windows 11 and 10. According to the company, KB5014019 introduced a bug causing IE tabs in Microsoft Edge to get stuck. After installing KB5014019 and later updates, IE mode tabs in Microsoft Edge might stop responding when a site displays a modal dialog box. A modal dialog box is a form or dialog box which requires the user to respond before continuing or interacting with other portions of the webpage or app. Developer Note: Sites affected by this issue call window.focus. Luckily, there is nothing the affected users should do to solve the problem. Microsoft applied its Known Issue Rollback mechanism to undo the buggy update with no need to install additional patches. The only thing IE Mode users can do is restart their computers to apply the rollback faster. According to the documentation, the bug affected users with Windows 11 21H2, Windows 10 21H2, 21H1, 20H2, and Windows Server 2022. Buggy IE tabs in Edge are not the only problem Microsoft had to resolve this month. The company recently released a massive optional update for Windows 11 to fix several annoying issues, such as broken Wi-Fi hotspots, authentication problems, games refusing to start, and others. As a cherry on top, the update introduced Search Highlights. Microsoft rolls back buggy cumulative update to fix IE tabs getting stuck in Edge
  20. Windows Insiders on Windows 10 21H2 received a new Cumulative Update today, perhaps notable in this release are further attempts at fixes for apps closing unexpectedly when dependent on d3d9.dll with certain graphics cards. The update also contains unrelated fixes that prevented Microsoft Excel and Outlook apps from opening. The new build 19044.1739 (21H2) (KB5014023), which is optional, tests if certain non-security fixes can make it through to the next Patch Tuesday, it is available now through the Release Preview Channel. This update includes the following improvements: New! We introduced new sorting version 6.4.3, which addresses the sorting issue that affects Japanese half-width katakana. We prevented users from bypassing forced enrollment by disconnecting from the internet when they sign into Azure Active Directory (AAD). We fixed an issue that might run an AnyCPU application as a 32-bit process. We fixed an issue that prevents Azure Desired State Configuration (DSC) scenarios that have multiple partial configurations from working as expected. We fixed an issue that affects remote procedure calls (RPC) to the Win32_User or Win32_Group WMI class. The domain member that runs the RPC contacts the primary domain controller (PDC). When multiple RPCs occur simultaneously on many domain members, this might overwhelm the PDC. We fixed an issue that occurs when adding a trusted user, group, or computer that has a one-way trust in place. The error message, “The object selected doesn’t match the type of destination source” appears. We fixed an issue that fails to display the Application Counters section in the performance reports of the Performance Monitor tool. We fixed an issue that might affect some apps that use d3d9.dll with certain graphics cards and might cause those apps to close unexpectedly. We fixed a rare issue that prevents Microsoft Excel or Microsoft Outlook from opening. We fixed a memory leak issue that affects Windows systems that are in use 24 hours each day of the week. We fixed an issue that affects the IE mode window frame. We fixed an issue that prevents internet shortcuts from updating. We fixed an issue that causes an Input Method Editor (IME) to discard a character if you enter the character while the IME is converting previous text. We fixed an issue that causes print failures when a low integrity level (LowIL) application prints to a null port. We fixed an issue that prevents BitLocker from encrypting when you use the silent encryption option. We fixed an issue that occurs when you apply multiple WDAC policies. Doing that might prevent scripts from running when the policies allow scripts to run. We fixed an issue that affects the behavior and shape orientation of a mouse cursor for Microsoft Defender Application Guard (MDAG), Microsoft Office, and Microsoft Edge. This issue occurs when you turn on a virtual graphics processing unit (GPU). We fixed an issue that might cause the Remote Desktop client application to stop working when you end a session. We fixed a reliability issue in the Terminal Services Gateway (TS Gateway) service that randomly causes clients to disconnect. We deployed search highlights to devices that are domain-joined. For more information about the feature, see Group configuration: search highlights in Windows. You can configure search highlights at the enterprise scale using Group Policy settings defined in the Search.admx file and Policy CSP – Search. We fixed an issue that displays the wrong image for the Input Method Editor (IME) mode indicator icon when you turn on the Font Mitigation policy. We fixed an issue that causes a yellow exclamation point to display in Device Manager. This occurs when a Bluetooth remote device advertises the Advanced Audio Distribution Profile (A2DP) source (SRC). We fixed an issue in which the Cluster Windows Management Instrumentation (WMI) provider (ClustWMI.dll) generates high CPU usage in WMIPRVSE.EXE. We fixed an issue that causes Microsoft’s deduplication driver to consume large amounts of nonpaged pool memory. As a result, this depletes all the physical memory on the machine, which causes the server to stop responding. We fixed an issue that causes file copying to be slower. We fixed an issue that might cause a system to stop responding when a user signs out if Microsoft OneDrive is in use. We fixed a known issue that might prevent recovery discs (CD or DVD) from starting if you created them using the Backup and Restore (Windows 7) app in Control Panel. This issue occurs after installing Windows updates released January 11, 2022 or later. This build contains no Known Issues, and as previously pointed out, no new features either. To check and see which version of Windows 10 you’re running, just type winver into the Windows search box on the Taskbar (or right click on Start and choose Run and then type in winver). It should show as “Version 21H2”. This is an optional "C update" of which is generally released in the third or forth week of the month, and is designed to test new bug fixes and improvements for other non-security issues. C updates are optional, and Windows Update won’t automatically install them on your PC, when offered outside of Windows Insider channels. You can view the official press release for Build 19044.1739 here. Windows 10 Build 19044.1739 (KB5014023) in Release Preview Channel fixes app crashes
  21. Microsoft has released a new optional update for Windows 11 with build 22000.652 under KB5012643. The new update is a non-security, cumulative update or C-release that fixes a near-hour long Windows startup delay issue. It also brings several other fixes. Here are the highlights of the release: Updates an issue that delays OS startup by approximately 40 minutes. Updates an issue that incorrectly aligns video subtitles. Displays the temperature on top of the weather icon on the taskbar. Updates an issue that prevents you from using the minimize, maximize, and close buttons on a maximized app window. And here is the full changelog: New! Adds improvements for servicing the Secure Boot component of Windows. Addresses an issue that causes the AppX Deployment Service (AppXSvc) to stop working after you install certain MSIX apps. Addresses a race condition that occurs early in the startup process that might cause a stop error. Improves the Autopilot client to process updated Trusted Platform Module (TPM) capabilities that support self-deployment and pre-provisioning scenarios. Changes the timeout for Azure Active Directory (Azure AD) registration from 60 minutes to 90 minutes for hybrid Azure AD-joined Autopilot scenarios. This also addresses a race condition that causes an exception at timeout. Addresses an issue in which certain Point of Sale terminals experience occasional OS startup delays during restart of up to 40 minutes. Addresses a memory leak issue that affects Windows systems that are in use 24 hours each day of the week. Addresses an issue that affects the Dynamic Host Configuration Protocol (DHCP) option 119 (Domain Search Option) by preventing the use of the connection-specific DNS Suffix Search List. Addresses an issue that affects the Title attribute in Microsoft Ege IE mode. Addresses an issue in which mobile device management (MDM) policies were not allowed on Windows Enterprise editions that were upgraded to Enterprise using Azure AD-joined subscription entitlement. Addresses an issue that might cause video subtitles to be partially cut off. Addresses an issue that incorrectly aligns video subtitles. Addresses an issue that causes Kerberos authentication to fail, and the error is “0xc0030009 (RPC_NT_NULL_REF_POINTER)”. This occurs when a client machine attempts to use the Remote Desktop Protocol (RDP) to connect to another machine while Remote Credential Guard is enabled. Addresses an issue that causes Windows to go into BitLocker recovery after a servicing update. Addresses an issue that prevents retrieval of the Endorsement Key (EK) certificate from the TPM device. Addresses an issue that might fail to copy the security portion of a Group Policy to a machine. Addresses an issue that prevents the instantiation of the Microsoft RDP Client Control, version 11 and higher, inside a Microsoft Foundation Class (MFC) dialog. Displays the temperature on top of the weather icon on the taskbar. Addresses an issue that prevents you from using the minimize, maximize, and close buttons on a maximized app window. This issue occurs because the Notification Center keeps the input focus. Addresses an issue that might occur when you use Netdom.exe or the Active Directory Domains and Trusts snap-in to list or modify name suffixes routing. These procedures might fail. The error message is, "Insufficient system resources exist to complete the requested service." This issue occurs after installing the January 2022 security update on the primary domain controller emulator (PDCe). Addresses an issue that causes the primary domain controller (PDC) of the root domain to generate warning and error events in the System log. This issue occurs when the PDC incorrectly tries to scan outgoing-only trusts. Addresses an issue that occurs when you map a network drive to a Server Message Block version 1 (SMBv1) share. After restarting the OS, you cannot access that network drive. Addresses an issue that affects an SMB multichannel connection and might generate a 13A or C2 error. Addresses an issue that damages a pool when a Client-Side Caching (CSC) cleanup method fails to delete a resource that was created. Addresses an issue that might cause the server to lock up because the nonpaged pool grows and uses up all memory. After a restart, the same issue occurs again when you try to repair the damage. Reduces the overhead of resource contention in high input/output operations per second (IOPS) scenarios that have many threads contending on a single file. You can either download the update through Windows Update via Settings or you can try standalone download links on Microsoft Update Catalog here. New Windows 11 optional update (KB5012643) fixes a near-hour long startup delay bug
  22. Microsoft has released the optional KB5012636 cumulative update preview for Windows 10 1809 and Windows Server 2019, with fixes for system freezing issues affecting client and server systems. This update is part of Microsoft's scheduled April 2022 monthly "C" updates, and it allows Windows 10 users to test the fixes released on May 10th as part of next month's Patch Tuesday. Scheduled "C" non-security preview updates are optional, unlike regular Patch Tuesday Windows updates. They are only used to test performance improvements and bug fixes ahead of the general release, and they don't provide security updates. To install the KB5012636 update, you have to go to Settings > Windows Update and manually 'Check for updates.' Since it's an optional update, Windows will not install it until you click the 'Download now' button. You can also manually download and install this Windows 10 1809 cumulative update preview from the Microsoft Update Catalog. "The preview update for Windows 11 and other supported versions of Windows 10 will be available in the near term," Microsoft said. Fixes for system freeze problems As already mentioned above, today's Windows 10 optional update comes with fixes for issues that trigger system freezes and crashes on some devices. As Microsoft explained, KB5012636 addresses an issue that might cause Windows systems to stop working when applying Windows Defender Application Control (WDAC) policies that don't require a restart. This update also fixes an issue that may cause servers to lock up as the nonpaged pool grows and eventually uses up all available memory. Restarts won't help fix this problem either because the system will lock up again when trying to repair the damage. Microsoft also fixed a deadlock in the WebDav redirector when reading a file from the local TfsStore. On systems without the KB5012636 update, this bug causes the system to stop responding. KB5012636 also addresses an issue where some Point of Sale terminals might experience infrequent OS startup delays of up to 40 minutes during restarts. "If you installed earlier updates, only the new updates contained in this package will be downloaded and installed on your device," Microsoft added. What's new in the Windows 10 KB5012636 update After installing this non-security cumulative update preview, Windows 10 will have its build number changed to 17763.2867. The Windows 10 KB5012636 cumulative update preview includes 26 quality improvements and fixes, including: Adds improvements for servicing the Secure Boot component of Windows. Addresses an issue that causes the Key Distribution Center (KDC) code to incorrectly return the error message "KDC_ERR_TGT_REVOKED" during domain controller shutdown. Addresses an issue that causes virtual computer object (VCO) password settings failure on a distributed network name resource. Windows 10 KB5012636 cumulative update fixes freezing issues
  23. 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
  24. 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
  25. 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
×
×
  • Create New...