メモメモブログ

自由気ままに投稿します。

2019年1月 MSパッチ公開 Rev.5

2019/01/09:初版

2019/01/10 : Windows 7の既知の問題 2,3 を追加

2019/01/12 : Windows 7の既知の問題 2 の内容が更新されたため修正

2019/01/14 : Windows 7の既知の問題 4 を追加、見栄えを変更

2019/01/25 : Windows 10の既知の問題 2,3 を追加

==============================================

 2019年1月9日にマイクロソフトからMSパッチ(セキュリティパッチ)が公開

 

詳細はこちら↓

2019 年 1 月のセキュリティ更新プログラム (月例) – 日本のセキュリティチーム

 

セキュリティ更新プログラムガイドはこちら↓

https://portal.msrc.microsoft.com/ja-jp/security-guidance

 

各マシンに落ちてきた更新プログラムは以下より、

Windows 7

f:id:BlogJapan001:20190109205131p:plain

不具合

KB4480970

Symptom 1

After you apply this update, the network interface controller may stop working on some client software configurations. This occurs because of an issue related to a missing file, oem<number>.inf. The exact problematic configurations are currently unknown.

 

Workaround 1

  1. To locate the network device, launch devmgmt.msc. It may appear under Other Devices.
  2. To automatically rediscover the NIC and install drivers, select Scan for Hardware Changes from the Action menu.
    • Alternatively, install the drivers for the network device by right-clicking the device and choosing Update. Then choose Search automatically for updated driver software or Browse my computer for driver software.

 既知の問題1 

 これ昨年の5月?あたりから出ている不具合です、MSさん直す気ないのかしら。。。

 

Symptom 2

Some users are reporting activation failures and "Not genuine" notifications starting around January 8, 2019, or later, on volume-licensed Windows 7 KMS clients. Notifications may state:

  • "Windows is not genuine."
  • “Your computer might be running a counterfeit copy of Windows.”
  • On screen errors and logged events reference “0xC004F200 (non-genuine).”

 

Workaround 2

Note The timing of this issue coincides with the release of the January updates (KB4480960 and KB4480970) that were released on Tuesday, January 8, 2019. These events are not related.

The issue has been corrected on the backend Microsoft Activation and Validation servers. If you are affected by this issue, please follow the guidance in the Knowledge Base Help article, KB4487266.

既知の問題 2【対応済

 ライセンス認証ができない不具合のようです。

  → 修正されたようです。

 

Symptom 3

Local users who are part of the local “Administrators“ group may not be able to remotely access shares on Windows Server 2008 R2 and Windows 7 machines after installing the January 8th, 2019 security updates. This does not affect domain accounts in the local "Administrators" group.

 

Workaround 3

This issue is resolved in KB4487345.

既知の問題 3【対応済

 いまいち理解できていません(すみません)

 Adminietratorグループに属するローカルユーザーは Server 2008 R2 および Windows 7上の共有フォルダにアクセスできない って意味かな・・・?

 共有フォルダにアクセスできない不具合です。

  → 1月11日に公開された KB4487345 を適用することで修正されるようです。

     ※Windows Update から自動で適用できませんので、WindowUpdateCatalog から直接ダウンロードしインストールしてください。

 

Workaround 4

Applications that use a Microsoft Jet database with the Microsoft Access 97 file format may fail to open if the database has column names greater than 32 characters. The database will fail to open with the error, “Unrecognized Database Format”.

 

Workaround 4

Use one of the following options:
Option 1: Modify the database to ensure that all column names are less than or equal to 32 characters.
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.
Option 3: 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.
Microsoft is working on a resolution and estimates a solution will be available early February.

既知の問題 4 

 Accsess 97 形式のデータベースを使用するアプリケーションで 32文字 以上の列名が存在すると、「Unrecognized Database Format」エラーでファイルが開けなくなるようです。

 → 以下で対応可能です。

    ・32文字以上をなくす

    ・.accdbファイル形式に変換する

    ・データベースを新しい.mdbファイル形式

 

 

Windows 10 RS5 (バージョン1809) Home

f:id:BlogJapan001:20190109203002p:plain

不具合

KB4480116

Symptom 1

After installing this update, third-party applications may have difficulty authenticating hotspots.

 

Workaround 1

This issue is resolved in KB4476976.

既知の問題 1【対応済

サードパーティアプリケーションがホットスポット認証する場合の不具合らしい

1月下旬ごろに対策が出るらしい

KB4476976を適用することで修正されるようです。

 

Symptom 2

Applications that use a Microsoft Jet database with the Microsoft Access 97 file format may fail to open if the database has column names greater than 32 characters. The database will fail to open with the error, “Unrecognized Database Format”.

 

Workaround 2

Use one of the following options:
Option 1: Modify the database to ensure that all column names are less than or equal to 32 characters.
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.

  1. Use Microsoft Access to open a database that has an older file format.
  2. You will be asked if you would like to convert. Click Yes and save the database with the .accdb extension.

Option 3: Convert the database to a newer .mdb file format. This doesn’t require a change to the Connection string.

  1. Use Microsoft Access to open a database that has an older file format.
  2. You will be asked if you would like to convert. Click Yes and save the database with the .accdb file extension.
  3. Open the .accdb.
  4. From the File menu, click Save as and select Access 2002-2003 Database.

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

既知の問題 2

Accsess 97 形式のデータベースを使用するアプリケーションで 32文字 以上の列名が存在すると、「Unrecognized Database Format」エラーでファイルが開けなくなるようです。

 → 以下で対応可能です。

    ・32文字以上をなくす

    ・.accdbファイル形式に変換する

    ・データベースを新しい.mdbファイル形式

 

Symptom 3

After installing KB4480116, some users report that they cannot load a webpage in Microsoft Edge using a local IP address. Browsing fails or the webpage may become unresponsive.

 

Workaround 3

  1. Open the Control Panel and select Internet Options.
  2. On the Security tab, select the Trusted Sites icon.
  3. Select the Sites button.
  4. Clear the check box for Require server verification (https:) for all sites in this zone.
  5. In the Add this website to the zone: box, type the local IP address that failed to load, such as http://192.168.0.1.
  6. Select the Add button.
  7. Select the Require server verification (https:) for all sites in this zone check box.
  8. Select the Close button.
  9. Select the OK button.
  10. Restart Microsoft Edge.

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

既知の問題 3

[インターネットオプション] > [セキュリティ]タブ > [信頼済みサイト] > [サイト] > [このゾーンのサイト~]のチェックをOFF > [このWebサイトを~]に読み込み失敗したIPアドレスを追加 > [このゾーンのサイト~]のチェックをONに戻す > [Edge]を再起動する

 

Windows 10 RS5 (バージョン1809) Pro + Office 2010

f:id:BlogJapan001:20190109210221p:plain

不具合は上のHomeを変わらないので省略