Windows 11 has continued to notch up known issues as Microsoft admitted to problems in the Intel Smart Sound department and Microsoft Installer following a security update.

The [1]former turned up earlier this week, when Microsoft realised that "certain versions" of drivers for Intel Smart Sound Technology (SST) could tip Windows 11 into a blue screen (of death). The driver involved is IntcAudioBus.sys and file versions 10.29.0.5152 and earlier or 10.30.0.5152 and earlier are affected.

The workaround is, unsurprisingly, to get an updated driver from one's OEM. 10.30.00.5714 and later or 10.29.00.5714 and later should do it, according to Microsoft. Slightly confusingly, "for addressing this issue, 10.30.x versions are not newer than 10.29.x versions." The key bit is the last of the version number.

[2]

While a compatibility block was flung up to prevent any more users with sound drivers not to Windows 11's taste updating the OS, others optimistically applying the company's security patches may not have been so lucky.

[3]Survey shows XP lingers on while Windows 11 makes a 0.21% ripple in the enterprise

[4]There's something to be said for delayed gratification when Windows 11 is this full of bugs

[5]FYI: If the latest Windows 11 really wants to use Edge, it will use Edge no matter what

[6]Windows 10 2004 is nearing the end of the road. Time for a Windows 11 upgrade?

[7]KB5007215 was dispensed to the faithful on 9 November and, as well as noting problems with connecting to print servers in the patch's known issues, yesterday Microsoft had to add [8]one of its side effects to the Windows release health dashboard. In this case the Microsoft Installer has been left unwell following the update (or its later siblings) and could "have issues repairing or updating apps."

One of the affected apps is part of Kaspersky's Endpoint Security 11 for Windows. Kaspersky [9]noted that while its app would remain functioning correctly, problems might happen when updating or changing the scope of the application.

[10]

Kaspersky's recommendation is to temporarily hold off from the update (Microsoft said it is "working on a resolution and will provide a new update in an upcoming release"). Otherwise the mitigation appears to be an uninstall and reinstall of the afflicted application.

Very much the software equivalent of turning it off and on again. Even in 2021, the old ways remain the best, it seems. ®

Get our [11]Tech Resources



[1] https://docs.microsoft.com/en-us/windows/release-health/status-windows-11-21H2#2746msgdesc

[2] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/oses&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=2&c=2YZgsmKPwk4N-EyKmMDj2qgAAAJU&t=ct%3Dns%26unitnum%3D2%26raptor%3Dcondor%26pos%3Dtop%26test%3D0

[3] https://www.theregister.com/2021/11/17/lansweeper_windows_11/

[4] https://www.theregister.com/2021/11/15/windows_11_insiders_bug_fixes/

[5] https://www.theregister.com/2021/11/11/latest_windows_11_build_enforces_edge_links/

[6] https://www.theregister.com/2021/11/10/windows_10_2004_end/

[7] https://support.microsoft.com/en-gb/topic/november-9-2021-kb5007215-os-build-22000-318-775afa5b-dd28-4262-82d2-258da52291ec

[8] https://docs.microsoft.com/en-us/windows/release-health/status-windows-11-21H2#2746msgdesc

[9] https://support.kaspersky.com/15819

[10] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/oses&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44YZgsmKPwk4N-EyKmMDj2qgAAAJU&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0

[11] https://whitepapers.theregister.com/