Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.os.linux.advocacy > #475098

Re: Another failed Windows 10 Update

From Snit <usenet@gallopinginsanity.com>
Newsgroups comp.os.linux.advocacy
Subject Re: Another failed Windows 10 Update
Date 2018-11-03 15:51 -0700
Message-ID <g46n37Fs4r6U5@mid.individual.net> (permalink)
References (2 earlier) <priie0$hau$1@dont-email.me> <e6a54yu9zuj7.14d13h8han4ec$.dlg@40tude.net> <primpv$6b6$1@dont-email.me> <2z5dh52fdwax.122rmx71h5z2u$.dlg@40tude.net> <nFlDD.1315964$YL3.658022@fx48.iad>

Show all headers | View raw

On 11/3/18 11:20 AM, SilverSlimer wrote:
> On 2018-11-02 8:16 p.m., nobody wrote:
>> On Fri, 2 Nov 2018 23:32:15 -0000 (UTC), RonB wrote:
>>
>>> On 2018-11-02, proletariat <myemailisaol@defunct.org> wrote:
>>>> On Fri, 2 Nov 2018 22:17:36 -0000 (UTC), RonB wrote:
>>>>
>>>>> On 2018-11-02, nobody <nobodysaysitalldoesntit@nobo.org> wrote:
>>>>>> On Fri, 2 Nov 2018 11:57:56 -0000 (UTC), RonB wrote:
>>>>>>
>>>>>>> File this under "Typical Failed Update for Freaking Microsoft 
>>>>>>> Hobbyware"
>>>>>>>
>>>>>>> This time it was on the desktop computer. I don't know what the 
>>>>>>> dumbass
>>>>>>> update did, but it appears that there are now two Windows 10 
>>>>>>> installs
>>>>>>> (Windows 10 and Windows 10 Pro – I installed Windows 10 Pro). 
>>>>>>> Update seemed
>>>>>>> to have worked successfully this afternoon (took forever). Then I 
>>>>>>> had to
>>>>>>> pick up my son at work at 1:30 a.m. Checked a couple things on 
>>>>>>> this computer
>>>>>>> before leaving. Seemed slower than normal, but it was working and 
>>>>>>> it didn't
>>>>>>> look like anything was missing. (We can be thankful for small 
>>>>>>> blessings.)
>>>>>>> Than, when I got home, I saw a Recovery Error? Than, booting from 
>>>>>>> the USB, I
>>>>>>> tried all the fixes, trying rolling back to pre-update — all 
>>>>>>> these took a
>>>>>>> long time, but nothing helped. Restore finished, but said it wasn't
>>>>>>> successful. While going through some more options I noticed 
>>>>>>> "Choose OS."
>>>>>>> Sure enough, Windows 10 and Windows 10 Pro. Windows 10 was the 
>>>>>>> default now.
>>>>>>> I chose Windows 10 ... mouse with the little circle, for a long, 
>>>>>>> long time.
>>>>>>> Finally gave up. Went back to the Windows 10 one, this time it 
>>>>>>> actually
>>>>>>> booted up to a screen that said "Update failed, falling back to 
>>>>>>> previous
>>>>>>> version" (or words to that effect) and it actually booted in. Of 
>>>>>>> course,
>>>>>>> Microsoft Office had to be reactivated (again). I haven't tried 
>>>>>>> Visio or
>>>>>>> WordPerfect but I'm guessing they'll have to be reactivated as 
>>>>>>> well. Even
>>>>>>> though I booted into the version that just says Windows 10, it IS 
>>>>>>> still the
>>>>>>> Windows 10 Pro I installed ... so your guess is as good as mine 
>>>>>>> as what the
>>>>>>> two Windows boot-in choices mean. Hobbyware is so much fun!
>>>>>>>
>>>>>>> So I've been doing this for about five hours now so that my wife 
>>>>>>> would have
>>>>>>> a working computer when she woke up. And I guess I've succeeded, 
>>>>>>> unless it
>>>>>>> decides to quit again (or tries to update again). Microsoft, can 
>>>>>>> it be any
>>>>>>> more hobbyware? What total crap.
>>>>>>
>>>>>> My advice to you is to find another hobby and have your family locate
>>>>>> someone who is competent at managing computers because looking at 
>>>>>> your
>>>>>> posting history you do seem to have an inordinate amount of 
>>>>>> problems with
>>>>>> Windows computers.
>>>>>
>>>>> Either that or convince them to quit using the Hobbyware Malware 
>>>>> Magnet
>>>>> Swiss Cheese Crapware OS from Microshit. Actually I would be MORE 
>>>>> than happy
>>>>> to let someone else work on their Winshit installs. But, unlike the 
>>>>> vast
>>>>> majority of Winshit owners who have had this problem, I WAS able to 
>>>>> get the
>>>>> machine back up and running without having to reinstall. So I was 
>>>>> able to
>>>>> avoid the normal Winshit "Reboot, reboot, reinstall" "fix."
>>>>>
>>>>>> Interesting that you never seem to post about Linux update 
>>>>>> headaches and
>>>>>> please don't insult people who know more about Linux than you do by
>>>>>> claiming Linux updates just work because we all know that's not 
>>>>>> any more
>>>>>> truthful than your Windows update claims.
>>>>>> They both have problems at times.
>>>>>
>>>>> Well, what's really "interesting" is that this installation of 
>>>>> Linux Mint
>>>>> 17.1 was installed on this computer in 2014 and I have NEVER had to 
>>>>> fix
>>>>> that. That might be a hint as to why I hate Windows and love Linux. 
>>>>> I don't
>>>>> cringe every time Linux updates. Can't say the same for Winshit.
>>>>>
>>>>>> Next time post some screen shots to imgur or another site because you
>>>>>> either have the worst luck on the planet or you are concocting 
>>>>>> fairy tales.
>>>>>
>>>>> I'm not lying, but I did take screenshots of the Recovery screen 
>>>>> so, in case
>>>>> it wouldn't get to that point when I rebooted I would at least know 
>>>>> what
>>>>> error it WAS giving. ...
>>>>>
>>>>> Here's what it read ...
>>>>>
>>>>> ~~
>>>>> Recovery (yeah, right)
>>>>>
>>>>> Your PC/Device needs to be repaired (because we f***ed up the 
>>>>> "update" again)
>>>>>
>>>>> A requested device is not connected and can't be accessed (though 
>>>>> it was
>>>>> fine before the "update").
>>>>>
>>>>> Error code: 0xc000000f (we like to offer useless information)
>>>>>
>>>>> You'll need to use recovery tools. If you don't have any 
>>>>> installation media
>>>>> (i.e. a disk or USB device), contact your PC administrator or 
>>>>> PC/Device
>>>>> manufacturer. (And they'll tell you to reinstall after a couple 
>>>>> reboots.)
>>>>> ~~
>>>>>
>>>>> I was able to find the error code (lots of people get it after an 
>>>>> update)
>>>>> and multiple "maybe" "fixes" (none of which worked) — found the 
>>>>> same problem
>>>>> on Microshit's "support" boards (where the consensus was to 
>>>>> reinstall).
>>>>> Ended up just lucking into the fix. (Typical of Microcrap hobbyware 
>>>>> shit.)
>>>>>
>>>>> When I hit F8 I was given a list of options for fixing the "OS" 
>>>>> (other than
>>>>> the real fix, installing Linux over the crap and never looking 
>>>>> back) so I
>>>>> chose Enable debugging. It gave me (I'm going by memory) an error 
>>>>> Code of
>>>>> 0xc0000098 which had something to do with the HAL.DLL in the
>>>>> Windows\System32\ subdirectory. Looking at that error I saw this 
>>>>> meant that
>>>>> the HAL.DLL was "missing" but, using the recovery USB, I was able 
>>>>> to confirm
>>>>> that it wasn't missing. It was probably incompatible with something 
>>>>> on my
>>>>> computer and Microcrap Winshit was too "stupid" to figure that out 
>>>>> before
>>>>> bricking the computer. Of course, on the Winshit support forum the 
>>>>> consensus
>>>>> seemed to be "reinstall" and "hope you had your stuff backed up."
>>>>>
>>>>> Fortunately I knew that there was nothing wrong with the HD and 
>>>>> that the
>>>>> files were still intact because I used my Linux Mint USB to check 
>>>>> out the
>>>>> files. So worst case, I would have to back up the files and reinstall
>>>>> Winshit (not that I haven't done that before ... and before ... and 
>>>>> before
>>>>> ... and before).
>>>>>
>>>>> But, yeah, if someone wants to fix my wife's computers, gratis, 
>>>>> when Wincrap
>>>>> takes yet another dump after yet another failed update, they're 
>>>>> more than
>>>>> welcome to do so. Hopefully BEFORE I throw the poor, Wincrap infested
>>>>> computers out the window.
>>>>
>>>> I agree with the others.
>>>>
>>>> I read a thread where recently some family member had a new laptop 
>>>> that was
>>>> hosed up and you refused or at least did not call the company for 
>>>> support.
>>>> So yet another boondoggle by you.
>>>>
>>>> Personally, and don't take this the wrong way, but without screen 
>>>> shots I
>>>> don't believe you unless you are getting your paws into these machines
>>>> prior to the fuck up because you obviously don't have a clue what 
>>>> you are
>>>> doing.
>>>
>>> Not used on this computer — so these two paragraphs are pretty much 
>>> useless.
>>> But if you like yammering on when you don't have a clue, go for it.
>>>
>>>> Running programs like CCLeaner, System Mechanic and so forth to resolve
>>>> your problems is the first indication that you are out of your league.
>>>> Those programs are for idiots and more often than not cause more 
>>>> problems
>>>> than they resolve.
>>>>
>>>> Next time post screen shots because not everyone reading this group 
>>>> is a
>>>> Linux fanboy who will take your word about Windows woes without a CV.
>>>
>>> Next time, chickenshit, shove it up your a** and rotate on it. You're
>>> calling me a liar. I don't lie. I've made no claims to being proficient
>>> using Windows 10 shit, but these are real problems with my wife's 
>>> computers
>>> and they also show up all the time when you do Google search (even on 
>>> the
>>> Microsoft forums), so your bullshit is just that, pure bullshit.
>>>
>>>> And BTW I run Linuxmint as well and it screws the pooch quite often.
>>>> Just read their forums for details.
>>>
>>> Not for me it doesn't. I don't lie about that either. I guess liars 
>>> think
>>> everyone lies.
>>
>> Your response says it all.
>> Sorry you keep getting caught in your own web of lies.
>> And sorry you didn't get the message that slamming Windows is the lowest
>> form of Linux advocacy. Especially without any form of proof and 
>> expecting
>> people to just believe your statements.
>>
>> Fact based reality is sometimes difficult for the Linux advocate to
>> understand.
> 
> I truly don't believe that RonB is exaggerating; my own experience with 
> Windows is that it does sometimes create issues even though you've done 
> a good job of maintaining the machine.
> 
> 

Of course he is obsessing over weaknesses, real AND imagined. And of 
course what he describes is not the norm. He is very, very bitter.

-- 
Personal attacks from those who troll show their own insecurity. They 
cannot use reason to show the message to be wrong so they try to feel 
somehow superior by attacking the messenger.

They cling to their attacks and ignore the message time and time again.

<https://youtu.be/H4NW-Cqh308>

Back to comp.os.linux.advocacy | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Another failed Windows 10 Update RonB <ronb02NOSPAM@gmail.com> - 2018-11-02 11:57 +0000
  Re: Another failed Windows 10 Update RonB <ronb02NOSPAM@gmail.com> - 2018-11-02 12:04 +0000
    Re: Another failed Windows 10 Update SilverSlimer <silver@slim.er> - 2018-11-02 11:41 -0400
      Re: Another failed Windows 10 Update RonB <ronb02NOSPAM@gmail.com> - 2018-11-02 18:00 +0000
        Re: Another failed Windows 10 Update SilverSlimer <silver@slim.er> - 2018-11-03 11:29 -0400
          Re: Another failed Windows 10 Update Steve Carroll <frelwizzen@gmail.com> - 2018-11-03 08:59 -0700
  Re: Another failed Windows 10 Update chrisv <chrisv@nospam.invalid> - 2018-11-02 07:22 -0500
    Re: Another failed Windows 10 Update Steve Carroll <frelwizzen@gmail.com> - 2018-11-02 05:52 -0700
    Re: Another failed Windows 10 Update RonB <ronb02NOSPAM@gmail.com> - 2018-11-02 18:10 +0000
      Re: Another failed Windows 10 Update Steve Carroll <frelwizzen@gmail.com> - 2018-11-02 11:22 -0700
      Re: Another failed Windows 10 Update Snit <usenet@gallopinginsanity.com> - 2018-11-02 11:33 -0700
        Re: Another failed Windows 10 Update Steve Carroll <frelwizzen@gmail.com> - 2018-11-02 12:40 -0700
      Re: Another failed Windows 10 Update Steve Carroll <frelwizzen@gmail.com> - 2018-11-02 11:37 -0700
    Re: Another failed Windows 10 Update Steve Carroll <frelwizzen@gmail.com> - 2018-11-02 12:24 -0700
  Re: Another failed Windows 10 Update SilverSlimer <silver@slim.er> - 2018-11-02 11:32 -0400
    Re: Another failed Windows 10 Update Steve Carroll <frelwizzen@gmail.com> - 2018-11-02 10:03 -0700
      Re: Another failed Windows 10 Update Steve Carroll <frelwizzen@gmail.com> - 2018-11-02 11:53 -0700
    Re: Another failed Windows 10 Update RonB <ronb02NOSPAM@gmail.com> - 2018-11-02 18:14 +0000
      Re: Another failed Windows 10 Update SilverSlimer <silver@slim.er> - 2018-11-03 11:44 -0400
        Re: Another failed Windows 10 Update RonB <ronb02NOSPAM@gmail.com> - 2018-11-03 17:02 +0000
          Re: Another failed Windows 10 Update Snit <usenet@gallopinginsanity.com> - 2018-11-03 12:18 -0700
          Re: Another failed Windows 10 Update SilverSlimer <silver@slim.er> - 2018-11-03 15:53 -0400
            Re: Another failed Windows 10 Update Snit <usenet@gallopinginsanity.com> - 2018-11-03 15:50 -0700
            Re: Another failed Windows 10 Update RonB <ronb02NOSPAM@gmail.com> - 2018-11-03 23:36 +0000
              Re: Another failed Windows 10 Update Steve Carroll <frelwizzen@gmail.com> - 2018-11-03 17:02 -0700
              Re: Another failed Windows 10 Update Snit <usenet@gallopinginsanity.com> - 2018-11-04 11:38 -0700
                Re: Another failed Windows 10 Update nobody <nobodysaysitalldoesntit@nobo.org> - 2018-11-04 16:35 -0500
                Re: Another failed Windows 10 Update Steve Carroll <frelwizzen@gmail.com> - 2018-11-04 13:54 -0800
                Re: Another failed Windows 10 Update Steve Carroll <frelwizzen@gmail.com> - 2018-11-04 17:17 -0800
                Re: Another failed Windows 10 Update Snit <usenet@gallopinginsanity.com> - 2018-11-04 16:07 -0700
                Re: Another failed Windows 10 Update Steve Carroll <frelwizzen@gmail.com> - 2018-11-04 16:30 -0800
                Re: Another failed Windows 10 Update Steve Carroll <frelwizzen@gmail.com> - 2018-11-05 01:52 -0800
                Re: Another failed Windows 10 Update Steve Carroll <frelwizzen@gmail.com> - 2018-11-06 05:05 -0800
                Re: Another failed Windows 10 Update Steve Carroll <frelwizzen@gmail.com> - 2018-11-05 03:42 -0800
    Re: Another failed Windows 10 Update Steve Carroll <frelwizzen@gmail.com> - 2018-11-02 12:09 -0700
  Re: Another failed Windows 10 Update nobody <nobodysaysitalldoesntit@nobo.org> - 2018-11-02 16:59 -0400
    Re: Another failed Windows 10 Update Steve Carroll <frelwizzen@gmail.com> - 2018-11-02 14:15 -0700
    Re: Another failed Windows 10 Update RonB <ronb02NOSPAM@gmail.com> - 2018-11-02 22:17 +0000
      Re: Another failed Windows 10 Update owl <owl@rooftop.invalid> - 2018-11-02 22:35 +0000
        Re: Another failed Windows 10 Update Steve Carroll <frelwizzen@gmail.com> - 2018-11-02 15:49 -0700
        Re: Another failed Windows 10 Update Steve Carroll <frelwizzen@gmail.com> - 2018-11-02 16:05 -0700
      Re: Another failed Windows 10 Update proletariat <myemailisaol@defunct.org> - 2018-11-02 18:45 -0400
        Re: Another failed Windows 10 Update RonB <ronb02NOSPAM@gmail.com> - 2018-11-02 23:32 +0000
          Re: Another failed Windows 10 Update Steve Carroll <frelwizzen@gmail.com> - 2018-11-02 16:36 -0700
          Re: Another failed Windows 10 Update Steve Carroll <frelwizzen@gmail.com> - 2018-11-02 16:52 -0700
          Re: Another failed Windows 10 Update Snit <usenet@gallopinginsanity.com> - 2018-11-02 17:07 -0700
          Re: Another failed Windows 10 Update nobody <nobodysaysitalldoesntit@nobo.org> - 2018-11-02 20:16 -0400
            Re: Another failed Windows 10 Update nobody <nobodysaysitalldoesntit@nobo.org> - 2018-11-02 20:23 -0400
              Re: Another failed Windows 10 Update RonB <ronb02NOSPAM@gmail.com> - 2018-11-03 00:46 +0000
                Re: Another failed Windows 10 Update Steve Carroll <frelwizzen@gmail.com> - 2018-11-02 17:55 -0700
                Re: Another failed Windows 10 Update proletariat <myemailisaol@defunct.org> - 2018-11-02 21:13 -0400
                Re: Another failed Windows 10 Update Snit <usenet@gallopinginsanity.com> - 2018-11-02 20:39 -0700
                Re: Another failed Windows 10 Update Steve Carroll <frelwizzen@gmail.com> - 2018-11-02 23:54 -0700
            Re: Another failed Windows 10 Update RonB <ronb02NOSPAM@gmail.com> - 2018-11-03 00:44 +0000
              Re: Another failed Windows 10 Update proletariat <myemailisaol@defunct.org> - 2018-11-02 21:11 -0400
                Re: Another failed Windows 10 Update nobody <nobodysaysitalldoesntit@nobo.org> - 2018-11-02 21:20 -0400
                Re: Another failed Windows 10 Update SilverSlimer <silver@slim.er> - 2018-11-03 14:32 -0400
                Re: Another failed Windows 10 Update Snit <usenet@gallopinginsanity.com> - 2018-11-03 12:36 -0700
              Re: Another failed Windows 10 Update Snit <usenet@gallopinginsanity.com> - 2018-11-02 20:39 -0700
                Re: Another failed Windows 10 Update Steve Carroll <frelwizzen@gmail.com> - 2018-11-03 04:34 -0700
            Re: Another failed Windows 10 Update SilverSlimer <silver@slim.er> - 2018-11-03 14:20 -0400
              Re: Another failed Windows 10 Update Snit <usenet@gallopinginsanity.com> - 2018-11-03 15:51 -0700
                Re: Another failed Windows 10 Update Steve Carroll <frelwizzen@gmail.com> - 2018-11-03 16:47 -0700
          Re: Another failed Windows 10 Update DFS <nospam@nospam.com> - 2018-11-16 10:00 -0500
            Re: Another failed Windows 10 Update Steve Carroll <frelwizzen@gmail.com> - 2018-11-16 07:12 -0800
        Re: Another failed Windows 10 Update owl <owl@rooftop.invalid> - 2018-11-03 18:27 +0000
          Re: Another failed Windows 10 Update RonB <ronb02NOSPAM@gmail.com> - 2018-11-03 22:28 +0000
            Re: Another failed Windows 10 Update Snit <usenet@gallopinginsanity.com> - 2018-11-03 15:49 -0700
      Re: Another failed Windows 10 Update Snit <usenet@gallopinginsanity.com> - 2018-11-02 17:17 -0700
        Re: Another failed Windows 10 Update proletariat <myemailisaol@defunct.org> - 2018-11-02 20:18 -0400
          Re: Another failed Windows 10 Update Snit <usenet@gallopinginsanity.com> - 2018-11-02 17:24 -0700
            Re: Another failed Windows 10 Update proletariat <myemailisaol@defunct.org> - 2018-11-02 20:28 -0400
              Re: Another failed Windows 10 Update Snit <usenet@gallopinginsanity.com> - 2018-11-02 17:36 -0700
              Re: Another failed Windows 10 Update Steve Carroll <frelwizzen@gmail.com> - 2018-11-02 17:40 -0700
              Re: Another failed Windows 10 Update RonB <ronb02NOSPAM@gmail.com> - 2018-11-03 01:03 +0000
                Re: Another failed Windows 10 Update proletariat <myemailisaol@defunct.org> - 2018-11-02 21:17 -0400
                Re: Another failed Windows 10 Update Snit <usenet@gallopinginsanity.com> - 2018-11-02 20:31 -0700
                Re: Another failed Windows 10 Update chrisv <chrisv@nospam.invalid> - 2018-11-05 07:49 -0600
                Re: Another failed Windows 10 Update Steve Carroll <frelwizzen@gmail.com> - 2018-11-06 04:34 -0800
              Some people think a $1000 bottle of wine tastes better, others don't. Jeff-Relf.Me  @. - 2018-11-03 07:48 -0700
                Re: Some people think a $1000 bottle of wine tastes better, others don't. Steve Carroll <frelwizzen@gmail.com> - 2018-11-03 07:57 -0700
              Re: Another failed Windows 10 Update Chris Ahlstrom <OFeem1987@teleworm.us> - 2018-11-06 05:21 -0500
                Re: Another failed Windows 10 Update Steve Carroll <frelwizzen@gmail.com> - 2018-11-06 03:14 -0800
                Re: Another failed Windows 10 Update proletariat <myemailisaol@defunct.org> - 2018-11-06 08:14 -0500
                Re: Another failed Windows 10 Update SilverSlimer <silver@slim.er> - 2018-11-06 08:42 -0500
                Re: Another failed Windows 10 Update DFS <nospam@nospam.com> - 2018-11-06 11:57 -0500
                Re: Another failed Windows 10 Update SilverSlimer <silver@slim.er> - 2018-11-06 12:52 -0500
                Re: Another failed Windows 10 Update DFS <nospam@nospam.com> - 2018-11-08 09:09 -0500
                Re: Another failed Windows 10 Update SilverSlimer <silver@slim.er> - 2018-11-08 20:55 -0500
                Re: Another failed Windows 10 Update Snit <usenet@gallopinginsanity.com> - 2018-11-08 19:04 -0700
                Re: Another failed Windows 10 Update Steve Carroll <frelwizzen@gmail.com> - 2018-11-09 01:50 -0800
                Re: Another failed Windows 10 Update Steve Carroll <frelwizzen@gmail.com> - 2018-11-09 03:41 -0800
                Re: Another failed Windows 10 Update Chris Ahlstrom <OFeem1987@teleworm.us> - 2018-11-09 05:25 -0500
                Re: Another failed Windows 10 Update Steve Carroll <frelwizzen@gmail.com> - 2018-11-09 03:09 -0800
                Re: Another failed Windows 10 Update RonB <ronb02NOSPAM@gmail.com> - 2018-11-06 18:46 +0000
                Re: Another failed Windows 10 Update Snit <usenet@gallopinginsanity.com> - 2018-11-06 11:56 -0700
                Re: Another failed Windows 10 Update Steve Carroll <frelwizzen@gmail.com> - 2018-11-06 11:21 -0800
                Re: Another failed Windows 10 Update proletariat <myemailisaol@defunct.org> - 2018-11-06 17:02 -0500
                Re: Another failed Windows 10 Update Snit <usenet@gallopinginsanity.com> - 2018-11-06 16:30 -0700
                Re: Another failed Windows 10 Update proletariat <myemailisaol@defunct.org> - 2018-11-06 18:43 -0500
                Re: Another failed Windows 10 Update owl <owl@rooftop.invalid> - 2018-11-06 23:47 +0000
                Re: Another failed Windows 10 Update proletariat <myemailisaol@defunct.org> - 2018-11-06 19:07 -0500
                Re: Another failed Windows 10 Update Snit <usenet@gallopinginsanity.com> - 2018-11-06 17:28 -0700
                Re: Another failed Windows 10 Update proletariat <myemailisaol@defunct.org> - 2018-11-06 20:56 -0500
                Re: Another failed Windows 10 Update Snit <usenet@gallopinginsanity.com> - 2018-11-06 19:10 -0700
                Re: Another failed Windows 10 Update owl <owl@rooftop.invalid> - 2018-11-07 00:47 +0000
                Re: Another failed Windows 10 Update Snit <usenet@gallopinginsanity.com> - 2018-11-06 17:56 -0700
                Re: Another failed Windows 10 Update proletariat <myemailisaol@defunct.org> - 2018-11-06 21:01 -0500
                Re: Another failed Windows 10 Update Snit <usenet@gallopinginsanity.com> - 2018-11-06 19:11 -0700
                Owl and DFS write code. Jeff-Relf.Me  @. - 2018-11-06 20:18 -0800
                Re: Owl and DFS write code. proletariat <myemailisaol@defunct.org> - 2018-11-07 01:12 -0500
                Re: Owl and DFS write code. DFS <nospam@nospam.com> - 2018-11-07 08:05 -0500
                Re: Owl and DFS write code. Steve Carroll <frelwizzen@gmail.com> - 2018-11-07 05:33 -0800
                Re: Owl and DFS write code. Steve Carroll <frelwizzen@gmail.com> - 2018-11-07 07:22 -0800
                What's "mad" about mono-/duo- spaced glyphs in a console ? Jeff-Relf.Me  @. - 2018-11-07 06:02 -0800
                Re: What's "mad" about mono-/duo- spaced glyphs in a console ? Steve Carroll <frelwizzen@gmail.com> - 2018-11-07 06:20 -0800
                Re: Another failed Windows 10 Update Steve Carroll <frelwizzen@gmail.com> - 2018-11-06 17:20 -0800
                Re: Another failed Windows 10 Update proletariat <myemailisaol@defunct.org> - 2018-11-06 20:58 -0500
                Re: Another failed Windows 10 Update Snit <usenet@gallopinginsanity.com> - 2018-11-06 19:13 -0700
                Re: Another failed Windows 10 Update Steve Carroll <frelwizzen@gmail.com> - 2018-11-06 23:52 -0800
                Re: Another failed Windows 10 Update Snit <usenet@gallopinginsanity.com> - 2018-11-06 17:25 -0700
                Re: Another failed Windows 10 Update Snit <usenet@gallopinginsanity.com> - 2018-11-06 17:28 -0700
                Re: Another failed Windows 10 Update Steve Carroll <frelwizzen@gmail.com> - 2018-11-06 15:46 -0800
                Re: Another failed Windows 10 Update Steve Carroll <frelwizzen@gmail.com> - 2018-11-06 11:05 -0800
                Re: Another failed Windows 10 Update proletariat <myemailisaol@defunct.org> - 2018-11-06 17:00 -0500
          Re: Another failed Windows 10 Update RonB <ronb02NOSPAM@gmail.com> - 2018-11-03 00:48 +0000
            Re: Another failed Windows 10 Update proletariat <myemailisaol@defunct.org> - 2018-11-02 21:14 -0400
              Re: Another failed Windows 10 Update Steve Carroll <frelwizzen@gmail.com> - 2018-11-02 18:41 -0700
            Re: Another failed Windows 10 Update Snit <usenet@gallopinginsanity.com> - 2018-11-02 20:39 -0700
              Re: Another failed Windows 10 Update Steve Carroll <frelwizzen@gmail.com> - 2018-11-02 22:35 -0700
                Re: Another failed Windows 10 Update Steve Carroll <frelwizzen@gmail.com> - 2018-11-03 06:07 -0700
          Re: Another failed Windows 10 Update RonB <ronb02NOSPAM@gmail.com> - 2018-11-03 00:55 +0000
            Re: Another failed Windows 10 Update Snit <usenet@gallopinginsanity.com> - 2018-11-02 20:37 -0700
            Re: Another failed Windows 10 Update SilverSlimer <silver@slim.er> - 2018-11-03 14:29 -0400
              Re: Another failed Windows 10 Update Snit <usenet@gallopinginsanity.com> - 2018-11-03 12:39 -0700
              Re: Another failed Windows 10 Update Steve Carroll <frelwizzen@gmail.com> - 2018-11-03 13:24 -0700
        Re: Another failed Windows 10 Update nobody <nobodysaysitalldoesntit@nobo.org> - 2018-11-02 20:24 -0400
          Re: Another failed Windows 10 Update RonB <ronb02NOSPAM@gmail.com> - 2018-11-03 01:06 +0000
            Re: Another failed Windows 10 Update proletariat <myemailisaol@defunct.org> - 2018-11-02 21:18 -0400
            Re: Another failed Windows 10 Update Steve Carroll <frelwizzen@gmail.com> - 2018-11-02 18:25 -0700
            Re: Another failed Windows 10 Update Snit <usenet@gallopinginsanity.com> - 2018-11-02 20:30 -0700
        Re: Another failed Windows 10 Update Steve Carroll <frelwizzen@gmail.com> - 2018-11-02 17:24 -0700

csiph-web