Follow the steps in the wizard to diagnose and resolve your network problems. Run Windows Update again. Did this resolve the issue? Run the network troubleshooter. Download the version of the latest SSU. That matches your version of Windows from the Microsoft Update Catalog. Restart your device and check for updates.
Microsoft has released a host of improvements and bug fixes for the recent Windows 10 Creators Update.
The fixes are available in the KB4020102 update, Build 15063.332, for Windows 10 version 1703, otherwise known as the Creators Update. It's the fourth update since the Creators Update began arriving on PCs in early April. Microsoft began ramping up the rollout this month, as it continues to address glitches experienced by users on specific hardware.
This update should improve the experience for those who've already moved to the latest version of Windows 10, with fixes for bugs in the Windows client-server authentication service NTLM, Internet Explorer, Split View, fonts, messaging, and support for third-party apps.
Installing the update should fix a problem introduced by Creators Update, which broke audio output run through external decoders. It also fixes an issue that stalled SMS and messaging apps when the user tries to delete messages.
Setting up printers on machines with less than 4GB RAM should also be a easier with this update. On top of that, it addresses printer queuing issues.
Microsoft has fixed an problem in the Creators Update where NTLM was failing 'to generate a challenge response when CredGuard is enabled, NTLMv2 is used, and no target information is provided by the server'.
Previously, starting Split View would stop apps such as Edge, Hub, and Cortana from receiving inputs for multi-display setups. That issue is now fixed.
The fonts fix addresses an issue where users would see black bars or other objects due to a problem rendering non-Unicode fonts on non-Latin scripts.
Non-administrative users should also now able to install an ActiveX control, according to Microsoft.
There are also fixes for the IoT shell, and proxy settings. The update only brings quality improvements and no new features.
Separately, Microsoft has been doing some house-cleaning on the Surface Pro 4's drivers, which improves its battery life in sleep mode, disables touch when the cover is closed, and fixes a post-sleep screen brightness issue.
Microsoft Security Patch And Download
More on Microsoft Windows 10
Related Topics:
Microsoft Enterprise Software Windows PCs ReviewsI know that I just posted a fairly long rant about Windows Update last week, and I don't want this to turn into a blog called 'Jamie's Mostly 'I Hate Windows' Stuff', so I am going to make this quite short and to the point. But I think it is important to post it, because it looks like I have experienced a problem that might specifically target people who are likely to read a blog such as mine.
First, this problem affects my Lenovo T400 laptop, which I use with a docking station on my desk at home, and which is loaded with Windows 7 Professional 64-bit and a variety of Linux distributions. It is not Windows 8, it is not UEFI boot, and it is not a GPT partitioned disk - it is a 'plain vanilla' (bog standard? could be appropriate for Windows...) Windows 7 MBR system.
A large part of this problem can be placed directly in the category of 'Selber Schuld!' (German for 'It's my own fault').
No, it wasn't just you. This month's Patch Tuesday updates from Microsoft contained an epic number of updates. Here's what was included.
After spending last weekend recovering from Windows wiping the disk in one of my Acer Aspire One netbooks, you might think that I would be smart enough to stay away from Windows Update. The only thing I can say in my defense is that this time I didn't ask for it: Windows took it upon itself to install the latest batch of updates, and I didn't notice that it was going to do so when I shut it down.
What happened was that, when my machine started to shut down, it told me it was going to 'Configure Windows Updates'. Then it rebooted, and on startup it continued with 'Configuring Windows Updates'. But after a while it said, 'Update Installation Failed', and it was backing out the updates. Grr.
Then it rebooted again, and said again that it was 'Removing Update Installation' or some such, and after a while it rebooted again.
Just as I started to fear that it had stuck itself in an endless reboot loop, the third reboot succeeded. But then when I went to shut down again, it started the same cycle... and it is obvious that it is going to do that over, and over, and over again now. Three reboots and a lot of waiting for 'Configuring Windows Updates' followed by 'Removing Windows Updates'.
Microsoft Download Patches
I was going to go into Windows Update and just disable installation of that patch, but I decided to have a quick look around to see if I could find anything about it. The specific patch that is failing is KB3033929, and it fails with Code 80004005. Clicking on the 'Help with this error' link in Windows Update produces no useful information - in fact, it produces a window that essentially says 'Please check your typing'.
A web search produced some interesting results, though. InfoWorld has an article which describes exactly the same problem, and failures with some other error codes as well. It says that this patch is actually a re-issue of a patch that was originally released last October, but had to be withdrawn because it caused so many problems. Alas this article doesn't have any information about a solution.
One other interesting hit from the web search was on WindowsITPro, which also describes exactly the same problem I am having. Again, there is no solution but it does state:'KB3033929 just adds new capability, so it's not a critical install yet. If you fear you might experience trouble, delay installing it until things get sorted.'
So, my original plan seems to be the only workaround for the moment.
Oh, and the author of the WindowsITPro article also writes that if you are having this problem, 'definitely let me know so we can figure out a solid reason together'. Isn't that the job of the QA department?
This patch should have been tested before it was released, and then when it turned out to be so awful that they had to take it back, it should have been tested a whole lot more before they released it again, right?
Read more of my blog: