![](\"https:\/\/images.techhive.com\/images\/article\/2015\/12\/bsod-100633647-primary.idge.jpg\"\/)
<\/p>\n
Credit to Author: Woody Leonhard| Date: Fri, 25 May 2018 12:28:00 -0700<\/strong><\/p>\n Looks as if we have a solution for the Avast-related blue screens in Win10 1803 upgrades that I talked about <\/span>earlier this week<\/span><\/a>. Avast heavyweight Ondrej Vlcek chose his words carefully but threw lots of shade at Microsoft for the upgrade installer\u2019s bug.<\/span><\/p>\n Posting on the Avast forum, <\/span>Vlcek says<\/span><\/a>:<\/span><\/p>\n In cooperation with Microsoft we have identified an element of the latest Windows 10 1803 update that is incompatible with the Avast Behavior Shield, causing the aforementioned update to fail in some instances (related to a timing issue, Internet connectivity issue, etc).<\/span><\/p>\n \u201cFail in some instances\u201d is polite shorthand for the symptoms originally described quite accurately by <\/span>gcdrm on Reddit<\/span><\/a>:<\/span><\/p>\n Upon restarting, the computer boots to a blue screen asking the user to choose a keyboard language. After doing so, a few options are given, including to ‘boot from another operating system’. Clicking here will take the user to another blue screen with three options to continue “booting” to:<\/span><\/p>\n The lower two options are identical.<\/span><\/p>\n Running around to get ahead of the band, on May 23, \u201cMicrosoft Agent\u201d Freddrick Pal <\/span>posted on the Microsoft Answers forum<\/span><\/a>:<\/span><\/p>\n Windows 10 April 2018 Update may boot to a \u201cChoose your keyboard layout\u201d screen or to a blank screen with a Recycle Bin \u00a0<\/span><\/p>\n During the upgrade to Windows 10 version 1803, Windows automatically restarts and one of these two conditions might be experienced:<\/span><\/p>\n As is becoming increasingly common on the Answers forum, especially on posts by “Microsoft Agents,” comments to the post are shut off. No discussion possible. It’s not an answer, it’s a diktat. Vlcek goes on to say:<\/span><\/p>\n Luckily, we have found a way to prevent the problem and are now automatically pushing a VPS update to all customers which makes sure that the problem doesn’t happen. The VPS number is 180524-08; all users running this version (or later) should be 100% safe.<\/span><\/p>\n (A VPS is a full update of Avast Behavior Shield.)<\/span><\/p>\n He then gives a complex 18-step procedure for manually getting your computer back if you got zapped by the bug. It\u2019s not for the faint-hearted. And it\u2019s not from Microsoft \u2014 Avast picked it up from <\/span>The Computer Cellar<\/span><\/a>.<\/span><\/p>\n Worth noting: There\u2019s no mention of this bug, or its possible solution, in the second May cumulative update for Win10 version 1803, released two days ago, <\/span>KB 4100403<\/span><\/a>.<\/span><\/p>\n Vlcek ends with an interesting barb:<\/span><\/p>\n In the meantime, we continue to investigate this issue which appears to affect only a small subset of our customers. BTW at this stage, we know it’s not an Avast-specific issue as the problem affects other software as well.<\/span><\/p>\n Based on the evidence I\u2019ve seen, and some of Avast\u2019s comments, I\u2019d be willing to speculate that we\u2019re seeing another timing-dependent bug in the Win10 1803 installer. Why this bug took out so many copies of Avast \u2014 and what \u201cother software\u201d mentioned by Vlcek may be affected \u2014 remains a mystery. Of course, Microsoft isn\u2019t saying anything.<\/span><\/p>\n Gcdrm on Reddit wraps up his coverage with this statement:<\/span><\/p>\n In response to all the people who have written comments with their thanks and success, and all the people who have emailed my business with similar thanks, including those who have offered to donate to us or to charity in exchange for the free advice, and so on:<\/span><\/p>\n <3<\/span><\/p>\n pay it forward<\/span><\/p>\n support small and independent businesses<\/span><\/p>\n Here, here.<\/span><\/p>\n Thx to <\/span><\/i>@Microfix<\/span><\/i><\/a>, <\/span><\/i>G\u00fcnter Born<\/span><\/i><\/a>\u00a0and <\/span><\/i>Martin Brinkmann<\/span><\/i><\/a>.<\/span><\/i><\/p>\n Got problems with 1803? Don\u2019t we all. Join us on the <\/span><\/i>AskWoody Lounge<\/span><\/i><\/a>.<\/span><\/i><\/p>\n http:\/\/www.computerworld.com\/category\/security\/index.rss<\/a><\/p>\n","protected":false},"excerpt":{"rendered":" Credit to Author: Woody Leonhard| Date: Fri, 25 May 2018 12:28:00 -0700<\/strong><\/p>\n Looks as if we have a solution for the Avast-related blue screens in Win10 1803 upgrades that I talked about <\/span>earlier this week<\/span><\/a>. Avast heavyweight Ondrej Vlcek chose his words carefully but threw lots of shade at Microsoft for the upgrade installer\u2019s bug.<\/span><\/p>\n Posting on the Avast forum, <\/span>Vlcek says<\/span><\/a>:<\/span><\/p>\n
<\/span><\/p>\n<\/p>\n