Windows 10: Unable to install Windows Fall Creators Update

That's ok. You've logged in, run Setup.exe, and it's going to do an install-like procedure to upgrade Windows.

The boot disk created from your iso can
- be used as a repair tool if you boot from it and click Repair your computer
- be used to clean install Windows if you boot from it and then install Windows
- be used to upgrade your Windows from an older edition or build to the one on the iso if you log in and run setup.exe
- be used to repair your Windows if you have the same build etc installed, something is wrong, and you wish to replace all the system files and some registry settings to an initial install state (so-called in-place upgrade repair install).

In both the 3rd and 4th cases you will keep your programs and data.

 

Manually trying to update from the website got me the same error as noted in my first post.

Just running the setup is purely a install Win 10 disk as far as I can tell. There are no other options, so I will try booting to it later today after the shopping trip I am forced to take *Smile
If it wont work, I will try to find a way to just hide the update

 

I've tried to explain that for you. The same disk can be used in different ways. Sorry that's not clear enough. Naturally you're free to try whichever way you feel you understand and are happy with.

See:
Repair Install Windows 10 with an In-place Upgrade Installation Upgrade Tutorials
and you'll find exactly that picture at 12.

That's the same procedure as you need.

Please upload the update logs to an accessible site:
SetupAct.log and SetupErr.log

Location of log files:
Resolve Windows 10 upgrade errors - Windows IT Pro | Microsoft Docs

I return to my question as to what the first partition at the start of Disk 4 is. I suggest you disconnect that disk when you try to upgrade.

 

Sorry I am so dim. I will go by the link you gave.

 

The install failed.

setupact.log

setuperr.log

 

Hi, How did you attempt that update? By download, automatically, or using your Win 10 disk?
Did you allow updates or not?

My recommended approach is to use the setup disk with no updates. If you've not tried that yet, have one last attempt. And disconnect your other disks before doing so, leaving only your system disk.

Are you quite sure you have no external devices connected, e.g. a wireless device or dongle?

