News, tips, advice, support for Windows, Office, PCs & more. Tech help. No bull. We're community supported by donations from our Plus Members, and proud of it
Home icon Home icon Home icon Email icon RSS icon
  • Search Results for 'KB4517389'

    Home Forums Search Search Results for 'KB4517389'

    Viewing 15 results - 1 through 15 (of 26 total)
    • Author
      Search Results
    • #1981225

      gborn
      AskWoody_MVP

      Edge is broken for me.  Out of Band patches already applied: 4522014 and 4524149.  After application of 4520008, Edge will not launch.

      Concering the Edge issue mentioned from some users: my suspicion has been confirmed by affected blog reader. Have a look at my blog post Windows 10 V1903: Update KB4517389 breaks Edge Browser [Fix]. There I outlines the root cause and a possible workaround. German users has confirmed, that the solution works.

      #1979836

      anonymous
      #1979280

      EP
      AskWoody_MVP

      what about KB4517389, mr anonymous? have you tried that new update with Wordpad?

      • This reply was modified 4 days, 8 hours ago by  EP.
      1 user thanked author for this post.

      anonymous

      The real fun was brought to users with Hyper-V VMs running 1903. After installing KB4517389, VMs hang on boot because the new and broken Hyper-V GFX driver (introduced in 1903, bugs reported back in May to the Feedback Hub, nothing fixed as of today) crashes. Best of all, after uninstalling KB4517389 via Windows built-in recovery tools (pulling the virtual plug 2 two times to get into the recovery console? Really, Microsoft?), Windows Update gets mad and hogs on the CPU forever. The workaround? Ditch the VM and build a new one from scratch; and don’t install 1903 even if previous versions run out of support soon! Better running an unsupported version than a version that has severe memory leaks (new Hyper-V GFX driver) and in the end, won’t boot.

      2 users thanked author for this post.

      petesmst
      AskWoody Plus

      See reply #1861126 above. This “work-around” worked fine until KB4517389 arrived. Versions prior to vMWare 15 no-longer work with the latest version of Windows 1903. If you are “happy” to operate only 1 VM at a time, VMware Workstation 15 Player (free for non-commercial use) works just fine.

      My Rig: AMD Ryzen 9 3900X 12-Core CPU; MSI X570-A PRO Mobo; Win 10 Pro (64 bit)-(UEFI-booted); 32GB RAM; 2TB Corsair Force Series MP600 2TB PCIe Gen 4.0 M.2 NVMe SSD. 1TB SAMSUNG 960 EVO M.2 NVME SSD; 512GB SAMSUNG 850 PRO SSD; Seagate 2TB Barracuda SATA6G HDD; Nvidia GeForce TX 2060 Super Ventus Graphics Card (SLI); Office 365 Home; Condusiv SSDKeeper Professional; Acronis TI 2020 Premium, VMWare Workstation12 Pro. WD My Book 3 1TB USB External Backup Drive). Dell G-Sync 144Hz Monitor.

      • This reply was modified 4 days, 16 hours ago by  petesmst. Reason: Corrected typos
      • This reply was modified 4 days, 16 hours ago by  petesmst.
      1 user thanked author for this post.

      Alex5723
      AskWoody Plus

      We are now getting the Windows 10 November 2019 Update (19H2) ready for release. We believe that Build 18363.418 is the final build and we will continue to improve the overall experience of 19H2 on customers’ PCs as part of our normal servicing cadence. Build 18363.418 includes all of the latest 19H2 features as well as the latest fixes included as part of KB4517389. Windows Insiders in the Release Preview ring already have this build, so no action is needed from them to get this build.

      As we have communicated previously, the May 2019 Update (version 1903) and November 2019 Update (version 1909) share the same servicing content. That means they share the same Cumulative Update packages….

      Getting the November 2019 Update Ready for Release

      Anyone wishing to download : Feature update to Windows 10, version 1909 (18363.418) amd64

      https://uupdump.ml/download.php?id=3cef64fc-87f1-4490-9d21-3a632babecb1&pack=en-us&edition=CORE

      • This topic was modified 4 days, 20 hours ago by  Alex5723.
      #1978872

      gborn
      AskWoody_MVP

      I also was seeing the start menu search problem along with the action center refusing to open after installing the patches from before the October patch Tuesday.  removing the cumulative updates allowed the task bar search and action center to run again.

      I probably wasn’t very prudent, but I did decide to let Windows Update install the October Patch Tuesday update.  My task bar search, Cortana and Action Center all failed after reboot so I removed the latest patch.

      Concerning the start menu, search and action center issues in Windows 10 Version 1903 (and probably older Win 10 build) I wrote a blog post Windows 10 October 2019 Patchday (Start menu) issues. It seems not isolated cases. Here’s the beef derived with the help from my German blog readers and some MS Answers users confirmed that.

      Addendum: Startmenu issues are not fixed! German blog reader Janami25 left this comment for Windows 10 Version 1903 (I’ve translated it):

      My original guess with the first problem update KB4524147 has been confirmed here [within my German blog post]. Once you have installed this first “problematic” update, you will notice that you have issues with the start menu. If you only uninstall this update, newer patches can’t fix the issues.

      In my opinion, it mandatory to restore a system backup made BEFORE installing KB4524147 for the first time. And then install the very latest patch [from October 8, 2019]. Only then the issues with the start menu was solved. At least with me. So, before installing the KB4517389 (18362.418) restore a much older Windows version.

      Janami25 postet also a link to this Microsoft Answers forum post, where user Al McNaught also reported a broken start menu and user mirovb confirmed the obervation zited above. I’ve made a few suggestions within my article to overcome this situation. Maybe it helps.

      Windows 10 is a wonder box – but Microsoft’s position is clear Patching as a social responsibility – year, they force their Windows 10 users to gain high administrator skills and keep them trained at a daily base – we are all weaponed for the challenges of the 21th century ;-).

      2 users thanked author for this post.
      #1978531

      mark.busby
      AskWoody Lounger

      Hi there,

      Is anyone aware of issues/a fix for the symptoms below please.  Desperate for a fix asap !

      – Windows 10 (1903 latest version/updates as on today) or Windows 7 32-bit
      – After installing KB4517389 on these Windows systems, when opening 16-bit applications an error message is displayed “unexpected error; quitting”
      – After removing the update the application works fine once more.

      I’d like to establish what is causing this error so I can prevent it from crashing my 32-bit apps, or how to prevent this single update from installing automatically as part of the Windows Updates process in the future.

      Thank you,
      Mark Busby
      Moderator Edit: Removal of email address

      1 user thanked author for this post.
      #1978494

      smcabery
      AskWoody Lounger

      Observation,

      Just manually installed KB4517389 on a VM and the printing issue does seem to be fixed however Edge would not run. Outlook would not run. Upon further review there were several processes suspended.  Uninstalled KB4517389 and VM was working perfectly with no processes suspended.  VM is currently sitting at 18362.357

      1 user thanked author for this post.
      #1978439

      anonymous

      My nephew has an HP Pavillion laptop running Windows 10 v1903 – assuming home version.

      it automatically downloaded and installed three updates on 10-9-19:
      KB4517389
      KB4515871
      KB4521863 – security patch

      After the pc rebooted, once the desktop icons loaded, the pc started flashing on and off – like a strobe effect.  A restart did not clear this up.
      Some programs launched, others wouldn’t.
      I was able to finally, uninstall the first 2 updates , didn’t think the security patch would have messed things up, restart the pc and all was fine.
      I looked up both those KBs, but did not see anything glaring that might cause this issue.

      Anyone else see anything similar?

      thanks,
      George

      #1978094

      E Pericoloso Sporgersi
      AskWoody Plus

      I requested the October 8 update(s).

      I got KB4517389, and the usual anti-malware and AV updates.

      They installed flawlessly. No issues at all. 

      All that on a Clevo P17SM-A, Windows 10 Home x64 v.1903

      What’s keeping v.1909? Or will that be skipped in favour of v.2003? 

      #1978006

      EP
      AskWoody_MVP

      it looks like Microsoft has redeemed themselves with the KB4517389 update released on 10/8

      #1977974

      Jon
      AskWoody Plus

      The version you see with the “winver” command is the version you are running.

      Currently the bug with the cumulative updates showing twice is due to this:  the cumulative updates are silently packaged with the Servicing Stack Updates.  They’re supposed to install at the same time, but in certain circumstances, such as the system being too far behind on CU updates and missing certain Servicing Stack prerequisites, they do not.  The servicing stack update will report that it’s installed as the CU, and then during the actual CU update, the same update will show as having installed twice, with a (2) listed in the Windows Update History.

      To verify what actually made it into the system, go to the “C:\Windows\servicing\Sessions” directory, and read the numbered XML docs that have today’s timestamp.  Near the top will be a line similar to the following:

      <Phase seq=”1″>
      <package id=”Package_for_KB4521863~31bf3856ad364e35~amd64~~18362.411.1.3″ name=”KB4521863″ targetState=”Installed” options=”17″/>
      </Phase>

      That tells you what actually installed.  My guess is that in one of those files, you’ll see the KB4521863 number I just pasted, because that’s the servicing stack update from today.  Were you to reboot and check again, you’d indeed see KB4517389 available to install (“again”) and that is what you want to hold off on doing.

      Hi Anonymous,

      Good call. The KB4521863 SSU from October 8th was indeed installed. I opened the XML files, did a “Ctrl+F” search for keyword “Installed” and found the following packages installed:

      Package~31bf3856ad364e35~amd64~~10.0.18362.1″ name=”Windows Foundation” targetState=”Installed”

      <package id=”Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~10.0.18362.1″ name=”Windows Foundation” targetState=”Installed” options=”5″/>

      <package id=”Package_for_KB4521863~31bf3856ad364e35~amd64~~18362.411.1.3″ name=”KB4521863″ targetState=”Installed” options=”17″/>

      <package id=”Package_for_KB4516115~31bf3856ad364e35~amd64~~10.0.1.0″ name=”KB4516115″ targetState=”Installed” options=”0″/>

      <package id=”Package_for_DotNetRollup~31bf3856ad364e35~amd64~~10.0.1.3012″ name=”KB4515871″ targetState=”Installed” options=”0″/>

      <package id=”Package_for_RollupFix~31bf3856ad364e35~amd64~~18362.418.1.9″ name=”KB4517389″ targetState=”Installed” options=”17″/>

      This may sound silly, but try checking for updates again. There have been incidents where the CU (supposedly) installs twice at least as recorded in the History, but maybe just didn’t finish the first time. If it shows up again, install it again.

      (It’s happened to me)

      Thanks PKCano. I checked for updates a second time and KB4517389 began installing again. Now to roll back to September 10th – OS Build 18362.387 (KB4517211).

      • This reply was modified 6 days, 4 hours ago by  Jon.
      • This reply was modified 6 days, 4 hours ago by  Jon.
      #1977779

      Kobold Curry Chef
      AskWoody Lounger

      I can corroborate. I built a new Win10 Pro v1903 VM earlier this week, using the current v1903 ISO, and experienced the Start menu critical error after KB4524147 was installed. (But not the printer spooler crash that I saw on other, newly upgraded to 1903 boxes.)

      After applying KB4517389 and rebooting, the Start menu critical error persists. Hooray!

      1 user thanked author for this post.
      #1977760

      woody
      Da Boss

      Mayanik Parmar at Windows Latest reports on more Start menu problems:

      Users have reported on Microsoft community forum and Reddit that Windows 10 KB4517389 also breaks the Start menu with a critical error, and it’s still unclear what is causing Start menu problems.

      (The Reddit link points back to the discussion I noted here.)

    Viewing 15 results - 1 through 15 (of 26 total)