Rene Lamontagne wrote:
> On 2021-06-12 1:26 p.m., ...w¡ñ§±¤n wrote:
>> Rene Lamontagne wrote:
>>> On 2021-06-12 12:56 a.m., ...w¡ñ§±¤n wrote:
>>>> Rene Lamontagne wrote:
>>>>>
>>>>>   According to Tenforums, Seeing as this notification bull crap was a
>>>>> new feature installed with KB5003214 and I am suffering from it as
>>>>> many others and a fix for it is to uninstall that KB update, The
>>>>> problem is that I don't seem to have that one in , uninstall updates,
>>>>> can it be hiding somewhere else?
>>>>>
>>>>> Rene
>>>>>
>>>> Hi, Rene.
>>>> Not sure if this applies in your case...
>>>>
>>>> KB5003214 was the May 'Preview' cumulative update
>>>> KB5003637 the June 8th Cumulative Update included the bits in KB5003214
>>>>
>>>> i.e. if KB5003637 was installed KB5003214 won't be found as an item to
>>>> uninstall.
>>>>
>>>> I suspect the Tenforums article referencing KB5003214 was written
>>>> before the June 8th update thus the May KB number while valid at the
>>>> time, is no longer applicable.
>>>>
>>>>
>>> Thanks for the explanation  ...wi, Yes, I do havveKB5003637 so now I
>>> will try working on that one.
>>>
>>>    Rene
>>>
>>>
>> You're welcome.
>> I noticed, well I guess I'd call it an anomaly.
>> Two devices both running W10 Pro and fully updated Win10.
>> Both previously installed the the May Preview and the subsequent June
>> 8th update.
>>   The one device I looked at prior to my earlier reply did not show
>> KB5003214 as an item for uninstall in (Control Panel/Programs
>> Features/View Installed Updates).
>>   The other device had both items in the CP/P&F/View Installed updates)
>>    - which apparently indicates there may be some variation across
>> different devices on how Win10 treats an earlier installed preview update.
>>   (lol...with the amount of systems using Win10 that variation could be
>> more normal than rare)
>>
>> Good luck...and note it may be necessary to use the DISM command to
>> remove the LCU(latest cumulative update 5003637)since the LCU included
>> the Servicing Stack Update(SSU) which can't be removed/uninstalled.
>>
>
> OK, Uninstalled kb5003637 and shut the system down, then did a cold boot
> at which time Windows did some updating or installed something cause I had
> to answer some more setup questions. Looked again in update file history
> and sure enough kb5003637 was back.
> But now the notification area came back on normally and news and interests
> is working properly.
> So I have done 4 warm and cold boots and everything is working as it
> should, Hallelujah :-)
>
> Rene
>
>
Glad to hear it worked out uninstalling the June update.
Since the June was removed, it would seem normal that WU would check the
post removal status, then provide the latest again.
If WU was checked, it should have also offered KB5004476(1904x.1055), the
June 11 'Out of Band' as an Optional Quality Update(user prompt to
'Download and Install).
- KB5004476 includes the latest Servicing Stack Update(1904x.1022) and
also a fix for XBox Game Pass that incorrectly redirected to the MSFT
Store for Gaming Services when installing or starting and XBox Game Pass
game. Nothing else was included if KB5004476 was installed.

--
....w¡ñ§±¤n

On 2021-06-13 9:57 p.m., ...w¡ñ§±¤n wrote:
> Rene Lamontagne wrote:
>> On 2021-06-12 1:26 p.m., ...w¡ñ§±¤n wrote:
>>> Rene Lamontagne wrote:
>>>> On 2021-06-12 12:56 a.m., ...w¡ñ§±¤n wrote:
>>>>> Rene Lamontagne wrote:
>>>>>>
>>>>>>   According to Tenforums, Seeing as this notification bull crap
>>>>>> was a new feature installed with KB5003214 and I am suffering from
>>>>>> it as many others and a fix for it is to uninstall that KB update,
>>>>>> The problem is that I don't seem to have that one in , uninstall
>>>>>> updates, can it be hiding somewhere else?
>>>>>>
>>>>>> Rene
>>>>>>
>>>>> Hi, Rene.
>>>>> Not sure if this applies in your case...
>>>>>
>>>>> KB5003214 was the May 'Preview' cumulative update
>>>>> KB5003637 the June 8th Cumulative Update included the bits in
>>>>> KB5003214
>>>>>
>>>>> i.e. if KB5003637 was installed KB5003214 won't be found as an item
>>>>> to uninstall.
>>>>>
>>>>> I suspect the Tenforums article referencing KB5003214 was written
>>>>> before the June 8th update thus the May KB number while valid at
>>>>> the time, is no longer applicable.
>>>>>
>>>>>
>>>> Thanks for the explanation  ...wi, Yes, I do havveKB5003637 so now I
>>>> will try working on that one.
>>>>
>>>>    Rene
>>>>
>>>>
>>> You're welcome.
>>> I noticed, well I guess I'd call it an anomaly.
>>> Two devices both running W10 Pro and fully updated Win10.
>>> Both previously installed the the May Preview and the subsequent June
>>> 8th update.
>>>   The one device I looked at prior to my earlier reply did not show
>>> KB5003214 as an item for uninstall in (Control Panel/Programs
>>> Features/View Installed Updates).
>>>   The other device had both items in the CP/P&F/View Installed updates)
>>>    - which apparently indicates there may be some variation across
>>> different devices on how Win10 treats an earlier installed preview
>>> update.
>>>   (lol...with the amount of systems using Win10 that variation could
>>> be more normal than rare)
>>>
>>> Good luck...and note it may be necessary to use the DISM command to
>>> remove the LCU(latest cumulative update 5003637)since the LCU
>>> included the Servicing Stack Update(SSU) which can't be
>>> removed/uninstalled.
>>>
>>
>> OK, Uninstalled kb5003637 and shut the system down, then did a cold
>> boot at which time Windows did some updating or installed something
>> cause I had to answer some more setup questions. Looked again in
>> update file history and sure enough kb5003637 was back.
>> But now the notification area came back on normally and news and
>> interests is working properly.
>> So I have done 4 warm and cold boots and everything is working as it
>> should, Hallelujah :-)
>>
>> Rene
>>
>>
> Glad to hear it worked out uninstalling the June update.
> Since the June was removed, it would seem normal that WU would check the
> post removal status, then provide the latest again.
> If WU was checked, it should have also offered KB5004476(1904x.1055),
> the June 11 'Out of Band' as an Optional Quality Update(user prompt to
> 'Download and Install).
>  - KB5004476 includes the latest Servicing Stack Update(1904x.1022) and
> also a fix for XBox Game Pass that incorrectly redirected to the MSFT
> Store for Gaming Services when installing or starting and XBox Game Pass
> game.  Nothing else was included if KB5004476 was installed
>
>

Yes, both KB5004476 and also have the servicing stack 1904.1022 are
installed, so now everything seems to be back in order and working properly.

Thanks for all the help, really appreciated.

Rene

Rene Lamontagne <rlamont@shaw.ca> wrote:
....
> Yes I have had a few strange updates lately and had some asking for
> reboot, had one Friday but I don't see it in File history, I think
> Microsoft is playing genes behind our back.

Genes? I noticed I got the same updates in three of my 64-bit W10
machines over the weekend that I got from Tuesday! MS is wack.
--
So many issues, and so little time and energy! Crazy last week and soon this hot week. :(
Note: A fixed width font (Courier, Monospace, etc.) is required to see this signature correctly.
/\___/\ Ant(Dude) @ http://aqfl.net & http://antfarm.home.dhs.org.
/ /\ /\ \ Please nuke ANT if replying by e-mail.
| |o o| |
\ _ /
( )

ant@zimage.comANT (Ant) wrote:

> Rene Lamontagne <rlamont@shaw.ca> wrote:

>> Yes I have had a few strange updates lately and had some asking for
>> reboot, had one Friday but I don't see it in File history, I think
>> Microsoft is playing genes behind our back.
>
> Genes?

Games. That sort of error happens a lot nowadays, with Google supplying speech
recognition to the masses who don't bother proofreading what they write. To
figure out what they actually said, just read it and apply common sense. If it
looks weird and it's not a spelling error, it's probably a speech recognition
error. That assumes English as their native language.

> I noticed I got the same updates in three of my 64-bit W10
> machines over the weekend that I got from Tuesday! MS is wack.

On 2021-06-13 10:29 p.m., Ant wrote:
> Rene Lamontagne <rlamont@shaw.ca> wrote:
> ...
>> Yes I have had a few strange updates lately and had some asking for
>> reboot, had one Friday but I don't see it in File history, I think
>> Microsoft is playing genes behind our back.
>
> Genes? I noticed I got the same updates in three of my 64-bit W10
> machines over the weekend that I got from Tuesday! MS is wack.

Boy, I wonder what made me type genes instead of Games and not notice it?
Maybe those 87 years are starting to show! :-)

Rene

>

On Mon, 14 Jun 2021 07:30:54 -0500, Rene Lamontagne
<rlamont@shaw.ca> wrote:

>Boy, I wonder what made me type genes instead of Games and not notice it?
>Maybe those 87 years are starting to show! :-)
>
>Rene
>
I'm only 78, but I was a pretty good touch typist a generation
ago. But there are many words that I could think of and muscle
memory would type automatically for me. That doesn't work any
more. "That" becomes "than." What bugs me the most is
thinking/typing a 5-letter word and seeing myself type a
different 4-letter word.

