×
all 80 comments

[–]ravenomega 19 points20 points  (0 children)

Never had an issue with updates until this one. System randomly rebooted after the update once it was installed. Had event id errors 1101 and 41. Rolled back and everything is good.

[–]badchip 14 points15 points  (3 children)

Improvements and fixes

This update includes quality improvements. No new operating system features are being introduced in this update. Key changes include:

  • Addresses an issue that causes modern applications to reappear after upgrading the OS version even though those applications have been deprovisioned using remove-AppXProvisionedPackages-Online.
  • Addresses an issue in which running an application as an administrator causes the application to stop working when pasting the user name or password into the user elevation prompt (LUA).
  • Addresses an issue that causes Skype and Xbox to stop working.
  • Addresses an issue that prevents Autodiscover in Microsoft Outlook 2013 from being used to set up email accounts when UE-V is enabled.
  • Addresses an issue where AppLocker publisher rules applied to MSI files don’t match the files correctly.
  • Addresses an issue that prevents Windows Hello from generating good keys when it detects weak cryptographic keys because of TPM firmware issues. This issue only occurs if the policy to require the TPM is configured.
  • Addresses an issue that prevents users from unlocking their session and sometimes displays incorrect user-name@domain-name information on the logon screen when multiple users log on to a machine using fast user switching. This specifically happens when users are logging on from several different domains, are using the UPN format for their domain credentials (user-name@domain-name), and are switching between users using fast user switching.
  • Addresses an issue that causes the browser to prompt for credentials often instead of only once when using the Office Chrome extension.
  • Addresses an issue related to smart cards that allow PINs or biometric entry. If the user enters an incorrect PIN or biometric input (e.g., a fingerprint), an error appears, and the user must wait up to 30 seconds. With this change, the 30-second delay is no longer required.
  • Increases the minimum password length in Group Policy to 20 characters.
  • Addresses an issue that displays name-constraint information incorrectly when displaying certificate properties. Instead of presenting properly formatted data, the information is presented in hexadecimal format.
  • Addresses an issue that blocks failed NTLM authentications instead of only logging them when using an authentication policy with audit mode turned on. Netlogon.log may show the following:
  • SamLogon: Transitive Network logon of <domain><user> from <machine2> (via <machine1>) Entered
  • NlpVerifyAllowedToAuthenticate: AuthzAccessCheck failed for A2ATo 0x5. This can be due to the lack of claims and compound support in NTLM
  • SamLogon: Transitive Network logon of <domain><user> from <machine2> (via <machine1>) Returns 0xC0000413
  • Addresses an issue that generates a certificate validation error 0x800B0109 (CERT_E_UNTRUSTEDROOT) from http.sys.
  • Addresses an issue in which resetting the Windows Hello PIN at the logon prompt puts the system in a state that makes resetting the PIN again impossible.
  • Addresses an issue where the right-click context menu for encrypting and decrypting files using Windows Explorer is missing.
  • Addresses an issue that suspends BitLocker or Device Encryption during device unenrollment instead of keeping the drive protected.
  • Addresses an issue that causes Microsoft Edge to stop working after a few seconds when running a software restriction policy.
  • Addresses an issue that may cause a file system mini-filter to fail to unload because of a leak in Filter Manager, which requires a restart.
  • Addresses an issue that causes the connection bar to be missing in Virtual Machine Connection (VMConnect) when using full-screen mode on multiple monitors.
  • Addresses an issue that prevents certain devices from working on Windows 10, version 1709, machines when the “Disable new DMA devices when this computer is locked” Group Policy is active. The non-working devices are internal, PCI-based peripherals (wireless network drivers and input and audio peripherals). These peripherals can fail on systems whose firmware blocks the peripherals from performing Direct Memory Access (DMA) at boot.
  • Addresses an issue that might cause Windows Server 2016 Domain Controllers to log Microsoft Windows Security audit events ID 4625 and ID 4776. The username and domain name in the events may appear truncated, only showing the first character for logons coming from client applications using wldap32.dll.
  • Addresses an issue in which users may exist in a domain that is trusted using transitive trust, but are unable to locate a PDC or DC for the Extranet Lockout feature. The following exception occurs: “Microsoft.IdentityServer.Service.AccountPolicy.ADAccountLookupException: MSIS6080: A bind attempt to domain 'globalivewireless.local' failed with error code '1722'”.
  • Also, the following message appears on the IDP page: "Incorrect user ID or password. Type the correct user ID and password, and try again."
  • Addresses an issue that prevents you from modifying or restoring Active Directory objects that have invalid backlink attributes populated in their class. The error you receive is “Error 0x207D An attempt was made to modify an object to include an attribute that is not legal for its class.”
  • Addresses an issue that prevents the AdminSDHolder task from running when a protected group contains a member attribute that points to a deleted object. Additionally, Event 1126 is logged as “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.”
  • Addresses an issue that occurs when Volume Shadow Copy is enabled on a volume that hosts a file share. If the client accesses the UNC path to view the properties in the Previous Version tab, the Date Modified field is empty.
  • Addresses an issue that occurs when a user with a roaming user profile first logs on to a machine running Windows 10, version 1607, and then logs off. Later, if the user tries to log on to a machine running Windows 10, version 1703, and opens Microsoft Edge, Microsoft Edge will stop working.
  • Addresses an issue that makes a Japanese keyboard unusable in remote assistance sessions.
  • Addresses an issue that causes the cursor to unexpectedly move to center of the screen when changing the display mode.
  • Addresses a potential leak caused by opening and closing a new web browser control.
  • Addresses an issue that causes the ContentIndexter.AddAsync API to throw an unnecessary exception.
  • Addresses an issue with the first launch performance of UWP Desktop Bride apps.
  • Addresses an issue with the Search tab of Microsoft Outlook 2016 during the upgrade from Windows 10, version 1703, to Windows 10, version 1709.
  • Addresses an issue that causes updates for large game apps to fail.
  • Addresses an issue that removes user-pinned folders or tiles from the Start menu in some cases
  • Addresses an issue that causes invisible apps to appear in the Start menu.
  • Addresses an issue that might cause some users to experience unexpected panning or scrolling in certain apps while using the pen.