After trying that (unless you've already done so) I would recommend attempting an in-place upgrade repair install of 1703 which keeps all programs and data and most settings, for which you will need a 1703 iso.

You can get one here:
Windows 10 Creators Update 1703 Download Windows ISO
To repair your existing installation before upgrading:
Repair Install Windows 10 with an In-place Upgrade Installation Upgrade Tutorials
==========================================================================

A quick glance shows:
2018-02-10 21:04:42, Error SP CDownloadDUUpdates:*BiggrinoExecuteInternal: Did not find hard disk space needed, when update cab files will not be extracted. This is unexpected! hr = 0x8000ffff

setuperr.log contains many errors-however there is a repeated pattern
2018-02-10 17:57:48, Error SP CSetupPlatform:*BiggrinownloadDynamicUpdates: Failed to download updates. Error: 0x8000FFFF
2018-02-10 17:57:48, Error MOUPG DUImage: Failed to execute GDR search and download [0x8000ffff]
2018-02-10 17:58:20, Error DU DU::CDUSession::Search: Failed to set WU internal configuration property for targeted scans. hr = 0x80070057
2018-02-10 17:58:20, Error DU DU::CDUSession::BuildSearchCriteria: Caller profile search criterion is not supported. hr = 0x80070032
2018-02-10 17:58:20, Error DU DU::CDUSession::Search: Failed to build the search criteria. hr = 0x80070032
2018-02-10 17:58:26, Error SP Failed to get driver packages from the online system. Error: 0x80070057[gle=0x0000007a]
2018-02-10 17:58:27, Error SP CDownloadDUUpdates:*BiggrinoExecuteInternal: Failed to filter updates. hr = 0x80070057
2018-02-10 17:58:27, Error SP CSetupPlatform:*BiggrinownloadDynamicUpdates: Failed to download updates. Error: 0x80070057
2018-02-10 17:58:27, Error MOUPG DUImage: Failed to execute driver search and download [0x80070057]

This sequence repeats numerous times:
2018-02-10 18:00:07, Error CONX 0x80070057 Failed DismGetDrivers

2018-02-10 18:00:07, Error CONX 0x80070057 Failed to add driver store drivers

2018-02-10 18:00:07, Error CONX 0x80070057 Failed to collect driver information

2018-02-10 18:00:07, Error CONX 0x80070057 DeviceMap failed to collect driver information

2018-02-10 18:00:07, Error CONX 0x80070057 Unable to initialize Device Driver Map

2018-02-10 18:00:07, Error CONX 0x80070057 GetDeviceMap failed

 

I followed the sequence on the page you linked to. It did help me understand what you are trying to get me to do.
I have just unhooked all drives and will give this another go. Film at 11

 

Commendable patience- well done. It's just unfortunate the process can be upset by trivial things and give such obscure indications.

Naturally there's no guarantee.. the backstop is the in-place upgrade repair.

The log seems to indicate issues with drivers, and accessing disk - I've searched around but can't find anything clearly helpful.

Sometimes you can spend a great deal of time trying to fix things, when doing an in-place upgrade repair can help- but not always of course.

 

Here is todays failure logs. All drives unplugged. Only the wired internet plugged in. I ran it without installing updates, and saving only personal files.setupact.log Processing...x I had to zip the setupact log

setuperr.log

setupact.zip

Will look into the creators update iso

I do notice that everything always ends with the error 0x80070057, which seems to be prevalent among some people having problems

 

Run this version of the log collector and post a zip into this thread:
log collector v2-beta08.zip

 

SHIVA (2018-02-11 11 06).zip

This may be a better result. I had the 1703 ISO open at the same time

SHIVA (2018-02-11 11 11).zip

 

The logs displayed multiple problems that included drive file corruption, paging errors, I/O retried, BSOD, failed fast startup, WHEA controlled hardware errors, Nvidia GPU driver problems, etc.

For all steps please post images into the thread.
If there are any problems posting images please use one drive or drop box share links.

Some steps that were made will be repeated so that there are updated tests and results.
The steps will be to tune up the computer and to prepare for the next upgrade attempt.

1) In the left lower corner search type msinfo32 > save as NFO to the desktop > post a zip into the thread.

2) Please update the specs in the "My Computer" section:
System Specs - Fill in at Ten Forums:
System Specs - Fill in at Ten Forums Site Use Tutorials
In the left corner below in your post you find 'My System Specs'.
After clicking it you can find a link a little below that says 'Update your System Spec', click on this link to get to the page where you can fill in your system specs.
System Info - See Your System Specs - Windows 7 Help Forums

Include PSU. cooler, case, peripherals and anything attached to the computer by wired or wireless (mouse, keyboard, headset, printer, xbox, USB wireless network card, etc.)

3) open administrative command prompt and type or copy and paste:
4) sfc /scannow
5) dism /online /cleanup-image /scanhealth
6) dism /online /cleanup-image /restorehealth
7) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

8) Uninstall Hitman Pro:
Sophos Central for Windows: How to uninstall using command line or batch file - Sophos Community
9) Uninstall Bitdefender:
Uninstall Bitdefender
10) Uninstall Malwarebytes
Malwarebytes Cleanup Utility download and instr... | Official Malwarebytes Support
11) Turn on Windows defender

12) Make sure that there is no over clocking while troubleshooting.

13) Sometimes there are problems in the bios that produce bsod.
14) Please check to see that the BIOS version is up to date.
15) Open the website for the computer or motherboard manufacturer to view the drivers and post a URL or hyperlink into the thread.

16) To ensure that there are no improper bios settings please reset the bios.
17) Sometimes there can be failure to boot after resetting the bios.
18) Backup the computer files to another drive or to the cloud.
19) Make a backup image usig Macrium:
Macrium Software | Macrium Reflect Free:
Macrium Software | Macrium Reflect Free

20) And please create a brand new restore point.

