Avast says Microsoft to blame for the Win10 1803 upgrade bluescreens and non-sensical boot loop options

Topic

New Reply

Avast has released a new version of their antivirus software and, in a carefully worded explanation, take a jab at Microsoft’s botched Win10 1803 inst
[See the full post at: Avast says Microsoft to blame for the Win10 1803 upgrade bluescreens and non-sensical boot loop options]

5 users thanked author for this post.

Microfix, Great Lake Bunyip, Elly, Cascadian, satrow

Reply | Quote

Replies

I think MS made too many unadvertised changes at once to the underlying system in 1803 and so potentially making a lot of software (especially something as deeply embedded as an AV) incompatible along with the hardware incompatibility already discussed.

4 users thanked author for this post.

lurks about, Great Lake Bunyip, lanceboil, columbia2011

Reply | Quote

It is definitely MSFT’s fault. Had it built a flawless OS, there would be no need for anti-virus software to exist.

1 user thanked author for this post.

Cayennejim

Reply | Quote

To me, changing to a new operating system has always been a painfully drawn out process, first figuring out which of the software installed and working OK under the old OS — the programs and scripts developed by me or obtained elsewhere and often at some significant cost — still work with the new OS… and with what to replace those that do not. Then figuring out, with much time wasted both asking around and trawling the Web for some relevant and useful information, how to deal with the quirks, wrinkles and actual bugs in the new OS, a task that never really ends, although it becomes a less frequent bother as time goes by.

So I can’t begin to imagine how frustrating it might be to have the OS pulled from under one’s feet every few months, without having any choice or say on that. Specially when the developers of the new OS version are doing it in such a hurry, under the pressure of time, that the number of bugs is uncommonly large. And the changes and new features do not make things really better from the point of view of the user, anyway.

So, for now, I am still hanging tough with Windows 7 and using more and more a Mac, whose OS issues, for now at least (touch on wood), are few and far between, and the update cycle still is three years.

Ex-Windows user (Win. 98, XP, 7); since mid-2017 using also macOS. Presently on Monterey 12.15 & sometimes running also Linux (Mint).

MacBook Pro circa mid-2015, 15" display, with 16GB 1600 GHz DDR3 RAM, 1 TB SSD, a Haswell architecture Intel CPU with 4 Cores and 8 Threads model i7-4870HQ @ 2.50GHz.
Intel Iris Pro GPU with Built-in Bus, VRAM 1.5 GB, Display 2880 x 1800 Retina, 24-Bit color.
macOS Monterey; browsers: Waterfox "Current", Vivaldi and (now and then) Chrome; security apps. Intego AV

2 users thanked author for this post.

Cascadian, HiFlyer

Reply | Quote

@Oscar P – Definitely the poorly thought out upgrade cycle for 10 is the primary culprit. A major issue is the design of Windows does not lend it self to a rapid upgrade cycle as too much is tightly linked internally. Besides applications suddenly not working add the problem of peripherals not being supported that worked on the previous version. This becomes a burdensome problem and potentially expensive one as the unplanned replacement may cost some real money.

4 users thanked author for this post.

OscarCP, Karlston, Cascadian, HiFlyer

Reply | Quote

This happened on my wife’s laptop (Acer Aspire V5-571 running Avast). It updated to 1803, then went into the boot-loop.

I finally used a system disc to get to a troubleshooting screen. I told it to repair, saving my files. It finally booted to a desktop with only the Recycle bin. When I went to File Explorer, everything was gone; documents, downloads, desktop, everything.

I had to use the Media Creation Tool to download and run an ISO of 1803.

Everything seems to be working fine now.

One last note: At some point, I realized I had left a 128GB PNY thumb drive plugged in during all this. I unplugged the drive and continued on with the fix.  I can’t say if this had any bearing on the upgrade issues. (There were no boot files on the thumb drive.)

Reply | Quote

“I can’t say if this had any bearing on the upgrade issues. (There were no boot files on the thumb drive.)”

Anonymous #194540 : Based on my own (and by now twenty-five years long) experience with Windows (95, 98, NT, XP and 7) I can say this: Most arcane, but merely annoying, problems with Windows (any OS, really, but none  can hold a candle to Windows in this regard) are quite often solved by a technique that can be generally described as: “rub your tummy and tap the top of your head simultaneously three times, read out loud the Plea of Allegiance backwards, and crow like a cockerel, in that precise order”: problem fixed.

 

Ex-Windows user (Win. 98, XP, 7); since mid-2017 using also macOS. Presently on Monterey 12.15 & sometimes running also Linux (Mint).

MacBook Pro circa mid-2015, 15" display, with 16GB 1600 GHz DDR3 RAM, 1 TB SSD, a Haswell architecture Intel CPU with 4 Cores and 8 Threads model i7-4870HQ @ 2.50GHz.
Intel Iris Pro GPU with Built-in Bus, VRAM 1.5 GB, Display 2880 x 1800 Retina, 24-Bit color.
macOS Monterey; browsers: Waterfox "Current", Vivaldi and (now and then) Chrome; security apps. Intego AV

Reply | Quote

After reading the trials and tribulations of Microsoft month after month on Ask Woody and needing to replace my laptop I decided to get a ChromeBook.  So far none of the Update hassles and no Windows 10 to contend with.

5 users thanked author for this post.

OscarCP, Cascadian, lurks about, woody, HiFlyer

Reply | Quote

[off topic conversation starter deleted by Cascadian]

Your comment gave me reason to start a topic:
https://www.askwoody.com/forums/topic/does-isp-billing-rate-rise-with-a-chromebook

I invite you to share your thoughts.

1 user thanked author for this post.

Kirsty

Reply | Quote