windows 10 recovery disk

Hi,

My Win10 ran into a boot problem. I googled for a windows 10 recovery disk
and found 'winpese-x64-14393_17.01.16'. When that booted it said there was a
problem with a particular file and I should look for an install disk.

My question is which is the best Windows 10 64-bit install disk today?
Thanks.

On Fri, 11 Sep 2020 19:44:13 -0700, Norm Why wrote:

Hi,

My Win10 ran into a boot problem. I googled for a windows 10 recovery disk
and found 'winpese-x64-14393_17.01.16'. When that booted it said there was a
problem with a particular file and I should look for an install disk.

My question is which is the best Windows 10 64-bit install disk today?
Thanks.

See https://www.microsoft.com/en-us/software-download/windows10

"Download Windows 10"
* Using the tool to create installation media (USB flash drive, DVD, or ISO file) to install Windows 10


--
Kind regards
Ralph

Norm Why wrote:
Hi,

My Win10 ran into a boot problem. I googled for a windows 10 recovery disk
and found 'winpese-x64-14393_17.01.16'. When that booted it said there was a
problem with a particular file and I should look for an install disk.

My question is which is the best Windows 10 64-bit install disk today?
Thanks.

If you were using "dism... restorehealth" or "sfc scannow"
commands to restore the complement of files, then using a DVD
of the same vintage as your installed OS might help. Maybe you
are not running the most recent release (2004). Ralphs link
would give you a nice 2004 ISO.

This tool generates URLs to a Techbench site at Microsoft,
so that you can download particular versions of Windows 10.
Using the Copy To Clipboard buttons, you can copy the URL
generated, to any browser you want to use for the download
from the Microsoft site. The ISO does not come from Heidoc.
You can close the Heidoc tool, once the URL you want has
been copied into Firefox and the download started.

https://www.heidoc.net/joomla/techno...-download-tool

Download: Windows-ISO-Downloader.exe

Version: 8.38
Release Date: 7 July 2020
Requirements: Windows 7 or newer,
.NET Framework 4.x,
Internet Explorer 8 or newer.

The current version of Windows 10 is 19041 (2004). The
Heidoc gives access to 18363 (1909) for example, that's
their most recent archived version. Ralphs link will give
you 2004. Heidoc will give you any older version, all the
wayt back to the year 2015 (10240). Your OS version isn't
likely to be 10240, but it also might not be 19041 either.

https://en.wikipedia.org/wiki/Window...ersion_history

Detecting the OS version while it isn't running, I don't
think that is going to be all that much fun, unfortunately.
You could do Properties on a file which is critical to the
OS, to get an approximate answer. For example, 18363 (1909)
had some 18362 (1903) files in it. And pawing through the
registry, it can be done most conveniently from a Kaspersky
rescue CD (which has a Registry Editor), but, knowing that
the KAV disc registry editor does not edit *all* of the
Registry hives. Occasionally you'll be out of luck doing it that
way, because that Registry file can't be accessed from KAV.

https://superuser.com/questions/3630...the-filesystem

If the OS was running, you would use "winver.exe", easy to do.
It's the "OS isn't running" aspect that makes it non-easy.

*******

Your OS was most likely damaged by a false positive of an
AV scanner (Windows Defender?), and if you could find
the quarantine folder, your "missing file" might be there.
Note that files in Windows, are hardlinked from WinSXS into
System32. You would "move" the file back from the quarantine
folder to preserve the linkage if possible. Perhaps you'd
still profit from sfc scannow and dism restorehealth, just
so the OS "maintainability" was sewn back together properly.
Otherwise, some Windows Update coming in, may have "side effects"
because WinSXS isn't operated correctly by you. That's one
of the responsibilities of manual maintainers to the OS,
is doing it the right way and not breaking something else.

*******

The disc images that come from Microsoft, come in two versions.
An 11 OS disc. A 7 OS disc. Ralphs link will get you a 7 OS
disc (which fits on a single-layer DVD). If you download Windows 10
from a WinXP machine, you get the 11 OS version, 5GB and slightly
too big for single-layer media.

This isn't a big deal, unless you're aiming for a DVD for
portability in the computer room.

Not everyone wants to put this stuff on a USB flash, and Ralphs
method (MediaCreationToolXXXXX.exe) will give the smaller media.
You get the MediaCreationTool if using Ralphs link from Windows 7
or later.

The Heidoc links on the other hand, are direct URLs to an ISO,
which unfortunately for the 64-bit version, you get the 11-OS
version and you'd need dual-layer DVD media. I only have one
blank left of that stuff, and I don't waste those on Windows
discs.

It's possible to remove OS versions from a disc ISO, and I have
taken an 11-OS disc to a 1-OS setup, and saved 500MB or so from
the image. You can shrink a too-large one, but that was a
bar bet exercise, and not really all that practical. When they put
11 OS versions on the DVD, most of the files are "linked" from
a single file version on the disc. Home and Pro OS versions
share a lot of files, so they don't put two unique copies on
the DVD, just use ISO linkages on the disc so the file is available
to both. That's why removing 10 OS versions, only saves 500MB.

I'd prefer to see you match OS versions for this exercise, but
this isn't all that easy to do when only "offline" access to
the OS is available. When using your "sfc /scannow" and
"dism... restorehealth" commands, you need the "offline"
flavor of the command, to run from the Command Prompt on
the DVD boot/install disc.

I would not think a 14393 disc would be of that much use,
it all depends on whether you've been freezing the OS
a certain way, as to whether that's a practical disc to use.
At a guess, unless you've been hacking this, you're either
at 1909 or 2004, so there are likely to be two choices
at work here, rather than all versions being equally likely.
The 1909 could be found on Heidoc, the 2004 via Ralphs link.

Paul