The latest Windows 10 update can make your printer crash your PC

The latest Windows update is creating issues for some printer owners and leading to the PC crashing.

Microsoft is aware that attempts to print anything from a Windows machine post the latest update is blue screening the PC and has listed the bug on Windows 10 support page. (Wikipedia )

If you own a printer and are on a Windows machine we have some bad news for you. The latest Windows update has been causing problems for some people and users have been reporting that they are getting the blue screen when they try to open a print dialogue from Office or Notepad or any other program. Users are getting to see error messages like - “Your PC ran into a problem and needs to restart”.

Now, Microsoft is aware that attempts to print anything from a Windows machine post the latest update is blue screening the PC and has listed the bug on Windows 10 support page. However, they do not have a fix for this at the moment. “We are presently investigating and will provide an update when more information is available,” the website states.

At this point in time it is not clear how widespread the issue is but according to Windows Latest there are numerous reports of errors and the bug seems to have impacted printers of multiple brands. One reader told Windows Latest that there have been at least 20 confirmed cases from four different clients an hour into his day.

Windows users have been complaining about this issue on Reddit too. One Reddit user mentioned that the issue was confirmed across four computers. Another person said that they got three calls from clients experiencing the same issue.

If you are getting blue screened post the latest update the easiest fix for now is to roll back to the last update. For this,

- Go to Settings

- Click on Update & Security

- Click on Windows Update

- Go to View Update History

- Now, click on Uninstall Updates and uninstall or you can remove the patch manually in Command Prompt.

Some Reddit users have said that this workaround has fixed their problem.

There is also a Reddit user claiming to be a Microsoft employee who has posted two temporary workarounds. One is to enable direct printing in the Command Prompt, or use the Compatibility Administrator tool to apply a fix depending on the application you are running.

Both these workarounds are a little complicated though, so read the instructions carefully.