Gots to proofread a lot harder now. (And I was too old to get
relief from a cubital tunnel release to try to cure my numb left
pinky and ring finger. There and MANY keys that the left pinky
is responsible for on the QWERTY keyboard. And I hit them all
instead of typing an "a".

============

Was watching a snippet of the Mecum car auctions yesterday. There
is an immaculate restored 1963 Vette split windows coupe that
sold for $160,000. Immediately after it came another Vette '63,
a convertible, that only brought $60,000.

Rene Lamontagne wrote:
>
> Boy, I wonder what made me type genes instead of Games and not notice it?
> Maybe those 87 years are starting to show!  :-)
>
> Rene
>

I'd bet on a spellchecker event, Rene. I do those sometimes without
noticing.
You could have input "gemes" or "gmes" and the good old friendly
spellchecker does its stuff.

Ed

On 2021-06-14 12:26 p.m., Ed Cryer wrote:
> Rene Lamontagne wrote:
>>
>> Boy, I wonder what made me type genes instead of Games and not notice it?
>> Maybe those 87 years are starting to show!  :-)
>>
>> Rene
>>
>
> I'd bet on a spellchecker event, Rene. I do those sometimes without
> noticing.
> You could have input "gemes" or "gmes" and the good old friendly
> spellchecker does its stuff.
>
> Ed
>
>
>

