Trying to upgrade to version 1803, and always fails in Windows Update

bilateral · 06 May 2019

[Okay, I got it now. It's like magic. This with the text pasted over the previous text.]

Okay, thanks for the explanation. Here is the result. Does this tell you anything or get us any closer to being able to get a good copy of msinfo32?

Microsoft Windows [Version 10.0.16299.492]
(c) 2017 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>set
ALLUSERSPROFILE=C:\ProgramData
APPDATA=C:\Users\Michael\AppData\Roaming
CommonProgramFiles=C:\Program Files\Common Files
CommonProgramFiles(x86)=C:\Program Files (x86)\Common Files
CommonProgramW6432=C:\Program Files\Common Files
COMPUTERNAME=TOSH-3
ComSpec=C:\WINDOWS\system32\cmd.exe
configsetroot=C:\WINDOWS\ConfigSetRoot
FP_NO_HOST_CHECK=NO
HOMEDRIVE=C:
HOMEPATH=\Users\Michael
LOCALAPPDATA=C:\Users\Michael\AppData\Local
LOGONSERVER=\\TOSH-3
NUMBER_OF_PROCESSORS=4
OneDrive=C:\Users\Michael\OneDrive
OS=Windows_NT
Path=C:\ProgramData\Oracle\Java\javapath;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\ WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Toshiba\Bluetooth Toshiba Stack\sys\;C:\Program Files (x86)\Toshiba\Bluetooth Toshiba Stack\sys\x64\;C:\Program Files\Windows Imaging\;C:\Program Files (x86)\Windows Kits\10\Windows Performance Toolkit\;C:\Program Files (x86)\Windows Kits\10\Microsoft Application Virtualization\Sequencer\;C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\Users\Michael\AppData\Local\Microsoft\WindowsApps
PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
PROCESSOR_ARCHITECTURE=AMD64
PROCESSOR_IDENTIFIER=Intel64 Family 6 Model 37 Stepping 2, GenuineIntel
PROCESSOR_LEVEL=6
PROCESSOR_REVISION=2502
ProgramData=C:\ProgramData
ProgramFiles=C:\Program Files
ProgramFiles(x86)=C:\Program Files (x86)
ProgramW6432=C:\Program Files
PROMPT=$P$G
PSModulePath=C:\WINDOWS\system32\WindowsPowerShell\v1.0\Modules\;C:\Program Files (x86)\Windows Kits\10\Microsoft Application Virtualization\Sequencer\AppvPkgConverter;C:\Program Files (x86)\Windows Kits\10\Microsoft Application Virtualization\Sequencer\AppvSequencer
PUBLIC=C:\Users\Public
SystemDrive=C:
SystemRoot=C:\WINDOWS
TEMP=C:\Users\Michael\AppData\Local\Temp
TMP=C:\Users\Michael\AppData\Local\Temp
USERDOMAIN=TOSH-3
USERDOMAIN_ROAMINGPROFILE=TOSH-3
USERNAME=Michael
USERPROFILE=C:\Users\Michael
windir=C:\WINDOWS
windows_tracing_flags=3
windows_tracing_logfile=C:\BVTBin\Tests\installpackage\csilogfile.log

C:\WINDOWS\system32>

zbook · 06 May 2019

Please edit the above displayed results.

After posting text > click edit post > paste over the first post > click save changes

This edit should allow you to correct the layout to as it was seen in the admin command prompt box.

bilateral · 06 May 2019

Okay, now I understand the intention, but I could not find any icon or button with " > paste over the first post >". Is there a button for this somewhere, or how do I do it? You seem to indicate this is a choice under "edit post" but I did not see it. Or do I need to go back to the original elevated Command Prompt, Select All and Copy; then Paste this into the post over the old one?

zbook · 06 May 2019

When pasting text into the thread it may lose it structure on the initial post. Using the edit post button you can post the same text and it should maintain the layout.

bilateral · 06 May 2019

Okay, now I understand. It's not a special icon, just pasting over the previous text. See above.

Do you see anything significant from the results of the Set command?

Ztruker · 07 May 2019

Nothing unusual in the SET output, but can you upload C:\BVTBin\Tests\installpackage\csilogfile.log here please. No idea what will be in it but who knows, may be something useful. It's shown at the bottom of the SET output and not something I hav eever seen before.

bilateral · 07 May 2019

I found no folder on C that begins with \BVTBin I also found no file on C: (with a complete search) named: csilogfile.log.

Ztruker · 07 May 2019

Ok, was worth looking for. Thanks.

zbook · 07 May 2019

1) Place the computer in safe mode:
Boot into Safe Mode on Windows 10

2) Run both DM and BETA log collectors in safe mode and upload results into this thread:
BSOD - Posting Instructions

3) Place the computer in clean boot:
Perform a Clean Boot in Windows 10 to Troubleshoot Software Conflicts

4) Create a bootable windows 10 iso with the identical build:
Download Windows 10 ISO File
Microsoft Windows and Office ISO Download Tool
TechBench by WZT (v4.1.1)

5) With the computer in clean boot see if you can perform an in place upgrade repair with the identical windows 10 iso build.

Repair Install Windows 10 with an In-place Upgrade

6) Power on the computer
7) Open file explorer
8) Insert the windows 10 iso flash drive into any USB port
9) Identify the iso within file explorer
10) click on the iso and launch setup or setup.exe
11) follow the text and images in this link:
Repair Install Windows 10 with an In-place Upgrade

12) Delay updates until there is a successful in place upgrade
13) Turn off wireless
14) Disconnect Eternet

bilateral · 09 May 2019

Sorry for the delay getting back to the thread. I placed the computer in safe mode, and attempted to run both DM and BETA log collectors in safe mode. I stopped here because of a confusion about where the files are being stored. Apparently the DM log collector does not like the fact that I moved my documents and Desktop folders to my D:/ partition; but the Beta log collector does not mind at all--it tells me where to find them--on D:\. Last time also, I could not find the file for the DM log collector. Taking a guess, I decided to look in the original location under Users in C:\ I guess some part of the system does not recognize the relocation.

I also found the old DM log collector from the last time I tried this, but that zip file turns up as only 1 KB. The current file (done in Safe Mode) shows as 2076 KB. I am uploading both zip files--from DM and Beta. --One other thing: The most recent Beta log collector zip file is considerably smaller than the previous one.

I assume you still want me to try to do an in-place upgrade with version 1709 first. I'll need to copy some changed files first in my downloads directory, in case it gets deleted again. Unless I hear from you about these log collector files, I'll work on the 1709 upgrade tomorrow.