Microsoft Blocks Windows 10 Version 1809 on Some Intel PCs Stemming from Bad Drivers

UPDATE: Intel has released new drivers remedy the bug, however, the October 2018 Update remains blocked on systems that haven’t installed them yet. Intel says:

Windows 10 October 2018 Update update might well be blocked as a consequence of issues seen with Intel Display Audio Driver versions through that may lead to excessive processor demand and reduced life of the battery. A treatment for these issues is definitely included in Intel Display Audio Driver version, that could be bundled with Intel Graphics Driver version and newer. Intel strongly recommends which users with 6th Generation (codenamed Skylake) or newer processors ensure that Intel Graphics Driver version or newer comes free with their computers before eager to update to Windows 10 October 2018 Update.”

Read the original story below and we’ll keep monitor the glitch in the instance that further updates are important.
“Windows 10 October 2018 Update (version 1809) may cannot install on certain systems caused by incompatible Intel drivers.”

A warning that comes out when trying the first the new OS feature update inside the Media Creation Tool reveals that culprit is a Intel Display Audio device driver (intcdaud.sys, versions –

Microsoft says at an advisory that users should choose new drivers are let go of, and the company emphasizes that manual updates to version 1809 produces further issues.

“Microsoft and Intel have identified a compatibility downside to a range of Intel Display Audio device drivers that may result in excessive processor demand and reduced life cycle of battery. As a result, the update way to Windows 10 October 2018 Update (version 1809) will fail,” the company explains.

“Update already blocked”

Microsoft has blocked the update on systems following these incompatible Intel drivers, in addition to the software giant further explains that this block will likely be removed when new drivers are readily available.

“To ensure a seamless experience, we are going to blocking devices from to choose from Windows 10 version 1809, until updated Intel device drivers they covered your current main system,” the company explains.

“We suggest you do not attempt manually update to Windows 10, version 1809, in the Update Now button or maybe the Media Creation Tool with the Microsoft Software Download Center until newer Intel device drivers are available with the update.”

The block basically prevents Windows 10 October 2018 Update from looking in Windows Update – the manual download alternative for the new OS version. However, users may perhaps also upgrade their PCs making use of Media Creation Tool, though a stern warning would be displayed in the room.

There’s no ETA regarding when the block could be removed, simply because it all depends about how exactly fast Intel publishes new drivers.

How to Download and Install iTunes for Windows 10, 8, 7

You need to iPhone but doesn’t possess a mac?, No issue, in this article we provided you solutions. Know about tips to download and install iTunes for Windows 10, 8 ,7. iTunes is actually a media player or media library software which give the iOS user store and organize its music collections. It’s a common software and used billions of people on the planet. Good thing is that gardeners can download iTunes for Windows and set it up in minutes with very little hiccup.

The best part for this software is that it exists for the popular Os such as Windows and MacOS.

For Mac users, it appears pre-loaded. For Windows, an individual needs to download it separately and for that reason we are here that may help you on how to upload iTunes for Windows OS like 7, 8 and 10

Specification of iTunes for Windows 10, 8, 7

The specifications we mentioned here are provided by Apple itself. So before proceeding further make sure to read it carefully.


PC which includes a 1GHz Intel or AMD processor with support for SSE2 and 512MB of RAM.
To play Standard Definition video coming from the iTunes Store, an Intel Pentium D or faster processor, 512MB of RAM, along with DirectX 9.0-compatible video card is required.
To play 720p HD video, an iTunes LP, or iTunes Extras, a 2.0GHz Intel Core 2 Duo or faster processor, 1GB of RAM, as well as Intel GMA X3000, ATI Radeon X1300, or NVIDIA GeForce 6150 or better is usually recommended.
To play 1080p HD video, a 2.4GHz Intel Core 2 Duo or faster processor, 2GB of RAM, along with Intel GMA X4500HD; ATI Radeon HD 2400; NVIDIA GeForce 8300 GS or better is required.
Screen resolution of 1024×768 or greater; 1280×800 or greater is needed play an iTunes LP or iTunes Extras.
16-bit sound card and speakers.
Internet link to use Apple Music, the iTunes Store, and iTunes Extras.
iTunes-compatible CD or DVD recorder to make audio CDs, MP3 CDs, or back-up CDs or DVDs. Songs from Apple Music catalog is not to be burned to some CD.


Windows 7 or later.
64-bit editions of Windows demand iTunes 64-bit installer.
400MB of available disk space.
Some third-party visualizers may no longer be suitable for this version of iTunes. Please contact the developer to have updated visualizer that’s compatible with iTunes 12.1 or later.
Apple Music, iTunes Store, and iTunes Match availability may vary by country.
Apple Music trial requires sign-up but is available for new subscribers only. Plan automatically renews after trialor later.

If your main device specifications match up with the above-mentioned specifications then you may proceed further.

Microsoft releases new Windows 10 preview with input, accessibility, and check improvements

Microsoft today released completely new Windows 10 preview with input, accessibility, and search improvements. This build arises from the 19H1 branch, that may arrive in initial half of still.

Windows 10 has developed being service, meaning it receives the latest features on a regular basis. Microsoft has released six major updates finished so far: November Update, Anniversary Update, Creators Update, Fall Creators Update, April 2018 Update, and October 2018 Update.

When you write in Vietnamese, you’ll like the chance to learn this build adds support for Vietnamese Telex and Number-key based (VNI) keyboards. You can think about them out with either a hardware keyboard or touch keyboard (Start => Settings => Time & Language => Language => Add a preferred language => Vietnamese => Options => help the Vietnamese Telex keyboard or Vietnamese Number key-based keyboard).

When it comes to the touch keyboard, it now has more symbols. After changing to the number and symbols view (&123), tap this newDue to accessibility improvements, the Narrator now works better with Chrome (directory arrows in scan mode, navigate with tab key, continuous reading commands, and navigating by headings and links). The UI Automation framework now supports translating IAccessible2 information from Chrome, to help IAccessible2 rather than UI Automation. Speaking about Narrator, Braille users will probably be happy to are conscious of a few updates: BRLTTY version 5.6 adds USB support for Inceptor and Orbit 20 displays, BrailleNote Touch is recognized by using USB, Baum displays are able to use B9 and B10 interchangeably, and Liblouis binaries and tables have been updated to version 3.7.0.

This build also introduces a brand new indexing feature that lets Windows search every one of your folders and drives, rather than your documents, pictures, videos, and desktop, by default. You’ll have to switch it on (Windows search settings => Find My Files => Enhanced, intended to start a one-time indexing process ?a be sure that your system is plugged in). After indexing, that could take about Fifteen minutes (longer when you have had many files), you’ll manage to find all your files “almost instantly” with Windows Search, Microsoft promises.
Bug fixes and known issues

This 19H1 build includes another general bug fixes and improvements:

Fixed an issue giving you Settings crashing when invoking actions on certain places, including under Windows Security.
Fixed a matter resulting in some Insider experiencing green screens with IRQL_NOT_LESS_OR_EQUAL in the flight.
Fixed a major issue where the Action Center might suddenly show up on the opposite side of this screen before appearing along the correct side.
Fixed problems resulting in the Action Center icon sometimes showing some unread notifications, properly opened Action Center it might be blank.
Fixed an aspect resulting in Settings crashes on launch for that small number of users.
Fixed a matter resulting in recently opened items sometimes showing in jump lists in spite of “Show recently opened belongings in jump lists” was disabled in Settings.
Fixed an issue where the Built-in Phrases Setting page for ones Pinyin IME would hang temporarily if you clicked any phase throughout the list.
Fixed a worry where Uninstall would certainly be shown just as one option when right-clicking apps in Start if a group policy “Prevent users from uninstalling applications from Start” was enabled.
Fixed a major issue where if you had an inbox app having version number more than 20 characters it wouldn’t be returned this means that if you explore for it.
Fixed issues resulting in switching audio endpoints within the volume flyout within taskbar not working in the past few flights.
Fixed a worry resulting in some users having issues launching inbox apps after updating towards last few flights.
Fixed one factor where if word wrap was enabled when browsing with Notepad utilizing screen reader some words might unexpectedly be read out as two half words and not just one.

Today’s update bumps the Windows 10 build number in the 19H1 branch from 18262 (distributed around testers on October 17) to establish 18267.

This build has five known issues:

Task View ceases to show the + button under New Desktop after creating 2 Virtual Desktops.
Some users will feel the update status cycling between Getting Things Ready, Downloading, and Installing. This may be accompanied with error 0x8024200d because of a failed express package download.
If you change Task Manager settings, purchasing a Task Manager is opened it should revert to default.
If an individual has a have a more and more OTF fonts, or OTF fonts that develop the extended East Asian character set, you could potentially experience some unexpectedly missing text throughout system. We’re creating a fix. Should you encounter treatment plans, navigating for the Fonts folder (c:\windows\fonts) may resolve it.
If you put in any of the recent builds belonging to the Fast ring and move to the Slow ring – optional content as in enabling developer mode will fail. You must remain in the quick ring to add/install/enable optional content. For the reason that optional content is install on builds approved for specific rings.

As it ever was, don’t install this with your production machine.

Windows 10 glitch delays Windows Server 2019

Microsoft is recommending individuals who have downloaded Windows Server 2019 must not install it through to the company has resolved a remote issue with Windows 10, which works with a same code base.

Right after Microsoft announced the availability of Windows Server 2019, it retracted the release to get more detail testing to ensure that the issue with Windows 10 didn’t also affect Windows Server 2019.

At the blog to the move Microsoft said this: “We have temporarily removed all media for Windows Server 2019 and Windows Server, version 1809. We possess also paused the rollout in the latest feature update to Windows 10 inclusive of versions 1809, if we are investigating isolated reports of users missing some files after updating. When you have already downloaded media, please don’t set it up and postpone more information is on the market to proceed.”

Particularly, after the details the Windows 10 Update limited number of users reported any time they upgraded, a selection of their My Documents-type content was missing.

These were not really a broadly reported incidents, plus an overwhelming amount of users who upgraded reported no issues. However, with user data potentially on the line during an upgrade, Microsoft pulled the making of Windows 10 and also put it using a series of additional tests and verifications.

Since Windows Server 2019 is going to be the same codebase as Windows 10, Microsoft also pulled Windows Server 2019 from further downloads pending test results and remediation of these Windows 10 issue.

(When controling both Windows 10 and Windows Server 2019, and having deployed a lot of servers and client systems during the entire public and private preview program and afterwards rolled out a large number of laptops and a hundred servers using the general-availability code of Windows 10 and Windows Server 2019, In a health club have not make similar data issues with any of our implementations.)

Specific to Windows Server 2019, upgrading issue that impacts results are highly unlikely because many servers are built new over completely from scratch with workloads and business data installed or transferred organization systems, so in-place upgrades obviously wouldn’t affect those systems.

For other application servers that are being upgraded on a Windows Server 2016 release for the latest Windows Server 2019, business apps don’t try the Documents folders on servers. Applications and data on servers are located in dedicated folders or on distinct drives than the Windows Server boot drive.

As such we have didn’t have any concerns the fact that the isolated incidents reported on Windows 10 upgrades may possibly any impact on Windows Server systems.

Should the code does become available, most effective for you business as usual for organizations: Test the server against business scenarios, then slide contained in the latest Windows Server main system in a methodical, staged manner throughout on-premises and cloud datacenters.

New Windows 10 1809 bug: Zip data-loss flaw is months old but Microsoft missed it

Windows 10 version 1809 update ‘s still on ice as a result of data-deletion bug embarrassingly missed by Microsoft during preview testing.

Nevertheless few users who ended up getting the Windows 10 October 2018 Update have recently discovered its built-in zip tool is progressing weird things when copying files.

As a 1809 user reported on Reddit, this version of Windows 10 is missing the ‘Do you wish to replace these files’ dialog when copying from the zip archive onto a folder using the identically named file within it.

The problem only typically affect the built-in zip tool in Windows File Explorer as an alternative to third-party zip tools.

The dialog is an essential flag when transferring many files, because it is an opportunity for users to choose whether to replace the identical file, skip replacing the file, or compare your data stored in both files when considering any action.

But without the dialog, it is usually easy to unintentionally overwrite non-identical files.

“Pretty nasty bug since accidentally overwrite folders and have no way of getting it back,” wrote anybody.

Another Reddit user explains the identical zip archive problem differently. When copying from zip, it seems apparant that as if files are usually copied, and Windows File Explorer even indicates the transfer progress.

However, after it’s complete, files within the destination folder didn’t actually been updated. Users then may delete the zip archive and lose their copy of files founded on incorrect information.

Another Reddit user commenting with that report said: “The dilemma is that in 1809, overwriting files by extracting from an archive using File Explorer doesn’t lead to an overwrite prompt dialog and also doesn’t replace any files rrn any respect; it just fails silently. There’s some reports in which it did overwrite items, but accomplished it silently without asking.”

The bug is unable to appear to be as serious as the data-loss issues that prompted Microsoft to halt the Windows 10 1809 rollout.

However, simillar to that bug, this newer one has also been reported via Windows Insider tester 11 weeks ago in Microsoft’s Feedback Hub.

And just like the data-loss bug reports, this report nonetheless attract more than few upvotes, and was subsequently missed by Microsoft through the original round of 1809 testing.

Speculate spotted by BleepingComputer, an engineer for Microsoft’s Windows Insider Program, has confirmed this bug was fixed in the Windows 10 19H1 preview in build 18234, that has released on September 6, twenty eight days before the public turmoil Windows 10 1809.

That patch should mean a fix for the new bug will undoubtedly be available for Windows 10 1809 soon, but it’s another form of Microsoft missing important feedback from testers.

Following Microsoft’s 1809 data-loss debacle, the retailer updated its Feedback Hub to give testers to allocate a severity rating to bug reports, that would alert Microsoft’s Windows engineers to more pressing issues later on.

In the meantime, it’s left the zip bug reporter, Jacob Klein, wondering what else he will present done to attract the issue noticed by Microsoft.

“I ponder whether there was whatever that I may have done when reporting that bug. Get real … It’s gotten just four UpVotes since i have reported it 90 days ago. I filled it all out as completely as I could, and did ‘Recreate my problem’. Learn to impact selection will help you to in the future,” wrote Klein.

His Feedback Hub report explained the condition clearly: “Copying/pasting a list from inside a ZIP will not properly replace an ongoing file. Launch a ZIP file that only has a file to be had. Have another folder available who has the same file name, but different file data. Now make an effort to copy from insize (SIC) the ZIP file, into that other folder.

“What happens: You aren’t getting the prompt to overwrite the file, the file doesn’t copied, while the files modified date DOES get updated. What should happen: You DO take advantage of the prompt to overwrite the file, the file DOES get copied (because you agree to the prompt), also, the file’s modified date only gets updated Once FILE IS UPDATED.”

A Windows 10 insider MVP suggested reporting ingestion to one of Microsoft’s external Insider MVPs since their reports are given more weight than average testers.

There’s a BSOD Bug in Windows 10 Version 1809 Professionals who log in Trigger It Yourselves

We’ve renowned for a while that Windows 10 version 1809, also referred to as October 2018 Update, is regarded as buggiest OS updates ever release, and so it shouldn’t come as a sizable surprise that women have discovered another BSOD bug from your operating system.

And what’s more, it would appear that anyone can reproduce it if their systems have already been upgraded to Windows 10 version 1809, though it’s worth mentioning that some say the same issue exists on previous feature updates too.

Technically, things to do would likely be to head over to Bluetooth settings and repeatedly click the Bluetooth toggle to interchange it don and doff several times.

In the event the bug exists in your system, this few clicks should produce a system crash, forcing the pc and the to reboot.

“Bad Bluetooth drivers?”

Because of the looks of products, there is an issue with Bluetooth drivers and isn’t necessarily based on Windows 10, though simple fact that many claim the disorder has been around for a long time should be part of Microsoft to investigate and part of to correct it.

Reddit users have confirmed throughout this thread how the glitch are usually reproduced to their systems as a result, and even more surprising is usually that a few managed to trigger the BSOD on Microsoft’s own personal Surface computers. For sure, the system essential a Bluetooth adapter installed.

When you need to see the glass half full, it’s pretty complicated to hit hard to recognize by accident, and I’d actually be curious to learn how the first user chanced on it, especially because it requires clicking the Bluetooth toggle repeatedly in a row.

Windows 10 October 2018 Update isn’t readily available download anymore a result of file removal bug, so hopefully, when Microsoft resumes the rollout, that address this trouble as well.

Trivial Post-Intrusion Attack Exploits Windows RID

An novel post-intrusion attack technique allows hackers to hijack a Windows system component called RID, allowing the adversaries to assign administrative privileges to “guest” coupled with other low-level accounts.

The technique is simple and also require a massive amount sophistication, security researcher Sebastian Castro, who discovered the hack, told Threatpost. Microsoft was notified with the attack technique if it was discovered months ago – that has yet use a fix, the researcher said.

“We have realized and crafted a new post-exploitation technique called RID Hijacking,” Castro said inside the recent blog post. “By using only OS resources, you can actually hijack the Remove any existing account along the victim (even the 500 Administrator Built-in Account), and assign it the user account.”

The attack starts within the Relative Identifier (RID), part in Windows user accounts. RIDs truly are a label began this morning Security Account Managers (SAMs), which describe a user’s varying permissions. SAMs ordinarily have RID code end of it to define user permissions.

Two common RIDs particularly are the focus within the attack: the number 500 is normally used after SAMs for an Admin account, while 501 can be utilized for a Guest Account.

The hijacking technique effectively manipulates the registry keys storing this informative article, and modifies the RID with accounts. So, the 501 labeling a guest account is going to be changed to 500, indicating permissions associated with the administrator.

“After compromising a device, it is possible to automatize this attack remotely via PSExec, Remote Desktop, Powershell via using offensive tools like Metasploit,” Castro told Threatpost. “Since it’s really a persistence technique and not just a privilege escalation vector, it can be vital to have elevated privileges already to deploy the attack.”

The Metasploit software to automatize the attack needs meterpreter session contrary to the victim – the module to do this can be found for your latest official launch of the MSF framework at post/windows/manage/rid_hijack, Castro said.

The attack was tested on Xp, Windows Server 2003, Windows 8.1 and Windows 10.

The attack does have drawbacks – structured be done remotely (unless the laptop is left unprotected through the internet). However, examination actually system is often exploited, it’s difficult to detect.

“It can be carried out to find out if a working computer has been victim among the RID Hijacking attack by looking while in the registry and checking for inconsistencies across the SAM,” he told us. “On one other hand, it isn’t so easy to detect right when exploited, comes with attack may be deployed when you use OS resources without triggering any alert on your victim.”

Castro said he reached out Microsoft following module was created in December 2017, but did not receive any types of response internet site.

Microsoft, for its part, told Threatpost that it will be looking into the report.

“Microsoft shows a strong resolve for security including a demonstrated history of investigating and resolving reported vulnerabilities,” Jeff Jones, senior director at Microsoft, told Threatpost. “We’re seeking this report, if we determine found . take further action to remain customers protected, we are going to.?”

Google Nearly Solved Windows 10’s App Pitfall with a Single Browser Update

In 2012, Microsoft released Windows 8, was essentially the company’s first modern software coming with support for just a brand-new Microsoft Store.

This Store, which presently the Windows 8 launch only comprised some 5,000 apps, was designed to provide access to software who had been malware-free and specifically optimized to adapt to different screen resolutions, using focus also used touch input.

Windows RT, prestashop that Microsoft launched simply because foundation of it RT, was in its turn asked to benefit from this Microsoft Store, as apps published here were intended to run on any device, regardless of size or maybe the screen resolution.

This push for Microsoft Store apps has failed and also since then, Microsoft is trying to tackle the possible lack of apps with various concepts, including universal apps (UWP) created for all modern Windows devices, and more often recently, Progressive Web Apps (PWA).

Thinking behind a PWA is rather simple: websites is usually converted into apps, greater than the feeling Windows 10, users can launch them off their desktops, find a live tile throughout the Start menu, and also notifications throughout the Action Center.

But rrnspite of the obvious advantages that your PWA brings to users, developers have not attempted rushed to get rid of such apps, thus recommending customers to access their websites or, in fact, stick with mobile apps for Android and iOS.

Enter Google.

The brand new update for Google Chrome, that the browser to version 70, includes support for Progressive Web Apps too, also, the search giant is definitely an approach identical to the one on Windows 10.

Websites are generally converted into apps that have the benefit of native features like notifications and live tiles. The actual difference is that these apps run in Chrome and also need to be installed for the Microsoft Store, but directly from their official websites.

Unlike Microsoft’s approach, there’s the best chance that Google’s push for PWAs would work. With the same time, it’s planning to resolve the app problem on Windows 10.

It’s all about Google Chrome’s market share. Google’s browser currently runs on more than 60 percent of PCs across the world, and this shows the search company the ability conquer the platforms it’s targeting with latest features. Since through 6 users in 10 run Chrome, every little new feature does have a huge opportunity of becoming a hit. And this is the case of PWAs too.

Throughout their Windows 10 launching a PWA wasn’t a legitimate priority for developers because some people sees the Microsoft Store considering that the one destination for new apps, this isn’t the way it is of Google Chrome.

With its impressive share of the market, Google Chrome can convince developers that PWAs are required, especially this is because it would allow users to access their professional services easier. This technically indicates that PWAs become a factor for selecting a specific service or maybe an alternative, as quite a few users could just stick with a certain product given that it’s offering a PWA.

And due to the fact 6 in 10 users run Chrome, this scenario could actually happen more anticipated, so PWAs could simply turned into a must-have sooner or later.

At this point, there aren’t a considerable amount of PWAs with support for Google Chrome, nevertheless expect devs to push out such apps one at a time in the coming months. Google also wants to expand PWA support for Linux and macOS, technically providing devs with another big cause launching apps for their services.

2, Google will apparently resolve issues that Microsoft continues to be struggling consistently to address. So that it turns out, the search giant had been able to do it with a single browser update, while Microsoft still can’t see that brilliant undeniable fact that would convince devs to code due to platform.

Windows Server 2019 general availability: The direction to go

Microsoft has released Windows Server 2019 to general availability, formally bringing to promote the first major turmoil the Windows Server operating platform in a few years.

Subscribers have gotten the chance to explore the ultra-modern platform for months, but to those who have held off fiddling with Windows Server 2019 until this official release, today it is formally readily available for download.

Security, resiliency, SDN

Among the top features of Windows Server 2019 include enterprise-grade support for hyperconverged infrastructure which may be bundled with the server license, a new desktop GUI, the Project Honolulu server-management tool, security improvements, stronger containers and subsystem for running Linux located on the server.

The new release also embraces software-defined networking (SDN) including virtual-network peering and encryption, auditing and IPv6 support. One of many security features yields simpler to encrypt communications among systems to shield data.

Windows Server 2019 provides resiliency for shielded virtual machines by creating it possible to set up primary and secondary host guardian service (HGS) servers so in case one fails, the remaining kicks in. HGS provides attestation and key protection that are needed to run shielded VMs.
Replace beta code now

For those who haven’t prepped for moving to Windows Server 2019, a smart approach is always start with some of the most commonly deployed areas: native Windows Server features, data-center-focused components and new Windows Admin Center management tools.

Service repair shop that has downloaded a preview release should download and replace any beta code, files and installations along with the code from your general availability release.

Early adopters of Windows Server 2019 located the code base as extremely dependable due to its testing the fact that the semi-annual release cycle has enabled. As a result, hesitancy of organizations to leap into this major update need to be lessened and encourage the more aggressive adoption cycle by enterprises.
The new Windows Server release schedule

General method of getting any product release from Microsoft means the beta testing cycle has finished, the code is now through testing and validation but is formally provided to organizations to begin the process production deployment.

However, unlike previous releases of Windows Server where general availability would mean a significant overhaul from previous version, that may be 3 or 4 years old. But originating in Windows Server 2016, Microsoft initiated a cycle of interim releases of one’s Windows Server code.

It means for the past three years, organizations that elected to be semi-annual channel distribution plans have received code updates twice yearly, so many of the “new” features released in Windows Server 2019 have always been trialed.

These semi-annual releases have enabled the vetting newest features and functions so, unlike previous major releases where everything was cutting edge and untested in diverse environments, lots of features and functions are on second, third and sometimes even fourth updates.

Did your Windows 10 audio live and retire after the update? Microsoft features a fix

Microsoft has released a patch for its recent Windows 10 October 2018 update which fixes an audio issue that has got affected numerous those who completed the update. The fix is presently available through Windows Update oral appliance joins numerous others that Microsoft has released in recent weeks.

The October 2018 Update for Windows 10 was no cost major upgrade Microsoft can make to its flagship os in 2018. Following on within the April Update trapped on tape, this most popular update brought on it a number of exciting features and fixes, but caused a surprising number of problems, too. There seems to be the data deletion bug which halted the update’s rollout for a vacation, CPU usage problems, as well as audio issue, and others. Most of these, for example audio issue, have right now been fixed, though.

The audio update maintain a pool of catchy title of KB4468550, and Microsoft claims, via OnMSFT, the idea, ” addresses something where after installing the Intel Smart Sound Technology driver (version via Windows Update or manually, computer audio may stop working.”

Simply running Windows Update (searching for it from your Windows search bar) should download the most recent bug fix patch should you be affected by the difficulty, or you can download it manually from Microsoft’s Update Catalog if you like.

The bug itself materialized being loss of audio seen on affected systems. Users found themselves not having sound whatsoever, regardless audio source or solution they used. Muting and unmuting made no difference, though quite a few users did report having success with driver updates or rollbacks thus to their particular devices. Microsoft’s stopgap solution for the official fix were uninstall the Intel Audio Controller driver, depending on OnMSFT.

Although this latest audio issue with Windows 10 happens to be fixed, there are many more sound-related problems that you can actually run into aided by the operating system. As soon as you apply the above update and don’t maintain the audio you will need, or meet problems later, consider our help how to fix sound issues in Windows 10. We can have the tips you ought to fix it.