How to Clear Your Computers CMOS to Reset BIOS Settings:
How to Clear Your Computers CMOS to Reset BIOS Settings
3 Ways to Reset Your BIOS - wikiHow:
3 Ways to Reset Your BIOS - wikiHow

21) Open Ccleaner > click windows tab > scroll down to system and advanced > post an image into the thread

22) In the left lower corner search type clean > open disk cleanup > scroll up and down > post images into the thread

23) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings
> on the advanced tab under startup and recovery click settings > post an image of the startup and recovery into the thread.
> on the advanced tab under performance > click on settings > click on advanced tab > under virtual memory click on change > post an image of the virtual memory tab into the thread

24) Download and install Whocrashed > in the left upper corner above analyze click on tools > crash dump test > type: ACCEPT
Resplendence Software - WhoCrashed, automatic crash dump analyzer
25) Click analyze > look for dead or deaddead in the results > post the results into the thread
26) Run this version of the log collector after the above steps:
log collector v2-beta08.zip: Windows 10 Help Forums

27) Choose one of the temperature monitoring software applications: Speecy, HW monitor, Speed fan:Speccy - Free Download - Piriform: Speccy - System Information - Free
Speccy - System Information - Free Download
HWMONITOR | Softwares | CPUID: HWMONITOR | Softwares | CPUID
HWMONITOR | Softwares | CPUID
SpeedFan - Access temperature sensor in your computer: SpeedFan - Access temperature sensor in your computer
SpeedFan - Access temperature sensor in your computer

28) Turn off Windows fast startup:
Turn On or Off Fast Startup in Windows 10 Performance Maintenance Tutorials

29) List any antivirus software besides Hitman Pro, Bitdefender, Malwarebytes, that has been in use since the last Windows upgrade (always on and manual software)

30) List any drive encryption software that has been used besides Microsoft products.

31) Open administrative command prompt and type or copy and paste: chkdsk /x /f /r

C:\Windows\system32>chkdsk /x /f /r
The type of the file system is NTFS.
Cannot lock current drive.

Chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N)

Type: Y
reboot

Run the command on all drives using the syntax: chkdsk /x /f /r C: or chkdsk /x /f /r D: changing the drive letter to the applicable drive.
This may take many hours to run so plan to run it overnight.

32) Use the information in this link to find the chkdsk report in the event viewer. Copy and paste into notepade > save to desktop > post into the thread using one drive or drop box share link:
Read Chkdsk Log in Event Viewer in Windows 10 Windows 10 Performance Maintenance Tutorials
Read Chkdsk Log in Event Viewer in Windows 10 Performance Maintenance Tutorials




