Check out these bugs before installing the new update

Nov 15, 2017 09:46 GMT  ·  By

Microsoft rolled out a new batch of cumulative updates for Windows 10 a few hours ago, and while all of them installed correctly, there are users complaining about a number of issues experienced after completing deployment.

All these bugs are detailed by Microsoft in the KB page of each cumulative update, so they’re all known issues, though this is a bit unexpected given that most of them have affected previous cumulative updates as well. This means Microsoft needs more time to fix the problems, though you’d expect one month to be enough for this to happen.

In the case of cumulative update KB4048954, which is specifically aimed at the Windows 10 Creators Update, there are three different known bugs, all of which were first included in the known issues section of cumulative update KB4049370.

Known bugs and workarounds

For example, after installing this update, Czech and Arabic languages configured on your PC could be automatically switched to English in Microsoft Edge and other applications. Microsoft says it’s aware of the problem and “working on a resolution and will provide an update in an upcoming release.” The same thing was said last month, so we’ll probably have to wait a bit more for a fix.

Then, there’s a known issue affecting UWP apps. Microsoft says that in some cases, universal apps that use JavaScript and asm.js may stop working after installing this update, and this is again a problem that was first reported with an older cumulative update. In this case, a workaround is available, and you are recommended to reinstall the application completely to get it work. A bugfix is already in development, the company says.

And last but not least, KB4048954 could cause Internet Explorer 11 users with SQL Server Reporting Services to not be able to scroll through a dropdown menu using the scroll bar, despite everything working correctly using the scroll wheel. Microsoft says the problem has been reporting only on documents mode 11, so switching to document mode 10 should do the job.