Win10 1803 update frreezing at 43%, yep another one.....

On C: drive Windows found no problems and cleaned up unused areas.
The other drives can be tuned up overnight running the same command.
During the upgrade all drives will be removed and/or their cables disconnected for the next upgrade attempt.
At the time of the upgrade attempt there should be only one drive connected.
The computer will be tuned up in the thread and then a check list posted for the next upgrade.
Once the check list steps are completed an upgrade will be attempted.
If the upgrade attempt completes then that will complete the troubleshooting.
If it does not work it should generate a new error code.
The logs had been cleaned using Ccleaner and the error code 1900101-30018 was not found.
This code may appear in the Panther logs. When available please post them into the thread as they take a long time to process. Many times the error messages or codes are ambiguous.
Update the progress with backing up computer files and making a backup image.

The USB stick has 3.8GB on it, which would be about right for the full package created by MCT.

And yes, I am cognisant that doing a full clean install may be less time consuming, but man, that is a fair bit of work reinstalling Office, AutoCAD, a bunch of other stuff and the numerous little tweaks and customisations I've got. I'm really trying to avoid all that, I am quite happy with the way it is all setup at the moment and would like to preserve that if at all possible. But yes, it is an option....

zbook said:

1) For Ccleaner uncheck:
a) Memory Dumps
b) Windows Log Files
c) Windows Error Reporting

2) For startup and recovery system failure:
a) uncheck Automatically restart
b) reboot

3) Find a flash drive that you can format ( > or = 8 GB)
4) Create a bootable Windows 10 iso:
https://www.microsoft.com/en-us/soft...load/windows10

5) When available please post the zipped Panther logs

1) and 2) done.
4) is the one and the same that is on my USB stick now. To to the in place upgrade as I am trying to do, you simply run the setup file from within windows. If you wanted to do a full clean install you would boot from the USB and it would start the process directly. The content on the USB is the same, as far as I know and that appears to be the way it operates.
zbook,

5) Is the log collector program collecting all the files that you need?
Or do you need other files too? Can you be more specific with which files and folders you'd like, including full directory string please? Some of those file names have many instances over several folders so I'm not sure just which ones you want.

Perhaps whoever created the log collector program could do a "deeper" version that collects more files than the original version?

Download and install: Everything
voidtools
This software will index everything on internal and external drives.
It can be set to start on boot or when you need it.
As soon as you type a character there will be instantaneous results.

Look for these files.
If any of the files are found you will be looking for the most recent files.
With the many upgrade attempts you will be looking for only those files that were created in the past week.
Which ever files are found > zip > organize > post a one drive or drop box share link

File explorer can be used to find the files but you may need to display hidden files and it may take longer to find search results.

PANTHER logs
C:\Windows\Panther
setuperr.log
setupact.log
Setupmem.dmp
setupapi.dev.log
BlueBox.log
Event logs (*.evtx)
C:\$Windows.~BT\Sources\Rollback
$Windows.~bt\Sources\Rollback\setupmem.dmp
$Windows.~bt\Sources\Rollback\setupapi\setupapi.dev.log
$Windows.~bt\Sources\Rollback*.evtx
$Windows.~BT\Sources\Panther\UnattendGC
miglog.xml
Windows\Logs\Mosetup
Setupapi.offline.log




When using windows driver verifier the tool is used to find misbehaving drivers and malfunctioning hardware.
It will stimulate drivers and those that misbehave will crash with BSOD.
The BSOD will be repetitive until the misbehaving driver is fixed or until the tool is turned off.
With automatic restart unchecked you will see a bsod window with bugcheck and : (
At times you may see a misbehaving driver in the form *.sys
At the beginning of each BSOD you may see a % counter.
If you see it make sure that you allow it to rise to 100% before rebooting.

After each BSOD you will need to use the computer's windows advanced recovery menu.
For each BSOD you will need to turn the tool off and then uninstall the misbehaving driver. Windows by default may attempt to reinstall a default driver. Drivers can be reinstalled after all misbehaving drivers have been uninstalled or after each installation.

The source for drivers should be from the computer or motherboard manufacturer's website.
If drivers are not found then the next best source is from the component manufacturer's website (Intel Nvidia, AMD, Killer networks, Realtek, etc.)
Drivers should only be installed from these sources.

After each BSOD you will open the computer's windows advanced troubleshooting menu and select startup options > reset > safe mode with command prompt > type:
verifier /reset
If the verifier /reset command fails you will then use the windows advanced troubleshooting option command prompt and type:
verifier /bootmode resetonbootfail
If the above two commands fail to turn off the tool then use system restore. Often with system restore the bsod files are not available and then little progress is made in the troubleshooting. So this option should only be select if the prior two options fail to turn off the tool.

After each BSOD you will return to the desktop and run the BETA log collector and post a new zip into the thread. The files will then be troubleshooted and when identified the misbehaving driver will be uninstalled. Then the tool will be restarted to find the next misbehaving driver.

The tool will be used for 48 hours. After this period it will be used for an additional 36 hours after the last BSOD with the computer under typical use.

When using the tool the computer may become sluggish and the boots may be slow. At times the customized settings are modified to reduce the sluggishness.

Before using the tool all files should be backed up to another drive and a backup image made. Before starting to use the tool a brand new restore point should be created.
Please read the previously post logs and wait until it is communicated in the thread before using the tool.

OK, I think I've got all you asked for. (There was a couple of files that were empty so I haven't included them.)

Dropbox - Panther zip.zip

Hope that works! The zipped folder is about 36MB.

1) Have you been using a metered connection on either or both wifi and ethernet?

Code:

2018-08-12 16:46:45, Error                 CONX   Windows::Compat::Appraiser::IsMeteredConnection (178):   Failed to get NetworkCostType assuming metered network [0x80004005].[gle=0x80004005]

Result = 0xC1900201
Result = 0xC1800104[gle=0x00000003]

Code:

!    flq:                               MoveFile: 'C:\WINDOWS\System32\drivers\SETFC7B.tmp' to 'C:\WINDOWS\System32\drivers\rt640x64.sys' FAILED

Code:

!    flq:           MoveFile: 'C:\WINDOWS\system32\SET4121.tmp' to 'C:\WINDOWS\system32\atiesrxx.exe' FAILED

Code:

!    inf:                          Failed to load the OLE Control 'C:\WINDOWS\system32\atitmm64.dll'.

Code:

!    flq:           MoveFile: 'C:\WINDOWS\system32\SET40F1.tmp' to 'C:\WINDOWS\system32\atieclxx.exe' FAILED

0XC1900201
MOSETUP_E_COMPAT_SYSREQ_CANCEL
The user has chosen to cancel because the system does not pass the minimum requirements to install the update.


Please update the progress with the backup of files, backup image, etc.

No. Fortunately I have an unlimited data plan, albeit not very fast.

However, could it have been because I had configured startup with minimal services which might mean networking was all disabled? In which case the upgrade should have been attempting to do it "offline". At least that is my understanding of it.

I'll search for those files that failed to move and see what they belong to......

The problem with drivers should be found with windows driver verifier.

When you have made the backups and are comfortable with the instructions please report into the thread.

There was a different failure code than what was posted in the opening post.

So a computer tune up will be done and then a check list will be ran and then another upgrade attempt to get another failure code. If you are lucky it will upgrade.

How many user names are there on the computer?

zbook said:

1)

Code:

!    inf:                          Failed to load the OLE Control 'C:\WINDOWS\system32\atitmm64.dll'.

[.

This file was missing from that directory. There is a couple of instances of it buried in the FileRepository though.