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!goblin1!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 10:46:24 -0500
Organization: A noiseless patient Spider
Lines: 16
Message-ID: <270220181046240201%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> <p733kt$chf$1@dont-email.me>
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="12718"; mail-complaints-to="abuse@eternal-september.org";posting-account="U2FsdGVkX1/jYfzgZnwbEA/aO6JOTXlV"
User-Agent: Thoth/1.9.0 (Mac OS X)
Cancel-Lock: sha1:5SqbwqbuX2qufkWKYS7BOcEPbWw=
Print Article
Forward Article
In article <p733kt$chf$1@dont-email.me>, Paul<nospam@needed.invalid>
wrote:

> > all software has bugs.
> > 
> > the reality is that win10 bricking is extremely rare and in your case,
> > it's almost certainly due to something you did rather than microsoft's
> > error.
> 
> One of the recent issues (in 2018), was the refusal
> to boot of older AMD processor based systems. This isn't
> true bricking (ruining of file system), but it did prevent
> people from using their computers. 

that one was rushed, and once they realized it was causing problems, it
was pulled.