More uncertainty for Microsoft’s Windows 10 October Update

Giles Ensor avatar. By: Giles Ensor
3 minute read

Home » More uncertainty for Microsoft’s Windows 10 October Update

Oh dear. It’s been a pretty bad month for Microsoft concerning its Windows 10 October 1809 Update release. Microsoft eventually released the update a couple of days ago, but it has run into yet more problems. Let’s look at the issues that have been reported so far.

The Misadventures of Windows 10 October v1809 Continue

ARM Radeon Graphics Cards

The first problem is AMD Radeon graphic cards. Microsoft claims that the main problem is AMD no longer supports two specific graphic processor units (GPUs) – Radeon HD2000 and HD4000.

I’m not sure of all the the negative issues that users may experience with the Windows 10 October 1809 update, but there seems to still be a fair amount. Here are a few I have found:

  • Microsoft Edge may become unresponsive.
  • People are seeing the error “INVALID_POINTER_READ_c0000005_atidxx64.dll,”
  • The lock screen may experience performance issues.
  • The ShellExperienceHost may have issues.

All the above are caused by the two GPUs, and are enough of a concern that Microsoft has blocked the Windows 10 October 1809 update to all machines that contain either of these two GPUs. No figures have been published (so far) about how many machines have been affected.

Just for a change, Microsoft is keeping quiet about the release of the update for this update. As usual, if this has affected you, you will just have to wait and see.

Micro Security Products

It is also being reported that some Trend Micro security products are being affected by the Windows 10 October 1809 update, specifically ‘OfficeScan‘ and the ironically named ‘Worry-Free Business Security‘.

Trend Micro is working with Microsoft and is trying to get a fix out as quickly as possible. Until this happens, Microsoft is blocking updates for machines running these programs.

Intel Display Audio Device Drivers

Windows is also blocking the update for any machines running some Intel systems, specifically intcdaud.sys – versions 10.25.0.3 to 10.25.0.8. This from Microsoft:

To ensure a seamless experience, we are blocking devices from being offered Windows 10 version 1809, until updated Intel device drivers are installed on your current operating system. We recommend that you do not attempt to manually update to Windows 10, version 1809, using the Update Now button or the Media Creation Tool from the Microsoft Software Download Center until newer Intel device drivers are available with the update.

However, there is good news. Intel has already released an update, and are advising anyone who has a Intel rig that is 6th gen or later, to ensure they are running Intel Graphics Driver version 24.20.100.6286 or newer before running the Windows 10 October 1809 update.

If you are ready for the update, you can check it out by either going into the settings or by checking Microsoft’s Update Center.

As always, we’d like to here from you. Are you affected by these latest glitches? Have you found a new glitch that hasn’t been reported yet? Then let us know in the comments section below. Thanks!

RELATED POSTS TO CHECK OUT:

Discussions

Next up

New Windows 10 Tablet mode concept shows what could have been

Matthew Adams By: Matthew Adams
2 minute read

Microsoft added Tablet mode to Windows 10 primarily for 2-in-1 laptops and tablets, such as the Surface Pro. Tablet mode displays a start screen from […]

Continue Reading

8 stunning software to create booklets and rule the marketing game

Tashreef Shareef avatar. By: Tashreef Shareef
Less than a 1 minute read

There is no denying that booklets are powerful marketing tools that can help you bring in more leads when done right. Booklets are usually designed […]

Continue Reading

What to do if Hypervisor is not running Windows 10

Milan Stanojevic avatar. By: Milan Stanojevic
6 minute read

Many users use virtualization, but sometimes they might encounter Hypervisor is not running message on their PC. This message will prevent you from using virtualization, […]

Continue Reading