KB5001337 has broken VB6 vertical scrollbar in Windows 10 version 1909

Anonymous
2021-04-20T12:02:28+00:00

Since KB5001337 was applied to Windows 10 version 1909, the vertical scrollbar in our VB6 application now shows as a white box instead and no events are actioned from the vertical scrollbar meaning that scrolling is now disabled on all screens that use this control.

Later versions of windows 10 have not had this update and they are all working ok.

If the update is removed then the functionality starts working again.

Is there anything our customers on this version of Windows can do apart from updating to a later version of windows.

They are all on the enterprise version of windows so will still be in service for this version of windows for the foreseeable future and they did not have any plans to immediately update their version of windows and they have a vast estate to maintain so it will give them a problem to either keep the update rolled back or to upgrade to a new version of windows.

Windows for home | Windows 10 | Install and upgrade

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2021-05-12T17:59:26+00:00

May 11, 2021—KB5003169 (OS Build 18363.1556) (microsoft.com) appears to have fixed the issue.  

  • Addresses an issue that might cause scroll bar controls to appear blank on the screen and not function. This issue affects 32-bit applications running on 64-bit Windows 10 (WOW64) that create scroll bars using a superclass of the USER32.DLL SCROLLBAR window class. This issue also affects HScrollBar and VScrollBarcontrols and classes derived from System.Windows.Forms.ScrollBar. A memory usage increase of up to 4 GB might occur in 64-bit applications when you create a scroll bar control.

Was this answer helpful?

7 people found this answer helpful.
0 comments No comments

16 additional answers

Sort by: Most helpful
  1. Anonymous
    2021-05-10T12:30:36+00:00

    We originally just uninstalled this KB to get around this issue but does anyone know if the May KB for 1909 systems will also have the same effect?

    thanks

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2021-05-07T13:38:56+00:00

    I subsequently found

    Memory usage increase after applying KB5001337 Patch - Microsoft Q&A

    which says

    Scroll bar controls might appear blank on the screen and not function after installing this update. This issue affects 32-bit applications running on 64-bit Windows 10 (WOW64) that create scroll bars using a superclass of the USER32.DLL SCROLLBAR window class. This issue also affects HScrollBar and VScrollBar controls that are used in Visual Basic 6 applications and the classes derived from System.Windows.Forms.ScrollBar that are used in .NET Windows Forms applications. A memory usage increase of up to 4 GB might occur in 64-bit applications when you create a scroll bar control.Scroll bars you create using the SCROLLBAR window class or using the WS_HSCROLL and WS_VSCROLL window styles function normally. Applications that use the scroll bar control that is implemented in COMCTL32.DLL version 6 are not affected. This includes .NET Windows Forms applications that call Application.EnableVisualStyles().

    Microsoft is working on a resolution and will provide an update in an upcoming release.

    which offers some hope.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2021-05-05T09:08:42+00:00

    I feel your pain!

    I thought I noticed that they had posted a patch for a different reported problem in the same windows update that was causing gaming performance problems and that gave me hope that they might do the same for this issue but I haven't seen anything yet.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2021-05-04T18:17:51+00:00

    We are in the exact same situation.  Thousands of machines, rollback is not feasible and no plans to update at this time to 20H2.

    Was this answer helpful?

    0 comments No comments