
Workaround: To mitigate the issue, you can attempt to save or copy again.

Note: Apps are not affected by this issue if they are 64-bit or 32-bit and NOT large address aware. Microsoft Office apps such as Microsoft Word or Microsoft Excel are only affected when using 32-bit versions and you might receive the error, "Document not saved." This issue is unlikely to be experienced by consumers using Windows devices in their home or on non-managed comercial device. We are not receiving reports that copying files using File Explorer is affected, but CopyFile API used within apps might be affected. Windows devices are more likely to be affected by this issue when using some commercial/enterprise security software which uses extended file attributes. Perhaps we'll wake up soon and see the Mad Hatter.Saving or copying files might intermittently failĪfter installing KB5023773 or later updates, you might have intermittent issues saving, or copying, or attaching files using 32-bit apps which are large address aware and using the CopyFile API. The KB article says KB 3106932 replaces KB 3081452, which is good: As reported in comments to my story in August about KB 3081452, that patch refused to install on many PCs. Of course, the patch is being distributed to only Windows 10 systems. This update makes improvements to ease the upgrade experience to Windows 10. The second patch Microsoft released overnight, KB 3106932, took me further down the rabbit hole. 13 (KB 3096448 and KB 3096441), with no note made about further updates. Neither of the updates to the TechNet articles are dated Oct.

That V 1.1 change refers to CU 8, not CU 10. Customers who have already successfully updated their systems do not need to take any action. V1.1 (October 16, 2015): Bulletin revised to announce a detection change in the 3097617 cumulative update for Windows 10. The only change I could find for MS15-107 dates back to Oct. Only customers running Windows 10 systems need to install this new update. V2.0 (October 29, 2015) Bulletin revised to announce the release of a new Windows 10 cumulative update (3105210) to address an additional vulnerability, CVE-2015-6045, which has been added to this bulletin. On the TechNet site, though, there's one recent change noted for MS15-106: Predictably, if you click on the KB article's links, you'll find nothing.

KB3096441 MS15-106: Cumulative security update for Internet Explorer: October 27, 2015.KB3096448 MS15-107: Cumulative security update for Microsoft Edge: October 27, 2015.This update for Windows 10 includes functionality improvements and resolves the vulnerabilities in Windows that are described in the following Microsoft security bulletins and advisory:
