Windows 10 version 1607 receives KB4034661 cumulative update

Windows 10 version 1607 receives KB4034661 cumulative update

Windows 10 version 1607, called the Anniversary update is apparently still the most used Windows 10 version till now. The last time I heard about the statistics, version 1703 had a hold of about 30 percent and 1607 had a whooping share of 60 percent. This is the reason why the team still is continuously releasing updates that fixes a lot of things.
 Microsoft recently released KB4034661 that jumps the build number to 14393.1613. The previous update KB4034658 was released on Patch Tuesday. With this update, there are a lot of changes introduced by the team, which are:
  • This package contains d3dcompiler_47.dll; for more information, read the blog post,HLSL, FXC, and D3DCompile.
  • Addressed issue where a black screen appears when launching an application on Citrix XenApp that was deployed from Windows Server 2016. For more details, read CTX225819.
  • Addressed issue where the User Account Control (UAC) prompt sometimes appears hidden under other opened windows.
  • Addressed issue in the event collector data that caused data corruption with % symbols in the user logon events (ID 4624) from other Domain Controllers (DCs).
  • Addressed issue where the PowerShell command Add-HgsAttestationTpmHost fails to find the Endorsement Key Certificate for a system even though the certificate exists.
  • Addressed issue where, in some cases, an Encrypted Hard Drive device would not automatically unlock at system startup.
  • Addressed issue where the AppLocker rules wizard crashes when selecting accounts.
  • Addressed issue where third-party directory structures caused Disk Cleanup to render a boot drive inaccessible.
  • Addressed issue where unsynchronized access in NtfsQueryLinksInfo led to a system crash.
  • Addressed issue where an extremely high number of I/O flushes might lead to an error.
  • Addressed a reliability issue that occurs when a user gives the wrong input to the smart card pin prompt.
  • Addressed issue by increasing the time out window when starting Docker for Windows to avoid 0x5b4 errors.
  • Addressed issue with Azure Multi Factor Authentication (MFA) when an ADFX server is configured to use an HTTP Proxy.
  • Addressed issue where the calling IP address is not logged by 411 events in the Security Event log of ADFS 4.0 and Windows Server 2016 RS1 ADFS servers. This issue occurs even after enabling Success Audits and Failure Audits.
  • Addressed issue where a computer account loses its domain membership with the error 1789, “The trust relationship between this workstation and the primary domain failed.” The same problem happens internally when a user password cannot be changed with error 0xc0000206, “The size of the buffer is invalid for the specified operation.”
  • Addressed issue where, after a planned restart of the primary server, storage replication doesn't automatically resume as expected. Also, Storage Replication service randomly fails after restart.
  • Addressed issue where using a GPO logon script to map a network drive fails if the user disconnects from the network and restarts. When the user logs in again, the mapped drive is not available. This issue occurs even though the logon script has the persistence flag set to TRUE.
  • Addressed issue where after uninstalling SMBv1, if you set the SPN validation level to 2, when you access a UNC share remotely (e.g., \\<MachineName>\C$), the request will fail with STATUS_ACCESS_DENIED.
  • Addressed issue where the Remote Desktop client cannot connect or disconnects intermittently when trying to connect using the RD Gateway.

Known Issues with the update

There are some known issues with the update as well and the following table lists them:
SymptomWorkaround
“Update History” does not list previously installed updates.As an alternative, to see which quality updates have been applied, navigate to the inventory by going to Control Panel -> Programs -> “View Installed Updates”

Microsoft is investigating this issue and will provide an update as soon as possible.
Updates that were previously hidden may be offered after installing this update.Updates that were previously hidden can be hidden again.

Microsoft is investigating this issue and will provide an update as soon as possible.
WSUS servers will exhibit increased CPU, memory, and network utilization when Windows Update clients perform their first scan after installing KB4034658.Microsoft is investigating this issue and will provide an update as soon as possible.

Download the update

The update should as usual come down via windows updates in some time, but you can always use Catalog to download the manual update package. Here are the links:
You can get more information about this update from here:
See also:
New Windows Insider preview ISO now available for download

New Windows Insider preview ISO now available for download

As the Windows 10 Redstone 3 is almost feature complete, Microsoft has started releasing more builds to slow ring. In this context Build 16251 was released to slow ring last week.
Traditionally Microsoft doesn't release an ISO officially after releasing a fast ring build to do a clean Install, but it is not the case for slow ring. After releasing slow ring builds Microsoft makes available the ISOs for clean Install. Same is the case here. Microsoft has released ISOs of Build 16251 to public.
You can download it from the following link:
Download Windows Insider preview ISO
ISO files are available for the following versions of Windows 10:
  • Windows 10 Home and Pro
  • Windows 10 Home single language
  • Windows 10 N
  • Windows 10 Enterprise
  • Windows 10 home China 
The ISO files are available for both 32 bit and 64 bit editions.
See also:
New Build of Windows 10 Insider for fast ring now available

The latest update for Windows 10 v1607 would wipe down your update History

The latest update for Windows 10 v1607 would wipe down your update History

August patch Tuesday just was around the corner and as usual there were updates for each version of Windows. For windows 10, Microsoft shipped updates to each version including 1703,1607 etc.
With each update, the software giant generally tells if there are any known issues with the update. For 1607 update i.e. KB4034658. There was no known issues that have raised with windows updates according to MS. But there is one.
A lot of people are reporting issue with the one released with 1607 that the update released has removed all of the update history. The update history is generally erased with a feature upgrade which is not a case here.
For those who don't know, this update brings the following changes
  • Addressed issue where apps sometimes launch with a border when a device is in Tablet mode.
  • Addressed issue introduced in the June updates where some applications may not launch when a device resumes from Connected Standby mode.
  • Security updates to Windows kernel-mode drivers, Microsoft Windows Search Component, Microsoft Windows PDF Library, Internet Explorer, Microsoft Scripting Engine, Common Log File System Driver, Windows Server, Windows Hyper-V, and the Microsoft JET Database Engine.
This update also jumps the build number to 14393.1503.
Microsoft recently added the same in the known issues list of the support page:
“Update History” does not list previously installed updates. As an alternative, to see which quality updates have been applied, navigate to the inventory by going to Control Panel -> Programs -> “View Installed Updates”
Microsoft is investigating this issue and will provide an update as soon as possible.
 So people, who haven't updated yet, get a screenshot before!
[August] Microsoft updates all versions of Windows 10

[August] Microsoft updates all versions of Windows 10


Yesterday was the second Tuesday of August-also called Patch Tuesday in Microsoft. For someone who doesn't know, what it is, Microsoft releases the updates for all of its products on this day. As usual, Microsoft updated Windows 10 all versions. Here is a version by version detail:

Windows 10 version 1703

The creators update to Windows 10, has got KB4034674 which jumps the build number to 15063.540. Following issues are addressed with this update:
  • Addressed issue where the policies provisioned using Mobile Device Management (MDM) should take precedence over policies set by provisioning packages.
  • Addressed issue where the Site to Zone Assignment List group policy (GPO) was not set on machines when it was enabled.
  • Addressed issue where the AppLocker rules wizard crashes when selecting accounts.
  • Addressed issue where the primary computer relationship is not determined when you have a disjoint NetBIOS domain name for your DNS Name. This prevents folder redirection and roaming profiles from successfully blocking your profile or redirects folders to a non-primary computer.
  • Addressed issue where an access violation in the Mobile Device Manager Enterprise feature causes stop errors.
  • Security updates to Microsoft Edge, Microsoft Windows Search Component, Microsoft Scripting Engine, Microsoft Windows PDF Library, Windows Hyper-V, Windows Server, Windows kernel-mode drivers, Windows Subsystem for Linux, Windows shell, Common Log File System Driver, Internet Explorer, and the Microsoft JET Database Engine.
Known Issue: Installing this update in Czech and Arabic would make Microsoft Edge English. The next update should fix this issue.
Support Page: https://support.microsoft.com/en-us/help/4034674 helps you get more information about this update.
To download this update, either use Windows update or use the following direct download links:

 Windows 10 version 1607

The Anniversary update to Windows 10, has got KB4034658 which jumps the build number to 14393.1593. A small list of fixes include:
  • Addressed issue where apps sometimes launch with a border when a device is in Tablet mode.
  • Addressed issue introduced in the June updates where some applications may not launch when a device resumes from Connected Standby mode.
  • Security updates to Windows kernel-mode drivers, Microsoft Windows Search Component, Microsoft Windows PDF Library, Internet Explorer, Microsoft Scripting Engine, Common Log File System Driver, Windows Server, Windows Hyper-V, and the Microsoft JET Database Engine.
Support Page: https://support.microsoft.com/en-us/help/4034658
To download this update, head over to Windows update or use the MSUs:

Windows 10 version 1511

