Category: Windows Server

Have you experienced your computer bluescreening when printing to a Kyocera, Ricoh or Dymo printer?

Over the past week we have had many clients experiencing the infamous Bluescreen of Death (BSOD) when they have attempted to print, and this is a known issue with a Windows Update that was rolled out last week to Windows 10 computers.

The windows updates were released on Tuesday last week, and affect both client and server Windows versions including Windows 10 version 20H2, Windows 10 version 2004, Windows 10 version 1909, Windows 10 version 1809, Windows Server version 20H2, Windows Server version 2004, Windows Server version 1909 and Windows Server version 1809.

The updates causing the blue screens when printing are:

  • KB5000802
  • KB5000808
  • KB5000822
  • KB5000809


How can you fix this?

Microsoft has since released updates to fix the Windows 10 blue screens when printing as optional updates to install via Windows Update. To install these manually you will have to open Windows Update from your settings and ‘Check for updates’, and you will then be able to directly click a link to download and install the optional update.

The optional updates to fix this issue are:

  • KB5001567 for Windows 10 version 2004/20HT
  • KB5001566 for Windows 10 version 1909
  • KB5001568 for Windows 10 version 1809 enterprise/education/LTSC 2019
  • KB5001565 for Windows 10 version 1803 enterprise/education


If you are experiencing this problem, and can’t fix it get in touch with us today and we’d be happy to help you out!

We had a problem recently where we replaced the external backup drives on a client’s 2008 r2 server with a new suite of Samsung m3 portable 2tb USB 3.0 drives. The problem is that when the drives were plugged into the server on any USB port, they were detected as USB devices fine but did not appear in Windows Explorer. We checked in Disk Management and the drives appear ok but do not offer a drive letter. Also, the only option when right-clicking on the drive in Disk Management is to convert to a dynamic disk. There is no option to change drive letter.


After some research it was determined that the physical sector size on these drives was 4KB. Drives with physical sector size of 4KB represent the latest technology and as they are transitioning from the traditional 512 byte sectors which has existed since drives were measured in megabytes. The physical sector size represents the smallest unit that will be consumed even when the file being written is smaller. Years ago it would matter if a few Kilobytes were wasted but as the size of storage drives continually expanding, it makes sense for the physical sector size to grow too. A larger physical sector size means less error checking (ECC) required and therefore faster access.

It turns out that a lot of these Advanced Format Disk that have a 4KB physical sector size do still have the capability to be backwards compatible with 512 byte physical sector size systems. They do this by changing their logical addressing system to 512 bytes although their physical sectors remain at 4k. They are known as 512-byte emulation disks.

We did a check of the drives using FSUtil on a windows 8 machine which supports these drives natively…

Fsutil fsinfo ntfsinfo [driveletter]

It shows the Physical and logical “Bytes per sector” value. The drives we had were emulation disks.


Apparently this Server 2008 r2 had some issues seeing these drives properly. To solve this issue we installed the…

Microsoft KB 982018 – An update that improves the compatibility of Windows 7 and Windows Server 2008 R2 with Advanced Format Disks is available

and rebooted the server. The drives magically appeared with a drive letter and the correct sizing for 2tb.

The strange thing is that this update is supposed to be contained within SP1 of Server 2008 r2 which this server already had. Maybe the USB subsystem just needed to be reset in some way that this update helped with. In any case – if you are addressing this problem it might be worth a try!