Microsoft adds three known issues to last week's Patch Tuesday updates for Windows

Last week was Patch Tuesday, the day when Microsoft releases updates for all supported versions of Windows. But while the updates fixed a bunch of things, they apparently also broke some things. Microsoft has added some items to the list of known issues on all of the updates.

And to be clear, that's not just for Windows 10. These issues affect Windows 7 and 8.1 as well. The two new known issues that affect Windows 7, Windows 8.1, and all supported versions of Windows 10 are the following:

Symptom	Workaround
After installing this update, Internet Explorer may fail to load images with a backslash (\) in their relative source path.	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. Microsoft is working on a resolution and will provide an update in an upcoming release.
Applications that use a Microsoft Jet database with the Microsoft Access 95 file format may randomly stop working.	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. 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. Microsoft is working on a resolution and estimates a solution will be available late February.

Symptom

Workaround

After installing this update, Internet Explorer may fail to load images with a backslash (\) in their relative source path.

Change the backslash (\) to a forward slash (/) in the relative path of the image element.

Change the relative path to the full URI path.

Microsoft is working on a resolution and will provide an update in an upcoming release.

Applications that use a Microsoft Jet database with the Microsoft Access 95 file format may randomly stop working.

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.

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.

Microsoft is working on a resolution and estimates a solution will be available late February.

Interestingly, while last month's updates broke Access 97 databases and this month's fixed them, now the issue is with Access 95 databases. Also, if you're still using Internet Explorer, the issue about not showing images could be a significant one.

There's one more known issue, and this one affects Windows 7, along with all supported versions of Windows 10 except the original, which is version 1507:

Symptom	Workaround
After installing this update, the first character of the Japanese era name is not recognized as an abbreviation and may cause date parsing issues.	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" Microsoft is working on a resolution and will provide an update in an upcoming release.

Symptom

Workaround

After installing this update, the first character of the Japanese era name is not recognized as an abbreviation and may cause date parsing issues.

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"

Microsoft is working on a resolution and will provide an update in an upcoming release.

If any of these issues sound significant and you haven't installed te updates yet, it might be best to avoid them. It's possible that they might get fixed later on this month in another round of updates.