Subject: Re: A simple way to transfer photos from your phone to Windows withoutinstalling anything on either
David B. wrote:
> On 24/02/2018 08:07, Mike S wrote:
>> You can do a startup repair and then a complete 10 repair install with
>> a free w10 dvd (you d/l the iso for).
>> w10 disk image
> As I'm using a Mac, I was redirected to this URL to download the ISO:-
> Once I burn the ISO to a disk will it be 'bootable' or will additional
> action be required first?
It requires dancing a jig on one foot.
When Windows is installed on more than a 100 million machines, would
distributing a broken image work ? How many people would ever
figure it out ?
If 100 million people phone the Microsoft support line with
"help me convert the ISO I downloaded into something useful",
how many Tier 0 employees do you think that's going to take
to help them out ? The telephone switch board will be absolutely jammed
for months and months.
Common sense tells you "it's supposed to work".
Doing that from a Mac, comes with a risk. This risk also extends to
users on WinXP and Linux as well.
Downloads are handled two ways. On more modern platforms, BITS is
used to supervise the download (Microsoft gives you a stub EXE downloader
to use, and it calls BITS). The Microsoft servers seem to work
well with the BITS option. The stub downloader handles any post-processing
duties. A typical stub might be on the order of 5MB in size.
But a number of years back, regular HTTP downloads from the Microsoft
site, would become truncated during download. Sometimes around the
2GB mark, both ends of the transaction would just "stop" (no error message!).
And the ISO file would be ruined. You might not notice until you burned
the ISO, and maybe ImgBurn complained the structure wasn't right. I
saw this on Linux. I saw it on WinXP.
I got a number that way so I've actually experienced this first hand.
I detected them purely on size, before doing anything with the result.
But other download attempts ran to completion, just like normal.
The problem is intermittent.
This has also happened to other, non Windows 10 files. The bug
seemed to spread from the Windows distribution servers, into
other servers in the Microsoft CDN. The catalog server started
doing it. I got a bad 500MB Cumulative one day via HTTP.
You can convert an HTTP type download, into a BITS download via Powershell.
It's the Powershell equivalent of "wget". And it seems to work properly.
Why this makes a different, who can guess. A Linux user can't do this,
but someone on a Windows box could use it.
(Start PowerShell, then try...)
Import-Module BitsTransfer <=== some older Windows maybe...
Start-BitsTransfer -source "http://urlToDownload\"
where the URL to download would be pointing at the actual
file the catalog server is supposed to give you.
That's a way of converting an "unreliable" Microsoft
download, one where you were informed your download was
corrupted at some later point in time, into something
you can actually use.
Microsoft never admitted it was broken.
Microsoft never announced it was fixed.
Doing HTTP downloads from any other web site than a Microsoft
one, are not affected. It's not a networking stack problem
(especially as the bug is visible cross-platform).
A little trivia for you.
By all means, continue to download files via HTTP with your Mac.
But if the 2.5GB or 3.5GB ISO files seem "a tad short",
you have a place to start.
Even the breaking point in the download is not consistent.
It isn't a problem at exactly 2^31 for example. I did the
math on some of them, and no pattern of note emerged. And
it hardly ever breaks at the beginning.