Tuesday April patch also crashes with DNS and headset

A week ago, we saw how complaints were popping up regarding Windows 10 and the April Tuesday patch. Performance issues, profiles and even the appearance of blue screens that now see the continuation of new bugs reported by users.

Follow Microsoft’s test with updates and the KB5001330 patch was not going to be less. Associated with builds 19041.928 and 19042.928 for Windows 10 in branches 20H2 and 2004 respectively, new complaints appear, now related to crashes when connecting a Windows Mixed Reality headset or associated with DNS.

Failures with DNS and Shared Folders

This is an update intended to correct the print-time errors that were generated with the March update and which, however, are causing new ones. As reported in Windows Latest, some users complain about failures to access a shared folder on the network, especially for business customers.

In this case, the problem occurs when you try to access a shared folder on the network. According to Dentrix, the “Link Layer Multicast Name Resolution” (LLMNR) policy is typically enabled by default on all Windows 10 installations, but some users manually disable it to improve network quality.

“After working with Microsoft, we believe we have found a solution that allows us to keep the Microsoft security update installed”,

In this case, to resolve potential shared folder and DNS issues, users should re-enable the LLMNR policy or wait for the next update.

Mixed reality headset issues

Another issue affects users who attempt to update when they have a Windows Mixed Reality headset connected, so they cannot install the KB5001330 patch.

A failure that according to Microsoft can occur if Windows Update is still in bad shape after the last update. In some cases, they claim that the process can be resolved by removing Feature on Demand (FOD) for HoloLens or Mixed Reality.

If you get the error message 0x8007000d when you try to install the KB5001330 patch, you can try uninstalling your headphones and running the following command at the “Command Prompt” prompt.

dism / online / remove-capabilities /capabilityname:Analog.Holographic.Desktop~~~~0.0.1.0 After that restart the system and check if the updates are run again.

For now on the support page there is no reference to these failures and like on other occasions you have to wait or uninstall.

And is that if you have already downloaded the update and find one of these failures, you can eliminate them in the most drastic way, and we have already seen on other occasions, if your computer has been affected by one of these problems, an effective solution is to eliminate the update that caused the failures: a process that goes through the route “Configuration”, “Update and security” and within it, click on “View update history”. The next step is to use the “Uninstall updates” option by marking the corresponding update and then clicking on the “Uninstall” button. And if you haven’t updated yet and are not sure about these complaints, you can temporarily pause the update.

Via | Most recent windows

Back to top button