Search the Community

Showing results for tags 'windows 11 issues'.

  • Search By Tags

    Type tags separated by commas.

  • Search By Author

Content Type


Forums

  • Favorites
  • General Discussion
    • Introduce Yourself
    • General Discussion
    • Jokes & Funny Stuff
    • Members' Metropolis
    • Real World News
  • Technical Help & Support
    • Hardware Hangout
    • Smart Home, Network & Security
    • Tips, Tweaks & Customization
    • Software Discussion & Support
    • Programming (C#, C++, JAVA, VB, .NET etc.)
    • Web Design & Development
  • Platforms (Operating Systems)
    • Microsoft (Windows)
    • Apple (macOS)
    • Linux
    • Android Support
  • Submitted News, Guides & Reviews
    • Essential Guides
    • Back Page News
    • Member Reviews
  • Recreational Activities
    • Gamers' Hangout
    • The Neobahn
    • The Media Room
    • The Sporting Arena
  • Neowin Services & Support
    • Site Announcements
    • Site & Forum Issues

Find results in...

Find results that contain...


Date Created

  • Start

    End

Last Updated

  • Start

    End

Filter by number of...

Found 103 results

  1. hellowalkman
    Microsoft: We are working on KB5034441/KB5034440 "0x80070643 - ERROR_INSTALL_FAILURE" fix by Sayan Sen Microsoft released the first Windows 10 and 11 Patch Tuesday updates of 2024, last week, with the January updates KB5034122 and KB5034123 respectively. The updates are meant to address security issues within Windows. The one for 11 also fixes the recent Wi-Fi troubles that led to networks not connecting or the Wi-Fi icon not showing. In a separate article, the company has also detailed a fix for a WinRE (Windows Recovery Environment) security vulnerability that can lead to BitLocker encryption bypass. The issue is being tracked under ID "CVE-2024-20666". Microsoft said that the security flaw could allow attackers to bypass BitLocker encryption if they are able to get physical access to an unpatched PC. However, this is not one of those WinRE updates that is seamlessly installing on PCs. Users report that the update is failing to install with the error message "0x80070643 - ERROR_INSTALL_FAILURE" which indicates insufficient WinRE partition size. The solution is to resize the partition manually. You can do so by following this dedicated guide here. Neowin forum supervisor / mod and ESET's Distinguished Researcher Aryeh Goretsky (X account) also experienced the issue which they were able to fix by increasing the recovery partition. Goretsky writes: Hello, I can confirm that the KB5034441 hotfix failed on a Windows 10 VM with a Windows Recovery partition that was 511MB in size. I decided to increase it to 1024MB in size, just in case more space was needed in the future. The hotfix installed normally afterwards. Regards, Aryeh Goretsky Microsoft of course has been aware of this problem almost from the start which is why it has been recommending the manual resize workaround as soon as it published the WinRE updates. Yesterday, on its Windows health dashboard, the company has added the issue and notes that a fix is coming via a future update. Microsoft says: Devices attempting to install the January 2024 Windows Recovery Environment update ( KB5034441/KB5034440) might display an error related to the size of the Recovery Environment's partition. Resulting from this error, the following message might be displayed. "0x80070643 - ERROR_INSTALL_FAILURE" Workaround: It might be necessary to increase the size of the WinRE partition in order to avoid this issue and complete the installation. Note that 250 megabytes of free space is required in the recovery partition. Guidance to change the WinRE partition size can be found in KB5028997: Instructions to manually resize your partition to install the WinRE update. Next steps: We are working on a resolution and will provide an update in an upcoming release. Aside from this BitLocker encryption vulnerability, Microsoft has recently updated its Microsoft Printer Metadata Troubleshooter Tool to patch against a Remote Code Execution (RCE) security flaw.
  2. hellowalkman
    Microsoft confirms its Windows' HP Smart auto-install bugfix is vulnerable to code execution by Sayan Sen Towards the end of last month, users online started complaining about how their system was automatically installing HP's Smart app for printers, even when there was no printer on their PC. As the issue was fairly widespread, soon after Microsoft acknowledged it too, confirming that almost all versions of Windows were affected. Since it is HP's app that was being installed, the initial impression from many people would likely be that somehow the company may be responsible for this bug. However, after further investigation, Microsoft confirmed that such was not the case and the problem was not due to any update on HP's end. A week and a half later, Microsoft issued a fix for the problem in the form of a tool that would resolve the metadata issues that were apparently behind the problem. Microsoft stated that running the utility would restore the correct printer metadata (names, icons, and more), remove the incorrect HP LaserJet M101-M106 printer, and uninstall the HP Smart app (if incorrect metadata is present). Microsoft explains in its words the purpose of the tool: This tool is intended to help users and administrators address the known issue: Printer names and icons might be changed and HP Smart app automatically installs(See Related Links for more information on this issue) This tool will review your printer information. It will restore any previously downloaded model information and icons and will remove “HP LaserJet M101-M106” model information, icons, and application associations from printers that do not match this name and model. This tool will uninstall the HP Smart application if incorrect metadata was found, there are no HP printers or HP printer drivers installed, and the application was installed after Nov 25th, 2023. An updated version of the tool has now been quietly uploaded by Microsoft. You can download the updated version of the troubleshooter from the Microsoft Download Center: x86 systems: PrintMetadataTroubleshooterX86.exe x64 systems: PrintMetadataTroubleshooterX64.exe ARM32 systems: PrintMetadataTroubleshooterArm32.exe ARM64 systems: PrintMetadataTroubleshooterArm64.exe In the next part, Microsoft explains how the tool works. Users who run this troubleshooter tool will need to do it using an elevated Command Prompt: How to use this tool When it is run by enterprise administrators, correcting printers for all users and sessions on a system requires running the tool as the Local System account. Tools such as PsExec or Windows Task Scheduler can run commands as Local System. When it is run by users managing their own printers, this tool must be run using administrative credentials. The following are recommended steps to execute the file and confirm it worked: Click Start, type cmd, right-click Command Prompt, and then select Run as Administrator. In the opened command prompt, type cd /d “[path_to_downloaded_tool]” and then press Enter. Type the name of the file appropriate for your device from the list below (for instance PrintMetadataTroubleshooterX86.exe) and then press Enter. The tool will return the message Troubleshooter completed successfully on devices where incorrect printer information was found/fixed. Or, it will return the message Troubleshooter not applicable since metadata package not found on devices that are not affected. You may find more details on the official support page under KB5034510. Update: A couple of days ago, we published this story as Microsoft had updated its Printer Metadata Troubleshooter Tool. The update was published on January 5, 2024. However, the changelog indicating what changed was not put up until later (January 9), when the company pushed its first Windows 10 and 11 Patch Tuesday updates of 2024 under KB5034122 and KB5034123 respectively. According to Microsoft, the tool was updated to address a remote code execution (RCE) vulnerability that has been tracked under ID "CVE-2024-21325." The full changelog is given below: January 9, 2024 Added information about this tool addressing CVE-2024-21325 Updated the file lists More details may be available on the official support page under KB5034510.
  3. hellowalkman
    Microsoft: We know there're even more gaming bugs/issues now on your Windows 11 Insider PC by Sayan Sen Microsoft released its first Insider builds of 2024 earlier today, or last night, depending on the place and time zone you are in. The two builds dropped in the Dev channel and Canary channel, and the latter brought quite a few interesting features including the ability to pause and resume print queues, a new Taskbar icon for power-saving on desktops, and more. One of the interesting known issues highlighted by the company in the release notes is related to gaming as Microsoft has acknowledged that it has not been able to fix those issues even as we enter the new year. In fact, the tech giant has confirmed that even more games are going to be impacted. The release notes for the Canary build 26020 reads: [REMINDER] Some popular games may not work correctly on the most recent Insider Preview builds in the Canary Channel. Starting with Build 26016, more games have been impacted by several bugs – if you’re having any issues please submit feedback in Feedback Hub. In case you are wondering, Microsoft first started publishing this in the known issues section earlier last year in September starting with the Canary build 25947. And up until the latest build, the release note about the issue read: Some popular games may not work correctly on the most recent Insider Preview builds in the Canary Channel. Please be sure to submit feedback in Feedback Hub on any issues you see with playing games on these builds. It is not clear which popular titles Microsoft is referring to here, and which new games have been added to the list. Perhaps the bug is randomly occurring across a multitude of popular titles and games which is why none of them have in particular been named. It is also possible that the issue is fairly sporadic which is why the company has continued asking for feedback to better understand the underlying fault.
  4. TarasBuria
    Microsoft fixes Wi-Fi issues in the latest Windows 11 updates by Taras Buria It did not take too long for Microsoft to confirm and resolve the problem with broken Wi-Fi connections in the latest Windows 11 updates (version 22H2 and 22H3). On December 19, Microsoft acknowledged user reports and promised to release more information when available. After a little more than 24 hours, the company resolved the problem using the Known Issue Rollback system (KIR). Microsoft has received reports of an issue in which some Wi-Fi adapters might not connect to some networks after installing KB5032288. We have confirmed this issue was caused by KB5032288 and KB5033375. As reported, you are more likely to be affected by this issue if you are attempting to connect to an enterprise, education, or public Wi-Fi network using 802.1x authentication. This issue is not likely to occur on home networks. The beauty of Known Issue Rollback is that it does not require uninstalling updates or downloading extra files or patches. Microsoft can undo the damage remotely and deliver the necessary fixes to affected systems (consumer and non-managed devices) in about 24 hours. The company says you can speed up the process by restarting your computer. Things are slightly different on the enterprise side, and users with managed devices must install the Group Policy called "Windows 11 22H2 KB5032288 231029_032011 Know Issue Rollback" to mend their Wi-Fi. You can download the Policy from the official Windows Health Dashboard website. More information about Known Issue Rollback is available here. The problem with broken Wi-Fi connections affects systems with Windows 11 versions 22H2 and 23H2 with KB5032288 and KB5033375 installed. It does not affect home networks, and the scope of the damage is limited to enterprise, education, or public Wi-Fi access points with 802.1x authentication. Windows 10 users are also immune to the issue. In case you missed it, Microsoft recently fixed another Windows bug that was causing weird printing bugs and unsolicited app installs. However, that one requires more effort—you must download and run a troubleshooter utility to get everything back to working.
  5. hellowalkman
    Microsoft acknowledges it's not HP who's auto-installing printer Smart app on your Windows by Sayan Sen Towards the end of last month, users online started complaining about how their system was automatically installing HP's Smart app for printers, even when there was no printer on their PC. As the issue was fairly widespread, soon after Microsoft acknowledged it too, confirming that almost all versions of Windows were affected. Since it is HP's app that is being installed, the initial impression from many people would likely be that somehow the company may be responsible for this bug. However, after further investigation, Microsoft has confirmed that such is not the case. While the initial post about the issue on the Windows health dashboard only stated that printing processes and jobs shouldn't be affected, the tech giant has now edited that part to add that HP is not responsible for the mishap, along with additional information regarding printer functionality. Here's what the initial post stated: Note: Printing processes are not expected to be affected by this issue. It should be possible to queue printing jobs as usual, as well as other features such as copying or scanning. Printers on the device will continue to use the expected drivers for printer operations. As the symptoms are related to the automatic installation of the HP Smart app, Windows devices which do not have access to the Microsoft Store are not expected to be affected by this issue. And here's what the updated version of it is now: Note: Our investigations indicate that this issue is not caused by an HP update. In most cases, it should be possible to use the printer as expected, including queueing printing jobs, as well as other features such as copy, scan, or fax. Printers on the device will continue to use the expected drivers for printer operations. However, this issue might affect associations with other manufacturer-supplied printer apps used to extend basic printer capabilities. If this is the case, some or all of those extended functions might not work. As the symptoms are related to the automatic installation of the HP Smart app, Windows devices which do not have access to the Microsoft Store are not expected to be affected by this issue. You can view the issue on this page on Microsoft's official health dashboard website. On a somewhat related note, in case it isn't HP but you instead find Canon driver installed on your PC even if you don't have one, do leave your comment on this thread started by Neowin forum member cosrocket. We are trying to understand if this is an isolated case or more widespread.
  6. hellowalkman
    As Microsoft also pushes it to Windows 10, buggy Copilot puts the brakes on Windows 11 23H2 by Sayan Sen Although initially it was expected that Copilot is going to be an AI assistant exclusively for Windows 11, that changed quickly as Microsoft also introduced the feature to Windows 10. To entice those who weren't too keen about it, Microsoft explained in a lengthy blog post why users would want to have the feature even if they may feel they don't need it. Besides that, the company is also experimenting a lot with the Copilot button placement as it is now testing to see if it fits better somewhere around the corner of the screen where the Show desktop option lies. All this experimentation certainly comes at a cost as Copilot seems to be breaking one thing or the other fairly regularly, though it is sort of expected too given that the feature is pretty new. Still, users shouldn't need to be going through such experiences on non-Insider builds. Microsoft had already confirmed that Copilot can mess up desktop icons on Windows 11 as they would move unexpectedly on multi-monitor setups which is why the feature was blocked on such systems. And now that Copilot is on Windows 10, this unresolved bug, too, has invited itself there with the latest Windows 10 22H2 update (KB5032278). Aside from that, the company has also put a safeguard in place, which is essentially a compatibility hold such that these PCs will not be offered the Windows 11 23H2 update. The tech giant has also urged such users to not manually update their systems to version 23H2. On its Windows health dashboard, Microsoft writes: Windows devices using more than one (1) monitor might experience issues with desktop icons moving unexpectedly between monitors or other icon alignment issues when attempting to use Copilot in Windows (in preview). To prevent users from encountering this issue, Copilot in Windows might not be available on devices that have been used or are currently being used in a multimonitor configuration. You might also not be able to update to Windows 11, version 23H2 as we have applied a compatibility hold on devices encountering this issue. If your organization is using Windows Update for Business reports, the safeguard ID is 47615939. Note We recommend that you do not attempt to manually update to Windows 11, version 23H2 using the Update now button or the Media Creation Tool until this issue has been resolved and the safeguard removed. You may find more details about it on this page on Microsoft's official website.
  7. hellowalkman
    Microsoft: Windows 10 Patch Tuesday fails installation with "8007000D (ERROR_INVALID_DATA)" by Sayan Sen Microsoft recently published a blog post looking back at the origins and the journey of Patch Tuesday on the occasion of the 20th anniversary of the monthly security update. While this was to celebrate its efforts, oftentimes Patch Tuesdays turn up buggy and sometimes the only way to work around the issue is to perform a rollback. Such is the case with the October 2023 Patch Tuesday as well on Windows 10, though thankfully, it is not affecting all users as it is limited to version 21H2 only. Microsoft says that the bug is causing installation failure of the Patch Tuesday, even though at first glance it may appear to be working. On its Windows health dashboard website, Microsoft explains: Microsoft has received reports of an issue where Windows updates released October 10, 2023 ( KB5031356) fail to install. Devices might initially display progress, but then fail to complete installation. Based on our reports, some of the most common errors being encountered is Error 8007000D (ERROR_INVALID_DATA). This error can be found from the Windows Update view under System settings, by selecting Update History. In the next section, the tech giant has explained how affected users, including enterprises can perform the known issue rollback (KIR). Resolution: This issue is resolved using Known Issue Rollback (KIR). Please note that it might take up to 48 hours for the resolution to propagate automatically to consumer devices and non-managed business devices If necessary, the following manual steps can be used to speed up the recovery: Run command Prompt as Administrator. To do this, you can open the Start menu and type 'cmd'. From the right-side panel of the search results, select the option 'Run as administrator' In the window that opens, type the following to execute a restore command: Dism /online /cleanup-image /RestoreHealth Wait for it to complete successfully, then close the windows. You can now search for updates again from the Windows Updates from the Settings view. The Windows Updates settings view can always be found by opening the Start menu and typing 'Windows Updates'. Then select 'Check for updates' from the search results. 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. The special Group Policy can be found in Computer Configuration -> Administrative Templates -> . For information on deploying and configuring these special Group Policy, please see How to use Group Policy to deploy a Known Issue Rollback. Group Policy downloads with Group Policy name: ​Download for Windows 10, version 22H2 and Windows 10, version 21H2 - Windows 10 20H2, 21H1, 21H2 and 22H2 KB5026879 230627_173533 Known Issue Rollback.msi You may find more details on the issue on this page on Microsoft's health dashboard website.
  8. Qblade_
    Windows 11 KB5031455 Moment 4 update is causing various issues for some users by Mehrotra A Last week, Microsoft began the broader rollout of its Moment 4 update for Windows 11 users. While the update is still not mandatory, Microsoft is now offering it to users as a non-security update. This comes just a month after the Redmond giant officially started rolling out the Moment 4 update to Windows 11 users. However, things do not seem to go as per the plan for some users who are facing issues with the new update. Microsoft's update is causing issues while installing for some users while others say the new update is causing performance issues. Going through Reddit and Microsoft Feedback Hub, it looks like most of the users are facing installation issues with a variety of errors like 0x800f081f, 0x8007007e, 0x8000ffff, 0x800f0984, and 0x80073701. Unfortunately, it looks like the issues extend to Update Catalog as well with users saying that the installation froze even when using the update package from Microsoft's Update Catalog. More worryingly, there have been reports stating that individuals are not able to rollback if the installation is stuck or if they are facing issues with the update. According to posts on both Reddit and Microsoft Feedback Hub, users are getting stuck in a rollback loop where Windows tries to install the update and then tries to roll it back when the update fails. As of this moment, Microsoft has not acknowledged the issue on social media or on the Windows Health Dashboard. With Windows 11 now running on over 400 million devices worldwide, it is hard to assess the true severity of these issues. We here at Neowin recommend enabling System Restore on the Windows install disk (usually C:\) and doing a System Restore Point before installing new feature or Patch Tuesday updates, but also before installing third party software on your system. This can help individuals rollback if an update fails, without losing important data.
  9. hellowalkman
    Microsoft confirms "65000" BitLocker encryption error is haunting Windows 11 and Windows 10 by Sayan Sen Microsoft has confirmed a new issue that is affecting all Windows client versions, be it on Windows 11 (22H2, 21H2), Windows 10 (22H2, 21H2, and Enterprise LTSC 2019). The bug is related to BitLocker CSP encryption reporting. The BitLocker configuration service provider (CSP) is used by the enterprise to manage the encryption of PCs and devices. According to Microsoft, a "65000" error code is being displayed in the "Require Device Encryption" setting on Intune for Mobile Device Management (MDM). The tech giant notes here that other than Intune, similar third-party apps may be affected too. It explains: Using the FixedDrivesEncryptionType or SystemDrivesEncryptionType policy settings in the BitLocker configuration service provider (CSP) node in mobile device management (MDM) apps might incorrectly show a 65000 error in the "Require Device Encryption" setting for some devices in your environment. Affected environments are those with the “Enforce drive encryption type on operating system drives” or "Enforce drive encryption on fixed drives" policies set to enabled and selecting either "full encryption" or "used space only". Microsoft Intune is affected by this issue but third-party MDMs might also pe affected. Important: This issue is a reporting issue only and does not affect drive encryption or the reporting of other issues on the device, including other BitLocker issues. Although Microsoft has not been able to devise a resolution for this issue yet, the company has provided a simple workaround that can mitigate it. It involves changing the policy settings to "not configured". Workaround: To mitigate this issue in Microsoft Intune, you can set the “Enforce drive encryption type on operating system drives” or "Enforce drive encryption on fixed drives" policies to not configured. Next steps: We are working on a resolution and will provide an update in an upcoming release. You can read more about the issue on Microsoft's health dashboard website.
  10. Anurag Singhh
    Windows 11 bug ironically boosts File Explorer speed, making things load instantly by Anurag Singh The File Explorer in Windows 11 seemingly has its flaws. It might load slowly when you open files and sometimes, Explorer’s search bar may take too long to load your search results. In fact, in-depth tests have shown that Windows 10 is actually snappier than Windows 11. Some of the members of Neowin's own forum have echoed similar sentiments. But it seems a bug in the operating system is giving File Explorer an unexpected speed boost. Twitter user Vivy found a bug that can significantly speed up Windows File Explorer. They posted that switching File Explorer to full-screen mode (by pressing F11) and then exiting full-screen mode (by pressing F11 again) results in almost instant loading of folder contents and generation of thumbnail previews for files. The search function within File Explorer also becomes more responsive and snappier. Did you know you can speedup explorer by use of bugs? Turns out switching in and out of full screen mode (F11) noticeably improves load times! Wish this was the performance we get out of box. (Yes navbar breaks.. tho navbar shouldn't cause such a huge snappiness regression..) pic.twitter.com/GObybf1C8q — Vivy (@VivyVCCS) September 3, 2023 Users on the r/Windows 11 subreddit are reporting that a bug in File Explorer actually improves the loading time. One Redditor said: I tested it on a music folder with 1800+ subfolders, and 25,000+ files: Everything opens instantly, awesome. This is the performance that we had in the Explorer of Windows 7. Another wrote: I just tried it on an i7-7700HQ on 22H2... And it works. I can't believe it. It's so snappy suddenly. Now, I don't know if I should be happy or jaded by this. This bug is apparently affecting all versions of Windows 11, from the Canary Insider builds to all the way back to the original release (22000, 21H2). Although the bug makes File Explorer faster, it would be better if we could have this kind of performance by default. Windows 11 was supposed to have better overall performance than previous releases, but that doesn't seem to be the case.
  11. hellowalkman
    Microsoft puts little blame on its Windows update after UNSUPPORTED PROCESSOR BSOD bug by Sayan Sen Update: Intel too confirms Microsoft is right not to take the blame. It has been a pretty eventful week for Microsoft and Intel in terms of major news and rumors. First up, we had the "Downfall" GDS vulnerability which affects almost all of Intel's slightly older CPUs. This was followed by a leaked Intel document which suggests upcoming Wi-Fi 7 may only be limited to Windows 11, Windows 12, and newer. Meanwhile, users of the two latest generations of Intel CPUs were affected by a Windows update issue where the system crashes with a blue screen of death (BSOD) displaying a "UNSUPPORTED_PROCESSOR" error, even though it is supposed to work perfectly. (Microsoft recently updated its support list for both Intel and AMD.) MSI, which seems to be the most commonly affected motherboard vendor out of all, published a workaround yesterday which you can find here. The problem is mainly affecting Intel's Z690 and Z790 boards, which are chipsets accompanying 12th and 13th Gen Alder Lake and Raptor Lake parts respectively. Microsoft has also updated its health dashboard page today with new information and details about the issue. Interestingly, the company says that its latest non-security preview updates, ie, Windows 11 (KB5029351) and Windows 10 (KB5029331), which seemingly triggered this Unsupported CPU BSOD error, is not really what's to blame for the error. It says that this is an issue with a "specific subset of processors": After investigating these reports, we have found that the “UNSUPPORTED_PROCESSOR” error was not caused by issues in KB5029351 and is limited to a specific subset of processors. We are collaborating with device manufacturers (OEMs) and will temporarily mitigate this issue by not offering KB5029351 to Windows devices that might be affected by this issue. If you still experience this issue, please contact your device’s processor manufacturer. If you are one of those affected, you can still provide feedback to Microsoft The company's guidance on how to properly give feedback on the issue can be found in this article. You should also contact your motherboard maker and CPU maker, which seems to be Intel at the moment.
  12. hellowalkman
    Microsoft investigates Windows (KB5029351, KB5029331) Unsupported Processor BSOD crashes by Sayan Sen Update: MSI has offered a workaround. Microsoft is looking into a problem users on the latest Windows 11 and Windows 10 builds are facing. Despite running their systems on supported CPUs, the issue leads to an error wherein the PC crashes with a blue screen of death (BSOD) with an error message that says: "UNSUPPORTED_PROCESSOR". (Microsoft recently updated its support list for both Intel and AMD.) The tech giant is unsure at the moment if it is an issue with Windows or whether the root cause may be something else. As such, the company has requested feedback via the Feedback Hub app. On the Windows health dashboard it explains: Microsoft has received reports of an issue in which users are receiving an “UNSUPPORTED_PROCESSOR” error message on a blue screen after installing updates released on August 22, 2023 (KB5029331) [and KB5029351] and then restarting their device. KB5029331 might automatically uninstall to allow Windows to start up as expected. If you are experiencing issues, please use Feedback Hub to file a report following the below steps: ​Launch Feedback Hub by opening the Start menu and typing "Feedback hub", or pressing the Windows key + F ​Fill in the "Summarize your feedback" and "Explain in more detail" boxes, then click Next. ​Under the "Choose a category" section, click the "Problem" button, and select "Install and Update" category. Then select "Downloading, installing, and configuring Windows Update” subcategory. Click Next. ​Under the "Find similar feedback" section, select the "Make new bug" radio button and click Next. ​Under the "Add more details" section, supply any relevant detail (Note this is not critical to addressing your issue). ​Expand the "Recreate my problem" box and press "Start recording". Reproduce the issue on your device. ​Press "Stop recording" once finished. Click the "Submit" button. Browsing through Feedback Hub, it seems that MSI motherboards, mainly from Intel's 600 series (Z690) and 700 series (Z790), are the ones where the issue is infesting the most, though it is possible the problem is there on other OEM motherboards too. In case you have a board from some other maker, like say Asus, Gigabyte, or ASRock, among others, and experiencing this bug, Microsoft would likely appreciate some feedback about those.
  13. hellowalkman
    Microsoft: Windows 11 (KB5028254) Start menu not starting with third-party apps by Sayan Sen Microsoft has confirmed that third-party applications that let users customize the user interface (UI) are once again breaking the Start menu. The issue returned today with the latest Windows 11 update KB5028254 which was released earlier today for version 22H2. Microsoft says ExplorerPatcher is problematic at the moment, but others (like Start11, etc.,) may be affected too. Interestingly, the software fixes Windows 10 Start menu issues with its latest update. Microsoft notes the issue on its Windows health dashboard stating: After installing KB5028254 or later updates, the Start menu might not open on Windows devices with some third-party UI customization apps installed. The known affected third-party UI customization app is ExplorerPatcher but others might also be affected. These types of apps often use unsupported methods to achieve their customization and as a result can have unintended results on your Windows device. Workaround: We recommend uninstalling any third-party UI customization app before installing KB5028254 to prevent this issue. If your Windows device is already experiencing this issue, you might need to contact customer support for the developer of the app you are using. Next steps: If you are using any third-party UI customization app and encounter any issues, you will need to contact customer support for the developer of the app you are using. Affected platforms: Client: Windows 11, version 22H2 Server: None As mentioned up top, this problem is not new and was affecting Windows 11 22H2 previously as well. Towards the end of February, earlier this year, when the Moment 2 update went live, the issue was first seen. This time though, it is Moment 3 which is affected. In related news, the tech giant was able to resolve another Start menu issue in late June, something it had been struggling with for a while. Another issue affecting Windows 11, as well as Windows 10, at the moment, is a video codec problem, which you can find details about here. Edit: Brad Sams, VP and General Manager, Stardock Software, informed Neowin that Start11 is not impacted by this issue. They stated in a mail: "We are not impacted by the KB that broke explorer patcher - we use a different method for implementation." Neowin reader fishnet37222, who is probably a Start11 customer, confirmed a similar experience.
  14. hellowalkman
    ExplorerPatcher sets Windows 10 Start menu right, but breaks Windows 11's by Sayan Sen ExplorerPatcher, a third-party Windows UI customization utility, released its latest version, 22621.1992.56.1, earlier today. The new version fixes a bug wherein the Start menu on Windows 10 would break. The developer of the software notes that the bug would prevent the Pin to Start options from working properly. The issue has been resolved with this latest update. The release notes mention the update was tested on Windows 11 build 22621.1992 which is the latest Patch Tuesday release: Tested on OS build 22621.1992. Installer requires Internet connectivity. Details Windows 10 Start menu: Fixed a bug that prevented the menu from working on OS builds 22621.1413 and newer (46c5041). While the problem on Windows 10 is now fixed, Microsoft confirmed earlier that it's Windows 11 now which is having issues post the latest update, wherein the Start menu would fail to launch with ExplorerPatcher installed. Other third-party apps may be affected as well. The dev has detailed the issue separately too alongside their workarounds so if you are on the latest Windows 11 update and are having issues related to Pin to Start options, some of the solutions below may help: Pin to Start from Start menu does not work Details: This problem seems to happen because the tile data store seems to have changed for the Windows 11 menu, while the Windows 10 Start menu still uses the old data store to display tiles. The Windows 10 Start menu has to be disassembled and studied in order to redirect operations on the old data store to the new data store. Workaround: Until this gets fixed properly, you can pin tiles to Start by dragging the application entry to the pinned tiles area. Pinned tiles cannot be unpinned Details: This problem seems to happen because the tile data store seems to have changed for the Windows 11 menu, while the Windows 10 Start menu still uses the old data store to display tiles. The Windows 10 Start menu has to be disassembled and studied in order to redirect operations on the old data store to the new data store. Workaround: Until this gets fixed properly, you can unpin tiles by dragging the tile away and creating a new group with it. Then, right click the group heading and choose "Unpin group from Start". Cannot pin programs that are not displayed in Start Details: This problem seems to happen because the tile data store seems to have changed for the Windows 11 menu, while the Windows 10 Start menu still uses the old data store to display tiles. The Windows 10 Start menu has to be disassembled and studied in order to redirect operations on the old data store to the new data store. Applications like File Explorer and the Start menu search panel 'talk' to the new data store, thus their "Pin to Start" options try to pin tiles to the Windows 11 Start menu, not the Windows 10 one. Workaround: Restart File Explorer using the relevant option in Properties. This ensures that no Control Panel windows are opened, which is relevant for this workaround. Then, click the "Pin tiles to Windows 10 Start menu from File Explorer" option in Properties - Start menu. A File Explorer window opens - use this window to browse to the item you want pinned to the Windows 10 Start menu. Once you identify the program, right click and choose "Pin to Start". The program will be pinned to Start. If it does not work, try again one more time. If you can find the program only using Search, right click on it there, choose "Open file location". In the window that opens, copy the address to the program and navigate to it using the special File Explorer window from which you can pin tiles. You may find additional details about Start menu pinning on this GitHub page.
  15. John Callaham
    Windows 11 22H2 optional update KB5028254 makes brightness settings more accurate by John Callaham Microsoft has released the latest non-security update for Windows 11 22H2. The new build number for this release is 22621.2070 (KB5028254). It includes a number of improvements and bug fixes, including one that will make brightness settings more accurate. Here is the changelog: Highlights This update makes brightness settings more accurate. This update addresses an issue that affects certain display and audio devices. They are missing after your system resumes from sleep. This update addresses an issue that affects Widgets. They unpin from the taskbar when you do not expect it. This update addresses an issue that affects virtual private networks (VPN). There might be excessive Address Resolution Protocol (ARP) requests to the network gateway. This occurs when the VPN is on a wireless mesh network that uses an aggressive throttling algorithm. Because of this, network performance is poor. Improvements This non-security update includes quality improvements. When you install this KB: New! This update affects the Handwriting Software Input Panel (SIP), the Handwriting Engine, and the Handwriting Embedded Inking Control. They now support GB18030-2022 conformance level 2. Because of this, they meet the level 3 requirements. This update addresses an issue in the Windows Notification Platform. The issue affects how much power your device uses. This update affects the Windows Push Notification Services (WNS). It makes the connection between the client and the WNS server more reliable. This update addresses an issue that affects hybrid joined devices. You cannot sign in to them if they are not connected to the internet. This occurs when you use a Windows Hello for Business PIN or biometric credentials. This issue applies to a cloud trust deployment. This update affects Windows Autopilot profiles. The process to download the Windows Autopilot policy is more resilient. This helps when a network connection might not be fully initialized. This update increases the retry attempts when you try to download the Windows Autopilot profile. This update addresses an issue that affects Event Forwarding Subscriptions. When you add an Event Channel to the subscription, it forwards events you do not need. This update addresses an issue that affects the Windows Management Instrumentation (WMI) repository. This causes an installation error. The issue occurs when a device does not shut down properly. This update addresses an issue that affects certain CPUs. There is inconsistent reporting of the L2 cache. This update enhances hinting for some of the letters of the Verdana Pro font family. This update affects user mode printer drivers. They unload unexpectedly. This occurs when you print from multiple print queues to the same printer driver. This update affects text edit controls in XAML. You cannot edit the controls again after they become read only. This occurs when you use the new Microsoft Input Method Editor for Japanese, Chinese, and Korean. This update makes Narrator announce the “Change product key” label. This update addresses an issue that affects the Defender Firewall Profile. It fails to automatically switch from a LAN that is trusted to a public network. This update makes Country and Operator Settings Asset (COSA) profiles up to date. This update addresses an issue that affects a printing job. An unexpected Internet Printing Protocol (IPP) mode switch can cause the print job to abruptly stop. This occurs when there is an independent hardware vendor (IHV) driver. This update addresses an issue that affects certain wireless wide area network (WWAN) devices. After every restart, a dialog reappears. It asks you to switch to embedded SIM (eSIM) even when you choose "No." This update addresses a deadlock in Internet Protocol Security (IPsec). When you configure servers with IPsec rules, they stop responding. This issue affects virtual and physical servers. This update addresses an issue that affects the MPSSV service. The issues causes your system to restart repeatedly. The stop error code is 0xEF. This update affects the Windows Kernel Vulnerable Driver Blocklist, DriverSiPolicy.p7b. It adds drivers that are at risk for Bring Your Own Vulnerable Driver (BYOVD) attacks. This update addresses an issue that affects Windows Defender Application Control (WDAC). The issue copies unsigned WDAC policies to the Extensible Firmware Interface (EFI) disk partition. This partition is reserved for signed policies. This update addresses an issue that affects WDAC. The “Disabled: Script Enforcement” option might create audit events you do not need. This update addresses an issue that affects the fastfat file system driver. It stops responding because of a race condition. This update addresses an issue that affects I/O over Server Message Block (SMB). It might fail when you use the LZ77+Huffman compression algorithm. If you installed earlier updates, only the new updates contained in this package will be downloaded and installed on your device. Windows 11 servicing stack update - 22621.2061 This update makes quality improvements to the servicing stack, which is the component that installs Windows updates. Servicing stack updates (SSU) ensure that you have a robust and reliable servicing stack so that your devices can receive and install Microsoft updates. Known issues - Applies to IT admins Using provisioning packages on Windows 11, version 22H2 (also called Windows 11 2022 Update) might not work as expected. Windows might only be partially configured, and the Out Of Box Experience might not finish or might restart unexpectedly. Provisioning packages are .PPKG files which are used to help configure new devices for use on business or school networks. Provisioning packages which are applied during initial setup are most likely to be impacted by this issue. For more information on provisioning packages, please see Provisioning packages for Windows. Note Provisioning Windows devices using Windows Autopilot is not affected by this issue. Windows devices used by consumers in their home or small offices are not likely to be affected by this issue. Workaround If you can provision the Windows device before upgrading to Windows 11, version 22H2, this will prevent the issue. We are presently investigating and will provide an update in an upcoming release. How to get this update: This is an optional update that only appears when you manually search for updates in the stable (production) version of Windows 11 22H2. Go to Settings > Update & Security > Windows Update. After checking for updates, in the Optional updates available area, you’ll find the link to download and install the update. You can check out the full support page here.
  16. hellowalkman
    Microsoft confirms video codec issue on Windows 10 (KB5028244) and Windows 11 (KB5027303) by Sayan Sen Microsoft has confirmed that there is an issue plaguing WVC1 or VC-1 video codec at the moment. Windows 10 and Windows 11 apps using the codec may fail to playback, record, or capture videos, and the issue extends to cameras and webcams. The bug was introduced with Windows 11 update KB5027303 and Windows 10 users with update KB5028244. On its health dashboard, Microsoft explains that the way to resolve this issue is to perform a Known Issue Rollback (KIR). After installing KB5027303 or later updates, some apps might fail to playback, record, or capture video when using the WVC1 codec (VC-1). Certain cameras or webcams might also fail to work if they use the WVC1 codec by default. Resolution: 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-managed devices that have installed an affected update and encountered this issue, it can be resolved by installing and configuring a special Group Policy. The special Group Policy can be found in Computer Configuration -> Administrative Templates -> For information on deploying and configuring these special Group Policy, please see How to use Group Policy to deploy a Known Issue Rollback. Group Policy downloads with Group Policy name: Download for Windows 11, version 22H2 - Windows 11 22H2 KB5027303 230528_03453 Known Issue Rollback Download for Windows 11, version 21H2 - Windows 11 (original release) KB5028245 230630_032045 Known Issue Rollback Download for Windows 10, version 22H2 - Windows 10 20H2, 21H1, 21H2 and 22H2 KB5028244 230627_173555 Known Issue Rollback Important: You will need to install and configure the Group Policy for your version of Windows to resolve this issue. You will also need to restart your device(s) to apply the group policy setting. Both Windows 10 (versions 21H2 and 22H2) and Windows 11 (versions 21H2 and 22H2) are affected by this bug.
  17. hellowalkman
    Microsoft finally manages to fix Windows 11 Defender Local Security Authority protection off by Sayan Sen It is somewhat common for the Patch Tuesday OS security updates to break something, and the ones for March were no different. The updates introduced an issue with the Windows Security app wherein Microsoft Defender would wrongly report that the Local Security Authority (LSA) protection was off. It affected both Windows 11 22H2 as well as 21H2. The company stated: After installing "Update for Microsoft Defender Antivirus antimalware platform - KB5007651 (Version 1.0.2302.21002)", you might receive a security notification or warning stating that "Local Security protection is off. Your device may be vulnerable." and once protections are enabled, your Windows device might persistently prompt that a restart is required. Important: This issue affects only "Update for Microsoft Defender Antivirus antimalware platform - KB5007651 (Version 1.0.2302.21002)". All other Windows updates released on March 14, 2023 for affected platforms (KB5023706 and KB5023698), do not cause this issue. Microsoft provided a workaround for the issue at that time as it was still investigating the bug. After a month passed since then, the company announced that it was able to resolve the issue and the solution was to update to Defender version 1.0.2303.27001. However, this victory of Microsoft was short-lived as the issue returned, as it never left for some, including one of Neowin forum members kiddingguy. Today, the Windows health dashboard issues section was updated by the tech giant as it claims that the LSA off issue has been finally resolved. Microsoft says that the Defender version 1.0.2306.10002. Essentially, all you need to do is update to the latest version of Windows Security app via the Windows Update, and the issue should go away. Microsoft writes: Resolution: This issue was resolved in an update for Windows Security platform antimalware platform KB5007651 (Version 1.0.2306.10002). If you would like to install the update before it is installed automatically, you will need to check for updates. You can discuss the issue on this thread on our forum. Also, let us know in the comments below if you are still affected by the LSA bug even after applying the update.
  18. hellowalkman
    Microsoft cautions that Patch Tuesday Windows kernel bugfix could break something by Sayan Sen It was the second Tuesday of the month this week and as such, Microsoft released Patch Tuesday updates on Windows 10 (KB5027215, among others), and Windows 11 (KB5027231). The update addressed security issues, among other bugs, and as is often the case, there are major bugs affecting it as well. On Windows 11, Patch Tuesday was causing Malwarebytes to go a bit haywire and block Google Chrome. Meanwhile, users reported that Windows 10 update is having installation issues. While at the time of writing this article, Microsoft is yet to confirm and document either of these bugs, the company has announced that a kernel patch that was released on all versions of Windows, both 10 and 11, has the potential to break the OS. This issue was being tracked under ID "CVE-2023-32019". The patch notes on the update read: This update addresses an issue that affects the Windows Kernel. This issue is related to CVE-2023-32019. Microsoft gave additional information about the issue on a knowledge base support document on its website. However, since the release of the update, the company has added a portion to the support page which adds that the change has been disabled by default with an option added to enable it. The company explains: IMPORTANT The resolution described in this article introduces a potential breaking change. Therefore, we are releasing the change disabled by default with the option to enable it. In a future release, this resolution will be enabled by default. We recommend that you validate this resolution in your environment. Then, as soon as it is validated, enable the resolution as soon as possible. Here is a summary of the vulnerability as provided by Microsoft: An authenticated user (attacker) could cause an information disclosure vulnerability in Windows Kernel. This vulnerability does not require administrator or other elevated privileges. The attacker who successfully exploits this vulnerability could view heap memory from a privileged process that is running on the server. Successful exploitation of this vulnerability requires an attacker to coordinate the attack with another privileged process that is run by another user in the system. You can find the support document on Microsoft's site under KB5028407.
  19. hellowalkman
    Microsoft's latest Windows 11 Patch Tuesday causes Malwarebytes to block Google Chrome by Sayan Sen Yesterday was the second Tuesday of the month and as expected, Microsoft released Patch Tuesday updates on Windows 10 (KB5027215, among others), and Windows 11 (KB5027231). Although undocumented by Microsoft in the known issues section, the latter seems to be causing issues in accessing and launching Google's Chrome web browser for users with Malwarebytes anti-virus. A user with the name codesmitery posted the following complaint on the Malwarebytes forum: Updating to June 2023 Update (KB5027231) prevents Google Chrome from displaying after loading. Chrome will be listed in the task manager but you cannot get it to display. The only thing you can do is quite [sic] Malwarebytes. If you are wondering whether Windows 10 is affected as well, it seems to not be the case as a user Porthos points out that their Windows 10 system is not experiencing the same bug: That is ok. Staff responded with a workaround. I have Windows 10 and have no current issues with Chrome. Seems to be an 11 issue. A Malwarebytes staff with the username Arthi confirmed that they are looking at the issue and provided a couple of workarounds. One of those involves setting Chrome as the default browser while the other option is to disable protection for Chrome in Malwarebytes: Thanks for posting. Like you mentioned this issue is being reported to us since today's windows update, we are looking into it. As a workaround, there are a couple of options that have internally worked for us Try setting Chrome as a default browser OR Turn off Chrome as a protected application in the Malwarebytes product. you can find this in Settings->Security tab Other users have found that disabling "exploit protection" also works in case the above official workarounds don't work. Another Malwarebytes employee with the username Erix has stated that the firm is working on an update that will address the issue. They write: Ladies and gentlemen, We are currently working on an update that will address this problem. Thank you so much. -Erix We will keep you posted about the issue when there is any new development. Thanks for the tip! Update: Malwarebytes staff, username msherwood, has published more details regarding the issue, adding that Nebula and OneView are also blocking Chrome from launching: Issue On June 13, 2023, Microsoft’s KB5027231 update installed on Windows 11 caused a conflict between Google Chrome and exploit protection, resulting in browser crashes. Devices Windows 11 Nebula OneView Cause The cause is being investigated. Workaround As a workaround, we recommend disabling Google Chrome as a protected application in your Malwarebytes security settings. On your device, open Malwarebytes. On the top right, click the Settings wheel. Click the Security tab. Under Exploit Protection, click Manage protected applications. Toggle off Google Chrome (and plug-ins). Click Done. Once this issue is resolved, go back and enable Google Chrome as a protected application in your Malwarebytes security settings. Update 2: Malwarebytes has provided an update. As promised, the firm has managed to resolve the issue with the latest update which is now available as beta: Want to share an update on where we're at with this issue and what you can do right now to resolve the issue. Malwarebytes 4 We've got a fix ready via a beta build as well as we're working on something a bit more automated and we'll share that tomorrow. To get the beta build, please do this: Open Malwarebytes -> look for the Settings gear in the top right -> General -> scroll down and enable beta updates Then, go to About -> Check for updates and follow the updating prompts To verify you're on the correct beta build, go back to Settings -> About and look for these: Malwarebytes version: 4.5.31.270 Component version: 1.0.2047 or higher If you don't want to install the Beta build, you can use the workarounds provided above.
  20. TarasBuria
    Microsoft temporarily fixed broken webcams on ARM PCs by lowering their image quality by Taras Buria Last week, Surface Pro X owners suddenly discovered that their ARM-powered computers could no longer use cameras and camera-related features, such as Windows Hello. Any attempt to open an app utilizing integrated cameras resulted in the "0xA00F4271 (0x80004005)" error. Fortunately, Microsoft deployed a temporary fix relatively quickly, albeit not without a huge asterisk. The updated Windows Release Health dashboard contains all the details about the issue that crippled cameras in ARM-based Windows PCs. According to Microsoft, the bug affects devices with Qualcomm 8cx Gen 1, Gen 2, Microsoft SQ1, and Microsoft SQ2 processors running Windows 11 version 22H2 and 21H2, and Windows 10 22H2. In other words, it is not Surface-exclusive. At the same time, external USB cameras continue operating without issues. A few days ago, users started reporting that integrated cameras work again, thanks to Microsoft deploying a "critical troubleshooter" to mitigate the issue on most affected Windows devices. That troubleshooter kicked in automatically and did not require any action from the user. You can check your ARM-powered PC by looking for the following entry in the troubleshooting history: Hardware and devices troubleshooter Automatically change system settings to fix a problem on your device Although cameras are working again, Microsoft says the mitigation is temporary. Moreover, the fix is not available on managed devices, with troubleshooters disabled by administrators. Resolving the camera bug on those PCs requires executing the following command with administrator privileges: reg add "HKLM\SYSTEM\CurrentControlSet\Control\Qualcomm\Camera" /v EnableQCOMFD /t REG_DWORD /d 0 /f You can use the Command Line method on a non-managed device if it has not yet received the critical troubleshooter. However, Microsoft warns that it is intended for the affected devices only, so do not mess with your system's registry if the integrated cameras are working. Another thing worth noting is that the workaround has a side effect: Microsoft says it might disable some camera features or lower the image quality. The company is working with OEMs on a new camera driver to bring cameras back to their normal behavior.
  21. hellowalkman
    Microsoft: File copy/save on Windows 11, Windows 10 32-bit apps failing, Office affected too by Sayan Sen Microsoft has warned IT and system admins that a file copying, saving, and attaching issue is affecting applications on Windows 11 as well as Windows 10. Thankfully, File Explorer is unaffected, however, 32-bit applications are. Microsoft says that 32-bit apps that are large address aware and use the CopyFile API are affected. This API essentially helps copy a new file to an existing file and keeps track of the progress. Hence, with this functionality broken at the moment, copying and saving have become a major issue at the moment for affected applications. Microsoft has also added that 32-bit versions of Office apps like Word and Excel are affected as well, and users may receive a "Document not saved" error. Microsoft explained the issue in detail on its Windows health support page: You might have intermittent issues saving, or copying, or attaching files using 32-bit apps which are large address aware and using the CopyFile API. Windows devices are more likely to be affected by this issue when using some commercial/enterprise security software which uses extended file attributes. We are not receiving reports that copying files using File Explorer is affected, but CopyFile API used within apps might be affected. Microsoft Office apps such as Microsoft Word or Microsoft Excel are only affected when using 32-bit versions and you might receive the error, "Document not saved." This issue is unlikely to be experienced by consumers using Windows devices in their home or on non-managed comercial device. Note: Apps are not affected by this issue if they are 64-bit or 32-bit and NOT large address aware. There is a positive though. Microsoft says the issue is intermittent which means redoing the same action could likely work out. The company lists this as a potential workaround: Workaround: To mitigate the issue, you can attempt to save or copy again. Since the issue is intermittent, it is likely to succeed on a subsequent try. The above workaround is only for Windows 11 22H2 though. For other versions of Windows 11 and Windows 10, Microsoft recommends doing a known issue rollback (KIR): Workaround: To mitigate the issue, you can attempt to save or copy again. Since the issue is intermittent, it is likely to succeed on a subsequent try. Important: If the resolution below does not resolve intermittent save or copy issues in your environment, then you might be experiencing a different issue with similar symptoms. Resolution: This issue is resolved using Known Issue Rollback (KIR). Enterprise-managed devices that have installed an affected update and have encountered this issue can resolve it by installing and configuring a special Group Policy. The special Group Policy can be found in Computer Configuration -> Administrative Templates -> . Group Policy downloads with Group Policy name: Download for Windows 11, version 21H2 - KB5023774 230222_032017 Known Issue Rollback Download for Windows 10, version 22H2; Windows 10, version 21H2 - KB5023773 230222_032013 Known Issue Rollback Important: You will need to install and configure the Group Policy for your version of Windows to resolve this issue. In somewhat related news, Microsoft recently resolved a SMB file copy issue on Windows 11 21H2 with the KB5026436 preview update.
  22. hellowalkman
    Microsoft: We haven't yet been able to fix Start, UWP, Office issues on Windows 11 and 10 by Sayan Sen Microsoft announced that it managed to mitigate a major issue that affects the Windows Shell on all versions of Windows 10 and Windows 11. The bug, confirmed back in January, is related to the Windows Shell and Office APIs. On the Windows health website, Microsoft notes that the Start menu, Windows search bar, and Universal Windows Platform (UWP) apps may fail to open or have issues. Essentially it becomes un-clickable or non-interactive. The tech giant further notes that affected PCs can exhibit damaged registry keys or data that can affect applications based on the Microsoft Office APIs, that are integrated with Windows, Office, Outlook or Outlook Calendar. The workaround is to uninstall such apps, which is hardly awe-inspiring considering it has been four months since the issue was first opened. It writes: The Start menu, Windows search, and Universal Windows Platform (UWP) apps might not work as expected or might have issues opening. Affected Windows devices might have damaged registry keys or data which might affect apps using Microsoft Office APIs to integrate with Windows, Microsoft Office, or Microsoft Outlook or Outlook Calendar. An example of an app affected by this issue is ClickShare. The underlying Issue is not caused by the installation of an update to Windows and might be exposed by an update to an affected app. Workaround: To mitigate this issue, you can uninstall apps which integrate with Windows, Microsoft Office, Microsoft Outlook or Outlook Calendar. Updates to affected apps or guidance from the developer of the app might also be available. If you are using ClickShare by Barco, please see Symptom: Start Menu and other shell components fail when Apps including Barco's ClickShare access Office APIs and Unresponsive Windows taskbar or user shell folder permissions issues with ClickShare App Calendar integration. You may find more details on Microsoft's Windows health website here.
  23. hellowalkman
    Microsoft admits it couldn't really fix Windows 11 Security and Defender LSA issues by Sayan Sen Towards the end of March, Microsoft confirmed a Windows 11 issue where the Windows security app would incorrectly display "Local Security Authority protection is off", even when the feature was enabled. The company provided a workaround for the time being. Almost exactly a month later, the tech giant announced that it had fixed the issue. However, Microsoft may have been too quick to close the bug report. Neowin forum member kiddingguy, among others, noticed that the problem continued to persist even after they installed the latest Patch Tuesday. In fact, the latest update also apparently has other bugs according to various user reports online. Image via kiddingguy (Neowin forum) Microsoft has hence been forced to re-open the issue on its Windows Health dashboard. A new section has been updated that says affected users will need to use the workaround previously published. The Redmond company has also recommended disabling kernel-mode hardware-enforced Stack protection in case users were encountering blue screen or system restarts. Updated May 16, 2023: This known issue was previously resolved with an update for Microsoft Defender Antivirus antimalware platform KB5007651 (Version 1.0.2303.27001) but issues were found, and that update is no longer being offered to devices. If you encounter this issue, you will need to use the above workaround until the issue is resolved. If you have installed Version 1.0.2303.27001 and receive an error with a blue screen or if your device restarts when attempting to open some games or apps, you will need to disable Kernel-mode Hardware-enforced Stack Protection. To do this, select the Start button, type Windows Security and select it, select Device Security then select Core Isolation then disable Kernel-mode Hardware-enforced Stack Protection. You may find more details on Microsoft's official Windows health dashboard site.
  24. hellowalkman
    Windows 11 KB5026372 fails to install with 80070002, 0x800f081f errors, VPN issues too by Sayan Sen Last week, Microsoft released Patch Tuesday updates on Windows 10 (KB5026361), Windows 11 (KB5026372), and Servers. The Windows 11 update (KB5026372), however, is causing various issues on user systems. Many users are reporting that the update itself is failing to install. Typically, affected users are reporting about two error codes accompanying the installation failures. These are 0x800f081f, and 80070002, though a user "Federico Z" on Feedback Hub has also added the "8007054F" error to the list. The 0x800f081f is apparently a Deployment Image Servicing and Management (DISM) issue and seems to be happening to more people. Over on a thread by Srihan Tiwari on the Microsoft forum, the question has been upvoted by 37 using the "I have the same question" option. Meanwhile, the second most common error seems to be the 80070002 code. 9 people have upvoted this query. Over on the Reddit thread for the KB5026372 update, users noticed that Microsoft has reintroduced broken Security app wherein half the stuff does not work. ThorneBearer writes: Ooh, very nice. The broken grey and black boxes are back in windows security! And TPM detection and core isolation settings are still broken just as they have been for months! Neowin user kiddingguy, among others, are also continuing to see LSA is turned off bug, even though Microsoft says it fixed the issue. Another fairly common issue seems to be related to VPN where affected users are saying Layer 2 Tunneling Protocol (L2TP)/ IPSec (Internet Protocol Security) protocol has been broken by the latest Patch Tuesday. Meanwhile, users say the SSD speed degradation issue still remains. This bug was seemingly introduced back with the March Patch Tuesday.
  25. hellowalkman
    Latest Windows 11 and 10 Patch Tuesdays are trying to coax Chrome users to switch to Edge by Sayan Sen via Vivaldi It is probably not unfair to say that Microsoft really wants people to use its Edge web browser. The company has often adopted somewhat desperate means to coax more users into trying Edge and choosing it as their default browser. Just considering the Windows 11 era, the company first came under fire due to the way it set up the default app options as it was seemingly quite tedious to go through the process. There have been aggressive ads and promotions as well, like the time Microsoft called Google Chrome "so 2008" and suggested that Edge was more secure than Chrome. This kind of ad once again appeared when trying to download Chrome, only this time it took up the full screen instead of being just a tiny prompt in the corner up top, which kind of showed how much it wants users to notice it exists. And of course, from time to time Edge also wants you to choose it as the default browser. And if you thought Microsoft would try and pull something similar sooner rather than later, you'd be absolutely right. According to user reports online, the latest April Patch Tuesday updates for both Windows 11 and Windows 10 are now triggering the Default Apps Settings page when a web link is opened with Google Chrome. Hence when a user is opening a link with Chrome, the default app settings is trying to make users want to switch over to Edge instead. Joris Geutjes posted this issue on the Google Chrome forum: Since today, we have noticed on several Windows 10 users (version 22H2 with the latest updates from Microsoft that they released on patch Tuesday of April 11, 2023) that when starting the Google Chrome browser, the Default Apps settings are opened every time. We have already set Google Chrome as the default browser several times. But that makes no sense at all. Restoring all Google Chrome default settings also has no effect. Even uninstalling Google Chrome and reinstalling it does not provide a solution. The issue is pretty widespread. It seems as if 387 people have upvoted this by choosing the "I have the same question" option. Over on the Microsoft forum, a user Todd Fuhrman1 posted the same question and it too has been upvoted by 87 people. On the same Google forum thread, a user offers a solution which is basically to uninstall the updates (Windows 11 22H2: KB5025239, Windows 11 21H2: KB5025224, and Windows 10: KB5025221). This seems to resolve the issue, indicating that Patch Tuesday indeed messed something up, perhaps even deliberately. Via: Gizmodo