random
"Hot News"

The printer is causing the account to crash after updating Windows 10

Home
 The printer is causing the account to crash after updating Windows 10

The new Windows 10 update has caused problems for some printer owners.

Users report a blue screen when they try to open the print dialog from Notepad, Office, or other programs.

The printer is causing the account to crash after updating Windows 10


A message appears saying: Your computer has encountered a problem and needs to restart.

Microsoft realizes that trying to print under certain circumstances can expose the computer to the problem of blue screen display with the error message.

The company listed the error on its Windows 10 support page, but it doesn't appear to have released a fix at this time.

The support page said: We are investigating at the moment and providing an update as more information becomes available.

It is not clear how widespread the problem is, but according to Windows Latest, there are several error reports that appear.

The bug appears to affect several brands of printers, including Kyocera, Ricoh, and Zebra.

When the user sends a file to print, the computer crashes completely instead of the actual print, and a blue screen of death appears with the error code APC_INDEX_MISMATCH for win32kfull.sys.

According to Windows Latest, there are at least 20 confirmed cases from 4 different clients and it is only an hour ago today.

Windows users are complaining about the problem across many social media platforms, and one user said: This problem was confirmed on four computers, while another user said: We just received 3 calls from customers, all of whom are facing the same problem.

And if you are facing this problem, the easiest solution is to roll back the latest Windows update by opening Settings> Update & Security> Windows Update> View update history, then uninstall updates and then uninstall or remove patch manually in Command Prompt.

Some users confirmed that this fixed the problem, while a user claiming to be a Microsoft employee also published two temporary solutions that are working.

You can enable direct printing at the command prompt, or you can use the compatibility admin tool to apply the fix, depending on the application you're running.
google-playkhamsatmostaqltradent