Last week, Microsoft rolled out extensive February Patch Tuesday cumulative updates for Windows versions. 77 security flaws were addressed through the updates, but some have caused issues. It seems while fixing issues the updates also broke some, which Microsoft has detailed in known issues for the releases.
As Patch Tuesday roll outs are for all supported Windows platforms, the issues affect Windows 10, Windows 8.1, and Windows 7.
As usual, Microsoft has released documentation describing the known issues affecting Windows 7, Windows 8.1, and Windows 10. The company has also offered some details workarounds for users experiencing problems:
Known Issue: After installing this update, Internet Explorer may fail to load images with a backslash (\) in their relative source path.
Workaround: Change the backslash (\) to a forward slash (/) in the relative path of the image element Or Change the relative path to the full URI path.
Known Issue: Applications that use a Microsoft Jet database with the Microsoft Access 95 file format may randomly stop working.
Workaround: Option 1: 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.
Option 2: Convert the database to the .accdb file format. To use the .accdb file format, you must change the Connection string after conversion.
- 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.
Windows 10/Windows 7
Finally, Microsoft also describes an issue that is specific to Windows 7 and Windows 10, except the original (version 1507) build:
Known Issue: After installing this update, the first character of the Japanese era name is not recognized as an abbreviation and may cause date parsing issues.
Workaround: Modify the registry with the two-character abbreviation for Japanese eras as follows:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Nls\Calendars\Japanese\Eras]
- “1868 01 01″=”??_?_Meiji_M”
- “1912 07 30″=”??_?_Taisho_T”
- “1926 12 25″=”??_?_Showa_S”
- “1989 01 08″=”??_?_Heisei_H”
