Recently Browsing 0 members
No registered users viewing this page.
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:
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:
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.
By Rich Woods
Microsoft issues a fix for Patch Tuesday printer crashes
by Rich Woods
As always, Microsoft released new updated for all supported versions of Windows 10 on the second Tuesday of the month, a day affectionately referred to as Patch Tuesday. Unfortunately, these updates ended up being problematic in a big way, causing a bug that left users with a blue screen of death (BSOD) when they tried to use a printer.
After offering a temporary workaround over the weekend, the fix is now here in the form of an out-of-band cumulative update. In these updates, there is just one fix, which "addresses an issue that might cause a blue screen when attempting to print to certain printers using some apps and might generate the error, APC_INDEX_MISMATCH." In other words, this update is pretty straightforward.
It should be available for anyone affected - specifically those on Windows 10 versions 1803, 1809, 1909, 2004, 20H2, and Insiders on 21H1 - but it's not going to be installed automatically. If you go to Windows Update and check for updates, you'll see that there's a new optional update, which will look just like a C week update. That's the one that you'll need to fix the issue.
The regular C and D week updates will arrive later on this month, and Microsoft has already said that those are going to remove the old Edge browser, so we know they're coming. Any future cumulative updates will also include this fix.
Microsoft offers a temporary workaround for Patch Tuesday printer crashes
by Anmol Mehrotra
Earlier this week, Microsoft released a whole bunch of updates for Windows 10 users. These updates also included KB5000802 cumulative update that caused PCs to crash with 'APC_INDEX_MISMATCH' BSOD error when trying to use printers.
Yesterday, Microsoft acknowledged the issue and confirmed that the company was working on a fix for the problem. Now, it has updated the Windows Health status page to include a temporary workaround for the problem. According to Microsoft, the bug affects a subset of Type 3 printer drivers and does not affect Type 4 printers. As such, the company has shared a video for users to follow and fix the issue temporarily.
If you are unsure about the type of printer drivers you have, you can follow the steps below to check it:
Open Run by clicking Windows Search and typing "Run" or by pressing the Windows+R key. Type "printmanagement.msc" and click 'Ok'. This should open Print Management window. Now navigate to Print Servers > >Printers and you will see the list of installed printer drivers with their type listed in the adjacent column. Do note that if you get the "Windows can not find printmanagement.msc", you will need to install the service. To do that, open Windows Search and type "manage optional features" and press enter. Now click on 'Add a feature' and type 'print'. Click the checkbox next to "Print Management Console" and click on 'install'. Now, follow the aforementioned steps to determine the type of printer driver installed on your system.
Microsoft has not provided an ETA on a permanent fix, but the company is working on a solution which should be available in next couple of weeks.
Microsoft confirms Windows 10 printer crashes after Patch Tuesday updates
by João Carrasqueira
As it typically does, Microsoft unleashed an array of updates for all supported versions of Windows this past Tuesday, being that it was the second one in March, making it Patch Tuesday. Multiple Windows 10 versions received cumulative updates, and it wasn't long before issues started being reported by numerous users, claiming that they were encountering a blue screen of death (BSOD) error when trying to use printers.
Now, Microsoft has acknowledged the problems with the updates, as spotted by Windows Latest. The company has added a known issue for the updates labeled KB5000802, KB5000808, KB5000809, and KB5000822, which were the cumulative updates for Windows 10 versions 20H2, 2004, 1909, 1809, and 1803. These are all the versions still supported outside of the Long-Term Servicing Branch and the Surface Hub edition of Windows 10, called Windows 10 Team.
The new known issue reads:
Printing is a fairly basic feature of PCs, so naturally, this is an issue that will likely bother quite a few users. The error doesn't specify which printers or apps are more likely to be affected, but reports so far include brands like Kyocera, Ricoh, and Zebra. Some users have reportedly tried to fiddle with driver updates to no avail, and the only workaround right now seems to be uninstalling the update.
Microsoft has acknowledged the issue, but failed to provide a timeline for when it will be fixed, and the company simply says it will post an update when it has more information. For the time being, if you haven't installed the update yet, you may want to put updates on hold until the issue is fixed.
By Abhay V
Microsoft fixes Windows 10 chkdsk issue that corrupted disks and caused blue screens
by Abhay Venkatesh
Microsoft released the usual set of Patch Tuesday updates to supported Windows versions earlier this month. While the updates brought the usual bug fixes, improvements, and security patches, there were also known issues documented in the KB articles. However, one of the issues that wasn’t documented, which users began reporting (spotted by the Planet3DNow and Borncity), was that of a problem with the chkdsk error-checking utility.
The bug – supposedly introduced with KB4592438 – affects Windows 10 versions 2004 and 20H2, and causes the chkdsk /f command to affect file systems adversely, resulting in blue screens (BSOD) and corruption of the file system in the worst case. The issue seemingly affects SSDs and can be reproduced even when run on a virtual machine (VM). Microsoft has now acknowledged the issue, documented a workaround, and has begun rolling out a fix.
The Redmond firm has updated the list of known issues for KB4592438 and KB4586853 with a workaround for the error for those devices that are able to start up. Here are the steps that are to be performed:
The company adds that devices might run chkdsk after a restart once the steps are completed. As for the fix that prevents the error, it is currently being rolled out to "non-managed devices" - meaning consumers - and should propagate to all devices in the next 24 hours. It is not clear if the change is a server-side one, as there is no new KB article added to the update history. Enterprise-managed devices, however, can resolve the issue by installing and configuring a special Group Policy, which the company has provided here.
Source: Microsoft (1)(2) via BleepingComputer