If you installed KB5005033, watch out for these issues

It comes as no surprise that some bugs have managed to shimmy their way in some new software, especially if we’re talking about Microsoft’s Patch Tuesday patch release since we’ve always had to deal with such situations.

And although some thought that this might even be one of the rare occasions where the Redmond company delivers issue-free fixes, unfortunately, it’s not the case.

If you are running Windows 10 versions 21H1, 20H2, or 2004, it’s highly possible that you’ve dealt with some of the issues we are about to list, since you’ve installed KB5005033.

These are the bugs that came with KB5005033

KB5005033 creates issues with deskptop icons

It wasn’t long since the big patch package was released by Microsoft and already users are reporting on some serious problems that they’ve had to deal with it since installing said software.

We’ve now learned that, after installing KB5005033, some people are having trouble with their desktop icons. They either get deleted or turn blank and unresponsive.

There is no apparent reason for why this is happening, but we’re sure that the engineers at Microsoft will be looking into it.

Can’t install KB5005033

While some users are struggling with the issues that came with the cumulative update, others haven’t quite gotten around to installing it yet, and not for lack of trying.

Reports are coming in that many people are still having trouble with applying this software, after downloading it.

To be honest the only real reason I want to update is I have a Windows Mixed Reality VR headset and it likely needs the update. I have even tried manually downloading the update from Microsofts catalog but it fails during manual installation about 20% in. The source media I used for the installation of Windows was the Windows Media Creation Tool from a few months ago.

The user that reported this issue is trying to install KB5005033 on his Windows 10 Pro, version 20H2, device.

Error 0x80070003 while trying to install KB5005033

It seems that being unable to install this cumulative update is a much wider spread problem than we initially thought. Many people are struggling with installing the fix patch and are unsure why this is happening.

But this case doesn’t just relate to the new cumulative update, as the user explains that he has trouble trying to install other updates as well.

After only going through with half a quarter of the installation, the system stops the process, restarts, and then reverts the changes.

Trouble installing August SSU and CU if you lack May SSU

Apparently, if you skipped one of the SSU packages that came in the previous months, installing the current ones won’t be such a walk in the park after all.

As this Reddit user soon found out, he had to perform a few more tasks than initially planned, just in order to successfully apply KB5005033 to his OS.

I was excited to hear yesterday that MS had released a separate August SSU to resolve the issue with the superseded and required May SSU. However, with my initial testing on the machines in my org that fall into this category (still on April CU because of missing may patches), the August SSU installed and the CU KB5005033 show installed. However the OS build Version doesn’t change. Found it odd as well that when ConfigMgr finished installing CU, no restart required.

This is a matter worth looking into with more details so we will keep an open eye for reports concerning problems that users encounter after installing any of the August Patch Tuesday cumulative updates.

Once we hear of such issues, you will as well, so we can keep track and know exactly what to expect from Microsoft’s latest patch batch.

What issues have you run into since installing KB5005033? Let us know in the comments section below.