Re: Fatal Installer Error

JM Casey

Yes…it’s probably a temporary paralysis at worse and not truly fatal. :P

Brings me back to the old Applie II days when I found a game I really hated on one of the school’s disks, so I went into basic and re-wrote the first few lines of the programme to abort with a fake error message that said, ‘broken computer and bad disk error.” It was the easiest thing to do on a system where 90% of the stuff we used was done in Applesoft Basic.

“Boy,” I chuckled to myself with gremlinish glee, “some poor person is going to have a heart attack when they see or hear that.”

I never did get to find out if anyone discovered the prank, though.

Computers were a lot different then and there really weren’t any disastrous operating system errors – just damaged disks, which you simply had to throw out,  and total hardware failures, which didn’t really generate any error messages and which probably necessitated tossing your Apple II E into the garbage, too, since they were already obsolete by the early 90s…


Anyway, if it’s not malware you’ve got (and I suspect it’s probably not), my guess would be – a programme that automatically installs new updates, but that isn’t windows – for example, something like Java, or Adobe Flash Player or Acrobat. I bet you a few bucks that the error message will come back at some point, or else the programme will *successfully* install next time.




From: <> On Behalf Of Brian Vogel
Sent: November 18, 2020 04:47 PM
Subject: Re: [win10] Fatal Installer Error


On Wed, Nov 18, 2020 at 04:40 PM, Quentin Christensen wrote:

Without knowing the contents of the error message, it's basically impossible to tell what it was.

This bears repeating, and repeating, an repeating.   Any time an error message box is encountered, it is absolutely vital that you capture its content, by whatever method or methods you choose.  A potential assistant cannot be of any real assistance otherwise.

Also, just FYI, by the time you get a fatal error it means that whatever was running that triggered it was stopped dead in its tracks and is no longer continuing to run, so you need not panic and close a fatal error message in hopes of preventing damage.  Mind you, just because something got a fatal error does not mean, if it is something malicious, that it could not have already done damage before the fatal error occurred.  But once a fatal error has occurred the thing that got the fatal error is no longer able to continue in any way, shape, or form.  The term fatal error is really actually descriptive in that the program or process that triggered it is well and truly dead.

Brian - Windows 10 Pro, 64-Bit, Version 2004, Build 19041
The purpose of education is not to validate ignorance but to overcome it. 
       ~ Lawrence Krauss

Join to automatically receive all group messages.