KB4093105 for Windows 10 version 1709
Microsoft published KB4093105, a new cumulative update for Windows 10 version 1709, the Fall Creators Update, some hours ago. The non-security update is distributed via Windows Update and other updating services, and available as a standalone download from the Microsoft Update Catalog website.
The update brings the build number of the operating system to 16299.402. Microsoft released the cumulative updates KB4093120 and KB4093117 for Windows 10 version 1703 and 1607 last week, and KB4093105 shares several of the fixes with these earlier releases.
KB4093105 fixes issues in Microsoft Outlook, Windows Hello, File Explorer, BitLocker, Microsoft Edge and other programs and core operating system features.
Note: Windows Update failed to pick up the new update on a Windows 10 Pro machine. It returned KB4093112 instead which Microsoft released on the April 2018 Patch Tuesday; that update was installed on the machine already, however. Manual download from the Microsoft Update Catalog site and installation worked, however.
KB4093105 for Windows 10 version 1709
The list of issues that Microsoft fixed in the new update is quite large. You can check it out on the official release history page on the Microsoft website, or read the summary (of all fixes) below.
- Fixed an issue where the deprovisioning of apps using remove-AppXProvisionedPackages-Online did not work properly as apps returned after upgrades.
- Applications stopped working after pasting username or password into a user elevation prompt.
- Fixed an issue that caused Skype and Xbox to stop working.
- Autodiscover functionality in Microsoft Outlook failed when UE-V is enabled.
- AppLocker publisher rules for MSI files did not match files correctly.
- Fixed a key generation issue in Windows Hello if the policy to require TPM is enabled.
- Fixed a domain log in issue when using fast user switching.
- The Office Chrome extension prompted for credentials often.
- Removed the 30-second delay after entering an incorrect PIN or biometric input when using smart cards.
- Minimum password length in Group Policy increased to 20 characters.
- Fixed hexadecimal format of name-constraint information in certificate properties.
- Audit mode blocked failed NTLM authentications instead of logging them.
- Fixed validation error 0x800B0109 (CERT_E_UNTRUSTEDROOT).
- Resetting the Windows Hello PIN on the logon prompt blocked resetting the PIN again.
- Encrypting and decrypting options were missing in File Explorer.
- Fixed BitLocker and Device Encryption issue that kept the device unprotected during device unenrollment.
- Software Restriction Policy Caused Microsoft to stop working.
- A leak in Filter Manager caused file system mini-filters to fail to unload.
- Connection Bar was not displayed in Virtual Machine Connections in full-screen mode when using multiple-monitors.
- The "Disable new DMA devices when the computer is locked" policy prevented some devices from working o Windows 10 version 1709. Devices include PCI-based peripherals such as wireless network drivers, input, and audio peripherals).
- Fixed a logging issue in Windows Server 2016 Domain Controllers.
- Fixed cause of the exception "Microsoft.IdentityServer.Service.AccountPolicy.ADAccountLookupException: MSIS6080: A bind attempt to domain 'globalivewireless.local' failed with error code '1722'"
- Addressed the error "Error 0x207D An attempt was made to modify an object to include an attribute that is not legal for its class" when modifying or restoring certain Active Directory objects.
- Addressed the issue "Active Directory Domain Services was unable to establish a connection with the global catalog. Error value: 8430. The directory service encountered an internal failure. Internal ID: 320130e" that prevented AdminSDHolder tasks from running.
- The Date Modified field was empty on volumes with Volume Shadow Copy that hosts a file share.
- Fixed a Microsoft Edge stopped working issue for roaming profiles.
- Fixed Japanese keyboard not working correctly in remote assistance sessions.
- Cursor moved to center of the screen when changing display modes.
- Fixed a leak when closing or opening web browser controls.
- Fixed ContentIndexter.AddAsync API throwing an exception.
- Fixed first launch performance of UWP Desktop Bridge apps.
- Fixed Search Tab in Microsoft Outlook 2016 when upgrading from version 1703 to 1709.
- Updates for large game apps failed.
- User-pinned folders or tiles were removed from the start menu.
- Pen use in certain apps caused unexpected panning or scrolling.
The cumulative update has one issue: It reports that KB4054517 failed to install because of error 0x80070643 even though the update is installed.
Now Read: My Top 5 Feature wishes for Windows 10
Previous Post: « Windows Defender System Guard in Windows 10 Spring Creators Update
Next Post: Windows 10 Microcode updates KB4090007, KB4091663, KB4091664 and KB4091666 »
It’s been long ago since I got failed update D:
Error code: 0x800f0922 (very similar error code to earlier update, many users got error code: 0x800f0900)
Not surprised, if we see today or tomorrow more discussion about this, atleast reddit seem to be active about some problems.
So many issues.
Win 10 = Beta software
How many TERRABYTE are pushed out by Microsoft each year in updates for Windows 10 (a buggy and bloated Windows version that never reaches RTM) ?
Thanks a lot Martin !
Haven’t test it but expect they fixed the repulsive pen bug , after all the blame . People are wasting so much time and money for it.
Off-topic, sorry, but does someone happen to know where to find the monthly “Security Only” updates for Windows 8.1 x64? So not the full monthly “Quality” rollup, but just the security updates?
Somehow, since last January my searching in the Microsoft Update Catalog has not found any new “Security Only” updates for Win 8.1 at all. I can hardly believe MS discontinued these updates, but where have they gone? Maybe they’ve been named differently, or something like that?
Thanks in advance to whoever can shed a little light on this.
You can use the direct links that I post on each month’s coverage of the updates: see https://www.ghacks.net/category/microsoft-companies/
You can search this site for the “Security-Only” updates … https://www.ghacks.net/?s=%22microsoft+security+updates%22
Thank you both!
“Software Restriction Policy Caused Microsoft to stop working.”
Now that’s funny.
Windows 10 x64 Home KB4093105 installed without error for me per Windows Update history. I used manual Windows Update to initiate the install. It briefly hung at 80% download and downloaded again successfully. The install hung at 20% and also automatically began the install again successfully the second time..
“Note: Windows Update failed to pick up the new update on a Windows 10 Pro machine. …”
My Windows 10 pro machine picked it up. It delayed a bit at 99% downloaded. It then installed the update.
i guess no fix for the Sleep bug. Since 3 updates before this, my laptop will sometimes Blue Screen crash when attempting to Sleep, either by the time set in Power Settings or when i do it manually. So i disabled Sleep in the Power Settings and don’t put it into sleep myself, instead just close everything and shut down. No more blue screen crashes, fuck Microsoft.
Let’s take a step back for a moment.
It’s easy to blame Windows for everything that goes wrong when using Windows functions. However, this may not be a Windows issue. Maybe you have some other software running under Windows which does not allow the computer to sleep.
Try running in safe mode (use google to find out how) and then sleep. If that works, you have another issue.
Just my 2 cents.
Nah, it started immediately after the update as i use Sleep mode everyday. And i didn’t install anything else or update anything else.
Something in the update triggered a caused a glitch or is causing something else to cause this glitch.
BUT, that is a good idea to try Safe Mode. Can’t believe i didn’t think of that, Thanks.
Has this update been pulled? Not available via Windows Update nor WSUS for me.
If it was pulled, it would not be available right NOW on the catalog.
Update does have some funky quirks. In my case, it found it right away on one machine but not on another.
If you are anxious, you can manually download through the catalog. Or just wait for update to wake up and do its thing.
Some people seem to even NOT realize how to stop automatic updates in Windows 10, due to Martin and other Commenters often told here.
Play it again, Sam, play as time goes by, so….Win 10 updates nowadays is NOT a guarantee for a stable System. Why? because Win 10 is a Service, so how to stop annoying bugs in autoupdates? Block it,..and decide, like win 7 which you want to install, hide and so on.
How to? Use Windows Update Mini Toll, no bugs, no malware. no install, why? Because Win 10 is an On/Off System, so no install needed.
Then choose disable automatic updates and search manually, then see Internet to see what bugs are introduced and decide to hide update KB XYZ.
For me, easiest way to prevent BSOD and other annoying bugs.
Hey Microsoft, what’s up with the Windows Update KB4093105, released on 4/23/2018? Lots of users, including me, are having problems with installation. Here’s the details…
1. KB4093105 downloads and begins installation with no problems…or so it seems.
2. This update installs up to 30%, then my computer reboots, then finishes installing the remaining 70%. And then…
3. An error appears telling me it couldn’t complete the update, undoing changes, don’t turn off your computer.
I tried to install KB4093105 via Windows Update twice, once with the download/standalone version from the Microsoft Online Catalog and all three times I got the same error. Then it tried to install a 4th time on its own and again failed.
I tried the steps at these locations…
…but no such luck.
Anyone know what else I can try? In the meantime, I have disabled Windows Update to prevent further attempts to download/install KB4093105.
I still have the same problem, my last update that failed was on 5/17/2018. I’ve had 18 failed installations. I have tried to disable Windows Update but it does not work. I am using Windows 64 Home.
How many times does the update need to fail before Microsoft stops sending you the same update?
I went to Settings > Update & Security > View installed update history
2018-04 Cumulative Update for Windows 10 Version 1709 for x64-based Systems (KB4093105) (18)
Last failed install attempt on 5/17/2018 – 0x800f0922
Anyone know what else I can try? In the meantime, I have disabled Windows Update to prevent further attempts to download/install KB4093105.
Yes!
I had to do that also. The “couldn’t complete, unding changes” message (that and a long delay after) took place every time I restarted the machine. No way to fix it, other than to turn the Windows Update entirely OFF. All started with this KB4093105, wish it had never come into my life. Now must try to figure out what else to do?
Also having BSOD right after instalation of the Update for Windows 10 Version 1709 KB4093105