November update to Windows 10 is still being supported by Microsoft. It has got KB4034660 which jumps the build number to 10586.1045. The fixes are:
  • Addressed issue where, when deploying an application to a device that is managed by AppLocker, the application deployment fails.
  • Addressed issue introduced in the June updates where some applications may not launch when a device resumes from Connected Standby mode.
  • Security updates to Windows kernel-mode drivers, Microsoft Graphics Component, Microsoft Windows Search Component, Microsoft Windows PDF Library, Microsoft Edge, Internet Explorer, Microsoft Scripting Engine, Windows Server, Common Log File System Driver, Windows Hyper-V, and the Microsoft JET Database Engine.
You can download this update from Windows update or use the following links:
The original Windows 10-though called as unsupported by Microsoft is still getting updates though. It has got KB4034668 which jumps the build number to 10240.17533. Following is the changelog:
  • Addressed issue where some of the event data for user logon events (ID 4624) from Domain controllers were corrupted.
  • Addressed issue introduced in the June updates where some applications may not launch when a device resumes from Connected Standby mode.
  • Security updates to Microsoft Scripting Engine, Microsoft Edge, Internet Explorer, Microsoft Windows Search Component, Microsoft Graphics Component, Windows kernel-mode drivers, Microsoft Windows PDF Library, Windows Server, Common Log File System Driver, Windows Hyper-V, and the Microsoft JET Database Engine.
Download: You can head over to Windows update or use the following links:
That is it for this month, you can always check our website for regular updates. In case if the updates fail with an error code, see the following articles:

[Now Closed] Microsoft introduces skip ahead feature for fast ring insiders

Microsoft, through its testing program for Windows 10 called Windows Insider program allows you to test beta versions of Windows 10. The fast ring-which allows you to see the new Windows 10 build first and get early access to new features is being modified a bit, as said by Dona Sarkar.
Right now, when a feature upgrade stops getting new features(like FCU builds now) the fast ring Insiders or perhaps all the insiders try to fix all the bugs present in the feature upgrade build. The build deemed most stable like 14393 or 15063 is released to the masses. But in a future change from next feature release, a limited number of Fast ring Insiders would be able to test new builds from the next branch(which is RS4_PRERELEASE, for example) and the other insiders would continue to fix builds from current branch.

This was told by Dona Sarkar on Feedback hub. The full statement says:
To stabilize the Windows 10 Fall Creators Update for release, we have “forked” the release into its own branch we call “RS3_RELEASE”. Many Windows Insiders will recall we did the same thing for the Windows 10 Creators Update when we started flighting builds from the “RS2_RELEASE” branch. Going forward, Windows Insiders in the Fast ring will continue to get builds for the Windows 10 Fall Creators Update from this branch. However, Windows Insiders who choose to skip ahead will receive builds from the RS_PRERELEASE branch.
To summarize:
  • Fast ring: Builds from RS3_RELEASE branch with no inbox app updates.
  • Fast ring + Skip Ahead: Builds from RS_PRERELEASE with inbox app updates from the Store.
Dona has also said how the things would go. After Fall Creators update is released to public, all of the fast ring Insiders would get build from same branch.
At some point in the future, build numbers in the RS_PRERELEASE branch will jump ahead, engineering teams will start checking in new code, and things diverge. When this happens – you will not be able to leave Skip Ahead and go back to builds from the RS3_RELEASE branch without reinstalling Windows. Once the Windows 10 Fall Creators Update is released to the general public, this skip ahead option will go away and the Fast ring will be back to receiving builds from the RS_PRERELEASE branch for the next Windows 10 release and inbox app updates from the Store will be fully restored to all Windows Insiders in the Fast and Slow rings.
 This is how the settings would look like(Thanks to WinCentral)
This is for people like who want very early access of the new features-not like me! who are sitting on slow ring and waiting for next stable build to arrive.

Update: Microsoft has closed down the skip ahead feature keeping on what they said earlier- a limited number of Insiders would be permitted. The Windows update settings show:


Windows 10 build 16257 releases to fast ring Insiders

Windows 10 build 16257 releases to fast ring Insiders

After releasing Redstone 2 aka creators update to public, the focus now shifts to the builds from next Insider branch, widely called Redstone 3. Now, Microsoft has released 14th Redstone 3 build 16257 to public yesterday. Redstone 3 builds are almost feature complete, so expect some less new features from now.

What's new

  • Eye Control(beta): More accessibility options for persons with disabilities. Only supported with Tobil Hardware currently.
  • Microsoft Edge new features:
    • Some UX improvements incorporating fluent design.
    • Adjusted the design of address bar.
  • Windows console now supports full 24 bit colors.

Fixes and Improvements

  • Improved the performance of launching the touch keyboard after tapping the touch keyboard button in the taskbar.
  • [Fixed]an issue where using WIN+H to dictate into a UWP app’s text field wasn’t working.
  • [Fixed]aan issue resulting in the Japanese IME prediction candidates position being shifted and overlapping with typed text if you set the page zoom level to something other than “100%” in Microsoft Edge.
  • Adjusted the design of the Japanese curve-flick touch keyboard to display numbers and English letter keys in a smaller font that’s more consistent with the size of the Japanese character keys.
  • Added new status strings to the WDAG splash dialog to provide more information about the startup stages for WDAG. These new strings will be displayed to users when WDAG is starting up and when it’s being resumed from a paused state.
  • Made significant improvements to container launch times by optimizing background preparation of the WDAG container.
  • [Fixed] a number of issues that were impacting networking inside the WDAG container as well as a poor user experience when connecting to the WDAG container.
  • [Fixed] issue where the WDAG launch resulted in Error Codes 0x02 / 0x00 or 0x02 / 0c.
  • Fixed an issue where only part of the WDAG window was being displayed after launch.
  • Added a registry key to allow users to optimize WDAG launch times during active browsing by not suspending the WDAG container when the WDAG window is closed.  You can set the registry key to optimize for performance here: Computer\HKLM\Software\Microsoft\HVSI\, Value name: SuspendOnContainerClosed, REG_DWORD, Value data: 1.  Note: Setting this key will result in the container not pausing and the container will not release committed memory.
  • [Fixed]  an issue where right-clicking on an image in Microsoft Edge and selecting copy then later pasting the clipboard content would result in the image URL being pasted rather than the image itself.
  • [Fixed]  an issue where if a tab had been opened while Microsoft Edge was in full screen mode, using Ctrl + W to close that tab while still in full screen mode would close the content but leave the tab in the frame.
  • [Fixed] an issue where if you had two unrelated tabs in Microsoft Edge and opened a link from the first in a new tab, the new tab would appear to the right of the second tab rather than the first.
  • [Fixed] an issue where the battery flyout might have shown unexpected text for the % charged (specifically “%1!s!%2!s!% until fully charged”).
  • [Fixed] an issue resulting in certain network setting being lost on upgrade and reverting to default. Specifically, static IP address configuration was reverted to DHCP, and networks marked private were reverted to public.
  • If you had installed Builds 16226-16237 and had found Storage Spaces to not be working, today’s build expands upon the fix in 16241 to remediate those PCs that had upgraded from the impacted build range and were still in a bad state. Thanks again to the Insiders that have helped us investigate this!
  • [Fixed] an issue where if you switched to a new tab and back in Microsoft Edge, Narrator would start reading from the top of the page again, rather than remember where you had been on the page.
  • [Fixed]an issue where right-clicking on a folder in File Explorer and saying Scan with Windows Defender wouldn’t work if the folder name contained #.
  • [Fixed] a rare issue where the Windows Search Service might get stuck on initialization after upgrade, resulting in File Explorer showing “Working on it…” infinitely when accessing certain folders.
  • [Fixed]an issue resulting in certain games such as Wargaming’s World of Tanks, World of Warships, and World of Warplanes appearing to hang/freeze shortly after launch when played on x86 PCs in recent flights.
  • [Fixed] an issue where some Insiders were not being offered builds higher than Build 16241.
  • [Fixed] an issue where connecting to a VPN using a solution downloaded from the Windows Store may result in a system crash.

Known Issues

  • Start, Action Center and notification toasts may at times have a background that is 100% transparent. A fix will be available in later flight – for now, if you encounter this issue, try ending ShellExperienceHost.exe via Task Manager or rebooting to resolve the issue.
  • Investigating reports where Action Center shows it has some number of notifications but when you click to open Action Center, there are no notifications shown.
  • Investigating reports that suggested apps are visible in Start despite the related setting being off. For now, if you encounter this please try toggling Settings > Personalization > Start > “Occasionally show suggestions in Start”.
  • When installing or updating a Windows Store app, you may see error 80070057. As a workaround, you can get the latest app by uninstalling the older version of the app from your device and reinstall latest version from Store.
Read more here:
This update would be available via Windows update as always.

New Cumulative update for Windows 10 now available

New Cumulative update for Windows 10 now available