Yes, the poor old spellchecker can't read my mind, it only knows if it's
spelled right, not what it means.

Rene

Rene Lamontagne wrote:

> Ed Cryer wrote:
>> Rene Lamontagne wrote:

>>> Boy, I wonder what made me type genes instead of Games and not notice
>>> it? Maybe those 87 years are starting to show!  :-)

>> I'd bet on a spellchecker event, Rene. I do those sometimes without
>> noticing. You could have input "gemes" or "gmes" and the good old
>> friendly spellchecker does its stuff.

That's bullshit. You can "input", but everybody notices when the computer
OUTPUTS an incorrect HIGHLIGHTED word (at least when proofreading).

That sort of writing error has been EXTREMELY rare.

> Yes, the poor old spellchecker can't read my mind, it only knows if it's
> spelled right, not what it means.

Your first suggestion, dementia, is likely the underlying cause, spellchecker
or not. It's not just a matter of a spellchecker "reading your mind", you must
avoid noticing the obvious selection error too.

Those sorts of errors are commonly produced nowadays by Google's speech
recognition trying to read peoples' minds.

John Doe wrote:
> Rene Lamontagne wrote:
>
>> Ed Cryer wrote:
>>> Rene Lamontagne wrote:
>
>>>> Boy, I wonder what made me type genes instead of Games and not notice
>>>> it? Maybe those 87 years are starting to show!  :-)
>
>>> I'd bet on a spellchecker event, Rene. I do those sometimes without
>>> noticing. You could have input "gemes" or "gmes" and the good old
>>> friendly spellchecker does its stuff.
>
> That's bullshit. You can "input", but everybody notices when the computer
> OUTPUTS an incorrect HIGHLIGHTED word (at least when proofreading).
>
> That sort of writing error has been EXTREMELY rare.
>
>> Yes, the poor old spellchecker can't read my mind, it only knows if it's
>> spelled right, not what it means.
>
> Your first suggestion, dementia, is likely the underlying cause, spellchecker
> or not. It's not just a matter of a spellchecker "reading your mind", you must
> avoid noticing the obvious selection error too.
>
> Those sorts of errors are commonly produced nowadays by Google's speech
> recognition trying to read peoples' minds.
>

John Guggenheim wakled allong thi streat.

John good at home waked all Ongi St.

John glued an hamburger with a long thing.

Join good old Heinrich when on thick treat.

Joint GUNH I'm walled in at Crete.

Jolly google whacked Lawn Thistré.

ojhp rejujhrtprtg ugtrjokkklfdkmfdkmcvkl',mrfsd,mfk;lxzm.
You shouldn't end a sentence with a preposition.

