Microsoft began rolling out yet another cumulative update for the latest version of Windows 10. The update first became available to Insiders, but on September 29th, the company is making available update KB3194496 for everyone running the Windows 10 Anniversary Update.
KB3194496 bumps the build number to 14393.222, brings a number of fixes and improvements, but no features or visual changes are being introduced.
New changes on Windows 10 build 14393.222
- Fixed problem with mapping drives using elevated command prompt.
- Addressed issue causing ripped movies to play without sound in Windows Media Player and the Xbox One Media Player app.
- Fixed problem with Movies & TV app on Xbox not working with purchased content from the Store.
- Addressed issue causing “Print all linked documents” to not work in Internet Explorer 11.
- Fixed problem preventing some users from changing the default download location in Windows 10 Mobile.
- Addressed additional notification issue about fixing Microsoft account in Windows 10 Mobile.
- Fixed additional issues on the Windows kernel, Windows Shell, Remote Desktop, NFC, wireless networking, Cortana, PowerShell, Microsoft Edge, modern apps, storage system files, and various other components.
- Support for networks has been improved by adding new entries to the Access Point Name (APN) database.
- Reliability of the Windows Update Agent, shared drives, virtual private network (VPN), clustering, HTTP downloads, Internet Explorer 11, Hyper-V platform, multimedia playback, and Microsoft Edge have been improved.
- Performance has been improved for push and local notifications, Hyper-V platform, and some social media websites using Microsoft Edge.
On the other hand, Windows 10 Mobile is getting build 14393.221, which includes the same improvements except that the PC version brings a reliability update to improve game downloads.
Windows 10 build 14393.222 (KB3194496) for PC is available immediately. The new update will download and install automatically, but you can always force the update from Settings > Update & security > Windows Update and clicking the Check for updates button.
Update, September 30th, 2016: A small number of users are reporting problems installing the cumulative update KB3194496. The good news is that Microsoft is aware of the issue and it’s working on a fix.
Jason, a Microsoft employee, said on an statement:
“Teams have dug into this issue and do believe the cause has been identified. Looks like this will only be hitting a subset of Insiders. The correct team is developing a fix/workaround and once we have the full details, we’ll be posting that information. For your affected machines, there’s no need to keep attempting the install. It’ll keep failing.”
Update, October 3rd, 2016: As we continue to wait for an official fix to address the issue with update KB3194496 a workaround has surfaced. It appears that there are two tasks in the Task Scheduler that are failing to install the new update: XblGameSaveTask and XblGameSaveTaskLogon. This means that you can try disable and delete the to task to update your system:
Open Task Scheduler.
Expand Microsoft > XblGameSave.
Right-click XblGameSaveTask, and select Disable.
Right-click XblGameSaveTaskLogon and select Disable.
Close the Task Scheduler
Open File Explorer and navigate the following path:
Delete both files: XblGameSaveTask and XblGameSaveTaskLogon.
Use the Windows key + R keyboard shortcut to open the Run command.
Type regedit, and click OK.
Navigate to the following path:
Right-click and delete: XblGameSaveTask and XblGameSaveTaskLogon.
Click on Update & security.
Click on Check for updates and try to install the update one more time.
Update, October 6th, 2016: While Microsoft still working on a permanent fix, the company has now release an script to resolve the issue. You can find the script at this Microsoft support page, and you just click the download button for “Script to fix issues with the install of KB3194496 (Cumulative Update 14393.222).” Once you download the file, double-click it, and follow the on-screen instructions. Then try to update your system one more time.
Source Microsoft link 1, link 2