KB4493436 fixes memory leak issues and touchscreen bugs


Milan Stanojevic
by Milan Stanojevic
Deputy Editor
Loading Comments

install KB4493436

Microsoft is back with this month’s second batch of updates for various Windows 10 versions. The Redmond giant just released KB4493436 for Windows 10 version 1703. This release bumps the build number to 15063.1784. 

The update didn’t come with any new features but it brought some useful Japanese Era format changes and fixes.

  • Download KB4493436

What’s new in KB4493436?

IE download bug fix

Previously, Internet Explorer was blocking a sub-resource download. Microsoft fixed the issue in the latest release.

Japanese Era fixes

KB4469068 brought issues regarding Japanese Eras formats. The CALDATETIME structure was unable to handle more than four Japanese Eras. The latest update resolved the bug.

ShellExperienceHost.exe bug fix

Previously, a bug was forcing ShellExperienceHost.exe to stop working. Update KB4469068 fixed the issue as well.

Win32kfull.sys fixes

Win32kfull.sys triggered the error 0x3B_c0000005_win32kfull!vSetPointer when the driver accessed an invalid memory location. You should no longer encounter this problem after installing the latest updates.

Touch screen issue fixed

Some users reported that their touch screen stopped working after rebooting their devices. The recent update fixed the issue with the touch screen.

LSASS.exe memory leak bug fixed

Systems with cached logon enabled were previously experiencing a memory leak in LSASS.exe. This issue targeted servers that deal with various interactive logon requests.

Start menu settings issue fixed

KB4493436 fixed an issue for some users who lost their customized Start menu settings after installing a previous build.

KB4493436 bugs

Thankfully, KB4493436 brought a single known issue to the table. Microsoft warns Windows 10 users that some specific operations performed on CSV may fail. 

Microsoft recommends its users to try the following workarounds to fix the bug on their systems:

  • Perform the operation from a process that has administrator privilege.
  • Perform the operation from a node that doesn’t have CSV ownership.

However, this is a temporary workaround and the company promises to address the issue in the next update.

RELATED ARTICLES YOU NEED TO CHECK OUT: