Another controversy surrounding the latest Windows updates, although luckily this time no serious problems were found. As many of our readers know, Microsoft uses the second Tuesday of every month to release security updates not introduce new featuresbut which are necessary for Fix bugs and potential vulnerabilities.

In theory, those Windows updates are easier and should cause less problems than semi-annual updates, but unfortunately it is common for the opposite to happen. One of the most common errors that occur with these types of updates is installation failure or installation failure, which means that the installation will be attempted but the process will not complete.

With the December patch, Microsoft once again released updates for Windows focused on security and bug fixes. His arrival happened only a few days ago, but we could already confirm it they cause problemsand some are quite important, as we shall see next.

For a list of known issues, incl connection failures via the Microsoft ODBC SQL Server Driver and conflicts errors are added between installations and ISO images with Microsoft Edge Legacy prevent network adapters from being created on some Hyper-V hosts on Windows Server. The update is tagged as KB5021249 and Microsoft has already offered a workaround that involves entering the following commands in PowerShell with administrator privileges:

“$lang = (Get-WinSystemLocale).Name”

“C:\Windows\system32\wbem\mofcomp.exe C:\Windows\system32\wbem\$lang\VfpExt.mfl”

“C:\Windows\system32\wbem\mofcomp.exe C:\Windows\system32\wbem\VfpExt.mof”

Microsoft confirmed it working on a solution which will be patched soon, but hasn’t confirmed any release date, so all affected users can do now is wait.

A few days ago I updated Windows 10 to version 22H2 and within a few days one of my SSD drives disappeared. It wasn’t the first time this had happened, but only from one of those it had happened to I thought it might be a hardware failure. I uninstalled the update, reinstalled windows 10 without deleting the files and everything was still the same, so I tried the SSD in another PC and it worked, which made me think there might be something wrong with my motherboard

However, my surprise was great when the SSD it worked again on my pc when i plugged it back in, all this after reverting to Windows 10 21H1. I won’t lie to you I’m starting to dread upgrading the OSand I think the windows update problem is already going from brown to dark.