nir Posted October 15, 2018 Share Posted October 15, 2018 Intel and HP issues should now be correctedMicrosoft has released a pair of updates supposed to resolve issues experienced by HP and Intel systems upgraded to Windows 10 version 1809. The release of Windows 10 October 2018 Update (version 1809) has been far from smooth, and so far users have reported all kinds of bugs, including issues breaking down audio and causing BSODs after the upgrade. The first problem leaving them with no sound on Windows 10 version 1809 occurred in the case of Intel audio hardware. Update KB4468550 is specifically supposed to fix it and restore the sound on the impacted machines. “This update addresses an issue where after installing the Intel Smart Sound Technology driver (version 09.21.00.3755) via Windows Update or manually, computer audio may stop working,” Microsoft briefly says in the description of the update. The patch is released on Windows Update for affected systems, and users can also download it from the Microsoft Update Catalog. A system reboot is required to complete the installation. The HP fix KB4468304 repairs the HP bug triggering a BSOD at boot after upgrading to Windows 10 version 1809. Microsoft confirmed this issue late on Friday, and the fix is now available on Windows Update and on the Microsoft Update Catalog. Microsoft says the same glitch could be experienced on Windows 10 version 1803 (April 2018 Update), so the update would be offered to systems running this older release too. “After installing the HP keyboard driver, version 11.0.3.1, via Windows Update or if you manually installed it, HP devices may experience a blue screen stop error: WDF_VIOLATION,” Microsoft says. Right now, Windows 10 October 2018 Update is still suspended, and no other systems can install it. The rollout has been halted earlier this month after Microsoft discovered a critical bug leading to data loss on a number of systems. A fix has already been developed, but it’s currently being tested as part of the Windows Insider program.Source Link to comment Share on other sites More sharing options...
steven36 Posted October 15, 2018 Share Posted October 15, 2018 it dont matter that they dont offer Windows 10 October 2018 update atm because these driver updates didn't just just effect Windows 10 build 1809 Update for Windows 10 1709, Windows 10 1803 and Windows 10 1809 for x64-based Systems (KB4468550) Update for Windows Server 2016 and Windows Server 2019 for x64-based Systems (KB4468550) https://www.catalog.update.microsoft.com/Search.aspx?q=KB4468550 Windows 10 audio problems? Intel issued buggy driver but we fixed it, says Microsoft https://www.zdnet.com/article/windows-10-audio-problems-intel-issued-buggy-driver-but-we-fixed-it-says-microsoft/ It effects RS 4 as well and the HP BSOD fix is old news they released a fix for it last week and it effected RS4 as well. Bogdan Popa kept blaming it on cumulative update KB4464330 before , now hes figured out part of it the old news, but he still not figured out that the the botched audio driver effected builds 1803 and 1809 .. Your Pc could be messed up and you wouldn't even know why by reading softpedia windows news , you be trying remove the wrong updates or be using windows they not even post about. he writes a story about what happen every since Oct 9 and screw up on the audio issue witch what was wrong , and its been on auto updates for 2 days before most of the windows news posted it 10/13/2018, it was a Windows 10 problem not a build 1809 problem.. Poor journalism! Some sites posted about it yesterday but i was not on here.. Link to comment Share on other sites More sharing options...
Karlston Posted October 15, 2018 Share Posted October 15, 2018 Woody's take... Last week, Microsoft pushed two buggy drivers onto Win10 machines. A bad keyboard driver triggered blue screens on HP computers. A buggy audio driver turned off Intel Audio sound. They were fixed over the weekend with KB 4468304 and KB 4468550, respectively. Here’s how to protect your computer from Microsoft’s driver assault. Thinkstock Don’t know about you, but I’m well beyond fed up with all of the pushed Windows bugs. If you installed your Patch Tuesday patches last week like a good little lemming, Microsoft may have put you in an inescapable loop of blue screens, or turned off your audio. If either of those plagues hit you, there’s a complex series of manual steps you can take to work around the problem, combined with two new patches that may help if you can get your PC to boot. That’s assuming you haven’t already bought a new machine, or taken the busted one in for repair. First, the HP blue screens. I talked about the symptoms on Thursday: After installing the latest Win10 1803 or 1809 cumulative updates, HP machines sprouted WDF_VIOLATION blue screens. If you reboot, the BSOD comes back. Ends up that the BSODs weren’t caused by the cumulative updates — at least not directly — but were, in fact, caused by a bad keyboard driver update that was pushed out the Windows Update chute at the same time as the cumulative updates. Microsoft now documents the problem in KB 4468304: HP Devices may experience blue screen error WDF_VIOLATION after installing HP Keyboard driver (11.0.3.1). ... Microsoft has identified an HP driver with known incompatibility with certain HP devices on Windows 10 versions 1803 and 1809. On October 11, 2018 Microsoft removed the driver from Windows Update to reduce the number of devices affected. Additionally, Microsoft has released this update to remove the incompatible driver from devices pending reboot. HP is actively working on this issue. Which is all well and good, but if you’re in a blue screen boot loop, having a silver bullet like this one doesn’t help. You can't shoot your bad PC with a silver bullet from your phone. If you can’t get your HP PC to boot, you need to find KB 4468372, which has the details on booting around a serial BSOD. (A historical side note: The bad driver was released on Patch Tuesday, Oct. 9. This KB article says it was pulled on Oct. 11. The article was published late Friday, Oct. 12. Let’s hear it for rapid response.) Over on the audio driver side, folks running Windows Update for Win10 1709, 1803 and 1809 discovered that the sound stopped working, with the message “No Audio Output Device Is Installed” — something of a shock to those who have had audio output devices working for years. On Friday, Microsoft audio engineer Matthew van Eerde published this on the MSDN blog: If Windows Update sent you Intel Audio Controller version 9.21.0.3755 by mistake, uninstall it. … If Windows Update sent you Intel Audio Controller version 9.21.0.3755 by mistake, uninstall it On Saturday, Microsoft released KB 4468550, which fixes the problem by uninstalling the bad driver: This update addresses an issue where after installing the Intel Smart Sound Technology driver (version 09.21.00.3755) via Windows Update or manually, computer audio may stop working. The KB article extends the bug description to include Win10 version 1709. While it’s true that you may have manually installed the bad driver, it’s far, far more likely that Microsoft served it up as part of the Windows Update process. Reddit poster DriverCoyote had some choice comments: I manually installed 8544 and then Microsoft pushes this update, which puts me on 8549 (Realtek drivers). Welp, guess what the updater does after checking for an update? Now it downloads 8475! It reverted my audio driver for literally no reason. All of this has to make you wonder why in the Sam Hill anybody would want Microsoft pushing buggy drivers onto machines that are working fine with the old drivers. Yes, there are times when you might want to update a driver, but my recommendation has long been that you update drivers directly from the manufacturer’s site. This month demonstrates, once again, how foolish it’s become to let Microsoft blindly push patches onto your machine. If you want to stop automatic driver updates, it’s easy in Win10 Pro and Education, using the “Do not include drivers with Windows Update” group policy. It isn’t so easy in Win10 Home, where you have to manually edit a registry entry. Muaro Huculak has step-by-step details for both procedures on the Windows Central blog. If you think October’s Patch Tuesday has been easy, you haven’t been following along. Get the straight story on the AskWoody Lounge. Source: A second bad driver — this one for audio — gets pushed out by Windows Update. Protect yourself! (Computerworld - Woody Leonhard) Link to comment Share on other sites More sharing options...
steven36 Posted October 15, 2018 Share Posted October 15, 2018 4 minutes ago, Karlston said: Woody's take... The truth like i told everyone before best to disable auto driver updates on windows 10 if you use it ..i dont use windows 10 anymore but i keep up with it when a new upgrade comes out its always fun to watch them reak havoc on there users . Link to comment Share on other sites More sharing options...
Karlston Posted October 15, 2018 Share Posted October 15, 2018 4 minutes ago, steven36 said: best to disable auto driver updates on windows 10 if you use it Absolutely 100% great advice... Microsoft has a horrid history of updating drivers to older and/or buggier versions. And also for their Windows updates generally. Link to comment Share on other sites More sharing options...
BimBamSmash Posted October 16, 2018 Share Posted October 16, 2018 Owning aging hardware from 2012 means no driver updates for me. I suppose this is about the only occasion it doesn't feel like I am missing out. 😉 Link to comment Share on other sites More sharing options...
erp-ster0 Posted October 16, 2018 Share Posted October 16, 2018 On 10/15/2018 at 12:02 PM, Karlston said: Absolutely 100% great advice... Microsoft has a horrid history of updating drivers to older and/or buggier versions. And also for their Windows updates generally. driver updates can be easily disabled with either WUMT or wumgr from github Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.