Search the Community
Showing results for tags 'windows 10 cumulative update kb4495667'.
Found 1 result
The AchieVer posted a topic in Software NewsMicrosoft Says Windows 10 Cumulative Update KB4495667 Causes Excel Issues Microsoft has recently acknowledged a new issue in the latest cumulative updates for Windows 10, including KB4495667 for Windows 10 October 2018 Update, or version 1809. On the official KB page of each impacted update (the full list available below), Microsoft explains that after installing these cumulative updates, using certain fonts in Microsoft Excel could break down the layout of your documents. “When using the MS UI Gothic or MS PGothic fonts, the text, layout, or cell size may become narrower or wider than expected in Microsoft Excel. For example, the layout and cell size of Microsoft Excel sheets may change when using MS UI Gothic,” the company explains. Microsoft claims it’s already working on a fix, and it expects to release it in mid-May. This means the Patch Tuesday rollout kicking off in just a few hours could bring a further update to resolve this problem.Affected cumulative updatesIn the meantime, you can very well use a different font or uninstall the update. Microsoft explains the following: “Until a resolution is released, we recommend switching to a different Japanese font, such as Yu Gothic or MS Mincho. Alternatively, you can uninstall the optional update.” The issue exists in the following updates: Windows 10 version 1809: May 3, 2019—KB4495667 (OS Build 17763.475) Windows 10 version 1803: April 25, 2019—KB4493437 (OS Build 17134.753) Windows 10 version 1709: April 25, 2019—KB4493440 (OS Build 16299.1127) Windows 10 version 1703: May 2, 2019—KB4502112 (OS Build 15063.1785) Windows 10 version 1607: April 25, 2019—KB4493473 (OS Build 14393.2941) Microsoft will release new cumulative updates for Windows 10 later today as part of the May 2019 Patch Tuesday cycle. The focus this time will be on security improvements, albeit non-security refinements will be included as well, including a possible fix for the bug detailed here. Source