From: nospam <nospam@nospam.invalid>
Subject: Re: A simple way to transfer photos from your phone to Windows without installing anything on either
Full headers:
Path: news.netfront.net!goblin2!goblin.stu.neva.ru!aioe.org!eternal-september.org!feeder.eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail
From: nospam <nospam@nospam.invalid>
Newsgroups: rec.photo.digital,alt.windows7.general
Subject: Re: A simple way to transfer photos from your phone to Windows without installing anything on either
Date: Tue, 27 Feb 2018 13:49:51 -0500
Organization: A noiseless patient Spider
Lines: 31
Message-ID: <270220181349510679%nospam@nospam.invalid>
References: <1pat6bvdosd5h$.1v0zueckye1z0$.dlg@40tude.net> <N8CjC.87760$CZ2.56323@fx39.iad> <k1708hh1x1bm.4u71bsj0gbj3$.dlg@40tude.net> <p6n7mu$cuh$1@dont-email.me> <19gis5r2t3woe$.15ka8hlpcnip0$.dlg@40tude.net> <9K3kC.89577$CZ2.67163@fx39.iad> <1dxxhzinci9qd.hpx5dw75usol$.dlg@40tude.net> <p6r6ge$5f4$1@dont-email.me> <acakC.112774$mJ1.26756@fx13.fr7> <p6s785$nht$1@dont-email.me> <v9lfsboe3dmc.1o44r2zk1zgx8$.dlg@40tude.net> <p6t8p7$ckt$1@dont-email.me> <240220182343565132%nospam@nospam.invalid> <1xbui2c4r8cc2.hlcsh95dc0q$.dlg@40tude.net> <260220182258584968%nospam@nospam.invalid> <b3r1pb4p9fea$.mvm960z2aw29$.dlg@40tude.net> <270220180216183298%nospam@nospam.invalid> <18sbi2qwkqlde$.159rvr72ujz47.dlg@40tude.net> <270220180537565668%nospam@nospam.invalid> <12fh4vymm2iv$.1c6konrssjq94$.dlg@40tude.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Injection-Info: reader02.eternal-september.org; posting-host="3ff3cd690d33a67a3e982f56b17f2a55";
logging-data="4585"; mail-complaints-to="abuse@eternal-september.org";posting-account="U2FsdGVkX18gBR9h4nd7bDbLzW700Uzn"
User-Agent: Thoth/1.9.0 (Mac OS X)
Cancel-Lock: sha1:7LPzkfzrJ0XtzingnOE+ThB+dmQ=
Print Article
Forward Article
In article <12fh4vymm2iv$.1c6konrssjq94$.dlg@40tude.net>, ultred
ragnusen<ultred@ragnusen.com> wrote:

> 
> >  more than likely, it was a significant factor that
> > caused your bricking.
> 
> I checked my records on the old HDD now that it's mounted to Windows, where
> it was stable at "Windows 10 Pro Version 1511 OS Build 10586.1106" for
> years.
>
> So I was able to do the impossible, for a while, which is stave off the
> Windows 10 Pro updates.

that's a very, very stupid thing to do. you're not getting bug fixes,
security patches and new features. 

> I suspect Microsoft never coded the if-then-else to handle jumping from
> Windows 10 Pro Version 1511 OS Build 10586.1106 to the 16299 Upgrade from
> November 2017 (1709 release).

since just about nobody is in that situation, there's very little
reason to bother. 

there are far more important problems to address, ones that affect many
more people. 

you're using win10 *not* in the way it was designed to be used and will
end up with problems.

tl;dr user error.