Search the Community
Showing results for tags 'windows 10 bugs'.
Found 11 results
-
Microsoft: We are working on KB5034441/KB5034440 "0x80070643 - ERROR_INSTALL_FAILURE" fix
hellowalkman posted a topic in Front Page News
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. -
Microsoft acknowledges it's not HP who's auto-installing printer Smart app on your Windows
hellowalkman posted a topic in Front Page News
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. -
As Microsoft also pushes it to Windows 10, buggy Copilot puts the brakes on Windows 11 23H2
hellowalkman posted a topic in Front Page News
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. -
Microsoft puts little blame on its Windows update after UNSUPPORTED PROCESSOR BSOD bug
hellowalkman posted a topic in Front Page News
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. -
Microsoft investigates Windows (KB5029351, KB5029331) Unsupported Processor BSOD crashes
hellowalkman posted a topic in Front Page News
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. -
Microsoft: Windows 10 (KB5028244) app installs via ClickOnce incorrectly nagging users
hellowalkman posted a topic in Front Page News
Microsoft: Windows 10 (KB5028244) app installs via ClickOnce incorrectly nagging users by Sayan Sen Towards the end of July, Microsoft released KB5028244, its C-release non-security update for the month. The update was one which brought in multiple issues like those related to UWP and Win32, BitLocker, printers, and more. Find the full release notes of the update in its dedicated post. However, the update wasn't flawless as Microsoft confirmed a major bug that was causing video codec issues, and Windows 11 was affected too. Today, the tech giant has confirmed another bug in the update. Microsoft says that applications installed via ClickOnce are incorrectly showing as not installed. Microsoft has issued a known issue rollback for this bug. On its health dashboard, Microsoft explains the bug in detail as well as its workaround: After installing KB5028244 or later updates, apps which were deployed using ClickOnce might begin to prompt for installation even when the ClickOnce apps are already installed and marked as “trusted”. Workaround: To temporarily workaround the issue, uninstall the impacted ClickOnce Application and reinstall the application again. 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 can be resolved 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 10, version 22H2; Windows 10, version 21H2 - Windows 10 20H2, 21H1, 21H2 and 22H2 KB5028244 230814_02353 Feature Preview Important: You will need to install and configure the Group Policy for your version of Windows to resolve this issue. You can find the official announcement post here on the health dashboard site. -
Microsoft confirms Patch Tuesday broke OneDrive on Windows 10 22H2, and more
hellowalkman posted a topic in Front Page News
Microsoft confirms Patch Tuesday broke OneDrive on Windows 10 22H2, and more by Sayan Sen While Patch Tuesday is meant to deliver important security updates, it can often times lead to big issues elsewhere. With October's Patch Tuesday update on Windows 10, Microsoft has confirmed that OneDrive is broken, as in, it closes unexpectedly. Microsoft has described the issue in detail below alongside the affected platforms: After installing KB5018410 or later updates, OneDrive might unexpectedly close, and you might receive an error when attempting to do the following: Sign out or unlink your account in the Microsoft OneDrive sync app. Unlink sites or folders from syncing to your device from Microsoft SharePoint or Microsoft Teams sites. Uninstalling the OneDrive sync app might fail. Note: These issues might affect both OneDrive and OneDrive for Business [..] Affected platforms: Client: Windows 10, version 22H2; Windows 10, version 21H2; Windows 10, version 21H1; Windows 10, version 20H2 Server: None Microsoft, at this point in time, has not provided a solution or workaround for the issue. The company says it is investigating and expects to roll out a fix in the upcoming week. It writes: Next steps: We are working on a resolution and estimate a solution will be available in the coming week. This is the second major bug with this month's Patch Tuesday as previously, Microsoft had confirmed network issues related to TLS/SSL handshake failure. -
Microsoft issues fix for broken input indicator and language bar on Windows 10
TarasBuria posted a topic in Front Page News
Microsoft issues fix for broken input indicator and language bar on Windows 10 by Taras Buria 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 Store apps failed to install on Intel 11th, 12th Gen and AMD Ryzen 5000, 6000 PCs
hellowalkman posted a topic in Front Page News
Microsoft Store apps failed to install on Intel 11th, 12th Gen and AMD Ryzen 5000, 6000 PCs by Sayan Sen Microsoft has released an important out-of-band (OOB) update which resolves an issue that was leading to app installation failures from the Microsoft Store with an error code "0xC002001B". The issue was arising after installing the KB5011831 Windows 10 build. Microsoft has determined that the issue was plaguing modern Intel and AMD CPU systems which supported the Intel Control-flow Enforcement Technology (CET) or the AMD equivalent Shadow Stack technology (via TechBeezer). CET helps to mitigate Return-oriented Programming (ROP) exploits or CALL/JMP-oriented programming (COP/JOP) exploits. The affected CPUs include Intel 11th Gen Tiger Lake chips, as well as 12th Gen Alder Lake CPUs. On the AMD side, the Zen 3 Ryzen 5000 and the latest Zen 3+ Ryzen 6000 series CPUs are affected. The Microsoft advisory says: After installing KB5011831 or later updates, you might receive an error code: 0xC002001B when attempting to install from the Microsoft Store. Some Microsoft Store apps might also fail to open. Affected Windows devices use a processor (CPU) which supports Control-flow Enforcement Technology (CET), such as such as 11th Gen and later Intel® Core™ Processors or later and certain AMD processors. Resolution: This issue was resolved in the out-of-band update KB5015020. To download the OOB update KB5015020 which fixes this issue, head over to the Microsoft Update Catalog page at this link. -
Latest Windows 10 1909 update prevents some users from logging into Microsoft 365 apps
Abhay V posted a topic in Front Page News
Latest Windows 10 1909 update prevents some users from logging into Microsoft 365 apps by Abhay Venkatesh Microsoft has acknowledged that the latest Patch Tuesday updates for Windows 10 version 1909 (November 2019 Update) has a bug that is preventing some users from logging into some Microsoft 365 suite of desktop apps like Teams, Outlook, or OneDrive for Business. The company updated the knowledge base article KB5003169 (spotted by BleepingComputer) to detail the issue and provide a possible workaround. It has also updated the known issues documentation for that version of the OS on the release health information page. The Redmond firm notes that some users might be served with a “We ran into a problem. Reconnecting…" message or an error code '80080300' when trying to log into the mentioned apps post the restart initiated by the update. The issue might be resolved for some through a simple second system restart. However, the trick might not work for all users facing the issue. The company recommends that those users log into the web versions of the offerings or the clients on other operating systems, if possible, since those are currently not affected by the bug. The firm says that it is investigating the issue and that it will provide an update in the “upcoming release”. It is not clear if this means that a possible fix might be made available via an out-of-band update as soon as it is ready or if it could be served as part of the optional C/D releases later in the month. Windows 10 version 1909 is no longer supported for consumers and will only be serviced for users running Enterprise and Education SKUs. While the OS is currently running on around 11% of total Windows 10 PCs, the holdouts are likely enterprise customers, who will especially be affected by the issues caused by this month’s Patch Tuesday updates. Currently, those affected can switch to the web versions of the offerings, which is the only known workaround. Have you been facing issues with logging into the productivity apps? Let us know in the comments below! -
Microsoft releases additional updates to resolve some more printer problems
hellowalkman posted a topic in Front Page News
Microsoft releases additional updates to resolve some more printer problems by Sayan Sen Microsoft's Patch Tuesday update for March, which was released on the 9th of the month, introduced several printer-related problems, including in some cases a Blue Screen of Death (BSOD), when trying to print as a result of driver conflicts. The company was quick to acknowledge the issues and also provided a temporary workaround for the problem. A few days later on March 15, Microsoft released an official out-of-band cumulative update to fix the issues causing such BSODs. Today, the firm is releasing more such updates related to printers, although this time these updates are meant to resolve problems and errors related to printing graphical content and such, which were potentially also introduced with the March 9 Patch Tuesday update. Here's how Microsoft describes the newly identified problem: Affected devices might receive unexpected results when printing from some apps or to some printers. Issues might include missing or solid color graphics, misalignment/formatting issues, or printing of blank pages/labels. The updates should be available - as optional - to users on Windows 10 versions 1507, 1607, 1803, 1809, 1909, 2004, 20H2, and Insiders on 21H1, but Microsoft recommends you to proceed with the update only if you're affected by the problem. The list of updates with their corresponding compatible Windows version is given below: Windows 10, version 20H2 and Windows Server, version 20H2 (KB5001649) Windows 10, version 2004 and Windows Server, version 2004 (KB5001649) Windows 10, version 1909 and Windows Server, version 1909 (KB5001648) Windows 10, version 1809 and Windows Server 2019 (KB5001638) Windows 10, version 1803 (KB5001634) Windows 10, version 1607 and Windows Server 2016 (KB5001633) Windows 10, version 1507 (KB5001631) Microsoft says that more updates for the remaining affected versions of Windows will also be releasing very soon. To update, you can either go to the Windows settings' Update & Security section and look for the optional updates, or you can also visit the Windows Update Catalog website and download the particular update version compatible with your OS version.