However, Microsoft has recently acknowledged two new issues that have been reported in this cumulative updates for Windows 10. One of them is responsible for causing some serious issues in the functionality of Internet Explorer. Although these bugs do not appear very often still there is a chance that some of the users might be affected.
KB4487044 Installation Issues
1. IE Fails To Load Images
Microsoft explains the issue as those images that have a backslash () in their relative source path might not be loaded by Internet Explorer after installing the update. The company has suggested two possible workarounds for the issue. The issue can either be resolved by if the relative path of the image element contains a forward slash (/) instead of the backslash (). Secondly, changing the relative path to the full URI path also helps to get rid of the bug. The company is working to resolve the issue and a patch in the upcoming releases is expected to fix the bug.
2. Microsoft Access Issue
While this bug is responsible for randomly stopping those apps that are using Microsoft Jet database along with the Microsoft Access 95 file format. Microsoft has offered two solutions for this issue as well. The first option that is supposed to resolve the issue is converting the database to the .accdb file format. You can also convert the database to the .accdb file format. Microsoft is already working on the fix and all Windows 10 devices will be receiving the update in late February. You can automatically download KB4487044 via Windows Update. Moreover, the standalone package can also be downloaded by visiting Microsoft’s Update Catalog. Microsoft has recently suggested its Windows 10 users to replace Internet Explorer with a modern browser. The company no longer plans to release updates in the future. It is highly recommended that you should look for an alternate solution asap.
RELATED STORIES TO CHECK OUT:
Download Windows 10 February 2019 Patch Tuesday updates now Patch Tuesday updates install Candy Crush on Windows 10 PCs
Name *
Email *
Commenting as . Not you?
Save information for future comments
Comment
Δ