$R$$%£$%$$ (8545
No closing bracket found.

Ed

Idiot troll...

--
Ed Cryer <ed@somewhere.in.the.uk> wrote:

> Path: eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail
> From: Ed Cryer <ed@somewhere.in.the.uk>
> Newsgroups: alt.comp.os.windows-10
> Subject: Re: 21H1
> Date: Tue, 15 Jun 2021 18:40:46 +0100
> Organization: A noiseless patient Spider
> Lines: 57
> Message-ID: <saaoo3$k19$1@dont-email.me>
> References: <s9clte$s88$1@dont-email.me> <s9iuim$6aj$1@dont-email.me> <ii4ft6Fp90hU1@mid.individual.net> <s9j8pp$ekb$1@dont-email.me> <s9jjh9$gt8$5@dont-email.me> <ii52ivFsm05U1@mid.individual.net> <s9jkr8$od2$2@dont-email.me> <s9k1rf$pqf$2@dont-email.me> <iihluhFbs69U1@mid.individual.net> <sa1ibb$6qg$1@dont-email.me> <iik1ldFpn8iU1@mid.individual.net> <sa2u8c$7be$1@dont-email.me> <iil57pF1ovnU1@mid.individual.net> <sa4phm$59p$1@dont-email.me> <iimlhmFal5hU1@mid.individual.net> <W7SdnY9MPcmYUFv9nZ2dnUU7-dPNnZ2d@earthlink.com> <iip0fuFoglkU1@mid.individual.net> <sa83g1$tc6$1@dont-email.me> <iipm2mFsljuU1@mid.individual.net> <saamlf$3nh$1@dont-email.me>
> Mime-Version: 1.0
> Content-Type: text/plain; charset=utf-8; format=flowed
> Content-Transfer-Encoding: quoted-printable
> Injection-Date: Tue, 15 Jun 2021 17:41:23 -0000 (UTC)
> Injection-Info: reader02.eternal-september.org; posting-host="a1d8a34225c591c0af03b41e82c59452"; logging-data="20521"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/cVE+0GPMqTcoj3QXDJqxy"
> User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0
> Cancel-Lock: sha1:IKKKt/G/hfqYpqVWJdw5QuKyNRc=
> In-Reply-To: <saamlf$3nh$1@dont-email.me>
> Content-Language: en-GB
> Xref: reader02.eternal-september.org alt.comp.os.windows-10:146757
>
> John Doe wrote:
>> Rene Lamontagne wrote:
>>
>>> Ed Cryer wrote:
>>>> Rene Lamontagne wrote:
>>
>>>>> Boy, I wonder what made me type genes instead of Games and not notic
> e
>>>>> it? Maybe those 87 years are starting to show!�� :-)
>>
>>>> I'd bet on a spellchecker event, Rene. I do those sometimes without
>>>> noticing. You could have input "gemes" or "gmes" and the good old
>>>> friendly spellchecker does its stuff.
>>
>> That's bullshit. You can "input", but everybody notices when the comput
> er
>> OUTPUTS an incorrect HIGHLIGHTED word (at least when proofreading).
>>
>> That sort of writing error has been EXTREMELY rare.
>>
>>> Yes, the poor old spellchecker can't read my mind, it only knows if it
> 's
>>> spelled right, not what it means.
>>
>> Your first suggestion, dementia, is likely the underlying cause, spellc
> hecker
>> or not. It's not just a matter of a spellchecker "reading your mind", y
> ou must
>> avoid noticing the obvious selection error too.
>>
>> Those sorts of errors are commonly produced nowadays by Google's speech
>
>> recognition trying to read peoples' minds.
>>
>
> John Guggenheim wakled allong thi streat.
>
> John good at home waked all Ongi St.
>
> John glued an hamburger with a long thing.
>
> Join good old Heinrich when on thick treat.
>
> Joint GUNH I'm walled in at Crete.
>
> Jolly google whacked Lawn ThistrǸ.
>
> ojhp rejujhrtprtg ugtrjokkklfdkmfdkmcvkl',mrfsd,mfk;lxzm.
> You shouldn't end a sentence with a preposition.
>
> $R$$%��$%$$ (8545
> No closing bracket found.
>
> Ed
>
>
>
>
>

On Tue, 15 Jun 2021 at 18:40:46, Ed Cryer <ed@somewhere.in.the.uk> wrote
(my responses usually follow points raised):
[]
>John Guggenheim wakled allong thi streat.
>
>John good at home waked all Ongi St.
>
>John glued an hamburger with a long thing.
>
>Join good old Heinrich when on thick treat.
>
>Joint GUNH I'm walled in at Crete.
>
>Jolly google whacked Lawn Thistré.
>
>ojhp rejujhrtprtg ugtrjokkklfdkmfdkmcvkl',mrfsd,mfk;lxzm.
>You shouldn't end a sentence with a preposition.
>
>$R$$%£$%$$ (8545
>No closing bracket found.
>
>Ed
>
(-:
>
Machines are needed to wreck a nice beach.
>
(Mind you, that implies the speaker was too lazy to say the g.)
--
J. P. Gilliver. UMRA: 1960/<1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

.... basically it's another language and unless you've studied it, it's
difficult to grasp. I know people get outraged at me saying it, but it's only
my opinion. I'm not telling people who adore Shakespeare to stop adoring it
this minute. - Jane Horrocks, in Radio Times 30 July - 5 August 2011