Windows 10 v1903 blocked on PCs running 3rd-party antivirus tools
Microsoft confirmed that third-party antivirus products are causing Windows machines to suddenly freeze. The issue appears on different Windows versions after users installed the April 2019 Patch Tuesday update.
Microsoft is hardly recovering from the bad reputation caused by the October 2018 Update released last year. The company is determined to improve the quality of its biannual feature updates.
That was the reason the Redmond giant decided to delay the release of Windows 10 May 2019 Update. Windows Insiders in the Release Preview ring are currently working really hard to test the update.
Third-party antivirus products are to be blamed
It seems like Microsoft is back with another round of bugs with this month’s Patch Tuesday cycle. Recent reports suggest that some third-party antivirus products are causing various issues for Windows 7 and Windows Server 2008 R2.
Furthermore, Windows 10 users are also experiencing some serious performance issues after the installation of the latest update. The Windows April 2019 Update bugs are affecting users who are running antivirus products from Avira, Sophos, Avast, ArcaBit and McAfee.
That is the reason Microsoft decided to block the update for these third-party antivirus programs. Systems running any of these antivirus solutions can no longer download the updates.
Avast and ArcaBit recently addressed the issue by releasing a new round of updates. If you are facing any such issues, install the latest updates released by security vendors. Other security developers are also working on fixing the issue and the corresponding updates are expected to be released soon.
Apparently, Microsoft made some changes to a core Windows component, CSRSS and that is responsible for creating the deadlock. Microsoft needs to collaborate with security vendors to come up with a permanent solution for its users.
RELATED ARTICLES YOU NEED TO CHECK OUT:
- Download the April 2019 Patch Tuesday updates today
- Windows 10 April 2019 Update no longer affected by GSOD errors