Improvements and fixes

---

This update includes quality improvements. No new operating system features are being introduced in this update. Key changes include:

• Addresses an issue in Microsoft Edge that fails to trigger the focusin event if the focus event listener of an element shifts focus to another element.
• Addresses an issue that may prevent some applications from displaying the Help (F1) window correctly.
• Addresses an issue that may cause an application to stop working when converting long Kana to Kanji using a combination of predictive and non-predictive input.
• Addresses an issue in a multi-monitor configuration that causes a window to unexpectedly move to a different monitor when reconnecting to an existing user session.
• Addresses an issue in which the desktop wallpaper image set by a group policy will not update if it has the same name as the previous image.
• Addresses an issue that causes BitLocker Network Unlock to fail on generation 2 virtual machines when it’s used in a network that only supports IPv4.
• Addresses an issue that causes catalog signed scripts, including those shipped as part of Windows, to incorrectly generate a Windows Defender Application Control (WDAC) failure audit event.
• Addresses an issue that causes Scheduled Tasks created in a disabled state to not run.
• Addresses an issue that prevents you from overwriting a file in a shared folder because of an Access Denied error when a filter driver is loaded.
• Addresses an issue that may cause third-party applications to have difficulty authenticating hotspots.
• Addresses an issue that may cause a blue screen to appear when a Thunderbolt storage device is attached.
• Addresses an issue that may display the error code “0x139” for the RNDISMP6!KeepAliveTimerHandler when connecting to a Remote Network Driver Interface Specification (RNDIS) device.
• Addresses an issue that throws an exception when instantiating SqlConnection after you install the August Preview of Quality Rollup or September 11, 2018 .NET Framework update.
• Addresses an issue that fails to recognize the first character as the abbreviation for the Japanese Era name. For more information, see KB4469068.

If you installed earlier updates, only the new fixes contained in this package will be downloaded and installed on your device.

Known issues in this update

---

Symptom	Workaround
Applications that use a Microsoft Jet database with the Microsoft Access 97 file format may fail to open if the database has column names greater than 32 characters. The database will fail to open with the error, “Unrecognized Database Format”.	Use one of the following options: Option 1: Modify the database to ensure that all column names are less than or equal to 32 characters. Option 2: Convert the database to the .accdb file format. To use the .accdb file format, you must change the Connection string after conversion. The easiest way to convert is to use Microsoft Access 2010 or earlier. Use Microsoft Access to open a database that has an older file format. You will be asked if you would like to convert. Click Yes and save the database with the .accdb extension. Option 3: Convert the database to a newer .mdb file format. This doesn’t require a change to the Connection string. Use Microsoft Access to open a database that has an older file format. You will be asked if you would like to convert. Click Yes and save the database with the .accdb file extension. Open the .accdb. From the File menu, click Save as and select Access 2002-2003 Database. Microsoft is working on a resolution and estimates a solution will be available early February.
After installing KB4480978, some users report that they cannot load a webpage in Microsoft Edge using a local IP address. Browsing fails or the webpage may become unresponsive.	Open the Control Panel and select Internet Options. On the Security tab, select the Trusted Sitesicon. Select the Sites button. Clear the check box for Require server verification (https:) for all sites in this zone. In the Add this website to the zone: box, type the local IP address that failed to load, such as http://192.168.0.1. Select the Add button. Select the Require server verification (https:) for all sites in this zone check box. Select the Close button. Select the OK button. Restart Microsoft Edge. Microsoft is working on a resolution and will provide an update in an upcoming release.