Windows 10: Fall Creators Update 1709 Failed to install - need help

To begin here our PC specs currently running Windows 10 Home Version 1607 (build: 14393.321)




I'm now a member of the Fall Creators Update Failed to install group. I've tried to install with windows update and this came up.




I've tried using the media creation tool, windows update assistant, and downloaded a window 10 ISO for a standalone install but they have all failed. Windows update continues to attempt to install these updates but fails. It would be nice to stop these updates from attempting until a solution is found.

Here is the setupact and setuperr files.


Any words of wisdom would be much appreciated. thanks in advance.

:)

 

Fall Creator's Update, failure to install

Thank you for your response.

One of the reason why it is also not installing is, you need to check if your device is compatible with Windows 10 Fall Creators update 1709. Please check this thread and look for MVP Andre Da Costa's answer:

Fall Creators Update installation gets stuck. It contains explanation if your device is compatible with the software.

In the meantime, you can also check this thread:
Fall Creator's Update" (version 1709) failed to install. Look for Janet_Wu. It contains troubleshooting steps pertaining to the issue.

Feel free to post back your response.

 

Issues with version 1703 of windows 10 pro

In that case, it's best that you install the Fall Creators Update version 1709 Windows 10. There are great new features available in the update. To do that, check the article below to download and install the Fall Creators Update.

Get the Windows 10 Fall Creators Update

Let us know if you need further assistance.

 

Hi unclegennie. Sorry to hear about your membership.

First I would try the updated Trouble Shooter for Windows 10

https://support.microsoft.com/en-us/...troubleshooter

Once download disconnect from Internet.

Once you've run the Trouble Shooter I would then follow these items before retrying the update.
These are quick fixes from an article on resolving Window Updates issues.
Quick fixes
The following steps can resolve many Windows upgrade problems.

• Remove nonessential external hardware, such as docks and USB devices. (In a number of situations only having the OS drive connected has helped. Before doing this ensure you are not impacting any Raids or Storage Pools you have set up. If you are you may wish to leave them connected.)
• Check all hard drives for errors and attempt repairs. To automatically repair hard drives, open an elevated command prompt, switch to the drive you wish to repair, and type the following command. You will be required to reboot the computer if the hard drive being repaired is also the system drive.
  • chkdsk /F
• Attempt to restore and repair system files by typing the following commands at an elevated command prompt. It may take several minutes for the command operations to be completed. For more information, see Repair a Windows Image.
  • DISM.exe /Online /Cleanup-image /Restorehealth
  • sfc /scannow
• Uninstall Non Microsoft Anti Virus software
  • Use Windows Defender for protection during the upgrade.
  • Verify compatibility information and re-install antivirus applications after the upgrade.
• Uninstall all nonessential software.
• Update firmware and drivers. There is some risk to updating BIOS's. I noticed there is one for your board to improve compatibility with 5th Generation processors. Updating a BIOS is something only you can decide whether to do or not do.
• Ensure that "Download and install updates (recommended)" is accepted at the start of the upgrade process.
• Verify at least 16 GB of free space is available to upgrade a 32-bit OS, or 20 GB for a 64-bit OS.

Once complete connect to Internet, navigate to Setup and double click. (Assume you made USB key with MCT)


Ken

 

This is a log collector that we use in another forum.
Please run it and post a zip into the thread:
BSOD - Posting Instructions - Windows 10 Forums



0x8007001F, 0x50015
MSG_INSTALLUI_SWITCH_TO_ERROR_PAGE



Download and install Everything search:
voidtools

Look for these log files and post any that you find into the thread:
C:\Windows\Panther
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
C:\$WINDOWS.~BT\Sources\Panther\diagerr.xml

 

Ken Thanks for getting back to me so soon. I should let you know that I have tried many of your suggestions with no luck. I should also let you know I tried to run sfc /scannow and the Dism commands in admin cmd prompt, but received this: "windows resource protection could not start the repair service". I have an SSD as my main OS drive, so not sure if I need to or even can run chkdsk /f safely. I've also tried upgrading with a downloaded ISO from Microsoft while disconnecting during install, but no luck.

 

Open administrative command prompt and type or copy and paste:
1) dism /online /cleanup-image /checkhealth
2) dism /online /cleanup-image /scanhealth
3) dism /online /cleanup-image /restorehealth
4) scan /scannow
5) chkdsk /scan
6) When all of the above 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
7) This evening/night run this command overnight:
Open administrative command prompt and type or copy and paste: chkdsk /x /f /r
This may take many hours so plan to run overnight.
8) Use the information in this link to find the chkdsk report in the event viewer and post the results into the thread using a one drive or drop box share link:
Read Chkdsk Log in Event Viewer in Windows 10 Performance Maintenance Tutorials

 

Good to hear that you tried many of the ideas. That said did you run the trouble shooter? I think you really have to do all of them.

Chkdsk is fine on SSD. Have seen a couple of successes with people only having their boot drive connected.

 

Thanks for your help zbook. I've downloaded and ran DM log Collector, and attached the results. I've also used Voidtools (Everything) but have a few questions. For example, do I look in C:\Windows\Panther for the log files: setupmem.dmp, setupapi.dev.log, BlueBox.log,
Event logs (*.evtx), because their wasn't any. I'm a little confused about the rest of your instructions on locating the other logs, the actual pathways and where to look. I have no idea where to look for this "$Windows.~bt\Sources\Rollback*.evtx". When I enter this in the search area in Voidtools it shows nothing. I did find "C:\$WINDOWS.~BT\Sources\Panther\diagerr.xml and uploaded it.

 

By default the Panther logs are hidden.
So when using file explorer you should modify to show hidden files.
Everything search does not need to be modified to show hidden files.
Everything is much faster than file explorer search.
For everything it will display the most results with the fewest characters. Then as you type more characters the search results become narrow.
So enter the characters into the search and find as many of the panther files in the list and post what you can find into the thread using one drive or drop box share links.

For example to find: $Windows.~bt\Sources\Rollback\setupapi\setupapi.dev.log
it may not appear exactly in this form.
So type:
rollback
setupapi
dev.log
panther
etc.

 

Hi Ken I ran the troubleshooter and it said it fixed some problems. So I ran windows update again and this was the result.

 

The log files displayed that you had the following corruption problems:
a) Master File Table (MFT) drive files system
b) registry hive

There were BSOD with bugchecks 133 and 74
Bugcheck 74 is bad system config info and indicated that there was an error in the registry.




1) If you use Ccleaner > click windows tab > scroll down to system and advanced > post an image into the thread
2) In the left lower corner search type clean > open disk cleanup > scroll up and down > post images into the thread
3) 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
4) In the left lower corner search type services > open windows error reporting service > scroll to the startup type column > right click > left click on properties > post an image into the thread
5) 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
6) Click analyze > look for dead or deaddead in the results > post the results into the thread
7) Run the DM log collector after all of the above steps and post a zip into the thread:
BSOD - Posting Instructions - Windows 10 Forums
BSOD - Posting Instructions - Windows 10 Forums
8) Turn off Windows fast startup:Turn On or Off Fast Startup in Windows 10 Performance Maintenance Tutorials







Code: Event[3662]: Log Name: System Source: Microsoft-Windows-StartupRepair Date: 2016-10-23T21:31:30.566 Event ID: 1122 Task: N/A Level: Information Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-3P8045C Description: The registry hive was corrupt. Error information: Event[3663]: Log Name: System Source: Microsoft-Windows-StartupRepair Date: 2016-10-23T21:31:30.566 Event ID: 1122 Task: N/A Level: Information Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-3P8045C Description: The registry hive was corrupt. Error information: Event[3664]: Log Name: System Source: Microsoft-Windows-StartupRepair Date: 2016-10-23T21:31:30.566 Event ID: 1122 Task: N/A Level: Information Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-3P8045C Description: The registry hive was corrupt. Error information: Event[3665]: Log Name: System Source: Microsoft-Windows-StartupRepair Date: 2016-10-23T21:31:30.566 Event ID: 1122 Task: N/A Level: Information Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-3P8045C Description: The registry hive was corrupt. Error information: Event[3666]: Log Name: System Source: Microsoft-Windows-StartupRepair Date: 2016-10-23T21:31:30.566 Event ID: 1122 Task: N/A Level: Information Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-3P8045C Description: The registry hive was corrupt. Error information:[/quote] Code: Event[3598]: Log Name: System Source: Ntfs Date: 2016-10-23T19:54:05.588 Event ID: 55 Task: N/A Level: Error Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-3P8045C Description: A corruption was discovered in the file system structure on volume C:.The Master File Table (MFT) contains a corrupted file record. The file reference number is 0x2000000000090. The name of the file is "\Windows\System32\config\SOFTWARE.LOG2".[/quote] Code: Event[28597]: Log Name: System Source: Microsoft-Windows-Kernel-Boot Date: 2017-12-21T14:53:56.638 Event ID: 29 Task: N/A Level: Error Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Cindy-PC Description: Windows failed fast startup with error status 0xC00000D4.[/quote] Code: Event[3597]: Log Name: System Source: Microsoft-Windows-Ntfs Date: 2016-10-23T19:54:05.588 Event ID: 98 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-3P8045C Description: Volume C: (\Device\HarddiskVolume2) requires an Online Scan. An Online Scan will automatically run as part of the next scheduled maintenance task. Alternatively you may run "CHKDSK /SCAN" locally via the command line, or run "REPAIR-VOLUME <drive:> -SCAN" locally or remotely via PowerShell.[/quote] Code: Event[3823]: Log Name: System Source: Display Date: 2016-10-23T22:01:10.760 Event ID: 4101 Task: N/A Level: Warning Opcode: Info Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-3P8045C Description: Display driver nvlddmkm stopped responding and has successfully recovered.[/quote] Code: Event[3511]: Log Name: System Source: Ntfs Date: 2016-10-23T17:21:47.419 Event ID: 130 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-3P8045C Description: The file system structure on volume C: has now been repaired.Event[3512]: Log Name: System Source: Ntfs Date: 2016-10-23T17:21:47.775 Event ID: 130 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-3P8045C Description: The file system structure on volume C: has now been repaired.[/quote] Code: Event[2153]: Log Name: System Source: Microsoft-Windows-WER-SystemErrorReporting Date: 2016-10-01T09:03:14.902 Event ID: 1005 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-3P8045C Description: Unable to produce a minidump file from the full dump file.[/quote] Code: Event[9696]: Log Name: System Source: cdrom Date: 2017-02-12T15:09:46.249 Event ID: 7 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Cindy-PC Description: The device, \Device\CdRom0, has a bad block.[/quote] Code: Event[29236]: Log Name: System Source: Microsoft-Windows-TaskScheduler Date: 2017-12-22T11:13:39.239 Event ID: 414 Task: Task Misconfiguration Level: Warning Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Cindy-PC Description: Task Scheduler service found a misconfiguration in the NT TASK\OneDrive Standalone Update Task-S-1-5-21-824825727-3568302656-2114204064-1001 definition. Additional Data: Error Value: %localappdata%\Microsoft\OneDrive\OneDriveStandaloneUpdater.exe.[/quote] Code: Event[29059]: Log Name: System Source: Microsoft-Windows-FilterManager Date: 2017-12-22T07:42:05.981 Event ID: 4 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Cindy-PC Description: File System Filter 'wcifs' (Version 10.0, ?2016?-?09?-?15T08:42:03.000000000Z) failed to attach to volume '\Device\HarddiskVolumeShadowCopy5'. The filter returned a non-standard final status of 0xC000000D. This filter and/or its supporting applications should handle this condition. If this condition persists, contact the vendor.[/quote] Code: Event[28616]: Log Name: System Source: Microsoft-Windows-Kernel-Power Date: 2017-12-21T14:53:57.322 Event ID: 41 Task: N/A Level: Critical Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Cindy-PC Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.[/quote] Code: Event[28566]: Log Name: System Source: Microsoft-Windows-Kernel-Power Date: 2017-12-21T08:52:35.910 Event ID: 41 Task: N/A Level: Critical Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Cindy-PC Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.[/quote] Code: Event[22911]: Log Name: System Source: Microsoft-Windows-DriverFrameworks-UserMode Date: 2017-10-19T22:35:29.510 Event ID: 10116 Task: User-mode Driver problems. Level: Critical Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Cindy-PC Description: The device Apple iPod (location Port_#0004.Hub_#0004) is offline due to a user-mode driver crash. Windows will attempt to restart the device in the shared process 1 more times before moving the device in its own process. Please contact the device manufacturer for more information about this problem.[/quote] Code: Event[22910]: Log Name: System Source: Microsoft-Windows-DriverFrameworks-UserMode Date: 2017-10-19T22:35:29.509 Event ID: 10110 Task: User-mode Driver problems. Level: Critical Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Cindy-PC Description: A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices.[/quote]

 

Did some looking and I think you are making progress.

I would run the trouble shooter again and then follow the steps in Post 5 of this thread. This seems to be the more common fix for 80246010.

Problems with windows 10 installation Error 80246010



Weren't the MFT error and hive from over a year ago?

 

Yes both were old and were repaired.

 

Thanks for your help zbook. I followed your instructions completely. Here are the results.