Bitmaps no longer visible in Edge after 1803 update (Edge 42)

Not reproducible Issue #17508742


Michael S.
May 14, 2018
This issue is public.
Found in
  • Microsoft Edge
Found in build #
Reported by 1 person

Sign in to watch or report this issue.

Steps to reproduce

Our bitmaps no longer display in Edge after the 1803 update (Edge 42). We use a BITMAPV4HEADER or BITMAPV5HEADER structure, neither of which will display in the latest Edge. They have worked on all other platforms for years, and continue to work with Chrome, Firefox, IE, Opera, Safari, and in the OS (even the latest Win10 1803). See attached example bitmap. We have one Win10 1803 system that does display the bitmaps normally, but all other test systems fail to display the bitmaps. The images load normally with 200 OK and occupy their specified width/height in the DOM, but they are not visible.


1 attachment

Comments and activity

  • Microsoft Edge Team

    Changed Assigned To to “Steven K.”

  • Hi Michael,

    I are you still seeing this behavior in the latest Windows update?  Will you provide the extended version of Windows 10 you are using?  Win + S and type “winver” and hit enter.

    Will you provide 

  • I accidentally hit submit too soon.  I wanted to see if you could provide a repro for this issue.  I loaded the image you provide into a webpage and it displayed.  I am using 17134.167.

    Appreciate the help,


  • Microsoft Edge Team

    Changed Status to “Not reproducible”

  • My test system is currently using Windows 10 Version 1803 (OS Build 17134.228)

    The problem is still reproducible using Edge 42.17134.1.0 with EdgeHTML 17.17134.

    The test image will display properly on the Windows Desktop, Internet Explorer 11, Firefox, and Chrome. It will not appear in Edge (invisible).

  • We are having a related issue and can confirm this example.

  • We are also seeing this issue. After some tests, it seems to be related to RLE encoded bitmaps (we only tested 8 bits and not 4 bits). “Raw” bitmaps seem to be OK.

You need to sign in to your Microsoft account to add a comment.

Sign in