[–]if_it_is_in_a 11 points12 points  (2 children)

Wow, no Internet Explorer issues have been fixed this time. Can't believe my eyes...

[–]Xemanth 0 points1 point  (1 child)

Nobody cares of IE anymore :)

[–]tupac_cares_bot 0 points1 point  (0 children)

Tupac cares, if don't nobody else care.

[–]drexelspivey 7 points8 points  (1 child)

Getting the error 0x80070643 and saw the notes about the problem, but it did not update. Also tried to manually update it and it tells me that the update is not applicable for my computer.

[–]americanadiandrew 2 points3 points  (0 children)

Yep same error.

[–]FrankTheTank369 13 points14 points  (9 children)

Yes! That issue where my CPU speed was averaging 2.50 ghz while IDLING has been fixed! I've been waiting for that to be fixed for 2 weeks. Good job Microsoft.

[–]Shadestones 0 points1 point  (8 children)

My processor idles at around 3.19 to 3.45 GHz. How low/high are you expecting it to idle at? Or, what is your processor?

[–]Maxdec94 4 points5 points  (0 children)

It really depends on the processor, but for example in some laptops the frequency can go as low as 800 MHz - 1GHz in idle to save battery. Then if you need more power it will bump the frequency back up.

[–]SimmonsTheMad 1 point2 points  (5 children)

I have a Intel 4670K in a desktop and it will frequently drop to 800Mhz (from the 4.4Ghz OC I have set) when im not doing anything.

[–]Shadestones 0 points1 point  (4 children)

I wonder why my i5-6500 doesn't do that. Maybe Task Manager is just reading it improperly?

[–]SimmonsTheMad 2 points3 points  (3 children)

Maybe certain C states are disabled in your UEFI/BIOS? Maybe some software is running in the background preventing the CPU from ever truly idling?

