What is Windows doing?

Just tried to upgrade my Win 10 Pro to 1803. Got a stop code so back to
ground zero. But I noticed while I was twiddling my thumbs that the upgrade
process was talking to someone on the net, I assume Microsoft. Anyone have
any idea what might be going on with this? The only thing I can think of is
verifying which previous patches I have already had installed.

Tim wrote:
Just tried to upgrade my Win 10 Pro to 1803. Got a stop code so back to
ground zero. But I noticed while I was twiddling my thumbs that the upgrade
process was talking to someone on the net, I assume Microsoft. Anyone have
any idea what might be going on with this? The only thing I can think of is
verifying which previous patches I have already had installed.

The upgrade attempt keeps two log files. These
can amount to a couple hundred megabytes of text
messages, most of which are irrelevant.

Some operations in Windows, also keep ETW logs,
which is something ProcMon uses for tracing. That's
another mechanism Windows uses.

But as far as us being privy to what is actually
being sent, you can be assured the information
is passing over a secure socket layer, and tracing
with Wireshark likely isn't going to reveal anything
other than "binary baloney".

*******

You could use some DISM or SFC commands, to check
out the current OS state. Or alternately, consider
whether you've moved any Junction Points, thus upsetting
the balance of nature. While Microsoft might allow you
to move your home directory to the D: drive, the OS
installer won't be happy about such things.

Dism /Online /Cleanup-Image /CheckHealth

Dism /Online /Cleanup-Image /ScanHealth

Dism /Online /Cleanup-Image /RestoreHealth

sfc /scannow

Those commands in Windows 10 are network savvy,
as well as having options for running offline,
although more parameters might be needed in the
offline case. Since your OS is back to the
previous release, and still running, you should
be able to try the commands as they are above.

Back around RTM time, 17034 was causing problems
for a few people, but the actual RTM release is
17034_1 meaning some slight change was made,
without altering the contents. If you have the
STOP code number, that number would make it
easier to Google for inspiration and see if this
is a known issue.

You can download the 1803 DVD and install from
it if you want. The ISO can be "mounted" in the
OS without burning a DVD, and you can run "setup.exe"
off the virtual CD drive that results from mounting
the ISO file. So that's a way to run an upgrade
locally, without re-downloading over and over again
using a Windows Update path.

Paul

On 06/07/2018 09:15 PM, Tim wrote:
Just tried to upgrade my Win 10 Pro to 1803. Got a stop code so back to
ground zero. But I noticed while I was twiddling my thumbs that the upgrade
process was talking to someone on the net, I assume Microsoft. Anyone have
any idea what might be going on with this? The only thing I can think of is
verifying which previous patches I have already had installed.

Turn off 3rd Party AntiVirus. Avast killed several of mine.

Big Al wrote in news
On 06/07/2018 09:15 PM, Tim wrote:
Just tried to upgrade my Win 10 Pro to 1803. Got a stop code so back
to ground zero. But I noticed while I was twiddling my thumbs that
the upgrade process was talking to someone on the net, I assume
Microsoft. Anyone have any idea what might be going on with this? The
only thing I can think of is verifying which previous patches I have
already had installed.

Turn off 3rd Party AntiVirus. Avast killed several of mine.

Don't have a 3rd party antivirus. Just Microsoft Defender and MalwareBytes.
But I will turn off Malwarebytes before I try again.