Author Topic: Windows 10 failed update to 1803, maybe an Avast problem?  (Read 22038 times)

0 Members and 2 Guests are viewing this topic.

Offline Navvy

  • Jr. Member
  • **
  • Posts: 50
Windows 10 failed update to 1803, maybe an Avast problem?
« on: May 22, 2018, 05:24:15 PM »
On a friend's Compaq Presario CQ58 I used Settings to apply Windows Updates, and it downloaded and tried to install the latest feature update 1803.  Unfortunately it now just asks me on a blue screen to select a keyboard layout and then on the next page it has a Continue button which takes me back to the keyboard layout selection again.  System Restore points no longer exist, and there seems no way to get to the machine working again.  Looks like I'll need to do a clean install of Windows.

Reason for posting here is that a google search came up with this page https://www.yourwindowsguide.com/2018/05/what-if-your-computer-is-broken-after-1803-update.html

This page indicates that most people who've suffered this problem have had Avast installed, and they are advising people to uninstall Avast before applying the update.

Has anyone on the forum seem this problem?  It isn't just the Avast UI failing to run - it's behaving as though Avast has crippled part of the windows update, which has happened to me previously with the Anniversary update on a different computer.

Note that this Windows 1803 feature update is being delivered automatically to anyone who uses Settings, Windows Update.  In my case I was on a mobile hotspot metered connection, and it asked me for permission to download a very small 0.1MB update, and then used that permission to automatically start the 3GB download.

Offline Asyn

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 53402
    • >>>  Avast Forum - Deutschsprachiger Bereich  <<<
Re: Windows 10 failed update to 1803, maybe an Avast problem?
« Reply #1 on: May 22, 2018, 05:46:59 PM »
Easy test, does it work if Avast is disabled/uninstalled..?
Win 8.1 [x64] - Avast Premier 18.5.2342.BC - CC 5.43 - MCS - EEK - FF ESR 52.8.1 [NS5/uBO/AOS] - TB 52.8 [EM] - ACP/ASB/ASL.BC
Deutschsprachiger Bereich -> Avast Wissenswertes (Downloads, Anleitungen & Infos): https://forum.avast.com/index.php?topic=60523

Offline Evjls

  • Jr. Member
  • **
  • Posts: 76
Re: Windows 10 failed update to 1803, maybe an Avast problem?
« Reply #2 on: May 22, 2018, 06:02:16 PM »
https://news.softpedia.com/news/avast-antivirus-blamed-for-breaking-down-windows-10-april-2018-update-521227.shtml

https://www.reddit.com/r/Windows10/comments/8l5vim/the_latest_update_debacle_windows_10_1803_upgrade/

Quote
Reddit user gcdrm, who says is working at a small computer repair shop, reveals that multiple systems upgraded on May 20 and May 21 experienced the same issues.

“Thus far, the only solution we have found is a Windows reinstall,” they posted. “It appears that everyone that has fallen victim to this problem has been using Avast Antivirus. However, this problem has only occurred on systems that attempted the 1803 upgrade in the last two days. This infers that a very recent update to Avast is interfering with the upgrade process. It appears to be damaging read/write permissions on the problem computers.”

While neither Microsoft nor Avast acknowledged the issue, users who are being offered the upgrade to Windows 10 April 2018 Update are recommended to uninstall the antivirus before beginning the process. No action is required for users who have already completed the switch successfully.
« Last Edit: May 22, 2018, 06:04:01 PM by Evjls »

Offline Navvy

  • Jr. Member
  • **
  • Posts: 50
Re: Windows 10 failed update to 1803, maybe an Avast problem?
« Reply #3 on: May 22, 2018, 06:32:17 PM »
Thanks @Evjls

I think Avast had updated on Friday 18th, and the 1803 download started on Sat 19th and completed on Monday 21st, so this does match.  The laptop now seems to have no network connection at all, as the drivers for many services haven't started.  So there is no possibility of Avast or Microsoft being able to issue any retrospective bug fix online.

I'll try getting into Command mode and see if I can run aswclear from a USB drive, as that will show whether Avast has corrupted the update process or is just preventing the upgraded Windows from running.