[–]Shadestones 2 points3 points  (2 children)

I have High Performance mode turned on. Could that be it?

[–]MrAmos123 4 points5 points  (0 children)

Yes, High-Performance Mode will keep your CPU at max OC. Putting this on 'Balanced' will downclock, given you've enabled this in BIOS.

[–]FrankTheTank369 0 points1 point  (0 children)

I have a Skylake generation Intel i5 6600. Base speed is 3.30ghz but I thought 2.50ghz while idling was too high when I averaged around 1 - 1.2 and this all started around that last Windows update about two weeks ago. Finally fixed in this update.

[–]americanadiandrew 12 points13 points  (6 children)

We couldn’t complete the updates. Undoing changes. Don’t turn off your computer. 🤷‍♂️

[–]runboy93 9 points10 points  (2 children)

Got same message, and on updates there is error code: 0x800f0922

[–]crazyrobban 1 point2 points  (1 child)

finally someone with the exact same issue! Have you found a solution? I've tried all the usual troubleshooting tips regarding Windows Update. Also, cleared some space of my system reserved drive. Still no luck.

[–]Matt_13_ 3 points4 points  (0 children)

Same message here... Going to skip until 1803 Error Code: 0x80070643, No build change

[–]EyeFire 0 points1 point  (0 children)

You're not alone. Each and every update round, things just go so wrong. Microsoft, clearly, hasn't learned from past mistakes and keep repeating them, update round after update round.

It really is incredible how things can go so horribly wrong time and time again. I mean statistically speaking, wouldn't there be at least one time they actually did things right?

[–]war_story_guy 19 points20 points  (6 children)

These comments are not making me want to try and apply this update.

[–]thefleshlord 5 points6 points  (1 child)

I never trust such comments. Ever since windows 10 came out, I always did every update and never had a single problem.

[–]lucassilvas1 2 points3 points  (0 children)

Well me neither, never had a single problem with updates until this one, got stuck in the welcome screen and couldn't get access to the desktop, tried everything to fix it but was forced to reset the system and lose all of my apps and settings... It's going to be at least 3 weeks until i get everything back as it was. There really should be an option to postpone updates indefinitely, even if it makes pcs way more vulnerable. I can't afford to do this at every update.

EDIT: Typo.

[–]nikica251 7 points8 points  (1 child)

I did it and no bad things, yet

[–]phaze- 2 points3 points  (0 children)

Installed on my pc and my bro laptop. Nothing to worry about.

[–]CoffeeIsOverrated 0 points1 point  (0 children)

I'm downloading KB4093105 right now, will let you know how it goes haha

[–]santalint 6 points7 points  (6 children)

"Increases the minimum password length in Group Policy to 20 characters."
Um... what does this mean exactly?
Will that break my existing group policies that set 10 characters minimum??

[–]santalint 8 points9 points  (4 children)

Hate replying to myself, but through trying, I figured out what it means.
Before the change, you could only set up to 14 characters minimum in the group policy, now you can set up to 20 characters minimum.
So badly worded by Microsoft.

[–]ack_complete 0 points1 point  (1 child)

Yeah, this page could use some editing. Took me a bit to figure out what UWP Desktop Bride was supposed to be.

[–]santalint 0 points1 point  (0 children)

I had to go back and check when I read "Bride"...
They really need to work on checking those release notes.

[–]delfinom 0 points1 point  (1 child)

Not sure why they bothering putting a limit on it that isn't the storage size of the password string or any length variables.

[–]santalint 0 points1 point  (0 children)

Is anyone reasonably going to want a minimum password length longer than 20?
I understand your point though.

[–]tomschwanke -1 points0 points  (0 children)

Increased the maximum minimum password lenth in Group Policy...

[–]Zer4thul 5 points6 points  (0 children)

It was fine for me.

[–]SimmonsTheMad 5 points6 points  (0 children)

Everything installed fine on my end.

[–]Bioman52 2 points3 points  (1 child)

Long list of fixes in this release. Seems like the earlier April update was bug ridden.