The current latest version of Windows 10 is version 1703, which was released to public in April. Though the initial build 15063.0 was initially unstable, Microsoft has provided a lot of updates to fix bugs and get it more stable.
The most recent update was on Patch Tuesday of July that had KB number of KB4025342 which brought build number to 15063.482. You can get more information about it from the following:
Microsoft updates shipping versions of Windows 10
Now Microsoft following the 2 update policy/month has released a cumulative update for version 1703 yesterday. The update was quite silently released with no announcements from MS side. The KB number of the update is KB4032188 and the build number jumps to 15063.502
There is a long bug fixed list which is:
  • Addressed issue that causes a Microsoft Installer (MSI) application to fail for standard (non-admin) users when installed on a per user basis.
  • Addressed issue to enable support in the DevDetail Configuration Service Provider (CSP) to return the UBR number in the D part of the SwV node.
  • Addressed issue where NTFS sparse files were unexpectedly truncated (NTFS sparse files are used by Data Deduplication—deduplicated files may be unexpectedly corrupted as a result). Also updated chkdsk to detect which files are corrupted.
  • Addressed issue where the IME pad was not launching correctly in the Microsoft Edge browser for certain markets.
  • Addressed issue to allow Win32 applications to work with various Bluetooth LE devices including head tracking devices.
  • Addressed issue in the Mobile Device Manager Enterprise feature to allow headsets to work correctly.
  • Addressed issue where device drivers are not loading.
  • Addressed a reliability issue when playing specific types of spatial sound content.
  • Addressed issue with a dropped key on Microsoft Surface Keyboard and Microsoft Surface Ergo Keyboard, and addressed Wacom active pen connection failures.
  • Addressed issue to improve stability for USB type C during device arrival and removal during system power changes.
  • Addressed USB host controller issue where the host controller no longer responds to the attached peripherals.
  • Addressed MP4 compatibility issue while playing content from a social media site in Microsoft Edge.
  • Addressed issue with audio headsets connected to a PC through Xbox 360 controllers.
  • Addressed a reliability issue with launching a Settings app while another application is using the camera device concurrently.
  • Addressed issue with notifications (SMS, Calendar) for an activity tracker.
  • Addressed issue with video playback artifacts during transitions from portrait to landscape on mobile devices.
  • Addressed issue with Skype calls becoming unresponsive after about 20 minutes when using Bluetooth headsets with Hands-Free Profile (HFP) connections with negotiated mSBC codec (Wideband Speech).
  • Addressed issue where a service using a Managed Service Account (MSA) fails to connect to the domain after an automatic password update.
  • Addressed issue where, in some cases, a drive that utilizes on-drive hardware encryption would not automatically unlock at system startup.
  • Addressed issue where “cipher.exe /u” fails on client machines that are deployed with InTune, Windows Information Protection (WIP), and an updated Data Recovery Agent (DRA) certificate. Cipher.exe will fail with one of the following errors: “The request is not supported" or "The system cannot find the file specified”.
  • Addressed issue where a memory leak occurs in a nonpaged pool with the “NDnd” memory tag when you have a network bridge set up.
  • Addressed issue where you cannot add Work and School accounts in Windows Store, and you may get an error that reads, “We encountered an error; please try signing in again later.”
  • Addressed issue issue where if a Surface Hub enters Sleep mode and then resumes, it may require the user to sign in to Skype again.
  • Addressed issue where some Windows Forms (WinForms) applications that use DataGridView, Menu controls, or call a constructor for a Screen object experienced performance regressions in .NET 4.7. This was caused by additional Garbage Collections. In some cases, there was an empty UI because of a lack of GDI+ handles.
  • Addressed issue where Magnifier Lens users cannot click on buttons or select web content in Microsoft Edge or Cortana results.
  • Addressed issue introduced in the June updates where some applications may not launch when a device resumes from Connected Standby mode.

This update is available via both Windows update and Microsoft Update catlog.
For full information, you can refer the following article:

Direct Download links

[July] Windows 7 and others go down as Windows 10 share increases

August just started some days ago, and Netmarket share has accordingly updated the OS share statistics. Unlike last month, the Windows 10 share this month grew by a bigger margin and while others went down. Let us see details of each OS one by one:

Windows 10

Change: +0.83 percent.
Windows 10, the latest OS of the software giant got benefit of the Creators update and the share increased by 0.83 percent. It stands at 27.63 percent with second most used OS.

Windows 7

Change: -0.13 percent.
Windows 7, the most successful OS of Microsoft went down a bit this month standing at 48.91 percent while previous share was 49.08 percent in June. 

Windows 8.1

Change: +0.08 percent
Windows 8.1 had a slight increase, standing at 6.48 percent in July as compared to 6.40 in June.

Windows XP

Change: -0.91 percent
Windows XP is going down, as per the statistics say. Stragely it increased 1 percent last month, but it lost almost the same share in July. The OS had 6.1 percent share in July.

A detailed figure can be seen below:
Thanks to Netmarketshare.