From: ultred ragnusen <ultred@ragnusen.com>
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!.POSTED!not-for-mail
From: ultred ragnusen <ultred@ragnusen.com>
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 00:18:14 -0800
Organization: Aioe.org NNTP Server
Lines: 51
Message-ID: <18sbi2qwkqlde$.159rvr72ujz47.dlg@40tude.net>
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>
NNTP-Posting-Host: 9jqAqawZAHOhdYo12APfbA.user.gioia.aioe.org
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Complaints-To: abuse@aioe.org
User-Agent: 40tude_Dialog/2.0.15.84
X-Notice: Filtered by postfilter v. 0.8.3
Print Article
Forward Article
nospam<nospam@nospam.invalid> wrote:

>> You talk like the developers I used to work with long ago, where they
>> figured bugs were just something that you have to learn to live with.
> 
> all software has bugs.

True dat.

> 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.

What you say is probably true since I customized the hell out of that
Windows 10 Pro system such that I was able to do the impossible, which is
to stave off Windows updates for /years/, until the Spectre updates on
January 25th, 26th, and 27th, finally made it on to my system, and bricked
it when it rebooted on the 27th.
01 http://i.cubeupload.com/My174i.jpg
02 http://i.cubeupload.com/0lxuPw.jpg
03 http://i.cubeupload.com/Z2ZaDz.jpg
04 http://i.cubeupload.com/gQGe5w.jpg
05 http://i.cubeupload.com/Y34trY.jpg
06 http://i.cubeupload.com/FHzWVs.jpg
07 http://i.cubeupload.com/IF2Vlc.jpg
08 http://i.cubeupload.com/8v82ir.jpg
09 http://i.cubeupload.com/HfYA6Z.jpg
10 http://i.cubeupload.com/SBiaqx.jpg
11 http://i.cubeupload.com/FwZLFW.jpg
12 http://i.cubeupload.com/Mu43Tx.jpg
13 http://i.cubeupload.com/3L67JF.jpg
14 http://i.cubeupload.com/tV9jYD.jpg
 
>> It's a big deal when a mandatory Microsoft Windows 10 Pro update bricks the
>> system. It's due to poor coding. Very poor coding. Lousy testing too.
> 
> you have no idea what the cause is, nor do the 'geniuses' at the
> microsoft store.

I'm pretty sure it's poor coding on the part of Microsoft which couldn't
handle my customizations, which is why I'm trying to limit the necessary
customizations in this new install of Windows 10.

Remember, I was able to do the impossible, which was to stave off any
Windows updates, without having to use the metering trick on WiFi and
without having to pull the Internet connection in "off" hours.

It was a lot of settings that I changed though, perhaps fifty to a hundred,
so I'm not sure which particular ones are the ones Microsoft hated but I
kept the same Windows 10 Pro for a couple of years, as I recall (at least a
year).