[–]xdegen 0 points1 point  (0 children)

Those fixes are going to be released when the April update occurs..

[–]ocdtrekkie 1 point2 points  (1 child)

Microsoft fixed an issue with this cumulative I reported a year ago, on the release of the Creator's Update. (The Edge issue with software restriction policies.) It's actually why I stopped using Edge as my primary browser.

[–]321bluf 0 points1 point  (0 children)

What it means?

[–]SagnolThGangster 2 points3 points  (2 children)

What about spring creators ?

[–]Im_Special 6 points7 points  (1 child)

Well, it won't be tomorrow. That's about it.

[–]PCxforeverx 3 points4 points  (0 children)

Only a week left in April. The public release has got to come out soon or get pushed into May. Wondering what MS is doing at this point in time xD

[–]Anusman_ 2 points3 points  (0 children)

Update completed without any issues on my desktop.

[–]ignaciojn 2 points3 points  (4 children)

This update reset all my defaults and settings (apps, taskbar, Start Menu, etc), same as a Feature update.

UPDATE: After a reboot, it went back to normal.

[–]HS199401 5 points6 points  (1 child)

"reseted" isn't a word, you mean reset (cough)

[–]ignaciojn 0 points1 point  (0 children)

At first I wrote reset. Don't know why I edited it.

[–]maaky 0 points1 point  (1 child)

We've also experienced this fault. What Build number of Windows are you on?

[–]ignaciojn 0 points1 point  (0 children)

Build 16299.402. The update did install just fine.

But it took two reboots (the default and one after that) to bring things back to normal.

[–]mike2048 0 points1 point  (3 children)

There are some reports of this update possibly breaking WMR. Currently downloading too slowly for me to test before leaving for work, can anyone else confirm?

UPDATE: looks like false alarm, just tested and it works fine (at least when you already have it installed)