Offline Navvy

  • Jr. Member
  • **
  • Posts: 50
Re: Windows 10 failed update to 1803, maybe an Avast problem?
« Reply #4 on: May 22, 2018, 09:50:48 PM »
Update - I've run AvastClear, and it hasn't made any noticeable difference.  Windows is still unusable, and I'm getting "C:\WINDOWS\system32\config\systemprofile\Desktop is not accessible. Access is denied."

The network and audio icons in the system tray are both showing red-X. The hidden icons button contains a golden padlock.  What does that mean?  Left-click or right-click on the Windows button in the bottom left don't work.  Task Manager is about the only thing that does work.

Offline Evjls

  • Jr. Member
  • **
  • Posts: 76
Re: Windows 10 failed update to 1803, maybe an Avast problem?
« Reply #5 on: May 23, 2018, 02:39:03 AM »
Update - I've run AvastClear, and it hasn't made any noticeable difference.  Windows is still unusable, and I'm getting "C:\WINDOWS\system32\config\systemprofile\Desktop is not accessible. Access is denied."

The network and audio icons in the system tray are both showing red-X. The hidden icons button contains a golden padlock.  What does that mean?  Left-click or right-click on the Windows button in the bottom left don't work.  Task Manager is about the only thing that does work.
I recommend you to do a clean installation of your windows to clean up the mess and the incompatibility issue
or if you don't want a clean install, just perform a repair of windows AFTER UNINSTALLING AVAST

windows 10 1803 itself is quite buggy and hasn't been very stable yet to many users
« Last Edit: May 23, 2018, 01:17:06 PM by Evjls »

Offline lukor

  • Avast team
  • Super Poster
  • *
  • Posts: 1832
    • AVAST Software
Re: Windows 10 failed update to 1803, maybe an Avast problem?
« Reply #6 on: May 23, 2018, 08:08:56 AM »
Hi guys, thanks for reporting. We are working hard on reproducing the issue here, but so far no issue found with Avast at our test machines. Definitely, it seems that all affected users were also using Windows at the time of the attempted update, so that is also a possible suspect. I'll update here once we find more info. Thanks!

Lukas.

Offline MartinZ

  • Moderator
  • Advanced Poster
  • *
  • Posts: 789
  • Product Manager
Re: Windows 10 failed update to 1803, maybe an Avast problem?
« Reply #7 on: May 23, 2018, 10:15:58 AM »
Microsoft temporarily disabled the updates on version 1803 on PCs with Avast. We are working together with MS to find out the cause of this issue, but unfortunately right now neither MS nor us are able to reproduce the issue.

Offline janekm

  • Newbie
  • *
  • Posts: 4
Re: Windows 10 failed update to 1803, maybe an Avast problem?
« Reply #8 on: May 23, 2018, 11:21:46 AM »
MartinZ, Lukor - You said you are uneable to reproduce the problem? - I will be happy lending you PC of my parents for while. Im paying for their AVAST licence for their PC being safe a bit and now I have to go to them and repair their PC because Windows forced updating their PC yesterday even that many peoples have been reporting in previous days that the spring update conflicts totally with AVAST !
(even Im angry, really - if it could help, the PC may be inspected, Im based in Prague, email is in my account here)

Offline janekm

  • Newbie
  • *
  • Posts: 4
Re: Windows 10 failed update to 1803, maybe an Avast problem?
« Reply #9 on: May 23, 2018, 11:26:43 AM »
Easy test, does it work if Avast is disabled/uninstalled..?
oh, what for a suggestion! Should Navvy after succesfully perfoming clean reinstallation of Windows start to experiment with disabling, enabling AVAST and then performing the spring update again??? Navvy is writing that his PC is dead now (same as PC of my parents is dead and many, many PCs all over the world), have you read his post at all?

Offline Asyn

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 53402
    • >>>  Avast Forum - Deutschsprachiger Bereich  <<<