Code: Event[7683]: Log Name: System Source: Microsoft-Windows-DriverFrameworks-UserMode Date: 2018-02-09T17:39:07.294 Event ID: 10111 Task: User-mode Driver problems. Level: Critical Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: shiva Description: The device My Book tunes (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device 5 more times. Please contact the device manufacturer for more information about this problem.Event[7684]: Log Name: System Source: Microsoft-Windows-DriverFrameworks-UserMode Date: 2018-02-09T17:39:07.294 Event ID: 10111 Task: User-mode Driver problems. Level: Critical Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: shiva Description: The device SATA1 (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device 5 more times. Please contact the device manufacturer for more information about this problem.Event[7685]: Log Name: System Source: Microsoft-Windows-DriverFrameworks-UserMode Date: 2018-02-09T17:39:07.294 Event ID: 10111 Task: User-mode Driver problems. Level: Critical Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: shiva Description: The device CAR DRIVE (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device 5 more times. Please contact the device manufacturer for more information about this problem.Event[7686]: Log Name: System Source: Microsoft-Windows-DriverFrameworks-UserMode Date: 2018-02-09T17:39:07.294 Event ID: 10111 Task: User-mode Driver problems. Level: Critical Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: shiva Description: The device Seagate Expansion Drive (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device 5 more times. Please contact the device manufacturer for more information about this problem.[/quote]


Code: Event[3811]: Log Name: System Source: Disk Date: 2018-02-09T10:20:05.682 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: shiva Description: The IO operation at logical block address 0x40800 for Disk 5 (PDO name: \Device\00000063) was retried.Event[3812]: Log Name: System Source: Disk Date: 2018-02-09T10:20:07.274 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: shiva Description: The IO operation at logical block address 0x5b7ba8 for Disk 5 (PDO name: \Device\00000063) was retried.Event[3813]: Log Name: System Source: Disk Date: 2018-02-09T10:20:09.688 Event ID: 153 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: shiva Description: The IO operation at logical block address 0x61c2b8 for Disk 5 (PDO name: \Device\00000063) was retried.[/quote] Code: Event[7687]: Log Name: System Source: Microsoft-Windows-DriverFrameworks-UserMode Date: 2018-02-09T17:39:07.294 Event ID: 10111 Task: User-mode Driver problems. Level: Critical Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: shiva Description: The device Terra 5 (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device 5 more times. Please contact the device manufacturer for more information about this problem.[/quote]
Code: Event ID: 10111 Task: User-mode Driver problems. Level: Critical Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: shiva Description: The device Terra 5 (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device 5 more times. Please contact the device manufacturer for more information about this problem.[/quote]
Code: Event[7710]: Log Name: System Source: Display Date: 2018-02-09T22:38:47.037 Event ID: 4101 Task: N/A Level: Warning Opcode: Info Keyword: Classic User: N/A User Name: N/A Computer: shiva Description: Display driver nvlddmkm stopped responding and has successfully recovered.[/quote]
Code: Event[8246]: Log Name: System Source: Disk Date: 2018-02-10T17:49:12.485 Event ID: 51 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: shiva Description: An error was detected on device \Device\Harddisk3\DR3 during a paging operation.Event[8247]: Log Name: System Source: Disk Date: 2018-02-10T17:49:12.485 Event ID: 51 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: shiva Description: An error was detected on device \Device\Harddisk3\DR3 during a paging operation.[/quote]
Code: Event[8484]: Log Name: System Source: Microsoft-Windows-WHEA-Logger Date: 2018-02-10T20:19:15.526 Event ID: 19 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-19 User Name: NT AUTHORITY\LOCAL SERVICE Computer: shiva Description: A corrected hardware error has occurred.Reported by component: Processor CoreError Source: Corrected Machine CheckError Type: Cache Hierarchy ErrorProcessor APIC ID: 2The details view of this entry contains further information.[/quote]
Code: Event[7762]: Log Name: System Source: Disk Date: 2018-02-10T00:17:34.204 Event ID: 158 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: shiva Description: Disk 6 has the same disk identifiers as one or more disks connected to the system. Go to Microsoft's support website (http://support.microsoft.com) and search for KB2983588 to resolve the issue.[/quote]
Code: Event[2423]: Log Name: System Source: Microsoft-Windows-Kernel-Boot Date: 2018-02-01T18:11:59.782 Event ID: 29 Task: N/A Level: Error Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: shiva Description: Windows failed fast startup with error status 0xC00000D4.[/quote]

 

Drives never been encrypted
Emisoft anti virus was used before Bitdefender
Bitdefendewr was uninstalled yesterday but it left an agent of some kind. Will delete. All other progs removed

system.7z

 

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

C:\WINDOWS\system32> sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\WINDOWS\system32>dism /online /cleanup-image /scanhealth

Deployment Image Servicing and Management tool
Version: 10.0.15063.0

Image Version: 10.0.15063.0

[==========================100.0%==========================] No component store corruption detected.
The operation completed successfully.

C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.15063.0

Image Version: 10.0.15063.0

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

C:\WINDOWS\system32>

 

The msinfo32 file was corrupt or incompatible when using the beta log collector and when it was sent manually.
The msinfo32 is much harder to use when txt.
1) Save it as txt > post a zip into the thread.
2) Also see what happens with DM log collector: BSOD - Posting Instructions - Windows 10 Forums
3) Run the Emisoft uninstall tool:
How can I completely uninstall an Emsisoft Product? - Powered by Kayako Help Desk Software