UPDATE2: ok for me but breaks WMR for plenty others :(

[–]anthion 0 points1 point  (1 child)

Not a false alarm for me. This update did break my WMR. Both WMR and WMR for SteamVR worked before the update. After the update WMR broke and therefore WMR for SteamVR broke. Uninstalling the update allows WMR to work BUT now SteamVR refuses to start because it now requires that all of the latest updates be installed. Also, after uninstalling the update it downloads and installs in the background and will be applied again after a restart and I have no idea how to keep that from happening.

[–]mike2048 0 points1 point  (0 children)

So they did break WMR after all, way to go Microsoft :(

You may be able to prevent / hide this update from installing over and over again by following the steps outlined here

[–]anthion 0 points1 point  (0 children)

Oh another thing, after the update gets applied after the uninstall the on-screen keyboard keeps showing up when the computer starts for no apparent reason and it keeps doing it no matter what I try in keyboard settings.

[–]Emerald_boy 0 points1 point  (0 children)

i5 7600k and geforce 1070, everything is fine here.

[–]robotman5_ 0 points1 point  (0 children)

Updated to this and no issues as of yet.

[–]DavidB-TPW 0 points1 point  (11 children)

As is the case for every cumulative update patch I've tried to install on my fresh Windows 10 installation on my laptop, the update failed. Hopefully the SCU comes out soon so I can upgrade and hopefully get rid of this stupid error.

[–]4wh457 0 points1 point  (10 children)

Try to manually install first this (servicing stack update): http://www.catalog.update.microsoft.com/Search.aspx?q=KB4099989%20Windows%2010%20x64

And then this (the latest cumulative update): http://www.catalog.update.microsoft.com/Search.aspx?q=KB4093105%20Windows%2010%20x64

It's very important you do it in that order or the update will fail.

[–]DavidB-TPW 0 points1 point  (0 children)

Okay. I will try this tomorrow and let you know either way what happens. Thanks for the advice!

[–]DavidB-TPW 0 points1 point  (6 children)

Okay, so I tried this and it did not work unfortunately. When I tried installing the servicing stack update, I got the same "This update is not applicable" error that I've been getting for everything that I have tried.

[–]4wh457 0 points1 point  (5 children)

Are you on the fall creators update (1709)? If not you need to first update to that using this tool and only then can you install cumulative updates for it.

[–]DavidB-TPW 0 points1 point  (4 children)

I'm already on 1709. The Windows installation that I am having this problem on is only about a month old. It's a new laptop, and I always wipe everything to make sure all the crap from the OEM is gone.

[–]4wh457 0 points1 point  (3 children)

Try to completely reset windows update with this tool. This has worked for me when seemingly nothing else did before. Just be prepared for the first update check after the reset to take ages because it needs to rebuild the whole update database.

[–]DavidB-TPW 0 points1 point  (2 children)

Nope! Still didn't work!

[–]4wh457 0 points1 point  (1 child)

Other than doing the following:

  1. Restart PC

  2. Run the tool again and choose option 2 and let it finish

  3. Restart PC again

  4. Search for updates

I don't know really. If that doesn't work the next step I'd try is a repair windows install/in-place upgrade but since that's gonna happen anyway when summer creators update launches I'd just wait for that instead.

[–]DavidB-TPW 0 points1 point  (0 children)

I tried this too and it didn't work. The latest from the rumor mill suggests that the SCU has been pushed to May 8, which lines up with the May Patch Tuesday. Hopefully it's sooner than that. I really would like to get this fixed, but I really don't want to screw around with it unless the update doesn't fix it.

[–]COMPUTER1313 0 points1 point  (0 children)

Restart and update: Laptop only shows a black screen with a mouse cursor after the restart. Leaving it running overnight has no effect. Sometimes it refuses to go to sleep mode while showing the black screen. Multiple reboots are needed to get it working again, and it appears the update was never installed in the first place.

Restart and shutdown, then turn on again: "We couldn’t complete the updates. Undoing changes. Don’t turn off your computer."

DISM RestoreHealth, sfc/scannow, automatic maintenance and Windows Update Troubleshooter had no effect.

I'm probably going to wait for April Update and update by using a flash drive that has the installation files. Then again, the laptop manufacturer said only Windows 7, 8.1 and vanilla 10 (aka 2015 version) were supported, and the Anniversary update for Windows 10 was unsupported.

[–]xdegen 0 points1 point  (0 children)

After this update last night I shut down my PC. Then this morning when I logged in, and typed in my password, the screen sat there for a while logging me in.. then went blank for about 2 whole minutes and said there was "no signal" on my monitor. Then it turned itself back on and said my device was offline. Then it logged in fine right after that.

So I dunno wtf that was about..

[–]BlooM_HR 0 points1 point  (0 children)

I installed updates and for me when I play games or look at pictures,the window just crashes or closes by itself. Been experiencing quite weird behavior. Going to delete the update unfortunately. Not having a best experience with it so far.

[–]nickwithtea93 0 points1 point  (0 children)

updated and had no issues, windows 10pro on a desktop

[–]Ruga-chan 0 points1 point  (0 children)

Installed successfully, at first it kept saying in the Update tab that the PC needed to restart for the update to apply even though I already restarted it 2 times and the update showed up as successfully installed in the update history.

Just waited a bit and it went away on it's own, don't know what that was about.

[–]321bluf 0 points1 point  (0 children)

Taskbar appears on fullscreen videos in edge when it will be fixed. I have been reporting it for one year. Theres a thread on microaoft support comprising of 1500 messages with same complaint.

[–]anthion 0 points1 point  (0 children)

An update KB4093112 got pushed last night and everything seems to be good now!

[–]creepycoffeemonster 0 points1 point  (0 children)

This update made my laptop automatically restart. But thank fucking god it came through fine.

[–]MilkNutty 0 points1 point  (1 child)

If I am on 17134 can I get off insiders? Or stay on?

[–]mvaneerdeSenior Software Engineer 4 points5 points  (0 children)

Stay on until you see an official announcement from Microsoft.

[–]SnicketBottom 0 points1 point  (0 children)

Quick install with no issues 👌