Re: Windows 10 failed update to 1803, maybe an Avast problem?
« Reply #10 on: May 23, 2018, 11:46:44 AM »
Easy task if you got backups. (Which are a must have anyway, IMO.)
Win 8.1 [x64] - Avast Premier 18.5.2342.BC - CC 5.43 - MCS - EEK - FF ESR 52.8.1 [NS5/uBO/AOS] - TB 52.8 [EM] - ACP/ASB/ASL.BC
Deutschsprachiger Bereich -> Avast Wissenswertes (Downloads, Anleitungen & Infos): https://forum.avast.com/index.php?topic=60523

Offline Spec8472

  • Avast team
  • Full Member
  • *
  • Posts: 170
Re: Windows 10 failed update to 1803, maybe an Avast problem?
« Reply #11 on: May 23, 2018, 01:21:44 PM »
For all users with failed W10 1803 update: Can you please provide Windows update logs from "C:\$WINDOWS.~BT\Sources\Panther\" folder.

Thank you
« Last Edit: May 23, 2018, 02:08:42 PM by Spec8472 »

Offline janekm

  • Newbie
  • *
  • Posts: 4
Re: Windows 10 failed update to 1803, maybe an Avast problem?
« Reply #12 on: May 23, 2018, 02:28:43 PM »
For all users with failed W10 1803 update: Can you please provide Windows update logs from "C:\$WINDOWS.~BT\Sources\Panther\" folder.

Thank you
I will forward your request to my dad and my mam. They will be happy with AVAST effort for sure. Probably they will ask me whether its written somwhere on the backside of the silent PC box.

Offline acceso-acceso

  • Newbie
  • *
  • Posts: 2
Re: Windows 10 failed update to 1803, maybe an Avast problem?
« Reply #13 on: May 23, 2018, 04:18:34 PM »
Hello

i found some cain of solution, is in here i made the post. so i copy and paste....

I just step whit this windows10 and avast issue I can reinstall the system without losing applications or docs or conf

This windows10 dont want to install the spring update or do anything, just load the ER after read everywere, it look like a problem with avast

How i manage to solve this, i'll try to explain.

In the ER (environment recover) I manage to load the windows10 with the black desktop, is some cain of safe mode without the save mode-... weird, load some things. I connect the network cable just in case.
Go to troubleshooting and them try to load another operating system, the option. In my case i have 3 options, rollback, and 2 option with windows volume 3, i choose the third, and try several times to load the black desktop be patience take sometime to load.
When load, execute tasks manager, control+shit+esc, and execute any browser, internet explorer those the tricks and search avast uninstall. download the app, execute with win+r and uninstall.

After that i execute from a USB the installer of the spring update ISO and install the win10 and preserve all data and applications.
It takes almost several hours,4 h. to restore the win10 but i recover all.
Hope it helps
Sorry for my English is my third language

cu

Offline Navvy

  • Jr. Member
  • **
  • Posts: 50
Re: Windows 10 failed update to 1803, maybe an Avast problem?
« Reply #14 on: May 23, 2018, 06:57:57 PM »
@Spec8472  @MartinZ
Could you please give a clearer description of which log file you want to see?

I have now done a clean install of Windows 10-1803.  Fortunately this machine wasn't used for anything except browsing, as I've now lost the Word and Excel that were pre-installed on it.

I'm now able to see the C:\Windows.old.000\ directory which contains the user files from the original installation.  This contains a Windows folder, and within that there is no Sources folder.  However, there is a Panther folder, and that contains various files that look like logs.  One is MigLog.XML but that is 125MB.

I'm now using Defender, and I haven't installed Avast on the clean machine.

On my own machine I've switched Avast to passive mode, which required a reboot.  Defender eventually enabled itself, but needed to be manually updated (last Defender definitions update was several years ago).

The Avast icon has appeared again in the system tray, and when I hover over it, it says "Avast Free Antivirus - You are protected".  This seems to be a bug, since Avast is not providing protection.  I've set my broadband connection as a Metered connection to prevent the 1803 feature update.

Incidentally, the Microsoft Media Creation Tool for creating a Win10 installation USB seems to have a problem too.  It failed repeatedly at 50% despite running it as an Administrator.  Eventually I used it to download the ISO and used Rufus to put it onto the 16GB USB drive.  One difference I spotted was that Rufus insisted that the ISO needed NTFS instead of FAT32, which the USB drive was previously quick-formatted to.