Microsoft has released patch Tuesday updates for Windows 8.1 (KB5018474) and Windows 7 (KB5018454). You will need to be a customer who has purchased the Extended Security Update (ESU).
The improvements made this month for both Windows versions are the same, and the ones are the following:
This cumulative security update outlines improvements made in KB5017361 (Windows 7) and KB5017367 (Windows 8.1) (reported on September 13, 2022) and includes key changes:
The Security Update Guide for Deployments | Security Guide and the October 2022 Security Updates for more information
| Symptom | Next step |
|---|---|
After installing this update and restarting your device, you might receive the error, "Failure to configure Windows updates. Reverting Changes. Do not turn off your computer", and the update might show as Failed in Update History. | This is expected in the following circumstances:
If you have purchased an ESU key and have encountered this issue, please verify you have applied all prerequisites and that your key is activated. For information on activation, please see this blog post. For information on the prerequisites, see the How to get this update section of this article. |
To mitigate this issue, do ONE of the following:
Note This might not mitigate the issue for items that use a wildcard (*).
We are working on a resolution and will provide an update in an upcoming release. |
Next step
After installing this update and restarting your device, you might receive the error, "Failure to configure Windows updates. Reverting Changes. Do not turn off your computer," and the update may appear as Failed in Update History.
In the following situations, this is outlined.
- If you are installing this update on a device that is running an edition that is not supported for ESU. For a complete list of which editions are supported, see KB4497181.
- If you do not have an ESU MAK add-on key installed and activated.
If you have purchased an ESU key and have encountered this issue, please make sure that your key has been completed and that it is activated. This blog post can be used for information on the prerequisites.
Do one of the following tasks to mitigate this issue:
- Clear the "Run in logged-on user''''s security context (user policy option)" check box.
Note This may not mitigate the issue for items that use a wildcard (*).
- In the affected Group Policy, change "Action" from "Replace" to "Update".
- If a wildcard (*) is used in the location or destination, deleting the trailing "\" (backslash, without quotation marks) from the destination might allow the copy to be successful.
In an upcoming release, we are working on a resolution and will provide an update.
Next step
After installing this update and restarting your device, you may receive the error, "Failure to configure Windows updates. Reverting Changes. Do not turn off your computer," and the update may show as Failed in Update History.
In the following situations, this is the case.
- If you are installing this update on a device that is running an edition that is not supported for ESU. For a complete list of which editions are supported, see KB4497181.
- If you do not have an ESU MAK add-on key installed and activated.
If you have purchased an ESU key and have encountered this issue, please verify that you have applied all prerequisites and that your key is activated. This blog post is aimed at you. For more information on activation, please see the How to receive this update section.
Do one of the following things to help you avoid this issue.
- Clear the "Run in logged-on user''''s security context (user policy option)" check box.
Note This may not alleviate the issue for items that use a wildcard (*).
- In the affected Group Policy, change "Action" from "Replace" to "Update".
- If a wildcard (*) is used in the location or destination, deleting the trailing "\" (backslash, without quotation marks) from the destination might allow the copy to be successful.
In a future release, we are working on a resolution and will provide an update.
| Symptoms | Next step |
|---|---|
| After installing this update, file copies which use Group Policy Preferences might fail or might create empty shortcuts or files that have 0 (zero) bytes. Known affected Group Policy Objects are related to files and shortcuts in User Configuration > Preferences > Windows Settings in Group Policy Editor. | To mitigate this issue, do ONE of the following:
Note This might not mitigate the issue for items that use a wildcard (*).
We are working on a resolution and will provide an update in an upcoming release. |
Next step
Do one of the following activities to combat this issue:
- Clear the "Run in logged-on user''''s security context (user policy option)" check box.
Note: Certain items that use a wildcard might not be able to mitigate the issue.
- In the affected Group Policy, change "Action" from "Replace" to "Update".
- If a wildcard (*) is used in the location or destination, deleting the trailing "\" (backslash, without quotation marks) from the destination might allow the copy to be successful.
In a upcoming release, we are working on a resolution and will provide an update.
The next step is to set out.
Do one of the following things to help mitigate this problem:
- Clear the "Run in logged-on user''''s security context (user policy option)" check box.
Note This might not mitigate the issue for items that use a wildcard (*).
- In the affected Group Policy, change "Action" from "Replace" to "Update".
- If a wildcard (*) is used in the location or destination, deleting the trailing "\" (backslash, without quotation marks) from the destination might allow the copy to be successful.
In a upcoming release, we are working on a resolution and will give it an update.
Both updates will be available for their respective systems through Windows Update. If you need them to be downloaded offline, then you may download them from the Microsoft Update Catalog (Windows 7 update, Windows 8.1 update).